From: rich@example.invalid   
      
   bad sector wrote:   
   >   
   > Jockeying for cross-distro commonality I created a new group TheseUsers   
   > on all my systems with a GID like 1950. Somehow in Slackware this GID   
   > ended up being 1400 and I don't remember how it became 1400. Before   
   > editing it to the same value as all others like 1950, is there anything   
   > in Slackware that would throw a fit if I do that?   
      
   Any files/directories created by that user while it was GID 1400 would   
   remain 1400 unless you do a 'find' looking for gid 1400 items and   
   updating their values.   
      
   Any files/directories that are only accessible because the user has GID   
   1400 would become inaccessible until you change the files/directories   
   to be GID 1950.   
      
   Beyond that, nothing much should care, as 1950 or 1400 are not groups   
   typically assigned to system functions.   
      
   > Rationale:   
   > I generally like to stay out of the system's way in order not to get   
   > stepped on, so rather than use the canned 'users' group with the fairly   
   > canned GID of 100, I use a new group with another GID and assign   
   > all my stuff to to UserMe and this group TheseUsers   
      
   If you are the only user of the system, your particular user's group   
   value holds little usefulness. The majority use of groups for an   
   otherwise single user system is assigning system groups to your user so   
   you can access those system items (i.e., the audio group to be able to   
   control the mixer settings, etc.).   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|