Re: chroot(2) and bind mounts as non-root

[John Stoffel]

>>>>> "Colin" == Colin Walters <walters@xxxxxxxxxx> writes:

Colin> I've recently been doing some work in software compilation, and it'd be
Colin> really handy if I could call chroot(2) as a non-root user.  The reason
Colin> to chroot is to help avoid "host contamination" - I can set up a build
Colin> root and then chroot in.  The reason to do it as non-root is, well,
Colin> requiring root to build software sucks for multiple obvious reasons.

What's wrong with using 'fakeroot' or tools like that instead?  Why
does the Kernel need to be involved like this?  I'm not against your
proposal so much, as trying to understand how compiling a bunch of
source requires this change.

John
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/