From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Tue, 15 Mar 2005 23:41:00 +0000 Subject: Re: dev.d/ -- was Udev question PROGRAM= question Message-Id: <1110930060.605.64.camel@localhost.localdomain> List-Id: References: <423770C7.90108@jg555.com> In-Reply-To: <423770C7.90108@jg555.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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_id396&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