[lkml]   [2002]   [Jan]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: initramfs buffer spec -- second draft
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


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:18    [W:0.132 / U:0.448 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site