public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: L A Walsh <lkml@tlinx.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS-mounted, read-only /dev unusable in 2.6
Date: Wed, 04 Aug 2004 08:27:09 +0200	[thread overview]
Message-ID: <411081BD.6030706@bio.ifi.lmu.de> (raw)
In-Reply-To: <410FCB3A.9000401@tlinx.org>

L A Walsh wrote:
> 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?

Yes, that's an option. But all this needs to be done in the init script,
since with nfsroot I only get /. So mounting /dev rw from the server is
similar to figuring out which client-specific /dev should be mounted.
But in this init process things can fail and I want to see those messages.
If I fail to mount the server /dev rw for any reason, I won't see the
error message :-(

> 
> 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...

No, the real / is exported ro from the server and stays mounted ro on
the clients. Only the client specific /dev, /var and /etc are mounted
rw...

cu,
Frank

-- 
Dipl.-Inform. Frank Steiner   Web:  http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik    Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17           Phone: +49 89 2180-4049
80333 Muenchen, Germany       Fax:   +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

  reply	other threads:[~2004-08-04  6:27 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 [this message]
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=411081BD.6030706@bio.ifi.lmu.de \
    --to=fsteiner-mail@bio.ifi.lmu.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@tlinx.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