From owner-freebsd-current Fri Apr 11 17:45:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA04603 for current-outgoing; Fri, 11 Apr 1997 17:45:35 -0700 (PDT) Received: from mercury.uniserve.com (mercury.uniserve.com [204.191.197.248]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04595; Fri, 11 Apr 1997 17:45:31 -0700 (PDT) Received: from haven.uniserve.com (shell.uniserve.com [198.53.215.121]) by mercury.uniserve.com (8.8.2/8.8.2) with SMTP id RAA06896; Fri, 11 Apr 1997 17:38:57 -0700 (PDT) Date: Fri, 11 Apr 1997 17:49:56 -0700 (PDT) From: Tom Samplonius To: David Langford cc: bradley@dunn.org, freebsd-isp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: longer usernames In-Reply-To: <199704120022.OAA01332@caliban.dihelix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Apr 1997, David Langford wrote: > Whoops, no the confusion was whether or not FreeBSD to FreeBSD NIS would > work with long user names. > > In the past discusions it had usually been mentioned that NIS and long > user names would cause problems but it was never clear if this was > also the cause in homogenious environments. Misinformation being passed around by the misinformed. NIS is concerned with key-data pairs, the lengths of those pairs is imposed only by the underlying database (and a couple of other things). Even the SunOS 4.1 implementation of NIS has no problems with longer-usernames, its just that login truncates all user-ids to 8 characters before doing lookups (I guess, it is hard to verify without looking at the code). I did some real brief testing on this. Solaris 2.x has 16 character username support, and it definitely works with NIS. > :) > > -David Langford > langfod@dihelix.com > Tom