From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Andries Brouwer <Andries.Brouwer@cwi.nl>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] silence nfs mount messages
Date: Tue, 30 Mar 2004 03:33:02 +0200 [thread overview]
Message-ID: <20040330013300.GC17179@apps.cwi.nl> (raw)
In-Reply-To: <1080606053.2410.260.camel@lade.trondhjem.org>
On Mon, Mar 29, 2004 at 07:20:53PM -0500, Trond Myklebust wrote:
> The changes you are complaining about have *NOTHING* whatsoever to do
Wait. It seems you think I am complaining about changes. I am not.
I am complaining about kernel messages.
They have been there since 0.99. Hardly changes, but they are annoying.
Mount has to go through all kinds of contortions to avoid these messages.
Has an explicit list of kernel versions built-in.
Yecch.
These messages should have been silenced ten years ago.
People complain.
> > Mount tries the latest version it knows about, when that fails
> > goes back to an earlier version until either the mount succeeds
> > or we give up. The same binary must work over a large range of
> > kernel versions.
>
> That will break functionality for the user, and sounds like a bug in
> "mount". See my objection w.r.t. the user who thinks he is getting
> secure authentication via RPCSEC_GSS.
If the user installs some distribution, like RedHat or SuSE,
then hopefully the distribution authors know what they are doing.
If the user invents his own system, hopefully he knows what he
is doing. A few random messages hardly improve matters here.
That is what I meant when I mentioned "policy".
And again - if the user asks for "mount -t nfs" she gets an
nfs mount. If you say that she might wish some particular kind
of nfs mount instead of just any, then she should have said so -
by adding some mount option, or by using a different filesystem type.
Andries
next prev parent reply other threads:[~2004-03-30 1:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 19:00 [patch] silence nfs mount messages Andries.Brouwer
2004-03-29 19:11 ` Trond Myklebust
2004-03-29 19:54 ` Andries Brouwer
2004-03-29 23:24 ` Trond Myklebust
2004-03-29 23:46 ` Andries Brouwer
2004-03-30 0:20 ` Trond Myklebust
2004-03-30 1:33 ` Andries Brouwer [this message]
2004-03-30 1:56 ` Trond Myklebust
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=20040330013300.GC17179@apps.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=trond.myklebust@fys.uio.no \
/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