[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091105150250.GL6510@mit.edu>
Date: Thu, 5 Nov 2009 10:02:50 -0500
From: Theodore Tso <tytso@....edu>
To: Alexey Fisher <bug-track@...her-privat.net>
Cc: Greg Freemyer <greg.freemyer@...il.com>, linux-ext4@...r.kernel.org
Subject: Re: one way to dmesg
On Wed, Nov 04, 2009 at 04:59:14PM +0100, Alexey Fisher wrote:
>
> Great, look really nice :)
> but this is not all what i mean.
> For example fs specific messages: EXT4-fs blabla, if you look to source
> you'll see "EXT3 FS" "EXT II FS" (fat is worse), if you need to grep it
> will be nightmare. It seems like ext4 is mostly up to date, ext2/3 need
> some work. Are there any work on this?
What problem are you trying to solve?
Is it just an aesthetics thing? Is there a specific scenario where
you need some kind of extra functionality? If so, what is it?
There's some question about whether parsing dmesg is the best way to
get information about error/event reporting. See the following
presentation from this year's Plumber's conference for a set of
ruminations on this issue:
http://linuxplumbersconf.org/2009/slides/Andi-Kleen-plumbers-error.pdf
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists