documentation-packages team mailing list archive

[John Hall <johnhall2.0@xxxxxxxxx>]

Public bug reported:

# man init
Brings up the documentation for systemd but systemd is not being used as init.
This  confuses users about which system is being used as "init", and how to manage services on the system.

You can see that this is still upstart with:
# sudo readlink /sbin/init
or
# ls -l /sbin/init

# man init
Should still result in the same thing as
# man upstart

Until systemd is used for init.

This effects 14.10 as of Dec 21, 2014

One solution would be to rename this systemd man page to, for example, "systemd-init" 
Users that have installed systemd as init will know what they are doing and will be able to find that page. 
Ubuntu should document the default init in manpages.

** Affects: ubuntu-docs (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

- # man init 
+ # man init
  Brings up the documentation for systemd but systemd is not being used as init.
  This  confuses users about which system is being used as "init", and how to manage services on the system.
  
  You can see that this is still upstart with:
  # sudo readlink /sbin/init
- or 
+ or
  # ls -l /sbin/init
  
  # man init
  Should still result in the same thing as
- # man upstart 
+ # man upstart
  
  Until systemd is used for init.
  
- This effects 14.10 as of Dec 21, 2012
+ This effects 14.10 as of Dec 21, 2014
  
  The solution would be for systemd to register it's init man page as, for example, systemd-init .
  Users that have installed systemd as init will no what they are doing. Ubuntu should document the default int.

** Description changed:

  # man init
  Brings up the documentation for systemd but systemd is not being used as init.
  This  confuses users about which system is being used as "init", and how to manage services on the system.
  
  You can see that this is still upstart with:
  # sudo readlink /sbin/init
  or
  # ls -l /sbin/init
  
  # man init
  Should still result in the same thing as
  # man upstart
  
  Until systemd is used for init.
  
  This effects 14.10 as of Dec 21, 2014
  
- The solution would be for systemd to register it's init man page as, for example, systemd-init .
- Users that have installed systemd as init will no what they are doing. Ubuntu should document the default int.
+ One solution would be to rename this systemd man page to, for example, "systemd-init" 
+ Users that have installed systemd as init will know what they are doing and will be able to find that page. 
+ Ubuntu should document the default init in manpages.

-- 
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu.
https://bugs.launchpad.net/bugs/1404619

Title:
  "man init" results in systemd man page instead of upstart

Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  # man init
  Brings up the documentation for systemd but systemd is not being used as init.
  This  confuses users about which system is being used as "init", and how to manage services on the system.

  You can see that this is still upstart with:
  # sudo readlink /sbin/init
  or
  # ls -l /sbin/init

  # man init
  Should still result in the same thing as
  # man upstart

  Until systemd is used for init.

  This effects 14.10 as of Dec 21, 2014

  One solution would be to rename this systemd man page to, for example, "systemd-init" 
  Users that have installed systemd as init will know what they are doing and will be able to find that page. 
  Ubuntu should document the default init in manpages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1404619/+subscriptions