public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Laursen <xi@borderworlds.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: Problems with iso9660 as initrd
Date: 07 Feb 2002 11:01:33 +0100	[thread overview]
Message-ID: <m3g04dy5j6.fsf@borg.borderworlds.dk> (raw)
In-Reply-To: <m3r8ny8by5.fsf@borg.borderworlds.dk> <a3sei4$h5p$1@cesium.transmeta.com> <m3n0yl90xb.fsf@borg.borderworlds.dk> <a3te3d$7f2$1@cesium.transmeta.com>
In-Reply-To: <a3te3d$7f2$1@cesium.transmeta.com>

"H. Peter Anvin" <hpa@zytor.com> writes:

> Followup to:  <m3n0yl90xb.fsf@borg.borderworlds.dk>
> By author:    Christian Laursen <xi@borderworlds.dk>
> In newsgroup: linux.dev.kernel
> > > 
> > > Also, you don't have CONFIG_ZISOFS set...
> > 
> > Sorry for not being precise enough. It is not a zisofs, just compressed
> > with gzip as usual for an initrd image.
> > 
> 
> Still unusual, though.  Why iso9660?  It's not particularly well
> suited for an initrd, especially because of all the redundant data
> structures and extra blocking.

Mostly because it is easily scriptable to build it with tools usually
available.

-- 
Best regards
    Christian Laursen

      parent reply	other threads:[~2002-02-07 10:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-06 22:47 Problems with iso9660 as initrd Christian Laursen
2002-02-06 23:33 ` H. Peter Anvin
2002-02-07 12:20   ` Matthias Kilian
2002-02-07 22:30     ` Christian Laursen
2002-02-06 23:34 ` H. Peter Anvin
2002-02-07  8:00   ` Christian Laursen
2002-02-07  8:32     ` H. Peter Anvin
2002-02-07  9:01       ` Pozsar Balazs
2002-02-07 10:01       ` Christian Laursen [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=m3g04dy5j6.fsf@borg.borderworlds.dk \
    --to=xi@borderworlds.dk \
    --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