All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS-mounted, read-only /dev unusable in 2.6
Date: Wed, 04 Aug 2004 08:34:40 +0200	[thread overview]
Message-ID: <41108380.6080809@bio.ifi.lmu.de> (raw)
In-Reply-To: <ceouv0$7s8$2@news.cistron.nl>

Miquel van Smoorenburg wrote:

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

Which matches the fact the it works with server running 2.6 and
client running 2.4.

> 
> On all other filesystems (ext2, ext3, xfs etc) there's no problem
> opening devices r/w on a read-only filesystem.

Should I report that as bug to someone special?

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


  reply	other threads:[~2004-08-04  6:34 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
2004-08-04  6:34     ` Frank Steiner [this message]
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=41108380.6080809@bio.ifi.lmu.de \
    --to=fsteiner-mail@bio.ifi.lmu.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquels@cistron.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.