Hi,
On 22.12.2013 20:41, Vincent Lefevre wrote:
Sorry, I mixed up two bugs related to systemd and with similar bug
number (the other one is 732623, where the installation of systemd
breaks some lightdm features).
I have lightdm installed parallel to gdm3 and just switched to lightdm.
I cannot reproduce the issue described in bug 732623, i.e. for me all
the four menu entries are there, independent of how often I login/logout.
If GNOME developers want to require systemd as the init system,
I don't see this as a reason not to add the dependency. Users
are not forced to install GNOME packages. And if they want GNOME,
they would have to accept the consequences about the init system.
The problem is the policy [1]:
"Essential is defined as the minimal set of functionality that must be
available and usable on the system at all times"
So removing an essential package is not really allowed by the policy.
Have you tried using systemd as PID 1?
No, I don't want to do such kind of risky test. Since I was not
using the GNOME desktop environment, but just gdm3 and some GNOME
apps, I decided to drop those that depend on systemd. For me,
this meant:
* gdm3 -> lightdm (but systemd must *not* be installed due to
bug 732623),
Since this problem does not occur for me and I am using systemd as it
was meant to be used, i.e. as PID 1, perhaps you may want to reconsider
trying systemd as PID 1?
By the way, that is not 'risky' in any way: You can just edit the boot
entry in grub (or whatever boot loader you use) by appending
'init=\bin\systemd' (with the package systemd installed). With this, you
can try booting with systemd just for one session, without changing any
configuration on your hard disk.
Best regards,
Andreas
1: http://www.debian.org/doc/debian-policy/ch-binary.html#s3.8
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
