[262] in athena10
Local gid conflicts
daemon@ATHENA.MIT.EDU (Quentin Smith)
Sun Jun 22 00:51:07 2008
Date: Sun, 22 Jun 2008 00:50:23 -0400 (EDT)
From: Quentin Smith <quentin@MIT.EDU>
To: athena10@mit.edu
In-Reply-To: <485DD3B6.5040903@mit.edu>
Message-ID: <Pine.LNX.4.64L.0806220045320.23917@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Sun, 22 Jun 2008, Kenneth Charles Arnold wrote:
>> These are because the 'mit' group has gid 101, which conflicts with local
>> groups (I guess libuuid got 101 on your system). On Linerva we manually
>> renumber the local group with gid 101 to some other number.
>
> # find / -mount -group libuuid
> /var/lib/libuuid
> /usr/sbin/uuidd
>
> So it would not be too invasive to do said manual renumbering. But definitely
> not a good long-term solution :)
Ken brings up a good point. The mit/101 conflict is going to continue hitting us
again and again. I have two suggestions:
- Install a config package early in the Athena 10 installer (before most base
system packages are installed) and have this package squat the low-numbered gids
that are currently allocated, so that local system packages do not claim those
gids. In addition, allocate the rest of the gids in Moira up to some reasonable
bound (500?) so that no new low-gid groups are created. (this may already be the
case, I'm not sure)
or
- Install a config package early in the Athena 10 installer that changes
groupadd/addgroup to allocate out of a special pool of gids higher in the gid
space that has been allocated in Moira for local accounts
I personally prefer the first solution. Unfortunately, neither of these will
help Debathena, as it's significantly harder to renumber existing groups on
users' machines.
--Quentin
