dockstar: 1st update in months - systemd vs sysvinit, etc

[seagalimpersonator]

Hi all,

It's been quite a while since I updated my dockstar, but I needed some new apps. I had to jump through a number of hoops to get it updated, since /lib had moved to /usr/lib and so on. But I finally got everything updated.

My questions are about the following messages from pacman:

$this->bbcode_second_pass_code('', '(12/60) installing systemd [##########################################] 100%
Initializing machine ID from D-Bus machine ID.
==> Warning: setcap failed, falling back to setuid root on /usr/bin/systemd-detect-virt
ln -s '/usr/lib/systemd/system/getty@.service' '/etc/systemd/system/getty.target.wants/getty@tty1.service'
:: Append 'init=/bin/systemd' to your kernel command line in your
bootloader to replace sysvinit with systemd
Optional dependencies for systemd
cryptsetup: required for encrypted block devices
libmicrohttpd: systemd-journal-gatewayd
quota-tools: kernel-level quota management
python: systemd library bindings
python2-cairo: systemd-analyze
python2-gobject: systemd-analyze
systemd-sysvcompat: symlink package to provide sysvinit binaries
')

I tried to install systemd-sysvcompat and got
$this->bbcode_second_pass_code('', '
# pacman -S systemd-sysvcompat
resolving dependencies...
looking for inter-conflicts...
:: systemd-sysvcompat and sysvinit are in conflict. Remove sysvinit? [y/N]
')

If I install this package and remove sysvinit, will I need to update uBoot? I assume that I would if I don't install this package - and I remember uBoot as being a pain. If sysvinit will continue to work, I'm fine with keeping it.

$this->bbcode_second_pass_code('', '
(45/60) upgrading mkinitcpio [##########################################] 100%
==> If your /usr is on a separate partition, you must add the "usr" hook
to /etc/mkinitcpio.conf and regenerate your images before rebooting
==> The "block" hook has replaced several hooks:
fw, sata, pata, scsi, virtio, mmc, usb
Replace any and all of these in /etc/mkinitcpio.conf with a single
instance of the "block" hook
')

Do I need to run mkinitcpio? With the old kernel, there wasn't anything but the kernel in /boot.

$this->bbcode_second_pass_code('', '
(56/60) upgrading syslog-ng [##########################################] 100%
==> syslog-ng now reads from /run/systemd/journal/syslog in the
default config. If you still use sysvinit/initscripts, this
must be /dev/log in /etc/syslog-ng/syslog-ng.conf
')

`grep dev/log /etc/syslog-ng/syslog-ng.conf` finds nothing. Do I need to do anything here? If so, what? The message isn't very clear to me.

Thanks!

[pepedog]

Yes, remove sysvinit and install systemd-sysvcompat once services enabled and you are happy
systemctl enable the services, esp network and ssh
Look in /usr/lib/systemd/system to get a clue which services
If you are worried about network, this will at least give auto
systemctl enable dhcpcd@eth0
Don't touch uboot
Don't worry about mkinitcpio
Check /etc/systemd/system/multi-user.target.wants and you are happy before reboot

[WarheadsSE]

and
$this->bbcode_second_pass_code('', 'systemctl enable sshd')