All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Joy Almacen <joy@empexis.com>
Cc: 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 19:07:50 +0000	[thread overview]
Message-ID: <20011213190750.A4460@redhat.com> (raw)
In-Reply-To: <3C165586.457A26F0@empexis.com>
In-Reply-To: <3C165586.457A26F0@empexis.com>; from joy@empexis.com on Tue, Dec 11, 2001 at 01:50:46PM -0500

Hi,

On Tue, Dec 11, 2001 at 01:50:46PM -0500, Joy Almacen wrote:

> After which I added this line  my  /etc/lilo.conf file:
> 
> image=/boot/vmlinuz-2.4.9-12smp
>         label=2.4.9smp
>         append="initrd=/boot/initrd-2.4.9-12smp.img root=/dev/ram0
> init=/linuxrc rw"

That's your problem.  You need to specify your real root device in the
"root=" section; for example, mine looks like

image=/boot/vmlinuz-2.4.9-13
	label=linux
	initrd=/boot/initrd-2.4.9-13.img
	read-only
	root=/dev/md1

The initrd magic happens before the real root gets loaded: you don't
need to point root to /dev/ram0 to get a ramdisk.

Cheers, 
 Stephen

  parent reply	other threads:[~2001-12-13 19:08 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
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 [this message]
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=20011213190750.A4460@redhat.com \
    --to=sct@redhat.com \
    --cc=joy@empexis.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.