Openrc doesn't filter out the line "rootfs / rootfs rw 0 0" from mtab. Previous 1.X baselayout didn't show that entry. This is a redundant entry since the root fs is properly mounted from /dev/root. I don't know if that is a bug, but adding a simple grep command to /etc/init.d/mtab would solve this quite easily. Reproducible: Always
it isnt a redundant entry ... it is actually a completely different filesystem that /dev/root gets mounted over
That entry needs to be there so that / can be overmounted with tmpfs and umounted without error. See bug #194615 for the gory details.
No existing distribution (known to me) shows that entry. It's only a minor cosmetic problem to me though... I'm currently filtering it since I don't use a tmpfs root
maybe, but no other distro provides a flexible baselayout like Gentoo does. you do use a tmpfs root and you dont even know it ... everyone does -- they dont have a choice with linux-2.6. dont believe me; check your /proc/mounts. Roy: no chance to detect whether the / is initramfs and optionally filtering it ? i know what the entry means, and you know what it means, but really only people who play with initramfs knows this. the large majority of people are just confused.
Not easily afaik. Also, I seem to recall either udev or hal wanting it too many moons ago. Adding Cardoe and zzam for their comments.
Doug: in the meantime, can you add a note to the migration guide ?
Need to update docs.
with things moving towards /etc/mtab being a symlink to /proc/mounts, i wouldnt bother filtering the output to "protect" users. just add a note to the guide and call it a day.
(In reply to comment #8) > with things moving towards /etc/mtab being a symlink to /proc/mounts, i wouldnt > bother filtering the output to "protect" users. just add a note to the guide > and call it a day. > What note, exactly, and where would you put it in the guide? I can't see anything specific that needs to be added, based on the comments.
Documented in the openrc-migration guide now, that it's not a bug to be listed twice.
*** Bug 367637 has been marked as a duplicate of this bug. ***