[SOLVED] just did an update - seeing systemd related info from pacman

Question

EDIT:   re-reading through the archlinux grub2 docs, I just saw this:  https://wiki.archlinux.org/index.php/GR … _arguments    ... hoping that's all I have to do for a smooth reboot?
I just got done with major epic headaches dealing with the  'The /lib directory becomes a symlink' issue from 2012-07-14 - in fact I had to just freaking do a complete reinstall.  ( it went with no issues on one of my pc's, then when I later tried a major upgrade on my other pc, it all went to bloody hell )
... so, I _just_ got the other pc running via fresh install yesterday, and today I do a 'pacman -Syu'...  to get another ominous sounding warning of possible impending doom...
I'm concerned about the "Append 'init=/bin/systemd' to your kernel command line in your bootloader to replace sysvinit with systemd" :
# pacman -Syyu
:: Synchronizing package databases...
core 106.7 KiB 247K/s 00:00 [#############################################################################] 100%
extra 1421.7 KiB 714K/s 00:02 [#############################################################################] 100%
community 1777.2 KiB 646K/s 00:03 [#############################################################################] 100%
:: Starting full system upgrade...
:: Replace libsystemd with core/systemd? [Y/n] Y
:: Replace systemd-tools with core/systemd? [Y/n] Y
resolving dependencies...
looking for inter-conflicts...
Targets (12): cracklib-2.8.19-1 filesystem-2012.8-1 firefox-15.0-1 gdk-pixbuf2-2.26.3-1 glibc-2.16.0-4 ifplugd-0.28-13 initscripts-2012.08.3-2 libsystemd-188-2 [removal] pkg-config-0.27.1-1
rekonq-1.1-1 systemd-189-3 systemd-tools-188-2 [removal]
Total Download Size: 29.00 MiB
Total Installed Size: 91.14 MiB
Net Upgrade Size: 7.73 MiB
( 6/10) upgrading ifplugd [#############################################################################] 100%
* When used with initscripts, /etc/ifplugd/ifplugd.conf now uses
INTERFACES= again instead of NET_IFS=.
* This package no longer provides a default ifplugd.action script.
* To use ifplugd with systemd, run
systemctl enable [email protected]
( 7/10) installing systemd [#############################################################################] 100%
ln -s '/usr/lib/systemd/system/[email protected]' '/etc/systemd/system/getty.target.wants/[email protected]'
:: Append 'init=/bin/systemd' to your kernel command line in your
bootloader to replace sysvinit with systemd
Question #1: Will my system boot if I _don't_ add the "init=/bin/systemd" to my kernel command line in my bootloader?
Question #2: I'm using grub2 via bios MBR; yesterday when I installed the new system using the latest archlinux install iso, I generated the grub2 conf using the "grub-mkconfig -o /boot/grub/grub.cfg" technique... which build a crazy looking conf that looks more like a shell script than anything.  ( I'm used to editing the old grub1 config manually, and it made sense to me ).  So where the heck am I supposed to put this 'init=/bin/systemd' pragma?
Assistance and advice much appreciated!
Last edited by corey_s (2012-08-30 20:01:47)

Answer 1

silentsnake wrote:
Hi,
according to the mailing list they just merged libsystemd and systemd-tools to the systemd package. Since the initscripts are still present, you can leave it alone and it will boot as usual. The message is more like a friendly 'C'mon, we'll going to switch to systemd anytime soon, so just give it a try.'.
I haven't used grub2 for a while, but there should be a file called /etc/default/grub where you can add GRUB_CMDLINE_LINUX="init=/bin/systemd". Then regenerate the configuration via grub-mkconfig and you are good to go.
Edit: Too late
Thanks for your time in responding though anyhow - much appreciated!   (c8=