On Wed, Oct 28, 2015 at 06:13:54PM +0000, Julien Cristau wrote: > On Wed, Oct 28, 2015 at 19:05:29 +0100, skizzhg wrote: > > > Hi, > > I'm in the same situation and since I'm using sysvinit I'd like to have > > more explanations about this fix, especially what mario asked about it: > > "So from now is not possible to use X without systemd?" > > > > I can see a newest version in sid (2:1.17.3-2) that has libpam-systemd > > as recommended package, I don't get how can be possible just recommend it > > when the X session is not usable at all, you can't even switch on a tty > > and reset the machine is not funny. > > > > So, can I still use whatever init system I like? How? > > Because at the moment it seems Debian is acting a subtle obligation to > > make the switch. > > > libpam-systemd is not an init system.
Who ever said that? Xorg without libpam-systemd is not usable at all; the current "solution" is to install libpam-systemd, and consequently, systemd. As far as I understand it's because you are moving to run the X server as user, fine. Still, I fail to see how do you consider the bug closed with a recommended package that forces to install something else. Even if the systemd package description says that "Installing the systemd package will not switch your init system unless you boot with init=/bin/systemd or install systemd-sysv in addition." I don't know what kind of hybrid mess I will obtain... After diggin around xserver-xorg-legacy sounds like what I need. I was asking in order to avoid having to recover the system again but..."If you want something doing, do it yourself." > > Cheers, > Julien Ciao.
