From owner-freebsd-hackers  Sat Jun 22 01:33:05 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA13845
          for hackers-outgoing; Sat, 22 Jun 1996 01:33:05 -0700 (PDT)
Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA13838
          for <hackers@FreeBSD.ORG>; Sat, 22 Jun 1996 01:33:00 -0700 (PDT)
Received: from swoosh.dunn.org (swoosh.dunn.org [206.158.7.243]) by ns2.harborcom.net (8.7.4/8.6.12) with SMTP id EAA27010; Sat, 22 Jun 1996 04:32:47 -0400 (EDT)
Message-Id: <199606220832.EAA27010@ns2.harborcom.net>
Comments: Authenticated sender is <dunn@harborcom.net>
From: "Bradley Dunn" <dunn@harborcom.net>
Organization: Harbor Communications
To: Tom Samplonius <tom@sdf.com>
Date: Sat, 22 Jun 1996 04:28:31 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Longer usernames?
Reply-to: dunn@harborcom.net
CC: hackers@FreeBSD.ORG
Priority: normal
X-mailer: Pegasus Mail for Win32 (v2.31)
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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.
> > 
> > Ah.
> 
>   This is major oversight in my opinion.

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.

Bradley Dunn <dunn@harborcom.net>