From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: initramfs buffer spec -- second draft
Date: Sun, 13 Jan 2002 12:11:57 -0800 [thread overview]
Message-ID: <3C41EA0D.2050205@zytor.com> (raw)
In-Reply-To: <a1oqmm$is3$1@cesium.transmeta.com> <m1ofjyqb7t.fsf@frodo.biederman.org>
Eric W. Biederman wrote:
>
> Comments. Endian issues are not specified, is the data little, big
> or vax endian?
>
Not applicable. There are no endian-specific binary structure in the
format AT ALL. ASCII-coded fields are always bigendian.
> What is the point of alignment? If the data starts as 4 byte aligned,
> the 6 byte magic string guarantees the data will be only 2 byte
> aligned. This isn't good for 32 or 64 bit architectures.
They're ASCII-coded, so it supposedly doesn't matter (yet, it's a bit
daft, but blame the SysV people.) The alignment makes sure the *data*
field is 4-byte aligned.
> I do like having a c_magic that at least allows us to change things
> in the future if necessary.
It's pretty clear from a lot of the comments that a number of people
haven't understood that the cpio encapsulation *THIS IS A CODIFICATION
OF AN EXISTING FORMAT.*
-hpa
next prev parent reply other threads:[~2002-01-13 20:12 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 [this message]
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
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=3C41EA0D.2050205@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.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