I'm asking because "init 3" does not work anymore with my system (sysvinit-core installed)?
It seems siduction has altered the config for the runlevels. kdm, which I use instead of lightdm is now configured for RL 2-5 whereas it used to be configured for RL5 only. But what really is being in the way is sidu-base. I needed to deconfigure it entirely to get init to work agian. There may be other ways to configure it, but this seems the easiest way.
Init 3 works with lightdm.
It's a systemd issue kdm related.
KDM doesn't have until now systemd support and kdm defaults for debian are RL 2-5.
So siduction hasn't altered kdm config runlevels.
Thanks for this exhaustive info. You're aware I don't use systemd?
Do you have any insight what exactly sidu-base does? Because I didn't get init to work until I disabled it for RL 2-5.
sidu-base is the base package for sidu-manual, sidu-installer - delete it, if you don't use it.
Regarding kdm and sysvinit: you are on your own, we don't support it anymore.
I am not even sure if kde/kde-devs supports kdm anymore
Zitat melmarker: "Regarding kdm and sysvinit: you are on your own, we don't support it anymore"
apt-cache policy sysvinit*
...
sysvinit-utils:
Installiert: 2.88dsf-58
apt-get purge sysvinit-utils
...
WARNUNG: Die folgenden essentiellen Pakete werden entfernt.
Dies sollte NICHT geschehen, außer Sie wissen genau, was Sie tun!
e2fsprogs util-linux (wegen e2fsprogs) init systemd-sysv (wegen init) sysvinit-utils initscripts (wegen
util-linux)
0 aktualisiert, 1 neu installiert, 274 zu entfernen und 0 nicht aktualisiert.
Es müssen 42,6 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 892 MB Plattenplatz freigegeben.
Sie sind im Begriff, etwas potentiell Schädliches zu tun.
Zum Fortfahren geben Sie bitte »Ja, tue was ich sage!« ein.
?]
it seems a little dangerous :o
Clarification: we don't support kdm and sysvinit - that doesn't mean that one have to remove sysvinit-utils :)