On Tue, 08.02.11 16:49, Chanwoo Choi ([email protected]) wrote: > Dear members, >
Heya, > [ 4.310630] systemd[1]: Succesfully opened /dev/kmsg for logging. > [ 4.315351] systemd[1]: systemd 16 running in system mode. (-PAM -LIBWRAP > -AUDIT -SELINUX +SYSVINIT -LIBCRYPTSETUP; ubuntu) > Welcome to Linux! > [ 4.340060] systemd[1]: Your kernel apparently lacks built-in ipv6 > support. Might be a good idea to compile it in. We'll now try to work aroun > d this by calling '/sbin/modprobe ipv6'... > [ 4.356012] systemd[1]: About to execute: /sbin/modprobe -qab -- ipv6 > [ 4.363128] systemd[1]: Forked /sbin/modprobe as 1396 > [ 4.460776] systemd[1]: /sbin/modprobe failed with error code 1. This happens because ipv6 is blacklisted in your setup or not compiled into the kernel. > [ 4.469855] systemd[1]: Set hostname to <chan>. > [ 4.500345] systemd[1]: Looking for unit files in: > [ 4.503736] systemd[1]: /usr/local/build/etc/systemd/system > [ 4.509371] systemd[1]: /usr/local/build/lib/systemd/system > [ 4.517727] systemd[1]: Looking for SysV init scripts in: > [ 4.521716] systemd[1]: /etc/init.d > [ 4.525288] systemd[1]: Looking for SysV rcN.d links in: > [ 4.530565] systemd[1]: /etc > [ 4.535202] systemd[1]: Using cgroup controller name=systemd. File system > hierarchy is at /sys/fs/cgroup/systemd/system. > [ 4.546258] systemd[1]: Installed release agent. > [ 4.583644] systemd[1]: Created root group. > [ 4.586575] systemd[1]: Using notification socket > /org/freedesktop/systemd1/notify > [ 4.597105] systemd[1]: Successfully created private D-Bus server. > [ 4.601942] systemd[1]: Using kernel console ttySAC2 > [ 4.797077] systemd[1]: Failed to load configuration for udev.service: No > such file or directory Hmm, if you build udev with systemd support you should get the right service file for udev installed. > [ 5.020403] systemd[1]: Installed new job systemd-sysctl.service/start as > 26 > [ 5.134805] systemd[1]: Installed new job sysctl.service/start as 46 Hmm, so for some reason you have both sysctl and systemd-sysctl installed. Most likely you installed a new systemd version over an existing one. sysctl.service existed only in older versions and was recently replaced by a systemd internal implementation by the name of systemd-sysctl.service. Fixing this probably just means removing sysctl.service (or much better: removing all old cruft from old installations and installing systemd anew). Normally a package manager should do that for you. > [ 5.532744] systemd[1]: Failed to initialize automounter: No such file or > directory Most likely your kernel is lacking autofs4 support of some kind. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
