* Re: dev.d/ -- was Udev question PROGRAM= question
@ 2005-03-15 23:33 Jim Gifford
2005-03-15 23:41 ` Kay Sievers
0 siblings, 1 reply; 2+ messages in thread
From: Jim Gifford @ 2005-03-15 23:33 UTC (permalink / raw)
To: linux-hotplug
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?
--
----
Jim Gifford
maillist@jg555.com
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: dev.d/ -- was Udev question PROGRAM= question
2005-03-15 23:33 dev.d/ -- was Udev question PROGRAM= question Jim Gifford
@ 2005-03-15 23:41 ` Kay Sievers
0 siblings, 0 replies; 2+ messages in thread
From: Kay Sievers @ 2005-03-15 23:41 UTC (permalink / raw)
To: linux-hotplug
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-03-15 23:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-15 23:33 dev.d/ -- was Udev question PROGRAM= question Jim Gifford
2005-03-15 23:41 ` Kay Sievers
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).