Laurent Bigonville-5 wrote > Le Wed, 03 Dec 2014 10:18:36 +0100, > Martin Steigerwald <
> Martin@ > > a écrit : > >> Am Mittwoch, 3. Dezember 2014, 08:35:00 schrieb Erwan David: >> > Le 02/12/2014 23:15, Martin Steigerwald a écrit : >> > > Am Dienstag, 2. Dezember 2014, 18:47:38 schrieb Renaud OLGIATI: >> > >> On Tue, 2 Dec 2014 14:22:13 -0700 >> > >> >> > >> Aaron Toponce < > aaron.toponce@ > > wrote: >> > >>>> It's a waste. They shouldn't have left. I'm pretty neutral >> > >>>> about systemd as I'm only an end user but I disklike having it >> > >>>> forced upon me this way. >> > >>> >> > >>> # apt-get install upstart >> > >>> # apt-get install sysvinit-core >> > >>> # apt-get install openrc >> > >>> No one is forcing you to stick with systemd. The "fork" is just >> > >>> silly. >> > >> >> > >> Another way to look at it is "forward planning for the release >> > >> after Jessie, when systemd may well become compulsory..." >> > > >> > > Or going beyond what is offered in Debian… like making GNOME >> > > installable without having any systemd related package installed. >> > >> > The systemd package is just a small part of systemd. I'd like to >> > remove systemd-logind and lbpam-systemd, sinc I have no clue at all >> > that logind is better deisgned and programmed than resolved, which >> > showed it was designed without any care for well known attacks. >> >> I explicetely wrote "any systemd related package". >> [...] >> >> So you can still choose to what init system to use, but running >> completely without any systemd related packages gives you a really >> crippled system. > > As explained several times on this ML, depending against libsystemd0 > package doesn't mean anything about requiring systemd to be used as > PID1 or not. Even Ian's GR was not taking the "I don't want any systemd > package on my machine" use case into account you know. > > But if you have that special concern, you'll have to start recompiling > the packages I'm afraid. Start with policykit and network-manager (and > other package defining a dependency against libpam-systemd) to make > them use ConsoleKit again, you would at least be able to remove the > systemd package completely. And so it comes full circle. This is why there is a need for a Debian fork. /I/ don't have to do any of those things. You don't either. The good folks at Devuan will take care of all that for you. -- View this message in context: http://debian.2.n7.nabble.com/Debian-fork-Devuan-Debian-without-Systemd-tp3444438p3447295.html Sent from the Debian User mailing list archive at Nabble.com. -- 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/1417757630187-3447295.p...@n7.nabble.com
