public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Lingard <chris@ukpost.com>
To: "Jim Gifford" <maillist@jg555.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Initrd Question
Date: Fri, 13 Feb 2004 20:34:16 +0000	[thread overview]
Message-ID: <200402132034.16778.chris@ukpost.com> (raw)
In-Reply-To: <015501c3f1df$42cd7cf0$d300a8c0@W2RZ8L4S02>

On Friday 13 February 2004 3:12 am, Jim Gifford wrote:
> I wrote the initrd hint for the Linux from Scratch. I have followed the
> initrd.txt exactly to the letter. The problem I have noticed is with one of
> the commands, and I checked other mkinitrd scripts and they have the
> workaround in it.

With regards to the initrd.txt hint. (2.4.x kernels)

It does not work with the     "  root=/dev/rd/0   (with devfs) "
unless         { "rd/0",     0x0100 },   is added to the root_dev_names[] 
__initdata array; (init/do_mounts.c)

You need to use "root=/dev/ram0" with or without devfs. (or change 
init/do_mounts.c).  Patches to either code or documentation if you want.

Chris

  reply	other threads:[~2004-02-13 20:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13  3:12 Initrd Question Jim Gifford
2004-02-13 20:34 ` Chris Lingard [this message]
     [not found] <1oMkR-1Zk-21@gated-at.bofh.it>
2004-02-13 15:23 ` der.eremit
2004-02-13 16:42   ` Jim Gifford
2004-02-13 17:12   ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2004-02-13 14:14 "Andrey Borzenkov" 
2004-02-13 14:22 ` Valdis.Kletnieks
2004-02-18  2:05   ` Robert White
     [not found] <1oC26-8eW-9@gated-at.bofh.it>
2004-02-13 13:30 ` der.eremit
2001-06-18  7:20 initrd question Kelledin Tane

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=200402132034.16778.chris@ukpost.com \
    --to=chris@ukpost.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maillist@jg555.com \
    /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