From owner-freebsd-arch@FreeBSD.ORG  Wed Apr  9 01:17:43 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 4854337B401
	for <arch@freebsd.org>; Wed,  9 Apr 2003 01:17:43 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5D0EC43FBD
	for <arch@freebsd.org>; Wed,  9 Apr 2003 01:17:42 -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 h398HfZq031399
	for <arch@freebsd.org>; Wed, 9 Apr 2003 10:17:41 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: arch@freebsd.org
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Wed, 09 Apr 2003 10:17:41 +0200
Message-ID: <31398.1049876261@critter.freebsd.dk>
Subject: 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: Wed, 09 Apr 2003 08:17:43 -0000


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.


-- 
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.