Upgrading to systemd etc.

[caderoux]

I know there's some kind of switchover to systemd in the works, but I don't really understand what I need to do to get ready.

I have a couple Pogoplug 4 devices. I updated them today and got a couple interesting messages:

(1/3) upgrading filesystem [######################] 100%
warning: directory permissions differ on sys/
filesystem: 755 package: 555

and

The legacy configuration options are no longer supported in rc.conf,
convert your rc.conf to the new configuration formats.

Now I think I can ignore the first one.

For the second, I need some pointers to what to do. These are the DAEMONS on the two systems:

$this->bbcode_second_pass_code('', 'DAEMONS=(!hwclock syslog-ng network netfs crond openntpd sshd sabnzbd samba bftpd)')

$this->bbcode_second_pass_code('', 'DAEMONS=(hwclock syslog-ng network netfs crond sshd)')

I tried using systemctl to enable services according to an article I read online, but got this:

$this->bbcode_second_pass_code('', '[root@alarm ~]# systemctl
Failed to get D-Bus connection: No connection to service manager.
[root@alarm ~]# systemctl --all
Failed to get D-Bus connection: No connection to service manager.
[root@alarm ~]# systemctl --all list-units
Failed to get D-Bus connection: No connection to service manager.
[root@alarm ~]#
')

Sounds like I need to install something in addition to the regular upgrade?

This is my version information:

Linux alarm 3.1.10-14-ARCH #1 PREEMPT Sat Nov 24 20:33:17 UTC 2012 armv5tel GNU/Linux

[hydro]

The second warning does not imply you have to switch to systemd, but, as it says, to remove the legacy options from rc.conf and to create the necessary new configuration files.

https://wiki.archlinux.org/index.php/In ... ts/rc.conf
https://wiki.archlinux.org/index.php/Sy ... figuration

You can keep the DAEMONS array in rc.conf (and you should while using initscripts). If you decide to use systemd, it will start the related services or the old rc-scrips, if necessary. But it is a good idea to enable services directly, as you already did. However, systemd will not run unless you install systemd-sysvcompat (or modify your bootloader) and reboot. This is why you get the error messages, but systemctl enable service will create the necessary links even when systemd is not running.