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

[Debian Bug Tracking System]

reassign -1 release-notes

Bug #760947 [systemd] systemd: Does not start consoles configured in /etc/inittab
Bug reassigned from package 'systemd' to 'release-notes'.
No longer marked as found in versions systemd/208-8.
Ignoring request to alter fixed versions of bug #760947 to the same values previously set
--
760947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760947
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems

[Antoine Beaupre]

/etc/inittab is a sysvinit specific config file, which systemd won't
read. This is not going to change.
If you have custom changes to /etc/inittab, those need to be converted
into systemd equivalents manually, if necessary.

As I said in a previous mail, that's not what I call a seamless upgrade.
It be at least documented in the release notes or on
https://wiki.debian.org/systemd

I had a similar problem and documented this in the systemd manpage here:

https://wiki.debian.org/systemd#Virtual_and_serial_console_changes

I agree this could be part of the release notes - do you have any
suggestion as where the note should be?

If you looked for it in the release notes, where did you look?

Thanks!

A.

[Antoine Beaupre]

Control: tag -1 +patch

Post by Antoine Beaupre

/etc/inittab is a sysvinit specific config file, which systemd won't
read. This is not going to change.
If you have custom changes to /etc/inittab, those need to be converted
into systemd equivalents manually, if necessary.

As I said in a previous mail, that's not what I call a seamless upgrade.
It be at least documented in the release notes or on
https://wiki.debian.org/systemd

https://wiki.debian.org/systemd#Virtual_and_serial_console_changes
I agree this could be part of the release notes - do you have any
suggestion as where the note should be?
If you looked for it in the release notes, where did you look?

Here's a patch that may fix this for you... it would probably need to be
backported to Jessie to be really relevant at this point, but
whatever...


Index: en/issues.dbk
===================================================================
--- en/issues.dbk (révision 11433)
+++ en/issues.dbk (copie de travail)
@@ -306,6 +306,18 @@
basis.
</para>

+ <section id="systemd-inittab-changes">
+ <title>SystemD does not configure consoles from
+ /etc/inittab</title>
+ <para>Since the switch to SystemD in Jessie, the /etc/inittab
+ configuration file is ignored. See the <ulink
+ url="http://0pointer.de/blog/projects/serial-console.html">upstream
+ documentation on how to configure serial console</ulink> and the
+ <ulink url="https://wiki.debian.org/systemd#Virtual_and_serial_console_changes">Debian
+ wiki</ulink> for more information.
+ </para>
+ </section>
+
<section id="openssh-protocol-and-cipher-support-changes">
<title>Older ciphers and SSH1 protocol disabled in OpenSSH by default</title>
<para>

A.

[Debian Bug Tracking System]

Post by Antoine Beaupre
tag -1 +patch

Bug #760947 [release-notes] systemd: Does not start consoles configured in /etc/inittab
Added tag(s) patch.

[Michael Stapelberg]

nit: the correct capitalization of systemd is “systemd” (i.e. all
lowercase) :)

Post by Antoine Beaupre
Control: tag -1 +patch

Post by Antoine Beaupre

/etc/inittab is a sysvinit specific config file, which systemd won't
read. This is not going to change.
If you have custom changes to /etc/inittab, those need to be

converted

Post by Antoine Beaupre

into systemd equivalents manually, if necessary.

As I said in a previous mail, that's not what I call a seamless

upgrade.

Post by Antoine Beaupre

It be at least documented in the release notes or on
https://wiki.debian.org/systemd

https://wiki.debian.org/systemd#Virtual_and_serial_console_changes
I agree this could be part of the release notes - do you have any
suggestion as where the note should be?
If you looked for it in the release notes, where did you look?

Here's a patch that may fix this for you... it would probably need to be
backported to Jessie to be really relevant at this point, but
whatever...
Index: en/issues.dbk
===================================================================
--- en/issues.dbk (révision 11433)
+++ en/issues.dbk (copie de travail)
@@ -306,6 +306,18 @@
basis.
</para>
+ <section id="systemd-inittab-changes">
+ <title>SystemD does not configure consoles from
+ /etc/inittab</title>
+ <para>Since the switch to SystemD in Jessie, the /etc/inittab
+ configuration file is ignored. See the <ulink
+ url="http://0pointer.de/blog/projects/serial-console.html">upstream
+ documentation on how to configure serial console</ulink> and the
+ <ulink url="https://wiki.debian.org/systemd#Virtual_and_serial_cons
ole_changes">Debian
+ wiki</ulink> for more information.
+ </para>
+ </section>
+
<section id="openssh-protocol-and-cipher-support-changes">
<title>Older ciphers and SSH1 protocol disabled in OpenSSH by default</title>
<para>
A.

[Debian Bug Tracking System]

Your message dated Wed, 20 Feb 2019 22:01:39 +0100
with message-id <b65dfd52-aa10-4e79-7776-***@debian.org>
and subject line Re: systemd: Does not start consoles configured in /etc/inittab
has caused the Debian Bug report #760947,
regarding systemd: Does not start consoles configured in /etc/inittab
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)