lkml.org 
[lkml]   [2001]   [Nov]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [BUG] 2.4.16pre1: minix initrd does not work, ext2 does
Date
On Wednesday 28 November 2001 12:18, vda wrote:
> ext2.gz contains gzipped ext2 ramdisk image.
> minix.gz contains gzipped minix ramdisk image.
> minix is gunzipped minix.gz.
>
> Initrd 2.4.10 2.4.13,2.4.16pre1
> --------------- ------- -----------------
> ext2.gz ok ok
> minix.gz ok minix fs not detected (bad fs magic)
> minix ok minix magic ok, can't open console, can't find init
>
> (2.4.16pre1 was instrumented to show minix magic etc)
>
> As you can see, we have decompression bug: results for
> compressed and uncompressed minix ramdisks are different.
> Or maybe kernel corrupts ramdisk image after gunzip.
> I'm puzzled...
>
> Guys, who fiddled with zlib/ramdisk/??? in 2.4.11 - 2.4.13 range?

I narrowed it down to 2.4.10 -> 2.4.12 (2.4.11-dontuse wasn't tested)
2.4.10 can boot my minix initrd, 2.4.12 can't.
--
vda
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:13    [W:0.053 / U:1.808 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site