Date: Thu, 14 Jan 1999 18:27:57 -0800 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: Eivind Eklund <eivind@yes.no>, fs@FreeBSD.ORG Subject: Re: Mount bogosity Message-ID: <199901150227.SAA27492@salsa.gv.tsc.tdk.com> In-Reply-To: Eivind Eklund <eivind@yes.no> "Mount bogosity" (Jan 15, 2:55am)
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 15, 2:55am, Eivind Eklund wrote: } Subject: Mount bogosity } root(eetest)--# chroot buildstage sh -c 'mount /dev/wd2a /mnt' } root(eetest)--# umount buildstage/mnt } umount: buildstage/mnt: not currently mounted } root(eetest)--# chroot buildstage sh -c 'umount /mnt' } } This does NOT look correct. I couldn't find any way to unmount the FS } without repeating the chroot. umount /dev/wd2a? This stuff is kind of bogus. If you do a mount while chrooted, the full path to the mount point isn't recorded, so mount only displays the partial path. How are you supposed to find the mount point again? It would be nice if the path to the chroot directory was preserved so that the full path could be recorded in the kernel, but this sort of goes against the grain of the Unix philosophy. Even with the full path name in the mount table, you can still mess things up by renaming one of the intermediate directories ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901150227.SAA27492>