That's cool... I realized that, I was using sysvinit-core and then, libsystemd0 appeared, but it did not forced me to install systemd-sysv.
I'm seeing that systemd is spreading itself everywhere, kind of creepy but, well, I think that it is better to learn about it now, instead of fighting it. If uselessd appear in Debian, I'll experiment it, since it is a new cool init without "useless" systemd bits... Best! Thiago On 22 October 2014 19:38, Christian Seiler <christ...@iwakd.de> wrote: > Am 22.10.2014 23:03, schrieb Dimitrios Chr. Ioannidis: > > On 22/10/2014 11:29 μμ, Martinx - ジェームズ wrote: > >> I meant, it is possible to have sysvinit-core, of course, but, from > >> now on, at least libsystemd0 is required, you cannot remove it without > >> doing some harm. > > > > And this is precisely why the currently GR is so important to pass . > > > > Quoting "... It will avoid Debian becoming accidentally locked in to a > > particular init system (for example, because so much unrelated software > > has ended up depending on a particular init system that the burden of > > effort required to change init system becomes too great). ... " . > > Note that libsystemd0 does not require a particular init system to be > PID1 (it does not even require systemd to be installed, btw.), therefore > regardless of the outcome of the GR, it will NOT affect that specific > dependency. > > Christian > > > -- > 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/544823cc.8080...@iwakd.de > >
