From: "Martin Bogomolni" <martinb@www.igotu.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.6.2, initrd, /dev/ram
Date: Tue, 10 Feb 2004 20:45:36 -0500 [thread overview]
Message-ID: <20040211013227.M48358@www.igotu.com> (raw)
I have a mini-distribution that runs from CD-ROM using H Peter Anvin's
ISOLINUX/SYSLINUX boot loader. While upgrading it to kernel 2.6, I have
come across a behavioral difference between 2.4 and 2.6 that may impact
other users of the 2.6 kernel.
With kernel 2.4, to boot an initial ramdisk, I would use the following
arguments appended to the kernel :
linux24 ramdisk_size=32000 root=/dev/ram rw
----
With kernel 2.6, the same arguments result in an error message. Neither
devfs nor udev are enabled, the distribution relies on pre-created /dev
entries in the ramdisk.
However, the kernel will boot but -not- enter the ramdisk if root=/dev/ram.
The entry has to be changed to root=/dev/ram0 in order for a successful boot.
Why has this change of behavior occured?
Martin B.
next reply other threads:[~2004-02-11 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 1:45 Martin Bogomolni [this message]
[not found] <1nS8U-6lv-13@gated-at.bofh.it>
2004-02-11 18:02 ` Kernel 2.6.2, initrd, /dev/ram der.eremit
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=20040211013227.M48358@www.igotu.com \
--to=martinb@www.igotu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martinb@igotu.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