From: Norbert Kiesel <nkiesel@tbdnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: RE: initramfs buffer spec -- third draft
Date: 13 Jan 2002 13:42:26 -0800 [thread overview]
Message-ID: <1010958148.8691.0.camel@voyager> (raw)
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
H. Peter Anvin wrote:
> initramfs buffer format
> -----------------------
>
> Al Viro, H. Peter Anvin
> Last revision: 2002-01-13
>
> ** DRAFT ** DRAFT ** DRAFT ** DRAFT ** DRAFT ** DRAFT **
.....
>The full format of the initramfs buffer is defined by the following
>grammar, where:
> * is used to indicate "0 or more occurrences of"
> (|) indicates alternatives
> + indicates concatenation
> GZIP() indicates the gzip(1) of the operand
> ALGN(n) means padding with null bytes to an n-byte boundary
>
> initramfs := ("\0" | cpio_archive | cpio_gzip_archive)*
>
> cpio_gzip_archive := GZIP(cpio_archive)
>
> cpio_archive := cpio_file* + (<nothing> | cpio_trailer)
>
> cpio_file := ALGN(4) + cpio_header + filename + "\0" + ALGN(4) +
data
>
> cpio_trailer := ALGN(4) + cpio_header + "TRAILER!!!\0" + ALGN(4)
what's the purpose of the "*" behind cpio_file in the cpio_archive
definition? There is already repetition in the initramfs and the "*"
behind cpio_archive would e.g. allow a sequence of cpio_trailers
without any cpio_file inbetween.
--nk
--
Key fingerprint = 6C58 F18D 4747 3295 F2DB 15C1 3882 4302 F8B4 C11C
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-01-13 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-13 21:42 Norbert Kiesel [this message]
2002-01-13 22:37 ` initramfs buffer spec -- third draft H. Peter Anvin
2002-01-14 17:15 ` Andreas Dilger
2002-01-14 17:52 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2002-01-13 20:46 H. Peter Anvin
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=1010958148.8691.0.camel@voyager \
--to=nkiesel@tbdnetworks.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