"man init" reports MX init is systemd? [SOLVED]

[Richard]

As per the thread in Spanish reported by keos,
I now understand the problem.

It is a bug or an oversight in the "man" system.

[dolphin_oracle]

actually, its not reporting anything. its just the "man" entry for systemd. I'm not sure sysVinit has a man entry.

***edit*** I'm going to back up on that. the link does point to systemd's man page, but not sure that is because sysVinit doesn't have on maybe. At least, not one I can find.

[cpoakes]

You can use man telinit to see information about SYSV init.

[skidoo]

try this: apropos sysv
(FWIW, no matches found for "sys v" nor "sys-v")

On antiX, I get 4 matches (2 of which don't make sense to me).
manfs fs
man filesystems
^---- these describe "sysv" as a "Linux filesystem type". What?

v---- these 2 do contain info related to sysv
man inittab
man sysv-rc-conf

[newguy]

I can confirm the command "man init" is still showing the manual page for systemd, which MX doesn't use. Running "man telinit" brings up the SysV init page.

This should probably be fixed as it gives the mistaken impression MX is using systemd as the default init implementation. SysV init does have its own manual page, but it isn't displayed when running "man init".

I'm guessing this happens because systemd is installed, probably as a dependency for something else. systemd's man page takes priority over SysV's. The SysV man page is in the man8 sub-directory so it's there, but just isn't getting displayed.

[dolphin_oracle]

I can confirm the command "man init" is still showing the manual page for systemd, which MX doesn't use. Running "man telinit" brings up the SysV init page.

This should probably be fixed as it gives the mistaken impression MX is using systemd as the default init implementation. SysV init does have its own manual page, but it isn't displayed when running "man init".

I'm guessing this happens because systemd is installed, probably as a dependency for something else. systemd's man page takes priority over SysV's. The SysV man page is in the man8 sub-directory so it's there, but just isn't getting displayed.

how does one fix it?

[BitJam]

The "man init" command is working correctly on MX-17.RC1_x64 running live inside of Virtual Box here. It is the same page that "man telinit" produces.

When it is not working correctly maybe an init.?.gz symlink gets created pointing to the systemd.1.gz man page. In MX-17.RC1 the only "init.*.gz" file is the correct sysv init man page which shows up when I run "man init". Maybe this is only a problem on MX systems before MX-17. If it is a problem on MX-17 then when is the problem created? And how?

[timkb4cq]

Different result here. From an installed, unmodified RC1 in VirtualBox

Code: Select all

tim@mx1:~
$ cat /etc/mx-version 
MX-17.RC1_x64 Horizon December 10, 2017
tim@mx1:~
$ man init

SYSTEMD(1)                                   systemd                                   SYSTEMD(1)

NAME
       systemd, init - systemd system and service manager

SYNOPSIS
       systemd [OPTIONS...]

       init [OPTIONS...] {COMMAND}

DESCRIPTION
       systemd is a system and service manager for Linux operating systems. When run as first
       process on boot (as PID 1), it acts as init system that brings up and maintains userspace
       services.

       For compatibility with SysV, if systemd is called as init and a PID that is not 1, it will
       execute telinit and pass all command line arguments unmodified. That means init and
       telinit are mostly equivalent when invoked from normal login sessions. See telinit(8) for
       more information.

       When run as a system instance, systemd interprets the configuration file system.conf and
       the files in system.conf.d directories; when run as a user instance, systemd interprets
       the configuration file user.conf and the files in user.conf.d directories. See systemd-
       system.conf(5) for more information.

OPTIONS
       The following options are understood:
 Manual page init(1) line 1 (press h for help or q to quit)

[timkb4cq]

However, if I boot up the iso as a LiveUSB in Vbox I do get what you do. So whatever happens, happens during installation.

[dolphin_oracle]

However, if I boot up the iso as a LiveUSB in Vbox I do get what you do. So whatever happens, happens during installation.

or maybe when man pages get updated.