mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: 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: Sun, 15 Jun 2003 20:14:24 +0200	[thread overview]
Message-ID: <20030615181424.GJ1063@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20030615190349.A21931@infradead.org>

On Sun, 15 June 2003 19:03:49 +0100, Christoph Hellwig wrote:
> On Sun, Jun 15, 2003 at 07:58:15PM +0200, Jörn Engel wrote:
> > Ok, you win this one.  Leaves this case:
> > $ mount /dev/somewhere /mnt
> > cramfs: wrong magic
> > $ echo $?
> > 0
> > $
> 
> Umm, please explain.  You got a sucessfull mount of a non-cramfs
> filesystem type but an error from cramfs?  What version of mount
> do you use?

Actually, that is what I expect to get tomorrow, when I have access to
hardware and can verify it.

> It's not a debug printk.  Please leave the messages in, it's really
> helpful to see what failed when mount doesn't succeed.

Yes, I agree.  It is any the "Cramfs didn't find it's magic number,
now we'll try another filesystem instead. Usually this should be
harmless and you can safely ignore this message." that bothers me,
because the current wording sounds more like "Something terrible has
happened, go and find someone to bug with this."

What do you propose instead?

Jörn

-- 
Everything should be made as simple as possible, but not simpler.
-- Albert Einstein

  reply	other threads:[~2003-06-15 18:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-15 16:05 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 [this message]
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
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=20030615181424.GJ1063@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=brian@mdrx.com \
    --cc=hahn@physics.mcmaster.ca \
    --cc=hch@infradead.org \
    --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

all inboxes | Powered by JetHome®