Bug#761063: changes to /etc/inittab are not respected on upgrade from sysvinit

[Michael Biebl]

Am 04.10.2014 um 15:06 schrieb Tollef Fog Heen:
> ]] Marvin Renich 
> 
>> On a system with dbndns, daemontools, and daemontools-run installed,
>> when upgrading from sysvinit to systemd, the changes to /etc/inittab are
>> not respected, so dnscache and tinydns did not start.  In my case, this
>> left an entire local network without dns service.
> 
> /etc/inittab is a sysvinit-only configuration file, so this is
> expected.

Nod, I don't think we will start parsing /etc/inittab in systemd by
default. That said, if someone would be interested in doing that, this
would probably best be done via a generator [1].

  Arguably, we should warn once if the inittab has been changed
> from the shipped default. 

Agreed. As /etc/inittab is not a conffile but copied from
/usr/share/sysvinit/inittab on first installation of the sysvinit(-core)
package, we'd need to go through the history of that package and collect
the md5sums of that file (which IIRC also is different per arch) and the
compare it against the md5sum of the existing /etc/inittab.

As the plan is anyway, to implement a series of checks upon installation
of systemd-sysv, this could be just another one which would be run.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141006/a54f0525/attachment-0002.sig>