On Tue, 03 Oct 2006 00:09:11 -0400 Alec Warner <[EMAIL PROTECTED]> wrote:
> Mike Kelly wrote: > > Summarized, the format is: > > > > For each profile dir (e.g. profiles/base, profiles/default-linux, > > etc), a new subdirectory, called accounts is created as necessary. > > Inside that is a file called defaults, containing default uid/gid > > ranges, shells, etc for the given profile. Also, there are two > > directories, user/ and group/, which contain files named after the > > users and groups to be added. Those files contain more specific > > uid/gid info, etc. > > I hope to god they cascade like everything else ? > > All the files are handled like other files in cascading profiles. Yes, they do. Sorry, I guess I didn't word that clearly enough. > Also I don't see why we would have this in the profiles as opposed to > somewhere in /etc/? Because, first of all, this data must exist before a package is installed (so, it can't be part of the package itself). It shouldn't just be in some creandus-data package because all this is closely linked with the tree, and should be maintained by the individual package maintainers. Also, some specifics of the settings for users and groups are somewhat profile-specific (see below). > Have people expressed an interest in per-profile mangling of uid/gid ? That isn't as important as, say, properly setting the default shell on a per-profile basis. I mainly see stuff being set in the base, hardened, and default-* profiles, not in say the default-linux/x86/2006.1/server/ profile specifically. Only time I can see wanting to mangle uid/gid per profile is if this gets adopted for managing even the system users currently provided in the default /etc/passwd and /etc/group files, where some variance has to happen for each USERLAND. For example, there isn't a root group on FreeBSD, just a wheel group. -- Mike Kelly -- [email protected] mailing list
