>> Unless I'm misunderstanding this, it appears to be pointless since
>> only processes chroot'd to / or /proc could see the entries in the
>> proc file system anyway, as if they're chroot'd anywhere else,
>> they can't even access /proc ???
> It is possible to mount the proc file system onto a directory so
> that it is visible to chrooted processes. This can be useful,
> and should ideally be no more dangerous than allowing it to be
> visible to an unprivileged telnet account.
Are you referring to some means of mounting /proc so it appears
visible to ALL processes no matter where they're chroot'd to? If so,
I'd love to know how.
Sure, I know that the proc file system does not have to be mounted
over /proc (although it usually is), but I'd love to know how to mount
it so that it's visible to two processes that are respectively
chroot'd as follows:
1. /home/ftp (aka ~ftp)
2. /usr/mirrors (aka ~mirrors)
As you can see, there are no common subdirectories between those two
processes...
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/