--- xml/htdocs/proj/en/glep/glep-0027.html 2004/07/20 18:21:20 1.2 +++ xml/htdocs/proj/en/glep/glep-0027.html 2005/09/15 02:39:54 1.3 @@ -8,7 +8,7 @@ --> - + GLEP 27 -- Portage Management of UIDs/GIDs @@ -24,8 +24,7 @@ [GLEP Index] [GLEP Source] -
- +
@@ -43,7 +42,7 @@ - + @@ -113,23 +112,26 @@

Portage Structure

Defining Accounts

-

A new directory will need to be added to the rsync tree to store the -files that define the default values for new accounts.

+

New directories will need to be added to the rsync tree to store the files +that define the default values for new accounts. They will be stored on a +per-profile basis, that way sub-profiles may easily override parent profiles. +The default location will be the base profile since all other profiles inherit +from there.

-portage/profiles/accounts/
-    user/<username>.xml
-    group/<groupname>.xml
-    accounts.xml
+portage/profiles/base/accounts/
+    user/<username>
+    group/<groupname>
+    accounts
 

The files are named with the respective user/group name since they need to be unique in their respective domains. For example, the file -detailing the ntp user would be located accounts/user/ntp.xml. Each -username.xml file will detail the required information about each user. +detailing the ntp user would be located accounts/user/ntp. Each +username file will detail the required information about each user. Certain account features that exist on one class of systems (Linux) but -not on others (*BSD) can be tagged as such. Each groupname.xml will -follow similar guidelines. The accounts.xml will be used to describe -global account defaults such as the default range of 'valid system' ids. -For example, if the UID 123 is already used on a system, but the ntp +not on others (*BSD) can be redefined in their respective subprofiles. Each +groupname will follow similar guidelines. The accounts file will be used to +describe global account defaults such as the default range of 'valid system' +ids. For example, if the UID 123 is already used on a system, but the ntp user defaults to '123', we obviously cannot just duplicate it. So we would select the next available UID on the system based upon the range defined here.

@@ -138,9 +140,9 @@

Local Overrides

Following the tried and true style of custom local portage files being found in /etc/portage, this new system will follow the same. Users can -setup their own directory heirarchy in /etc/portage/accounts/ that mimics -the heirarchy found in the portage tree. When portage attempts to add a -new user, it will first check /etc/portage/accounts/user/<username>.xml. +setup their own directory heirarchy in /etc/portage/profile/accounts/ that +mimics the heirarchy found in the portage tree. When portage attempts to add +a new user, it will first check /etc/portage/profile/accounts/user/<username>. If it does not exist, it will simply use the default definition in the portage tree.

@@ -200,7 +202,7 @@

References

-
Type:Standards Track
Content-Type:text/x-rst
Content-Type:text/x-rst
Created:29 May 2004
+
@@ -211,13 +213,14 @@

Copyright

This document has been placed in the public domain.

- - +
[1]http://bugs.gentoo.org/show_bug.cgi?id=8634