From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: 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: Mon, 29 Mar 2004 21:54:35 +0200 [thread overview]
Message-ID: <20040329195435.GA19426@apps.cwi.nl> (raw)
In-Reply-To: <1080587480.2410.61.camel@lade.trondhjem.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1039 bytes --]
On Mon, Mar 29, 2004 at 02:11:20PM -0500, Trond Myklebust wrote:
> På må , 29/03/2004 klokka 14:00, skreiv Andries.Brouwer@cwi.nl:
> > People complain about the kernel messages when mounting NFS.
> > (Just like last time a new NFS version was introduced.)
> > It is perfectly normal to have mount newer than the kernel,
> > or the kernel newer than mount. No messages are needed or useful.
>
> I disagree...
>
> We should fix the printk to be KERN_NOTIFY so that you can filter them,
> but otherwise there is *no way* to know whether or not you have support
> for the features you are attempting to use.
> People might get somewhat confused if they try to enable strong
> security, and the kernel happily mounts the partition with AUTH_SYS, and
> does nothing to warn them...
The features that are being used are used by layers of software.
If there is information to be passed, it should be passed to
that software, not printed in a syslog.
It is not the kernel's job to set policy and have an opinion about user mode setup.
Andries
next prev parent reply other threads:[~2004-03-29 19:54 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 [this message]
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
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=20040329195435.GA19426@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