From: Theodore Tso <tytso@mit.edu>
To: Alexey Fisher <bug-track@fisher-privat.net>
Cc: Greg Freemyer <greg.freemyer@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: one way to dmesg
Date: Thu, 5 Nov 2009 10:02:50 -0500 [thread overview]
Message-ID: <20091105150250.GL6510@mit.edu> (raw)
In-Reply-To: <1257350354.2091.9.camel@mini>
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
next prev parent reply other threads:[~2009-11-05 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 14:26 one way to dmesg Alexey Fisher
2009-11-04 15:18 ` Greg Freemyer
2009-11-04 15:29 ` Alexey Fisher
2009-11-04 15:46 ` Greg Freemyer
2009-11-04 15:59 ` Alexey Fisher
2009-11-05 15:02 ` Theodore Tso [this message]
2009-11-05 15:51 ` Alexey Fisher
2009-11-04 15:19 ` Alexey Fisher
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=20091105150250.GL6510@mit.edu \
--to=tytso@mit.edu \
--cc=bug-track@fisher-privat.net \
--cc=greg.freemyer@gmail.com \
--cc=linux-ext4@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