From owner-freebsd-current Sat Dec 7 05:24:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA25855 for current-outgoing; Sat, 7 Dec 1996 05:24:12 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA25841 for ; Sat, 7 Dec 1996 05:24:06 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA08208 for ; Sat, 7 Dec 1996 14:24:04 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA13934 for freebsd-current@FreeBSD.org; Sat, 7 Dec 1996 14:24:04 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id OAA18895 for freebsd-current@FreeBSD.org; Sat, 7 Dec 1996 14:07:57 +0100 (MET) From: J Wunsch Message-Id: <199612071307.OAA18895@uriah.heep.sax.de> Subject: Re: cvs commit: src/include utmp.h To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 7 Dec 1996 14:07:57 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612041130.DAA25553@freefall.freebsd.org> from "Jordan K. Hubbard" at "Dec 4, 96 03:30:18 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > Modified: include utmp.h > Log: > Bump maximum username length to 16 characters. This brings us into > line with BSD/OS and Linux's username limits, making transitioning from > either operating system a lot easier than it is now. I'm currently > running with this change on my system, as are several others, and have > experienced no ill effects. We should provide a small tool that allows to convert the wtmp file into the new format. This should IMHO be part of the 3.0 upgrade procedure. Note that old wtmp files are being gzipped by default, so the tool should handle this case. Breaking backward compatibility to ourselves is IMHO a Bad Thing. I volunteer to write that tool (i think it's not a big deal anyway), but where should it go to? Alternatively, we could teach last(1) to handle both cases, based on some heuristics. (Haven't tried, but i assume that's also possible.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)