From: Vivek Dasgupta <vivek_dasgupta@email.com>
To: linux-kernel@vger.kernel.org
Cc: carlson@sibyte.com
Subject: RE: Ramdisk root filesystem strangeness
Date: Thu, 7 Dec 2000 16:50:03 -0500 (EST) [thread overview]
Message-ID: <380814282.976225806017.JavaMail.root@web176-ec> (raw)
Hi
I m sorry if this question doesn't belong to this list. But I couldn't
access the linux-admin list.
Is there support for using RAMDISK as the final root file system
in 2.2.x versions, or is it there in the 2.4.x versions.
I am trying to bring up linux on a diskless server which initially mounts
root FS thru NFS. Then I want to load HDD image to a RAMDISK and use it as
the final root filesystem.
I am not sure whether it is a ready supported or any kernel change will be
required for this?
Any pointers would be helpful.
thanks
vivek
-----Original Message-----
From: Justin Carlson [mailto:carlson@sibyte.com]
Sent: Thursday, December 07, 2000 11:52 AM
To: linux-kernel@vger.kernel.org
Subject: Ramdisk root filesystem strangeness
Am in the midst of bringing up the kernel on a new MIPS variant, and I'm
tryingthe mount a statically linked ramdisk as the root filesystem.
Note, this is NOT using initrd support, I really want to use a ramdisk as my
final filesystem, not as an intermediate step in booting the system.
In blkdev_get(), called from mount_root(), there's some code that grabs
an empty inode, sets up i_rdev, and calls open() for the root device
with the caveat that open() must not examine anything except i_rdev.
in rd_open, though, there's this code snippet:
/*
* Immunize device against invalidate_buffers() and prune_icache().
*/
if (rd_inode[DEVICE_NR(inode->i_rdev)] == NULL) {
if (!inode->i_bdev)
return -ENXIO;
I'm hitting the -ENXIO return, which is based on an uninitialized field of
the
inode structure.
Being relatively new to the code base, I'm not sure what this code is trying
to
do, nor how to fix it. Any suggestions?
The code involved is from the MIPS CVS repository at oss.sgi.com, which was
synced in the past couple days from 2.4.0test11
-Justin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
-----------------------------------------------
FREE! The World's Best Email Address @email.com
Reserve your name now at http://www.email.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-07 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 21:50 Vivek Dasgupta [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-08 1:12 Ramdisk root filesystem strangeness Jeff Chua
2000-12-07 19:51 Justin Carlson
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=380814282.976225806017.JavaMail.root@web176-ec \
--to=vivek_dasgupta@email.com \
--cc=carlson@sibyte.com \
--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