From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 013 release
Date: Fri, 16 Jan 2004 03:24:51 +0000 [thread overview]
Message-ID: <20040116032451.GA17090@vrfy.org> (raw)
In-Reply-To: <20040113235213.GA7659@kroah.com>
On Fri, Jan 16, 2004 at 02:25:08AM +0000, Nuno Silva wrote:
> Greg KH wrote:
> >
> >Hm, I just took Kay's patch instead. Care to make up a patch for this
> >based off of it?
> >
>
> You did the right thing :-) Now it's simplier and is almost a one-liner.
> (Anyway, still missing the SYSFS_* details).
>
> Sample output:
> Jan 16 01:53:42 puma udev[18505]: New device! Metrics: BUS='scsi',
> ID='71:0:0:0', KERNEL='sr0'
> Jan 16 01:53:42 puma udev[18505]: name, 'sr0' is going to have owner='',
> group='', mode = 0600
> Jan 16 01:53:42 puma udev[18505]: creating device node '/udev/sr0'
>
> I think this output is nice, easy to read and /etc/udev/rules oriented
> so, sooner or later, people will find it "natural".
>
> + info("New device! Metrics: BUS='%s', ID='%s', KERNEL='%s'",
> + sysfs_device->bus, sysfs_device->bus_id, class_dev->name);
Huh, what if sysfs_device = NULL ?
And why print it, if we apply a configured rule to a known device?
Kay
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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:[~2004-01-16 3:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 23:52 [ANNOUNCE] udev 013 release Greg KH
2004-01-14 1:38 ` Frédéric L. W. Meunier
2004-01-14 2:14 ` Jon Smirl
2004-01-14 5:15 ` Nuno Silva
2004-01-14 17:15 ` Greg KH
2004-01-14 17:46 ` Chris Friesen
2004-01-14 19:23 ` Nuno Silva
2004-01-14 21:14 ` Greg KH
2004-01-15 7:48 ` Nuno Silva
2004-01-15 23:03 ` Greg KH
2004-01-14 20:34 ` Clay Haapala
2004-01-14 20:47 ` Chris Friesen
2004-01-14 21:12 ` Greg KH
2004-01-14 21:10 ` Greg KH
2004-01-14 17:27 ` Greg KH
2004-01-15 4:14 ` Kay Sievers
2004-01-15 14:32 ` Kay Sievers
2004-01-15 22:40 ` Greg KH
2004-01-16 2:25 ` Nuno Silva
2004-01-16 3:24 ` Kay Sievers [this message]
2004-01-16 3:45 ` Nuno Silva
2004-01-19 20:29 ` Olaf Hering
2004-01-19 20:40 ` Greg KH
2004-01-19 20:44 ` Olaf Hering
2004-01-19 20:50 ` Greg KH
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=20040116032451.GA17090@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).