Public SourceMage Discussion List

["Jeremy Blosser (emrys)" <jblosser-smgl AT firinn.org>]

On Aug 09, Treeve Jelbert [treeve AT scarlet.be] wrote:
> On Tuesday 09 August 2005 14:07, David Brown wrote:
> > My 2 Cents
> >
> > 1)
> > A standardized place for this would be nice, one of the sorcery bugs
> > involves documenting where functions 'should' go, so figuring this out
> > would be nice.
> 
> 
>  how about an optional line in DETAILS, to specify ACCOUNT and/or GROUP ,
> so that sorcery could do the work in a consistent manner?

While it makes sense to have a common idea of where these go, I doubt it
really needs to be codified in the API.  For most spells it's one or two
lines at most to add the accounts they need.

> > 2)
> > Hard Coding of the groups and user system accounts,
> > Finding this kinda thru me off and took me a bit to figure out.
> > I was wondering the historical reasons for using this hard coding and
> > also wondering how many other people have SA added groups/users that
> > conflict with the hard coded ones.
> > After a little messing with I found several on my systems:

There is a lot of advantage in keeping the same UID/GIDs between installs
and through upgrades or even moving a system from one distro to another
while keeping some files around.  In the long term this prevents conflicts
more than it causes them.  Ideally every user would have one UID that could
follow them forever but barring that, it's good practice to at least have
the system accounts be standard.  Most distros do this to keep it standard
between installs of their distro and even standard across distros.  It's
somewhat analogous to the role /etc/services plays.

Attachment: pgp4sndu7OmsM.pgp
Description: PGP signature