On Sun, 2015-01-18 at 18:09 +0100, Richard Lucassen wrote:
> On Sat, 17 Jan 2015 16:06:15 +0000
> Ben Hutchings <ben@decadent.org.uk> wrote:
>
> > Control: tag -1 moreinfo
> >
> > I'm unable to reproduce the numeric root in /etc/mtab. I tried using
> > lilo with a non-UUID root, using the Debian packaged kernel and then
> > with a custom kernel with no initramfs. In both cases I see / mounted
> > from /dev/root and that device node does exist. I also tested using
> > both systemd and sysvinit. In all cases /etc/mtab is a symlink
> > to /proc/mounts (as both init systems create it).
>
> I think it is a misunderstanding. I created a symlink in the root
> directory (mind, in the meantime I changed to sda5 instead of sda3):
>
> # ln -s /dev/sda3 /805
> # ls -al /805
> lrwxrwxrwx 1 root root 9 Jan 17 21:41 /803 -> /dev/sda5
I understood that, but not where we got the name 803 (or 805) from.
[...]
> When I choose "Linux-nosd" using "root=UUID", the system boots and a
> mount shows this:
>
> /dev/sda5 on / type ext4 (rw,noatime,nodiratime,discard,data=ordered)
>
> mtab:
>
> rootfs / rootfs rw 0 0
> /dev/disk/by-uuid/d94d08f7-4b3d-47be-acaf-d425e71efece / ext4
> rw,noatime,nodiratime,discard,data=ordered 0 0
>
> When a new initrd.img is generated by apt, everything is ok.
>
> When I choose "test-805" using "root=/dev/sda5", the system boots, but
> "mount" shows:
>
> 805 on / type ext4 (rw,noatime,nodiratime,discard,data=ordered)
>
> mtab:
>
> rootfs / rootfs rw 0 0
> /dev/root / ext4 rw,noatime,nodiratime,discard,data=ordered 0 0
[...]
Oh I see, it's not in /etc/mtab but only in the mount output. It seems
like that's a bug in mount. Maybe we should only read /proc/mounts and
not run mount at all.
Ben.
--
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou
Attachment:
signature.asc
Description: This is a digitally signed message part