public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Andreas Steinmetz <ast@domdv.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.4.16pre1: minix initrd does not work, ext2 does
Date: Wed, 28 Nov 2001 15:41:51 -0200	[thread overview]
Message-ID: <01112815415100.00898@manta> (raw)
In-Reply-To: <XFMail.20011127151356.ast@domdv.de> <01112812184503.00924@manta>
In-Reply-To: <01112812184503.00924@manta>

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

  reply	other threads:[~2001-11-28 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-27 17:49 [BUG] 2.4.16pre1: minix initrd does not work, ext2 does vda
2001-11-27 14:13 ` Andreas Steinmetz
2001-11-28 14:18   ` vda
2001-11-28 17:41     ` vda [this message]
2001-11-30 12:21       ` vda

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=01112815415100.00898@manta \
    --to=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=ast@domdv.de \
    --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