From owner-freebsd-arch@FreeBSD.ORG  Mon Apr 28 07:13:48 2003
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2CCB837B401; Mon, 28 Apr 2003 07:13:48 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2F4F643F75; Mon, 28 Apr 2003 07:13:47 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h3SEDj46099401;
	Mon, 28 Apr 2003 16:13:45 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: "Jacques A. Vidrine" <nectar@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Mon, 28 Apr 2003 07:06:38 CDT."
             <20030428120638.GA3289@madman.celabo.org> 
Date: Mon, 28 Apr 2003 16:13:45 +0200
Message-ID: <99400.1051539225@critter.freebsd.dk>
cc: arch@freebsd.org
Subject: Re: endianess of /etc/pwd.db 
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2003 14:13:48 -0000

In message <20030428120638.GA3289@madman.celabo.org>, "Jacques A. Vidrine" writ
es:
>On Wed, Apr 09, 2003 at 07:26:20AM -0500, Jacques A. Vidrine wrote:
>> On Wed, Apr 09, 2003 at 10:17:41AM +0200, Poul-Henning Kamp wrote:
>> > 
>> > Kris ran into this problem:  copying a /etc/pwd.db from one endianess
>> > to another gave him really weird uid/gid numbers.
>> > 
>> > The DB code itself is endianess-agnostic, so the first warning one
>> > gets is the weird UID/GID.
>> > 
>> > Should we make the endianess of this file explicit to prevent this
>> > pit-fall for our users ?  The cost would be less than epsilon.
>
>In case you didn't otherwise notice, this is done.

I could be a bit worried about doubling the size of the file, but for a
transistion period it does make sense.

Great work!

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.