From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: NFS-mounted, read-only /dev unusable in 2.6
Date: Tue, 3 Aug 2004 21:09:52 +0000 (UTC) [thread overview]
Message-ID: <ceouv0$7s8$2@news.cistron.nl> (raw)
In-Reply-To: 64bf.410f9d6f.62af@altium.nl
In article <64bf.410f9d6f.62af@altium.nl>,
Dick Streefland <dick.streefland@altium.nl> wrote:
>Frank Steiner <fsteiner-mail@bio.ifi.lmu.de> wrote:
>| Or is there any other way to get an initial console or
>| output any messages from an init script if one boots via nfsroot
>| and / (and thus, /dev) is only exported read-only from the
>| server?
>
>You can boot with a ramdisk as root, initialized with an initrd, and
>then perform all NFS mounts manually in the init script. You can use
>pivot_root to switch to an NFS root to get rid of the ramdisk.
If having /dev mounted read-only means you cannot open devices
like /dev/console read/write then that is a bug in the NFS client
in the kernel.
On all other filesystems (ext2, ext3, xfs etc) there's no problem
opening devices r/w on a read-only filesystem.
Mike.
--
The question is, what is a "manamanap".
The question is, who cares ?
next prev parent reply other threads:[~2004-08-03 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 8:09 NFS-mounted, read-only /dev unusable in 2.6 Frank Steiner
2004-08-03 14:13 ` Dick Streefland
2004-08-03 14:42 ` Frank Steiner
2004-08-03 17:28 ` L A Walsh
2004-08-04 6:27 ` Frank Steiner
2004-08-03 21:09 ` Miquel van Smoorenburg [this message]
2004-08-04 6:34 ` Frank Steiner
2004-08-04 6:47 ` Miquel van Smoorenburg
2004-08-04 7:00 ` Frank Steiner
2004-08-04 7:05 ` Neil Brown
2004-08-04 10:35 ` Frank Steiner
2004-08-04 11:02 ` Neil Brown
2004-08-05 6:30 ` Frank Steiner
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='ceouv0$7s8$2@news.cistron.nl' \
--to=miquels@cistron.nl \
--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