From: ocomber <ocomber@cmedltd.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev & kernel names
Date: Thu, 28 Apr 2005 11:05:05 +0000 [thread overview]
Message-ID: <1114686305.8757.431.camel@localhost.localdomain> (raw)
In-Reply-To: <20050426231516.GD2740@us.ibm.com>
On Wed, 2005-04-27 at 09:05 -0700, Greg KH wrote:
<snip>
>
> > Is there a better way to go about getting these useful log messages?
>
> Modify your syslog program to do it.
>
Would it be possible to call udev's parser directly?
What I'm thinking is syslog Somehow (tm) knows it has a line with a
device name in it. It could then call udev's parser to execute the
appropriate rule, but instead of creating any devices, put udev's device
name on standard output. Syslog could then substitute this into place
on the log line.
I'm sure a well crafted regular expression could split out the kernel
device name to pass to the parser, and syslog then appends udev's idea
of the device name to the line. If the udev parser returns nothing, you
know your regex produced a red herring.
> Oh, and what about the fact that I can create 2 device nodes in the fs
> that really are the same kernel device?
>
> /me watches the ras developers get all agitated
>
> > If I need to clarify the problem/proposed solution further, please let
> > me know.
>
> Please let me know who is trying to drive such a misguided and
> ill-conceived issue and I will track them down...
>
> thanks,
>
> greg k-h
>
Thanks,
-Oli
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-04-28 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 23:15 udev & kernel names Nishanth Aravamudan
2005-04-27 16:05 ` Greg KH
2005-04-27 16:43 ` Daniel Stekloff
2005-04-27 16:53 ` Nishanth Aravamudan
2005-04-27 16:57 ` Greg KH
2005-04-27 17:24 ` Daniel Stekloff
2005-04-27 23:01 ` Martin Schwenke
2005-04-28 4:37 ` Greg KH
2005-04-28 11:05 ` ocomber [this message]
2005-04-28 11:21 ` Michael Buesch
2005-04-28 14:22 ` ocomber
2005-04-28 14:43 ` Kay Sievers
2005-04-28 23:15 ` Martin Schwenke
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=1114686305.8757.431.camel@localhost.localdomain \
--to=ocomber@cmedltd.com \
--cc=linux-hotplug@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).