All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Alexander Viro <viro@math.psu.edu>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org
Subject: Re: initramfs buffer spec -- second draft
Date: Tue, 15 Jan 2002 12:03:13 -0800	[thread overview]
Message-ID: <3C448B01.6030003@zytor.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0201131536480.27390-100000@weyl.math.psu.edu> <E16QXbx-0000wa-00@starship.berlin>

Daniel Phillips wrote:

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


Because we want to use existing tools.  It's a wart, but not compelling 
enough of one to rewrite the tools from scratch.  (I would also change 
the EOA marker from "TRAILER!!!" to "" since a null filename would not 
interfere with the namespace.)

I don't think think this application alone is enough to add Yet Another 
Version of CPIO.  However, if there are more compelling reasons to do so 
  for CPIO backup reasons itself I guess we could write it up and add it 
to GNU cpio as "linux" format...

	-hpa



  reply	other threads:[~2002-01-15 20:03 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-12  8:04 initramfs buffer spec -- second draft H. Peter Anvin
2002-01-13 19:43 ` Daniel Phillips
2002-01-13 20:08   ` H. Peter Anvin
2002-01-13 19:53 ` Eric W. Biederman
2002-01-13 20:11   ` H. Peter Anvin
2002-01-13 20:58     ` Eric W. Biederman
2002-01-13 21:59       ` Alexander Viro
2002-01-13 22:35         ` Eric W. Biederman
2002-01-14 18:31       ` Kai Henningsen
2002-01-15  0:26         ` H. Peter Anvin
2002-01-13 20:39   ` Alexander Viro
2002-01-15  6:34     ` Daniel Phillips
2002-01-16 19:19       ` [offtopic] duplicate mails (was: initramfs buffer spec -- second draft) Daniel Phillips
2002-01-15  6:34     ` initramfs buffer spec -- second draft Daniel Phillips
2002-01-15  6:54     ` Daniel Phillips
2002-01-16 20:40       ` Bill Davidsen
2002-01-15 15:15     ` Daniel Phillips
2002-01-15 20:03       ` H. Peter Anvin [this message]
2002-01-15 20:16         ` Daniel Phillips
2002-01-15 20:14           ` H. Peter Anvin
2002-01-15 23:01             ` Daniel Phillips
2002-01-15 23:47               ` H. Peter Anvin
2002-01-15 21:04           ` Andreas Dilger
2002-01-15 23:09             ` Daniel Phillips
2002-01-15 23:48               ` H. Peter Anvin
2002-01-15 23:59               ` Andreas Dilger
2002-01-16  0:29                 ` H. Peter Anvin
2002-01-16  3:33                 ` H. Peter Anvin
2002-01-16  3:25           ` Alexander Viro
2002-01-16  2:43   ` Aaron Lehmann
     [not found] <200201120804.AAA19339@cesium.transmeta.com>
2002-01-13  2:00 ` Alexander Viro
2002-01-13  2:17   ` H. Peter Anvin
2002-01-13  4:11     ` Alexander Viro
2002-01-13 19:55   ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C448B01.6030003@zytor.com \
    --to=hpa@zytor.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    --cc=viro@math.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.