public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: L A Walsh <lkml@tlinx.org>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS-mounted, read-only /dev unusable in 2.6
Date: Tue, 03 Aug 2004 10:28:26 -0700	[thread overview]
Message-ID: <410FCB3A.9000401@tlinx.org> (raw)
In-Reply-To: <410FA44F.1020804@bio.ifi.lmu.de>

Maybe I'm missing something, but in the 2.6 series, wasn't the ability
to mount subdirectories with different options, also, added?  Would
it be possible to export and mount /dev with rw options to a specific
client?

Or, more radical, if the roots of the clients end up being mounted RW
eventually anyway, why not specify 'rw' in the lilo option?  It's not
like it is a local filesystem that may be corrupt where one should
boot from it RO until it is checked...

But I've never tried either approach, so it's really only an 
idea/possibility.

Hope something works....the booting with a local initrd seems like it
would be a pain...

good luck,
Linda

Frank Steiner wrote:

> Dick Streefland 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.
>
>
> I'm hoping for an easier solution, because it's a lot of work just
> to get the console messages onto the screen. But maybe I have to go
> through this :-)
>
>
>

  reply	other threads:[~2004-08-03 17:28 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 [this message]
2004-08-04  6:27       ` Frank Steiner
2004-08-03 21:09   ` Miquel van Smoorenburg
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=410FCB3A.9000401@tlinx.org \
    --to=lkml@tlinx.org \
    --cc=fsteiner-mail@bio.ifi.lmu.de \
    --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