Bug#760947: systemd: Does not start consoles configured in /etc/inittab

Samuel Thibault sthibault at debian.org
Tue Sep 9 15:39:22 BST 2014


Brian Potkin, le Tue 09 Sep 2014 15:26:16 +0100, a écrit :
> On Tue 09 Sep 2014 at 13:37:50 +0200, Samuel Thibault wrote:
> > On a wheezy system, I had a serial console configured in /etc/inittab,
> > used as a secondary work terminal (i.e. no console=ttyS0 on the kernel
> > command line). After an upgrade to Jessie, logind doesn't start a getty
> > on ttyS0.
> 
> Is
> 
>    http://0pointer.de/blog/projects/serial-console.html
> 
> any use?

Sure, but that's not what I call a seamless upgrade. At least simple
cases like this should be handled by the upgrade.

> > On a freshly installed Jessie system, /etc/inittab still gets installed,
> > but has no effect. That will be very surprising to admins.
> 
> The init (1.20) package for d-i's beta-1 has
> 
>    Pre-Depends: sysvinit-core | systemd-sysv | upstart
> 
> sysvinit-core contains inittab,
> 
> init (1.21) has
> 
>    Pre-Depends: systemd-sysv | sysvinit-core | upstart
> 
> Admins may be surprised that /etc/inittab is absent but should rapidly
> catch on it is not used with systemd.

Ok, if /etc/inittab will not get installed on fresh Jessie installs,
admins will realize things are not being configured there any more.

It is however still worrying for upgraded systems that /etc/inittab will
now be meaningless.  That deserves a NEWS item.

Samuel




More information about the Pkg-systemd-maintainers mailing list