Re: initramfs buffer spec -- third draft

[H. Peter Anvin]

Followup to:  <1010958148.8691.0.camel@voyager>
By author:    Norbert Kiesel <[e-mail]>
In newsgroup: linux.dev.kernel
>
> 
> --=-9GEMJ19dnS3OnVEuQ1tM
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
> 
> 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  :=3D ("\0" | cpio_archive | cpio_gzip_archive)*
> >
> >    cpio_gzip_archive :=3D GZIP(cpio_archive)
> >
> >    cpio_archive :=3D cpio_file* + (<nothing> | cpio_trailer)
> >
> >    cpio_file :=3D ALGN(4) + cpio_header + filename + "\0" + ALGN(4) +
> data
> >
> >    cpio_trailer :=3D 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.
> 

Allow GZIP(cpio_file* + cpio_trailer), which is in fact a very common
configuration.

	-hpa
-- 
<[e-mail]> at work, <[e-mail]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<[e-mail]>