I downloaded the Fedora-17-arm-console.tar.xz rootfs and put it on my sheevaplug. Everything was fine except named wouldn't start, was getting a timeout error from systemd. i.e Jun 30 11:52:54 tau systemd[1]: PID file /run/named/named.pid not readable (yet?) after start. Jun 30 11:53:19 tau systemd[1]: named.service operation timed out. Terminating. Jun 30 11:53:19 tau systemd[1]: Unit named.service entered failed state. Turns out that the problem was due to /var/run being a directory and not a symlink to /run (as in F16) i.e from the rootfs tar drwxr-xr-x root/root 0 2012-06-18 02:32 var/run/ drwxr-xr-x root/root 0 2012-04-30 15:12 var/run/NetworkManager/ -rw-rw-r-- root/utmp 0 2012-06-17 21:56 var/run/utmp drwxr-xr-x root/root 0 2012-05-02 10:38 var/run/wpa_supplicant/ drwxr-xr-x root/root 0 2012-02-09 01:25 var/run/sepermit/ drwxr-xr-x root/root 0 2012-02-09 01:25 var/run/faillock/ drwxr-xr-x root/root 0 2012-02-09 01:24 var/run/console/ drwxr-xr-x root/root 0 2012-02-02 17:03 var/run/ppp/ drwxr-xr-x root/root 0 2012-05-02 09:02 var/run/setrans/ drwxrwxr-x root/root 0 2012-03-23 19:31 var/run/netreport/ And named was putting its pid file under /var/run/named/named.pid and systemd was looking for it in /run/named/named.pid Once I moved all the /var/run stuff to /run and made /var/run a symlink ro /run, i.e lrwxrwxrwx. 1 root root 6 Nov 20 2011 /var/run -> ../run named now starts fine under systemd. Also, (a minor thing) /run is a tmpfs mount, i.e tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) so having the following in the rootfs drwxr-xr-x root/root 0 2012-02-29 23:18 run/blkid/ drwxr-xr-x root/root 0 2012-02-29 23:19 run/mount/ -rw-r--r-- root/root 0 2012-02-29 23:19 run/mount/utab drwxr-xr-x root/root 0 2012-02-11 05:46 run/lock/ drwxr-xr-x root/root 0 2012-02-02 17:03 run/lock/ppp/ isn't much use. Cheers, Andrew _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
