norman.walsh.name: Comments on /2003/08/22/chroothttp://norman.walsh.name/2003/08/22/chroot/comments.atom2012-02-13T06:31:59.392894ZComment 1 on /2003/08/22/chroothttp://norman.walsh.name/2010/09/25/oauth#comment00012003-08-23T01:50:59Z2003-08-23T01:50:59ZDominic Mitchellda39a3ee5e6b4b0d3255bfef95601890afd80709

Damn, that's a neat solution. I like it. However, I reckon that you could have got away without mounting /tmp, and perhaps using the X's network transparency by connecting to localhost:0.0 instead of just :0.0. With a modern tcp stack the overhead shouldn't be much more than a Unix domain socket.

Anyway, nice work.

-Dom

Comment 2 on /2003/08/22/chroothttp://norman.walsh.name/2010/09/25/oauth#comment00022004-12-11T01:56:33Z2004-12-11T01:56:33ZC. Scott Ananianda39a3ee5e6b4b0d3255bfef95601890afd80709

Rock on! That --bind option is just what I was looking for. The --move option to mount looks pretty interesting, too --- a few months ago I was looking for a way to atomically update an entire webserver root in order to do atomic software upgrades, and that might just do it (create upgrade in new temp dir, mount --move it over the existing root, upgrade the (hidden) existing root, umount the temp dir).