Re: Installing an Alternative Init?
On Tue 11 Nov 2014 at 12:58:25 -0500, Miles Fidelman wrote:
> Brian wrote:
> >Everyone gets it. Not everyone boots with it. Not everyone who boots
> >first time with it gets to use it on subsequent boots.
>
> That is DEFINITELY a definition of "default" that is subject to very
> differing opinions.
Everyone gets systemd. This a a fact, not an opinion.
Everyone can alter what they first boot with. This is a fact, not an
opinion,
Everyone can change the init system after first boot. This is a fact, not an
opinion,
> And there is a very distinct difference between "installed by
> default" and "enabled by default."
There may be. But, everyone gets systemd. (Please see above).
> For the debian-installer, it ultimately comes down to which packages
> are marked as essential in the repo, and what the installer does
> with those packages "by default."
Indeed it does.
> Umm.... no-one has disputed that this is what happens. What many
> have disputed is whether or not alternatives should be possible.
>
> Specifically, if not for debootstrap bug #668001, for which a patch
> now exists, it would be possible to do a netinst that does not
> install systemd as PID1.
Really? You have tested this?
> Further, at least some are advocating for making that choice
> available as part of the menu presented by the installer.
Yes they have.
> The package management system provides for alternatives. A bug in
> debootstrap gets in the way.
When this bug is fixed all will be sweetness and light?
Reply to: