Date: Mon, 25 Oct 2004 15:05:24 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Doug White <dwhite@gumbysoft.com> Cc: Konrad Heuer <kheuer2@gwdg.de> Subject: Re: linux emulation: "/ " resolves to real root dir; why ? Message-ID: <417CEC04.3060705@icyb.net.ua> In-Reply-To: <20041022103516.I48519@carver.gumbysoft.com> References: <4178DBA0.8050605@icyb.net.ua> <20041022131342.W95775@gwdu60.gwdg.de> <4178EE95.6080708@icyb.net.ua> <20041022103516.I48519@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 22.10.2004 20:37 Doug White said the following: ... >>we are taking about different "break outs". Removing the check will >>*not* affect accessing any other filesystem node but "/". Only things like >> cd / >> ls / >>or >> "cd .." from /compat/linux/foo >>will be affected. > > > You missed the point. I am sorry but I think that's what you did. You will be able to do "cd /home" or "ls /home" just fine. Only one filesystem node corresponding to "/" will be affected. > This would mean you would not be able to access > stuff like /home, which would make it awful hard to access user home > directories, unless you create symlink copies in the /compat/linux tree. no, see what I wrote above. > > As long as you create the top-level dir in /compat/linux first, mkdir -p > will Do The Right Thing after that. No, it will not. As I wrote before it needs all path components but last to exist, otherwise it will do "cd /" first and this will be the wrong root. > The port seems to install fine on my systems; it doesn't spam any existing > files or directories, so I'm not sure why you think linux_base-7 has a > problem. I never said that this port has a problem, all I said is that "mkdir -p" with mkdir from this port doesn't properly work *because of the discussed linux emulation "feature"*. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?417CEC04.3060705>