Date: Wed, 15 Aug 2007 20:06:40 +0200 From: Ivan Voras <ivoras@fer.hr> To: freebsd-current@freebsd.org Subject: Re: SEC:ULarger NGROUPS_MAX in CURRENT ? Ready for 7.0-R ? Message-ID: <f9vfbj$lq4$1@sea.gmane.org> In-Reply-To: <alpine.BSF.0.999.0708151039340.98070@qbhto.arg> References: <20070812114017.GA93036@obelix.dsto.defence.gov.au> <20070815104929.GJ11649@obelix.dsto.defence.gov.au> <f9vc51$9vi$1@sea.gmane.org> <alpine.BSF.0.999.0708151039340.98070@qbhto.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE90AE4910C89F6F45982AB2E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Doug Barton wrote: > On Wed, 15 Aug 2007, Ivan Voras wrote: >=20 >> Wilkinson, Alex wrote: >>> Anyone ? rwatson@ ? >> >> AFAIK the only problem with this is that NFS will fail with larger >> number of groups, so (for those not using NFS) why not make the number= >> of groups an item in kernel configurations and make a compile-time and= >> module-load-time checks for this in the NFS code? >=20 > Sure, we look forward to reviewing your patches. So all this time it was just a matter of someone doing it? No other architectural problems? --------------enigE90AE4910C89F6F45982AB2E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGw0CwldnAQVacBcgRAmf9AJ45LPBryZ/0wB8W79upp1syWi37zwCgi9ZF 9LgQ9/nVnC4ijRfNbTLi6wA= =1uqi -----END PGP SIGNATURE----- --------------enigE90AE4910C89F6F45982AB2E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f9vfbj$lq4$1>