From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bryan Kadzban Date: Thu, 03 May 2007 11:12:42 +0000 Subject: Re: udev problem DVB-S/T Cards Message-Id: <4639C3AA.9090303@kadzban.is-a-geek.net> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============1338306870==" List-Id: References: <000301c78982$db8615e0$929241a0$@com> In-Reply-To: <000301c78982$db8615e0$929241a0$@com> To: linux-hotplug@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1338306870== Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig2B0F24C4AFDD835D2FF27253" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2B0F24C4AFDD835D2FF27253 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Razza wrote: > I have located path_id which is in /sbin on Fedora core 5 Hmm; it should be in /lib/udev AFAIK. But maybe this doesn't matter. > there are some pretty long case statements in there (one I counted > had 47 lines!), Yeah, it's complicated. But I don't think we can do much about that... > the simplest and last I could find is - >=20 > case "$TYPE" in > block) > handle_block > ;; > *) > RESULT=3D1 > ;; > esac That should be the right case, but that doesn't look like the current version of the script. The script from udev-110 looks like this: case "$TYPE" in block) handle_device echo "ID_PATH=3D$d" ;; scsi_tape) handle_device echo "ID_PATH=3D$d" ;; input) handle_device echo "ID_PATH=3D$d" ;; *) RESULT=3D1 ;; esac And then it's followed by: exit $RESULT But I don't think it's safe to modify the script that you have unless it has a case that matches this layout (because the script you have is quite different from mine, so I don't think my modifications are valid for your system). Is it possible to get an updated udev? I know that the path_id script from udev-105 should work with the changes I posted last night, and I know -110 should too, so I assume anything between those two should also work. (But use a distro version of udev, not the sources. The sources will put the path_id script in /lib/udev, and it sounds like your distro already has that script somewhere else. There will probably be other issues too.) > I'm not even sure if I have the right path_id file, the commented > section at the top of path_id states "provide the shortest possible > unique hardware path to a block device for the udev persistent disk > device naming scheme" - clearly i'm not playing with block devices. No, but that is the right script. :-) When it was first created, it only handled block devices, but other stuff can be added. --------------enig2B0F24C4AFDD835D2FF27253 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGOcOxS5vET1Wea5wRAysjAJsHZbZux12drGMpsyrcpGVNKZbVbQCfWi8i Y7rOq7R0o/Q19a5RmxEoJeM= =mhl7 -----END PGP SIGNATURE----- --------------enig2B0F24C4AFDD835D2FF27253-- --===============1338306870== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ --===============1338306870== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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 --===============1338306870==--