Date: Fri, 15 Jan 1999 05:20:08 +0100 From: Eivind Eklund <eivind@FreeBSD.ORG> To: Don Lewis <Don.Lewis@tsc.tdk.com> Cc: fs@FreeBSD.ORG Subject: Re: Mount bogosity Message-ID: <19990115052007.B362@bitbox.follo.net> In-Reply-To: <199901150227.SAA27492@salsa.gv.tsc.tdk.com>; from Don Lewis on Thu, Jan 14, 1999 at 06:27:57PM -0800 References: <eivind@yes.no> <199901150227.SAA27492@salsa.gv.tsc.tdk.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 14, 1999 at 06:27:57PM -0800, Don Lewis wrote: > 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? Doesn't work. It complains about not being able to find the mountpoint. > 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 ... Yeah. I don't really know a good way of handling it - I just thought I'd note that it is bogus so somebody else could think about it, too :-) Eivind. 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?19990115052007.B362>