From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: initramfs buffer spec -- second draft
Date: 14 Jan 2002 16:26:05 -0800 [thread overview]
Message-ID: <a1vsut$1qr$1@cesium.transmeta.com> (raw)
In-Reply-To: <3C41EA0D.2050205@zytor.com> <3C41EA0D.2050205@zytor.com> <m1elkuq87v.fsf@frodo.biederman.org> <8GpxaCDXw-B@khms.westfalen.de>
Followup to: <8GpxaCDXw-B@khms.westfalen.de>
By author: kaih@khms.westfalen.de (Kai Henningsen)
In newsgroup: linux.dev.kernel
>
> The latest existing formal spec is probably POSIX 2001 (look under "pax").
> An older POSIX version would have it under "cpio". You'll probably also
> find it there in Unix98 a.k.a. SuSv2. (POSIX 2001 (the Austin revision)
> supersedes all of those.)
>
> It's a bit long to post here - probably exceeds fair use.
>
POSIX only specifies the "old ASCII" cpio format anyway, which is so
limited as to be useless. POSIX specifies also specify "ustar" and
"pax", two extended tar formats, neither of which is suitable for this
application.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-01-15 0:26 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 [this message]
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
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='a1vsut$1qr$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox