[arch-general] /usr is not mounted. This is not supported.
ino-news at spotteswoode.dnsalias.org
Thu Oct 27 04:38:44 EDT 2011
Dwight Schauer wrote:
> My root= on my kernel boot line is using /dev/by-uuid/ so if the
> initramfs can find the root device, I'm sure it can find the /usr
> device from the rootfs /etc/fstab.
> I've not noticed any breakage on all my system's that have a seperate
> /usr, apart from the message doing boot.
Don't you have a boot message saying "minilogd not found" or somesuch?
$ which minilogd -> /usr/sbin/minilogd
By the time /etc/rc.sysinit starts minilogd, /usr is not available, so
there's no minilogd and hence, no log of early boot messages.
I'm thinking of solving this particular problem like this:
minilogd requires the following libs:
-rwxr-xr-x 1 root root 11K Oct 18 18:34 /usr/sbin/minilogd
lrwxrwxrwx 1 root root 12 Sep 9 01:23 /usr/lib32/libc.so.6 -> libc-2.14.so
-rwxr-xr-x 1 root root 1.4M Sep 9 01:23 /usr/lib32/libc-2.14.so
lrwxrwxrwx 1 root root 26 Sep 9 01:23 /lib/ld-linux.so.2 -> ../usr/lib32/ld-linux.so.2
-rwxr-xr-x 1 root root 141K Sep 9 01:23 /usr/lib32/ld-2.14.so
I don't know why it asks for libs out of usr/lib32, this output is from
(the recursive use of) readelf(1). This is on a 64bit PC.
So I could "mount -B / /mnt/root" and copy the needed file hierarchy to
On the other hand, rc.sysinit also invokes /sbin/bootlogd, which leaves
most of the interesting stuff in var/log/boot, so this would be an
academic exercise ...
More information about the arch-general