[OpenAFS-devel] Re: [OpenAFS] 2.6 kernel support anytime soon? Workarounds?

[Neulinger, Nathan]

I think Jeff's numbers were a bit too wide... I believe that if you
reserve over >=3D32512 you should be fine.

i.e. 7F00 - BF00 would be the range you want to avoid...=20

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-6679
UMR Information Technology             Fax: (573) 341-4216
=20

> -----Original Message-----
> From: openafs-devel-admin@openafs.org=20
> [mailto:openafs-devel-admin@openafs.org] On Behalf Of Garrett Wollman
> Sent: Tuesday, May 11, 2004 1:13 PM
> To: Jeffrey Hutzelman
> Cc: openafs-devel@openafs.org; noahm@csail.mit.edu
> Subject: Re: [OpenAFS-devel] Re: [OpenAFS] 2.6 kernel support=20
> anytime soon? Workarounds?
>=20
> <<On Tue, 11 May 2004 14:01:37 -0400, Jeffrey Hutzelman=20
> <jhutz@cmu.edu> said:
>=20
> > It had better not be.  As administrator of a machine, the=20
> GID space is=20
> > entirely under your control.  If you're going to run an AFS=20
> client, you=20
> > currently need to reserve GID's in the range 0x3F00-0xFEFF=20
> for AFS.  That=20
> > still leaves 16K groups for non-AFS uses, which is far more=20
> than most=20
> > systems will ever need.
>=20
> This could bite us very hard.  Our users are set up with primary gid
> =3D=3D uid, and the shared UID space runs from 5000 to 32000.
>=20
> -GAWollman
>=20
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20
>=20