From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: dev.d/ -- was Udev question PROGRAM= question
Date: Tue, 15 Mar 2005 23:41:00 +0000 [thread overview]
Message-ID: <1110930060.605.64.camel@localhost.localdomain> (raw)
In-Reply-To: <423770C7.90108@jg555.com>
On Tue, 2005-03-15 at 15:33 -0800, Jim Gifford wrote:
> Kay Sievers wrote:
>
> >This does not fit into the udev model. We can only support devices that
> >have a sane sysfs kernel representation.
> >You may call MAKEDEV it with a dev.d/ script triggered for the fd*
> >device.
> >
> >Kay
> >
> >
> >
> Ok, so I have my script modified. How do I setup dev.d/ to handle this.
> Do I need to create a directory block, and place the .dev file into this
> directory or what do I need to do?
Your script in "block" needs to exit if isn't a floppy, that should
work. I hope to be able to add the udev-rule based dev.d execution soon,
then it would be easy to match against a specific device or specific
device class.
Fedora does it that way:
/etc/dev.d/
...
|-- fd0
| `-- 10-MAKEDEV.dev -> ../../udev/scripts/MAKEDEV.dev
|-- fd1
| `-- 10-MAKEDEV.dev -> ../../udev/scripts/MAKEDEV.dev
|-- fd2
| `-- 10-MAKEDEV.dev -> ../../udev/scripts/MAKEDEV.dev
|-- fd3
| `-- 10-MAKEDEV.dev -> ../../udev/scripts/MAKEDEV.dev
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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
prev parent reply other threads:[~2005-03-15 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 23:33 dev.d/ -- was Udev question PROGRAM= question Jim Gifford
2005-03-15 23:41 ` Kay Sievers [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=1110930060.605.64.camel@localhost.localdomain \
--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).