From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alexander E. Patrakov" Date: Tue, 06 Jul 2004 09:26:44 +0000 Subject: Re: udev /dev/net/tun bug Message-Id: <40EA7054.9020205@ums.usu.ru> List-Id: References: <40EA08F5.1070303@ums.usu.ru> In-Reply-To: <40EA08F5.1070303@ums.usu.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org Greg KH wrote: > On Tue, Jul 06, 2004 at 08:05:41AM +0600, Alexander E. Patrakov wrote: >=20 >>To reproduce: >> >>cd /etc/hotplug >>modprobe tun >>udevstart >> >>Result: >> >>The following synthetic "net" hotplug event is received: >=20 > No, it's a real event. Why do I re-receive that when I re-run udevstart? AFAIK just re-running=20 udevstart doesn't produce any real hotplug events. >>DEVPATH=3D/class/misc/tun >>UDEV_NO_SLEEP=3D1 >>ACTION=ADd >>PWD=3D/etc/hotplug >>DEVNAME=3D/dev/net/tun >>SHLVL=3D2 >>INTERFACE=3D/dev/net/tun >>_=3D/usr/bin/env >>=3D=3D=3D=3D=3D=3D=3D >> >>This event is bogus, because there is really no interface, but a=20 >>character device /dev/net/tun is involved. >=20 > Exactly, that's why this event is important. Without it, udev would not > be able to create the character device. >=20 > What is the issue you are having with this? Yes, this is exactly the event due to which udev creates the=20 /dev/net/tun character device :) However, it also gets dispatched to=20 /etc/hotplug/net.agent for some reason. --=20 Alexander E. Patrakov ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 -=20 digital self defense, top technical experts, no vendor pitches,=20 unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ 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