Re: Installing an Alternative Init?
On 20141111_0733-0500, Miles Fidelman wrote:
> Brian wrote:
> >On Tue 11 Nov 2014 at 02:02:07 +0100, Michael Biebl wrote:
> >
> >>Am 11.11.2014 um 01:58 schrieb Miles Fidelman:
> >>
> >>>Michael Biebl wrote:
> >>>>Sorry, but that is not what I asked for. I asked for "specifics".
> >>>>Your answer doesn't contain any specific problem which would make me
> >>>>able to reproduce any problem.
> >>>>
> >>>>I've tested various use cases and "apt-get install -y sysvinit-core"
> >>>>always did the right thing.
> >>>>
> >>>>Please show me an example where it doesn't.
> >>>Frankly, no. 40 years of experience administering various kinds of
> >>>systems gives me some perspective. I've had enough experience with
> >>>dependency hell on Debian (apt is phenomenal, expect when it isn't), and
^^^^^^
I think you meant 'except', rather than 'expect'. Right?
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?
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?
And the apt-get command,
"apt-get install -y systemd"
should switch a host that is running sysvinit or upstart, to running systemd.
If not that is *another* bug in apt-get that must be fixed before release of
Jessie.
If the release team were to accept that *both* these (hypothesized)
bugs are release critical, and have them tested and fixed before
release, then there might be peace once again in Debian.
HTH
--
Paul E Condon
pecondon@mesanetworks.net
Reply to: