On Thu 18 Sep 2014 at 12:41:40 +0200, Martin Steigerwald wrote: > Am Donnerstag, 18. September 2014, 11:02:11 schrieb Brian: > > On Thu 18 Sep 2014 at 11:27:32 +0200, Martin Steigerwald wrote: > > > The following packages will be REMOVED: > > Install systemd-shim first. > > It was installed as I ran the apt commend and it still is, cause if systemd > doesn´t boot I like to say init=/sbin/init :) > > martin@merkaba:~> dpkg -l | egrep > "systemd-shim|cgmanager|sysvinit-core|systemd-sysv" | cut -c1-70 > ii cgmanager 0.32-4 > ii libcgmanager0:amd64 0.32-4 > ii systemd-shim 8-2 > ii sysvinit-core 2.88dsf-53.4 > > martin@merkaba:~> cat /proc/cmdline > BOOT_IMAGE=/vmlinuz-3.17.0-rc5-tp520 root=/dev/mapper/sata-debian ro > rootflags=subvol=debian init=/bin/systemd resume=/dev/mapper/sata-swap
The OP said >> a) If I will have to have systemd installed even if I do not want it. You replied > I wanted to say no as I thought systemd-shim *and* cgmanager together can > replace it, but according to At this point I wanted to say that systemd-shim and cgmanager replace systemd-sysv. not systemd. I let it go; my mistake. You went on to write > merkaba:~> LANG=C apt-get purge systemd Another mistake on my part: I decided that "systemd" was a typo for "systemd-sysv", especially as later on in your post you seemed to understand that in #727708 the TC were concerned with systemd as PID 1. The systemd-sysv package ensures that the wishes of the TC to make systemd the default init system are carried out. So, sorry about that. Your observation on libpam-systemd is correct. Note that the TC chose "...to not pass a resolution at the current time about whether software may require specific init systems" -- 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/20140918123056.gd4...@copernicus.demon.co.uk
