revinary wrote:Anyway, tried it just now
revinary wrote:From what I understand this is the case for regular Mint (ie non LMDE) which uses Ubuntu's upstart
which in turn still relies on some sysvinit functionality.
Brian49 wrote:revinary - thanks for the advice. However, on rebooting I couldn't get to my desktop, only to a console login. I thought the systemd-gui package might be of some help, but contrary to what I expected it doesn't in fact provide a GUI for configuring systemd.
jeffreyC wrote:In my Debian testing (not LMDE just Debian) i have several folders labeled systemd in /etc and /lib and I have not installed systemd yet.
It looks like that is the way Debian is going.
Roken wrote:I had the same problem, console boot only and a complete failure to start x/gdm3 when I tried. Back to the old way for now, for me.
revinary wrote:Hi Brian,
to try out systemd:
- apt-get update
- apt-get install systemd systemd-gui libpam-systemd
- when grub shows up select your kernel, press 'e' and add "init=/bin/systemd" to the kernel parameters and hit F10 to boot
To make systemd the default init system open /etc/default/grub, find GRUB_CMDLINE_LINUX_DEFAULT and add "init=/bin/systemd".
After that run update-grub as root.
I'm using e4rat which gets loaded as init process and then passes control to the actual init process so the process was slightly different.
Anyway, the above should work just fine.
Also, systemd requires cgroup support and a few other kernel options enabled.
Read http://wiki.debian.org/systemd for details.
For me it worked out-of-the-box, no configuration whatsoever.
A few error messages poped up during boot, mostly harmless. Rever to above link for details.
# cp -av /sbin/init /sbin/init.sysvinit
# apt-get install systemd-sysv systemd-gui
# echo "systemd-sysv hold"|dpkg --set-selections
# ln -sf /proc/self/mounts /etc/mtab
Roken wrote:Well, since I installed Debian I decided to give systemd another go, and whilst it did it's job well this time (on the first boot), it appears that there are still problems:
i. You lose persistant mount points in /media and have to recreate them before mounting. In my case this was not a big issue because the only persistant mount points I have are two truecrypt mount points and one for .iso images. It's easy enough to reconfigure to mount them in sub-directories of /home, so not a deal breaker.
ii. After the first boot everything checked out, but on the second and subsequent boots my bluetooth adapter was disabled and wouldn't re-enable (no errors, it just sat there silently doing nothing).
And at the end of the day, it only bought me 5 - 10 seconds off total boot time anyway. Maybe after more work has done it will be viable, but for now if you decide to try be prepared for some issues.
As an aside, on Debian installing systemd-svsv uninstalls sysvinit, but uninstalling systemd-svsv doesn't force a reinstall of sysvinit, which if not corrected would leave a none-booting system. Just something to be aware of if you are playing - remember to reinstall sysvinit before trying to reboot if you remove systemd. Also note that if you do remove systemd then shutdown won't work. You will need to do a hard reset to close the system before rebooting. (It's fine afterwards - a once only thing).
Users browsing this forum: No registered users and 3 guests