This bug is with the sys-apps/util-linux-2.12i-r1 package's /bin/mount command. The following line within /etc/fstab (no partition with SYSTEM label): LABEL=SYSTEM /mnt/system vfat gid=100,umask=0002 0 0 where there isn't any partition whose VFAT label is SYSTEM, causes this command: mount -a to generate a segment fault. Commenting the fstab line above prevents mount's segment fault. Similarly, the following fstab line also causes mount to segment fault (no partition with bootx label): LABEL=/bootx /boot ext2 noatime 1 2 This is quite noticable as it causes /sbin/rc to terminate, during the bootup sequence, without having mounted any of the local filesystems. This regression bug was introduced with sys-apps/util-linux-2.12i-r1 and is not present in the 2.12-r4 release. I will attach my emerge info outout.
Created attachment 46382 [details] "emerge info" capture from the computer demonstrating this bug
Created attachment 47055 [details, diff] Don't call streq(..) in mounted(..) if an argument would be NULL. 2.12-r4 and 2.12i behave the same if you apply the patch to 2.12i: They continue to mount other filesystems.
fixed in 2.12p, thanks guys :)
