| 1 |
On 15/09/2015 22:09, james wrote: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> So looking at /etc/portage/repos.conf, it seems root.root owns these |
| 5 |
> files; shouldn't it be portage.portage? and /usr/portage |
| 6 |
> |
| 7 |
> That got me thinking. Everywhere that portage operates or owns |
| 8 |
> things, should the ownership not be portage.portage |
| 9 |
> and what would the typical permissions be? |
| 10 |
|
| 11 |
Here, all of /etc/portage is root:root |
| 12 |
The tree and all overlays are portage:portage |
| 13 |
|
| 14 |
You can make a local overlay owned by user you want, stuff you hack away |
| 15 |
at yourself should probably be james:james or james:users |
| 16 |
|
| 17 |
Typically, permissions in /etc/portage are the usual 755 for dirs and |
| 18 |
644 for files |
| 19 |
|
| 20 |
I set overlays and the tree to be 2775 for dirs and 664 for files |
| 21 |
|
| 22 |
> |
| 23 |
> Is there a master list I can look at? Surely root not own all |
| 24 |
> these dirs, like /usr/portage/* ? My /usr/portage is root.root |
| 25 |
> and 755 on permissions, is that right? |
| 26 |
|
| 27 |
Permissions should be what YOU need them to be on your computer. There's |
| 28 |
a default, it's what portage makes them when you install stuff |
| 29 |
|
| 30 |
> |
| 31 |
> If so, why? |
| 32 |
|
| 33 |
Only root should change the master config files in /etc, just like in |
| 34 |
all other apps |
| 35 |
IIRC emerge can drop privs to a user account, if that user is portage |
| 36 |
then portage must own the files |
| 37 |
|
| 38 |
|
| 39 |
> |
| 40 |
> In my /usr/local/portage and it's subdirs where I hack on many |
| 41 |
> ebuild, portage.portage owns everything.....? |
| 42 |
|
| 43 |
Make your life easy, chaown that stuff to james |
| 44 |
|
| 45 |
> Curious, and I cannot remember ever looking at this.... |
| 46 |
> |
| 47 |
> |
| 48 |
> James |
| 49 |
> |
| 50 |
> |
| 51 |
> |
| 52 |
> |
| 53 |
|
| 54 |
|
| 55 |
-- |
| 56 |
Alan McKinnon |
| 57 |
alan.mckinnon@×××××.com |
Archives