Perhaps you need only to add it in the kernel line as: init=/bin/systemd....To make it permanent, enter it in grub.cfg after bootup.
Odd, there is no (nor should there be) any /boot/systemd.Are you by chance at the point where you add "init=/bin/systemd" to your bootloader kernel line? Could you have made a typo and put init=/boot/systemd? Or perhaps if you didn't put any path to systemd *perhaps* /boot/ would be inferred as that may be the current working directory when init is called.(edit: beat by
Shark wrote:One way allows you to not get rid of rc.local with systemd. See https://wiki.archlinux.org/index.php/Sy … s#rc.localYes, I've seen that - but I'd like to have a pure, systemd-only setup.ataraxia wrote:You shouldn't need the line with the "for" statement any more. ondemand has been the kernel default governor for a little while now.Oke, thanks.
Banton wrote:San2ban wrote:AllanWhat I meant is, it had become PID1. When I issued init 0, init 6 commandsit never worked. It said something about systmctl not recognizing something..So... I imagined it had replaced itself.I re-installed runit-run, and init 0, init 6 started workingThat's just not possible, Archlinux only boots systemd if you tell it to.Not really.
Hello,I turned into systemd booting. For convinience I choose to lxdm to log in. But my habit was the Archlinux look and I don't know which way should start xdm with that particular look&feel.What should be the equivalent to be launch by systemctl ?
Evidently there is a bug with systemd stopping networkmanager before remote filesystems are unmounted.https://bbs.archlinux.org/viewtopic.php?id=150029Are you using networkmanager? Have you tried using something else?