Date: Fri, 15 Jan 1999 22:29:35 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: eivind@FreeBSD.ORG (Eivind Eklund) Cc: Don.Lewis@tsc.tdk.com, fs@FreeBSD.ORG Subject: Re: Mount bogosity Message-ID: <199901152229.PAA14068@usr04.primenet.com> In-Reply-To: <19990115052007.B362@bitbox.follo.net> from "Eivind Eklund" at Jan 15, 99 05:20:08 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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 :-) Har. It's trivial. All you have to do is set curproc->p_fd->fd_rdir to the real root directory, instead of "NULL" when you create the first process, and then get rid of the "NULL implies root" code in the lookup code. The fd_rdir value is inherited on fork, and only set on chroot, so this is a trivial change. I've been after this (among other small changes) for years. It incidently solves your problem, since it removes the distinction for vnode covering in the chroot vs. non-chroot case. If you dig in the -current list archives, you'll find a set of patches that does this. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. 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?199901152229.PAA14068>