Bug#747535: systemd-fsck?

Svante Signell svante.signell at gmail.com
Thu May 15 10:21:58 BST 2014


On Thu, 2014-05-15 at 10:55 +0200, Gergely Nagy wrote:
> Thorsten Glaser <tg at debian.org> writes:

> > Integration of some components at the cost of disabling the freedom
> > of users to choose a different free component that also does the job,
> > and at the cost of removing some users' use cases: no. That is not
> > the job of a "Univeral OS". So-called Enterprise distributions can
> > do that, sure. Downstreams and pure blends, too. But not Debian.

Agreed!

> We have a default, that's what Debian is integrating to. You want to
> change the default, that's what downstreams are for. You have the
> freedom to change whichever component you want, if you find people to do
> the neccessary work. Trying to support N+1 options and integrating them
> *all* places a huge burden on every single maintainer, a burden you do
> not want, nor need.

The problem (for me) is not the default init system, the problem is that
init system is changed without a debconf prompt, in my case by
installing network-manager. And NM can be used outside the gnome
environment as well as other gnome components.




More information about the Pkg-systemd-maintainers mailing list