linux-kernel - Re: Ordering hotplug scripts vs. udev device node creation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200610221949.29260.s0348365@sms.ed.ac.uk>
Date:	Sun, 22 Oct 2006 19:49:29 +0100
From:	Alistair John Strachan <s0348365@....ed.ac.uk>
To:	"Aaron Cohen" <aaron@...onance.org>
Cc:	"LKML List" <linux-kernel@...r.kernel.org>
Subject: Re: Ordering hotplug scripts vs. udev device node creation

On Saturday 21 October 2006 18:21, Aaron Cohen wrote:
> Hope this is a reasonable list to post this to.
>
> I'm trying to modify the gpsd hotplug script to work better with my
> udev setup.  My USB serial devices are added to /dev/tts/USBx by udev
> and the default script assumes they are /dev/ttyUSBx.
>
> In any event, my hotplug script uses udevinfo to figure out the device
> file to use.  The problem seems to be though that my hotplug script is
> getting run before udev has actually created the device node.  Is
> there some ordering mechanism I'm missing that would help me out here?

Some distros have gotten rid of hotplug altogether and now use udev entirely 
for handling plugging events (udevd). It seems like what you could do here 
was write a simple udev rule to symlink the device when it's created.

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/