On 15/11/14 23:04, Paul E Condon wrote:
If one could absolutely rely on apt-get always getting it right, then
"apt-get install -y sysvinit-core"
could always be used to remove systemd even from a system that has
been booted into systemd and running, and not just in the context
of a pre-seed. Right?
That command is unlikely to actually remove systemd on any Debian jessie
system. What it will do is change what the symlink /sbin/init points to
so that next time the system on which you do it is rebooted, it will use
sysvinit as the init daemon.
But if that that apt-get command doesn't work on an installation of systemd,
*that* is a bug in apt-get that *should* be fixed in Jessie *before* it is
released. Right?
Probably wrong.
It seems to me that if doing "apt-get install -y sysvinit-core" on a
Debian jessie system fails, it's far more likely to involve a packaging
bug in one or more of the packages being added/removed than a bug in
apt-get.
And the apt-get command,
"apt-get install -y systemd"
should switch a host that is running sysvinit or upstart, to running systemd.
Nope. It should install the programs comprising the systemd suite...
If not that is *another* bug in apt-get that must be fixed before release of
Jessie.
... but if you meant "apt-get install -y systemd-sysv", I stand by my
statement above: any problems arising in this process are unlikely to be
bugs in apt-get.
And while writing this, I noticed that "apt-get install -y systemd-sysv"
on a system running upstart looks like it will have... *unhappy*
consequences, since unlike systemd and sysvinit, upstart has not had its
packaging restructured into a package full of programs and a package
that changes the /sbin/init symlink.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5467ee7c.6090...@zen.co.uk
