From owner-freebsd-isp Tue Dec 3 11:01:00 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA05608 for isp-outgoing; Tue, 3 Dec 1996 11:01:00 -0800 (PST) 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 LAA05599 for ; Tue, 3 Dec 1996 11:00:57 -0800 (PST) Received: from swoosh.dunn.org (swoosh.dunn.org [206.158.7.243]) by ns2.harborcom.net (8.8.3/8.8.3) with SMTP id OAA03896 for ; Tue, 3 Dec 1996 14:00:56 -0500 (EST) Date: Tue, 3 Dec 1996 13:56:44 -0500 () From: Bradley Dunn To: freebsd-isp@freebsd.org Subject: Ugh...long usernames Message-ID: X-X-Sender: bradley@harborcom.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. We have a BSD/OS box that we are going to be switching over to FreeBSD. There are about 100 logins on the BSD/OS box that are over 8 characters in length. After thinking this over, I have decided that getting all of those people to change their login names would be a tech. support nightmare. So that is not an option. The long names must stay. (Yes I know about sendmail aliases; no that is not an option because having the login name different from the email address is also a support nightmare.) >From discussions held on this matter in the past, my understanding is that UT_NAMESIZE in and MAXLOGNAME in are the numbers to change. So I change both of those numbers to 16, make the world, and hope everything works. Any caveats? I know this breaks NIS interoperability, but NIS between FreeBSD boxes will still work, correct? Thanks. -BD