Messages in this thread | | | Date | Fri, 9 Mar 2001 13:38:42 -0500 (EST) | From | Alexander Viro <> | Subject | Re: Ramdisk (and other) problems with 2.4.2 |
| |
On Fri, 9 Mar 2001, Mike Galbraith wrote:
> I was generally exercising with 'what can I do wrong' scenarios when I > noticed some strangness. If you boot a ramdisk root with init=/bin/sh, > mount a drive, cd to it and exec chroot . /bin/sh and then mount proc, > proc/mounts shows /dev/root and the freshly mounted drive as both being > root. /dev/root must still be the ramdisk, as no pivot (or playing > with remount) had been done at that time. > > I don't know if it would show the same using two partitions or not, > nor if it's a problem.. certainly looks odd though.
Why would it be a problem? /proc/mounts shows names in the context of process reading it. We could filter out stuff that happens to be outside of visible subtree, but that won't change anything.
Could somebody post the exact way to reproduce the problem? -o remount scenario is obvious, but that's a case of you get what you ask for. Anything else? Cheers, Al
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |