public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] initramfs
Date: 4 May 2002 15:04:12 -0700	[thread overview]
Message-ID: <ab1lss$2fi$1@cesium.transmeta.com> (raw)
In-Reply-To: <1744hw-0EYlYuC@fwd01.sul.t-online.com>

Followup to:  <1744hw-0EYlYuC@fwd01.sul.t-online.com>
By author:    "ChristianK."@t-online.de (Christian Koenig)
In newsgroup: linux.dev.kernel
> 
> I have tried to implement the "initramfs buffer spec -- third draft" by hpa 
> and Al Viro. 
> 
> It isn't complete yet, because off the following unresolved topics:
> 1. For the moment it only supports files,dirs and symlinks.
> 2. It still needs the "RAM disk" and "initrd" support compiled in the Kernel.
> 3. I haven't tried to support hardlinks.
> 4. Since i use the ramdisk for decompression the cpio image must be a 
> multiple of BLOCK_SIZE bytes.
> 5. The cpio crc field is ignored.
> 
> I have done this only for testing if the "initramfs buffer spec -- third 
> draft" suffers all requirements. And to give a starting point for 
> implementing this. The patch works for linux 2.5.9 - 2.5.13.
> 
> The only problem i found is that after a "TRAILER!!!" cpio (per default) 
> align on a 512 bytes boundary, not 4 bytes.

This is consistent with the spec.  It isn't *required* by the spec,
but a data generator is free to add arbitrary amounts of zero-padding.

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

      parent reply	other threads:[~2002-05-04 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04 19:57 [PATCH] initramfs Christian Koenig
2002-05-04 19:14 ` Alexander Viro
2002-05-04 22:05   ` H. Peter Anvin
2002-05-04 22:18     ` Alexander Viro
2002-05-06  6:34   ` Greg KH
2002-05-04 22:04 ` H. Peter Anvin [this message]

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='ab1lss$2fi$1@cesium.transmeta.com' \
    --to=hpa@zytor.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