@@ -200,7 +202,7 @@
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
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
@@ -138,9 +140,9 @@
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