On 7/28/07, Paul Dann <[EMAIL PROTECTED]> wrote: > That's great. I'd also really love it if it were possible to > ChrootCompile programs as an unprivileged user. Is there any reason that's > not possible, given that we're building in a fake root anyway?
The "chroot" system call fails when run as non-root. However, you could make an suid wrapper just for ChrootCompile. You would need root access to set the wrapper up, be thereafter non-root users could run ChrootCompile. Aside: I use Rootless a lot. I have never wanted to do a ChrootCompile in Rootless. So at least for me, the benefit would be minimal to nonexistent. > ... what do you think of the concept of having a separate > set of "mounted" programs for each program that is run? (That is, using the > current system as an analogy, each program has a different view of > /Programs.) That way, we could unclutter the PATH, which is a problem that > I still have with all Linux distros. We can then run, say, two versions of > GCC, just by opening two consoles, doing MountProgram for a different GCC in > each, then entering gcc as normal. The two will not conflict with each > other because they are in different namespaces, so to speak. Why not do the following instead: Either: "Compile -S GCC" (so that GCC does not get Symlinked into Programs) or: "DisableProgram GCC" (to remove the Symlinks post facto) Then simply: export PATH=$PATH:$goboPrefix/Programs/GCC/4.1.2/bin By changing PATH, you can choose which version of GCC will be used. Similar result without using chroot at all. -mpb _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
