From: Christian Laursen <xi@borderworlds.dk>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Problems with iso9660 as initrd
Date: 07 Feb 2002 23:30:24 +0100 [thread overview]
Message-ID: <m3d6zglybj.fsf@borg.borderworlds.dk> (raw)
In-Reply-To: <Pine.LNX.4.30.0202071316501.21862-100000@outback.escape.de>
In-Reply-To: <Pine.LNX.4.30.0202071316501.21862-100000@outback.escape.de>
Matthias Kilian <kili@outback.escape.de> writes:
> On 6 Feb 2002, H. Peter Anvin wrote:
>
> > > I am building a floppy using a compressed iso9660 filesystem as an
> > > initrd image.
> [...]
> > You definitely are... I don't think anyone else has ever tried running
> > a zisofs off a ramdisk before!
>
> On for an initrd, it will never work, since initrd checks for minix, ext2
> and romfs only (see drivers/block/rd.c, identify_ramdisk_image()).
It seems you are right. To be more precise it will not work on a ramdisk at
all.
A normal ramdisk will just fail to mount when there's an iso9660 fs on it,
whereas an initrd seems to cause a panic.
I guess it would be nice to output a somewhat friendly error message instead.
Oh well...
After further research I decided to use romfs instead, since it can too be
generated quite easily with a script, and it works quite well.
--
Best regards
Christian Laursen
next prev parent reply other threads:[~2002-02-07 22:32 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 [this message]
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
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=m3d6zglybj.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.