Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S290207AbSAORlT>; Tue, 15 Jan 2002 12:41:19 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S290205AbSAORlI>; Tue, 15 Jan 2002 12:41:08 -0500
Received: from [66.89.142.2] ([66.89.142.2]:26164 "EHLO starship.berlin")
	by vger.kernel.org with ESMTP id <S290119AbSAORks>;
	Tue, 15 Jan 2002 12:40:48 -0500
Content-Type: text/plain; charset=US-ASCII
From: Daniel Phillips <phillips@bonn-fries.net>
To: Alexander Viro <viro@math.psu.edu>,
        "Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: initramfs buffer spec -- second draft
Date: Tue, 15 Jan 2002 16:15:20 +0100
X-Mailer: KMail [version 1.3.2]
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
In-Reply-To: <Pine.GSO.4.21.0201131536480.27390-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0201131536480.27390-100000@weyl.math.psu.edu>
MIME-Version: 1.0
Content-Transfer-Encoding: 7BIT
Message-Id: <E16QXbx-0000wa-00@starship.berlin>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On January 13, 2002 09:39 pm, Alexander Viro wrote:
> On 13 Jan 2002, Eric W. Biederman wrote:
> > "H. Peter Anvin" <hpa@zytor.com> writes:
> > 
> > > This is an update to the initramfs buffer format spec I posted
> > > earlier.  The changes are as follows:
> > 
> > Comments.  Endian issues are not specified, is the data little, big
> > or vax endian?
> 
> Data is what you put into files, byte-by-byte.  Headers are ASCII.

Encoding the numeric fields in ASCII/hex is a goofy wart on an otherwise nice 
design.  What is the compelling reason?  Bytesex isn't it: we should just 
pick one or the other and stick with it as we do in Ext2.

Why don't we fix cpio to write a consistent bytesex?

--
Daniel

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/