Messages in this thread | | | From | Daniel Phillips <> | Subject | Re: initramfs buffer spec -- second draft | Date | Tue, 15 Jan 2002 16:15:20 +0100 |
| |
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/
| |