Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 16 Jan 2002 13:43:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 16 Jan 2002 13:43:17 -0500 Received: from [66.89.142.2] ([66.89.142.2]:47678 "EHLO starship.berlin") by vger.kernel.org with ESMTP id ; Wed, 16 Jan 2002 13:43:05 -0500 Content-Type: text/plain; charset=US-ASCII From: Daniel Phillips To: Alexander Viro , "Eric W. Biederman" Subject: Re: initramfs buffer spec -- second draft Date: Tue, 15 Jan 2002 07:34:44 +0100 X-Mailer: KMail [version 1.3.2] Cc: "H. Peter Anvin" , linux-kernel@vger.kernel.org In-Reply-To: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: 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" 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. Is there a problem with the available tools, are they not capable of generating the binary version of the headers? -- 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/