From: Nuno Silva <nuno.silva@vgertech.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Greg KH <greg@kroah.com>,
linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 013 release
Date: Wed, 14 Jan 2004 19:23:11 +0000 [thread overview]
Message-ID: <4005971F.4020608@vgertech.com> (raw)
In-Reply-To: <40058086.5000106@nortelnetworks.com>
Hi Chris!
Hi Greg!
Chris Friesen wrote:
> Greg KH wrote:
>
>> Yeah, but what exactly would udev print out? All of the sysfs files in
>> the device it found? Would it print it out for every device that comes
>> through? Or just for ones that no rule applied to?
>
>
>
> Maybe for ones with a matching rule, you could print something like:
>
> udev[1234]: new device found matching rule <blah>, creating device node
> <nodename>
>
> For ones that don't match any rules, you could dump out all the info:
>
> udev[1234]: new device found with no matching rules, device info: blah blah
>
This would be nice but I think that full info for every new hotplugged
device is even better. It's only 1 line :-)
Lame people, like myself, will make this rule:
BUS="scsi", SYSFS_model="CD-Writer cd4f*", KERNEL="sr*", NAME="cdrw"
When I connect a second drive (same model) /udev/cdrw will be
overwritten. So I'd want to check the logs, find some difference between
the two and create a new entry "myfriends-cdrw".
(I know that NAME="cdrw%n" would work but that depends on the order you
plug things).
Regards,
Nuno Silva
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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
WARNING: multiple messages have this Message-ID (diff)
From: Nuno Silva <nuno.silva@vgertech.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Greg KH <greg@kroah.com>,
linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 013 release
Date: Wed, 14 Jan 2004 19:23:11 +0000 [thread overview]
Message-ID: <4005971F.4020608@vgertech.com> (raw)
In-Reply-To: <40058086.5000106@nortelnetworks.com>
Hi Chris!
Hi Greg!
Chris Friesen wrote:
> Greg KH wrote:
>
>> Yeah, but what exactly would udev print out? All of the sysfs files in
>> the device it found? Would it print it out for every device that comes
>> through? Or just for ones that no rule applied to?
>
>
>
> Maybe for ones with a matching rule, you could print something like:
>
> udev[1234]: new device found matching rule <blah>, creating device node
> <nodename>
>
> For ones that don't match any rules, you could dump out all the info:
>
> udev[1234]: new device found with no matching rules, device info: blah blah
>
This would be nice but I think that full info for every new hotplugged
device is even better. It's only 1 line :-)
Lame people, like myself, will make this rule:
BUS="scsi", SYSFS_model="CD-Writer cd4f*", KERNEL="sr*", NAME="cdrw"
When I connect a second drive (same model) /udev/cdrw will be
overwritten. So I'd want to check the logs, find some difference between
the two and create a new entry "myfriends-cdrw".
(I know that NAME="cdrw%n" would work but that depends on the order you
plug things).
Regards,
Nuno Silva
next prev parent reply other threads:[~2004-01-14 19:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 23:52 [ANNOUNCE] udev 013 release Greg KH
2004-01-13 23:52 ` 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:15 ` Greg KH
2004-01-14 17:46 ` Chris Friesen
2004-01-14 17:46 ` Chris Friesen
2004-01-14 19:23 ` Nuno Silva [this message]
2004-01-14 19:23 ` Nuno Silva
2004-01-14 21:14 ` Greg KH
2004-01-14 21:14 ` Greg KH
2004-01-15 7:48 ` Nuno Silva
2004-01-15 23:03 ` Greg KH
2004-01-15 23:03 ` Greg KH
2004-01-14 20:34 ` Clay Haapala
2004-01-14 20:34 ` Clay Haapala
2004-01-14 20:47 ` Chris Friesen
2004-01-14 20:47 ` Chris Friesen
2004-01-14 21:12 ` Greg KH
2004-01-14 21:12 ` Greg KH
2004-01-14 21:10 ` 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
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=4005971F.4020608@vgertech.com \
--to=nuno.silva@vgertech.com \
--cc=cfriesen@nortelnetworks.com \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.