Alan McKinnon <[EMAIL PROTECTED]> writes: > It's more than that. It's the portage *BUILD*DIRECTORY* (which just > happens to be short-lived, not temp), that's where all your merges are > built. Just like you don't want to give just anyone the ability to > overwrite your binaries in /bin, you also don't want to give just > anyone the ability to overwrite the same binaries while they are being > built.
But I think giving group and others proper read and execute access is safe enough. Like everybody can read things under /bin. > You can start by investigating the various sandbox and userpriv FEATURES > in make.conf (info in the portage man pages), I doubt they could solve the issue.. ,----[ ls -l . | grep work ] | drwx------ 3 portage portage 80 Sep 3 10:43 work `---- ,----[ ls work -l ] | drwxr-xr-x 21 root root 1432 Sep 3 10:50 emacs-unicode `---- The problematic part is `work' directory. It better give normal users rx access. > or set up your sudoers to allow you to run commands as portage (I > imagine you don't want to debug as root as permission bugs won't show > up) No, I don't want to run sudo here. -- William -- [EMAIL PROTECTED] mailing list
