xfs
[Top] [All Lists]

Re: TAKE - mount msgs

To: linux-xfs@xxxxxxxxxxx
Subject: Re: TAKE - mount msgs
From: Ethan Benson <erbenson@xxxxxxxxxx>
Date: Tue, 4 Sep 2001 05:31:17 -0800
In-reply-to: <4.3.2.7.2.20010904152044.035d3b48@xxxxxxxxxxxxx>; from knuffie@xxxxxxxxx on Tue, Sep 04, 2001 at 03:23:12PM +0200
Mail-copies-to: nobody
Mail-followup-to: linux-xfs@xxxxxxxxxxx
References: <20010904225323.A344731@xxxxxxxxxxxxxxxxxxxxxxxx> <200109041139.VAA08035@xxxxxxxxxxxxxxxxxxxxxxx> <20010904134437.A28205@xxxxxxxxxxxxxxxxxxx> <20010904225323.A344731@xxxxxxxxxxxxxxxxxxxxxxxx> <20010904043217.U14519@xxxxxxxxxxxxxxx> <4.3.2.7.2.20010904152044.035d3b48@xxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Tue, Sep 04, 2001 at 03:23:12PM +0200, Seth Mos wrote:
> >no news is good news.
> 
> I like having at least one message that it mounted a certain fs. I can then 
> use dmesg to see if it actually worked, and if it needs to recover or if it 
> fails I like to see it as well.

running mount will also tell you that it worked.  

as for recovery, i have always said leave the message mentioning that
recovery was needed, i want to know that.  but if no recovery was
needed, and nothing went wrong then nothing should be printed at all.
the lack of news is telling me everything was fine.  

just like rm does not say `Sucessfully unlinked file: /blah' for
everything it removes, it only prints something if there was a
problem, eg: permission denied, readonly filesystem, or whatever.

or in this case:

rm: Starting unlink of file: /blah
rm: Successfully unlinked file: /blah

> One line is enough. What I don't know is if you could stick these messages 

zero lines is enough on clean sucessful mounts ;-)

> on one line. So the first mounting message without a \n and the succes or 
> fail message after it.
> 
> Don't know if it lets us do that.

dunno maybe, but i still prefer not to see anything if all went well.

so again, a compile time option perhaps?

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

Attachment: pgpf5ruyUJuvR.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>