From: "H. Peter Anvin" <hpa@zytor.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: initramfs buffer spec -- second draft
Date: Sun, 13 Jan 2002 12:08:37 -0800 [thread overview]
Message-ID: <3C41E945.9040700@zytor.com> (raw)
In-Reply-To: <a1oqmm$is3$1@cesium.transmeta.com> <E16PqXQ-0000BD-00@starship.berlin>
Daniel Phillips wrote:
>
>>The structure of the cpio_header is as follows (all 8-byte entries
>>contain 32-bit hexadecimal ASCII numbers):
>
> I thought there's a binary version of the cpio header. What is the
> point of the ascii encoding?
>
Byte order independence. The binary version of cpio is ancient and
obsolete. Unfortunately the SysV people didn't have the htons() etc
macros of BSD, so they had no concept of portable binary formats.
>>The c_mode field matches the contents of st_mode returned by stat(2)
>>on Linux, and encodes the file type and file permissions.
>>
>>The c_filesize should be zero for any non-regular file.
>>
>>If the filename is "TRAILER!!!" this is actually an end-of-file
>>marker; the c_filesize for an end-of-file marker must be zero.
>>
> It sure looks ugly, but I suppose the c_filesize=zero is the real
> end-of-file marker. Did I mention it sure looks ugly?
>
c_filesize == 0 does *NOT* imply a end-of-archive marker. It is the
filename "TRAILER!!!" that does. And yes, it's ugly.
-hpa
next prev parent reply other threads:[~2002-01-13 20:09 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 [this message]
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-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:54 ` initramfs buffer spec -- second draft 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=3C41E945.9040700@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
/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