linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arioch <the_Arioch@nm.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: +rule: query device inode by Major and Minor - am i inventing
Date: Thu, 18 Aug 2005 21:04:56 +0000	[thread overview]
Message-ID: <de2t50$7lq$1@sea.gmane.org> (raw)
In-Reply-To: <4300318B.8040505@nm.ru>

Greg KH пишет:

>>But what should tell character devices from, say, network interfaces ?
> Perhaps SUBSYSTEM=="net"?  :)

way to fragile rules.

SUBSYSTEM!="block", SUBSYSTEM!="net", ....

...and tomorrow this script would be run on another platform, that has 
subsystem i did not have. Or just new subsystem was invented. And the 
rule immediately fails.

Those matches, they do not tell character devices from subsystem, but 
they tell knon (to me) subsystems from the unknown rest (which i believe 
to be character devices and nothing else).

Guess i also can dp something like PROGRAM="/bin/file %P", 
Result=="*character*" but...
...then i again can stumble upon stderr
...and i cannot call another program

Oh, i guess i can determine something, then ENV{tmp_xxx}:='flag', then 
use it later. (i remember i heard that ENV can be LValue now)
Or again i can use scripts.

but that seems that rather simple task needs rather complex actions to 
implement :-)

>>Alas, i don't know where to et list of subsystems :-(
> 
> 'ls /sys/class/' is a good place to start (becides the block subsystem,
> which is still in /sys/block/ due to a whole bunch of kernel coding
> reasons...)
...assuming my kernel has all of them.
kernel docs sysfs.txt and kobject.txt  are written for oldschool 
  kernel hacker introducing him to new concepts. I wish to see someday 
SYSFS in 30 days for users ;)



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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

      parent reply	other threads:[~2005-08-18 21:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15  6:09 +rule: query device inode by Major and Minor - am i inventing brand Arioch
2005-08-15 13:40 ` +rule: query device inode by Major and Minor - am i inventing brand new bycicle ? Kay Sievers
2005-08-16 10:52 ` +rule: query device inode by Major and Minor - am i inventing Arioch
2005-08-16 17:13 ` Arioch
2005-08-16 18:18 ` Arioch
2005-08-16 18:29 ` +rule: query device inode by Major and Minor - am i inventing brand new bycicle ? Kay Sievers
2005-08-16 18:50 ` +rule: query device inode by Major and Minor - am i inventing Arioch
2005-08-16 21:28 ` +rule: query device inode by Major and Minor - am i inventing brand new bycicle ? Greg KH
2005-08-17  8:07 ` +rule: query device inode by Major and Minor - am i inventing Arioch
2005-08-18 17:59 ` +rule: query device inode by Major and Minor - am i inventing brand new bycicle ? Greg KH
2005-08-18 21:04 ` Arioch [this message]

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='de2t50$7lq$1@sea.gmane.org' \
    --to=the_arioch@nm.ru \
    --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).