On Wed December 14 2011, Vasanth Ragavendran wrote: > > > > > > > > Which looks exactly as expected from the previous condition > > you listed before the move. > > > > What do you want different about it? > >
I think I have stumbled onto a similar situation that does not involve auFS nor either of the *_root calls. Just setting up a directory with files for a chroot, mount /proc and then changing to that file system namespace with a "chroot /x/y/z" Then you can find some very strange things (with the 3.0.4 kernel): cat /proc/self/mounts (or the older cat /proc/mounts) shows the paths properly trimmed for the second view of proc: That is, it shows: /proc not: /x/y/z/proc __BUT__ is does not edit out those mount paths no longer accessible! That is, you can find mount paths listed that are outside of the /x/y/z path. Of course, any operations on them (since /x/y/z doesn't exist inside the chroot) return errors. Another interesting note: There will be a visible (and working) /dev inside of the chroot. I am not sure if this is a "feature" or an "error" - in the 2.6.x series kernels, you had to mount it to have it inside. When I have a chance, I will see if the same happens with the 3.1.y and 3.2.x series of kernels. Mike ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev
