From owner-freebsd-hackers  Sat Jun 22 04:59:21 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id EAA22017
          for hackers-outgoing; Sat, 22 Jun 1996 04:59:21 -0700 (PDT)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA22010
          for <hackers@FreeBSD.ORG>; Sat, 22 Jun 1996 04:59:19 -0700 (PDT)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id UAA21976; Sat, 22 Jun 1996 20:59:05 +0900 (JST)
Date: Sat, 22 Jun 1996 20:59:05 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: Bradley Dunn <dunn@harborcom.net>
cc: hackers@FreeBSD.ORG
Subject: Re: Longer usernames?
In-Reply-To: <199606220832.EAA27010@ns2.harborcom.net>
Message-ID: <Pine.SV4.3.93.960622205215.21923B-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 22 Jun 1996, Bradley Dunn wrote:

> On 20 Jun 96 at 20:00, Tom Samplonius wrote:
> 
> > > > > What do they do about NIS?  Truncate the usernames? Bad bad
> > > > > bad.
> > > > 
> > > >   BSDI 2.1 doesn't have NIS.
> > > 
> Especially for a company that markets its product as an "Internet 
> Server". If you are going to base the major selling point of your 
> product on its networking functionality, NIS seems to me to be almost 
> a requirement.

If you're a Sun shop.

I rather use rdist than NIS.  There is a need for something better than
either solution though.  LDAP/RFC1777?

-mh