Re: Problems with iso9660 as initrd

From: Pozsar Balazs (pozsy@sch.bme.hu)
Date: Thu Feb 07 2002 - 04:01:05 EST

Next message: Andres Salomon: "D state processes in 2.4.18-pre7-ac3"
Previous message: Oleg Drokin: "Re: [reiserfs-dev] Kernel(>2.4.16) BUG with reiserfs."
In reply to: H. Peter Anvin: "Re: Problems with iso9660 as initrd"
Next in thread: Christian Laursen: "Re: Problems with iso9660 as initrd"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> 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.

But even if it was zisofs, the kernel shouldn't give oops, should it?

-- pozsy

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: Andres Salomon: "D state processes in 2.4.18-pre7-ac3"
Previous message: Oleg Drokin: "Re: [reiserfs-dev] Kernel(>2.4.16) BUG with reiserfs."
In reply to: H. Peter Anvin: "Re: Problems with iso9660 as initrd"
Next in thread: Christian Laursen: "Re: Problems with iso9660 as initrd"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Feb 07 2002 - 21:00:59 EST