>
>>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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/