[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#727708: Bits from linux.conf.au



Le mardi 14 janvier 2014 à 11:31 -0700, Bdale Garbee a écrit :
> > If dependencies like "installing GNOME enforces systemd as init system"
> > would be legal, then after a few more such dependencies it would turn
> > out that systemd will be the only option available for virtually all 
> > users - and that all the hassle of supporting multiple init systems
> > was a waste of effort.
> 
> Please be careful about stacking assumptions like this.  Equating GNOME
> to "virtually all users" completely ignores the vast number of Debian
> instances on servers, virtual machines, and embedded systems.  And even
> if you only think about client systems, in my own circle of friends
> there's a lot more XFCE4 than GNOME these days.

As their maintainers have stated, Xfce4 and KDE are most likely going to
require systemd soon.

> > What is supposed to happen when I do "apt-get install sysvinit-core"?
> 
> That's a great question.  I suspect most of the effort in thinking about
> init system transitions so far has gone in to figuring out how to replace
> sysvinit.  But if we're truly going to support alternatives, ensuring we
> have a robust mechanism for deciding which of several init systems that
> may be simultaneously installed is "active" and will control the next
> boot is clearly a requirement.

Only one thing comes to mind when reading about supporting multiple init
systems and how to switch between them:
http://www.redhat.com/archives/fedora-devel-list/2008-January/msg00861.html

-- 
.''`.      Josselin Mouette
: :' :
`. `'
  `-


Reply to: