From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Smirl Date: Tue, 30 Dec 2003 01:48:51 +0000 Subject: Re: implementing hotplug event Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org --- Greg KH wrote: > > Now my userspace app needs to open the newly loaded device driver, how > > do I reliably find it? I know that it is at /dev/dri/cardX but what if > > the user is replacing /dev with /udev or /devfs? I know the > > major/minor I could just mknode in my program too. > > To be safe, you can always just read the sysfs "dev" file, and do a > mknod with that information. Otherwise you could query udev as to what > it has named your device, but we don't have those hooks in udev just > yet... someday soon... I just sent the major/minor to the hotplug event in the environment variables, it seemed easier than sending out the slot id and finding "dev" in sysfs. Doing mknod from the user space app seems to be the most reliable scheme. ==Jon Smirl jonsmirl@yahoo.com __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&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