From: "Robert White" <rwhite@casabyte.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"Christoph Hellwig" <hch@infradead.org>,
linux-kernel@vger.kernel.org, "Brian Jackson" <brian@mdrx.com>,
"Mark Hahn" <hahn@physics.mcmaster.ca>
Subject: RE: [PATCH] make cramfs look less hostile
Date: Tue, 17 Jun 2003 17:24:52 -0700 [thread overview]
Message-ID: <PEEPIDHAKMCGHDBJLHKGMECMDAAA.rwhite@casabyte.com> (raw)
In-Reply-To: <20030615181424.GJ1063@wohnheim.fh-wedel.de>
The "cut to the quick" version is that the message should be changed to
something both useful and non threatening. Something to make the message
stand out as informational.
how about:
"cramfs: info: device is not a cramfs filesystem: wrong magic"
Then add a note to the docs that says: this message means the system was
trying to see if this was a cramfs. In the absence of a later message
saying something like "could not mount device" this message is harmless.
There is then the "no-duh" factor to at least club people over the head with
for not doing their research.
This, of course, would make more sense if every filesystem mount attempt had
a similar message as well as a "thingyfs: file system mounted" too. Of
course that would be ugly.
Since that isn't going to happen, stick to the simple human engineering
solution and make the message scream "info" duck the terseness... 8-)
Rob.
next prev parent reply other threads:[~2003-06-18 0:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 16:05 [PATCH] make cramfs look less hostile Jörn Engel
[not found] ` <Pine.LNX.4.44.0306151245070.29663-100000@coffee.psychology.mcmaster.ca>
2003-06-15 17:17 ` Jörn Engel
[not found] ` <200306151157.10493.brian@mdrx.com>
2003-06-15 17:19 ` Jörn Engel
2003-06-15 17:26 ` Christoph Hellwig
2003-06-15 17:39 ` Jörn Engel
2003-06-15 17:44 ` Christoph Hellwig
2003-06-15 17:58 ` Jörn Engel
2003-06-15 18:03 ` Christoph Hellwig
2003-06-15 18:14 ` Jörn Engel
2003-06-15 18:18 ` Christoph Hellwig
2003-06-15 21:49 ` Andries Brouwer
2003-06-16 9:12 ` Jörn Engel
2003-06-16 11:21 ` Andries Brouwer
2003-06-16 11:37 ` Jörn Engel
2003-06-18 0:24 ` Robert White [this message]
2003-06-15 17:27 ` Jörn Engel
2003-06-16 5:54 ` H. Peter Anvin
[not found] <20030615161009$6dde@gated-at.bofh.it>
[not found] ` <20030615174004$76d0@gated-at.bofh.it>
[not found] ` <20030615175007$7f59@gated-at.bofh.it>
[not found] ` <20030615175012$0573@gated-at.bofh.it>
[not found] ` <20030615181004$3663@gated-at.bofh.it>
[not found] ` <20030615181010$7f10@gated-at.bofh.it>
[not found] ` <20030615182013$7a4e@gated-at.bofh.it>
[not found] ` <20030615183011$3fc0@gated-at.bofh.it>
2003-06-15 21:20 ` Pascal Schmidt
2003-06-16 5:37 ` Christoph Hellwig
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=PEEPIDHAKMCGHDBJLHKGMECMDAAA.rwhite@casabyte.com \
--to=rwhite@casabyte.com \
--cc=brian@mdrx.com \
--cc=hahn@physics.mcmaster.ca \
--cc=hch@infradead.org \
--cc=joern@wohnheim.fh-wedel.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;
as well as URLs for NNTP newsgroup(s).