public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Alexander Viro <viro@math.psu.edu>
Cc: Joy Almacen <joy@empexis.com>,
	wa@almesberger.net, linux-kernel@vger.kernel.org,
	"Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: pivot_root and initrd kernel panic woes
Date: Thu, 13 Dec 2001 11:22:20 -0200	[thread overview]
Message-ID: <01121311222003.01849@manta> (raw)
In-Reply-To: <Pine.GSO.4.21.0112130319160.19281-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0112130319160.19281-100000@weyl.math.psu.edu>

On Thursday 13 December 2001 06:19, Alexander Viro wrote:
> On Thu, 13 Dec 2001, vda wrote:
> > BTW, don't go for 2.4x, x>10. initrd is broken there and is still
> > unfixed.
>
> Bullshit.

I have a slackware initrd (minix) which is booting fine with 2.4.10
but fails to boot with 2.4.12 and later (same .config, same bootloader,
same hardware, same AC voltage in the wall outlet, time of day differs by
1 minute), so it might be true :-)

I have a report of romfs initrd with same symptoms. ext2 initrds OTOH
boots fine.
--
vda

  reply	other threads:[~2001-12-13  9:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11 18:50 pivot_root and initrd kernel panic woes Joy Almacen
2001-12-11 21:00 ` Marcel J.E. Mol
2001-12-13 10:09 ` vda
2001-12-13  8:19   ` Alexander Viro
2001-12-13 13:22     ` vda [this message]
2001-12-13 14:53       ` vda
2001-12-15 12:14       ` Mike Galbraith
2001-12-15 16:51         ` vda
2001-12-15 17:59           ` Mike Galbraith
2001-12-16  2:32             ` vda
2001-12-16  9:02               ` Mike Galbraith
2001-12-15 16:55         ` vda
2001-12-15 18:03           ` Mike Galbraith
2001-12-13 19:07 ` Stephen C. Tweedie
2001-12-13 18:35   ` Joy Almacen
  -- strict thread matches above, loose matches on Subject: below --
2001-12-17 18:38 Torrey Hoffman
2001-12-17 18:44 ` Alexander Viro
2001-12-17 19:02 ` Erik Andersen

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=01121311222003.01849@manta \
    --to=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=joy@empexis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=viro@math.psu.edu \
    --cc=wa@almesberger.net \
    /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