mpb wrote: > 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. > Yes, that sounds good. Would there be problems involving the program being compiled as root? > 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. > Well, the reasons for having ChrootCompile seem to me to apply just as much to a single user as an admin. For the sake of simplicity, I think it's best to have a single tool to compile, whether you're a user or admin. >> ... 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. > Yes, that looks like it would work a treat. However, I think the problems I have with this are:
* It is not that easy to learn or remember. * It could take some time to type in. * Tweaking environment variables can be confusing, especially to a new / desktop user. It seems to me that it's more of a backend system, and not used too much for general tasks. * What do you do when you want to switch versions in the same session? I may well be mistaken, but I don't think there's an easy way to remove something from the PATH, is there? * It uses the binary path directly, whereas GoboLinux seems to be promoting the notion of the Program as a whole, which is a good idea in my opinion. If possible, the average user shouldn't need to know too much about the inside of a Program (meaning program directory) in order to add it to the path. Thanks for your reply, Paul
_______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
