On 02/04/2010 11:00 PM, Gerardo Exequiel Pozzi wrote:
On 02/04/2010 08:28 PM, Thomas Bächler wrote:
diff --git a/archiso/hooks/archiso-early b/archiso/hooks/archiso-early index d57b73b..edd554b 100644 --- a/archiso/hooks/archiso-early +++ b/archiso/hooks/archiso-early @@ -2,7 +2,7 @@ run_hook () { if [ -n "${archisolabel}" ]; then - echo "ACTION==\"add|change\", SUBSYSTEM==\"block\", IMPORT{program}=\"vol_id --export \$tempnode\""> /lib/udev/rules.d/00-archiso-device.rules + echo "ACTION==\"add|change\", SUBSYSTEM==\"block\", IMPORT{program}=\"/sbin/blkid -o udev \$tempnode\""> /lib/udev/rules.d/00-archiso-device.rules echo "ENV{ID_FS_LABEL_ENC}==\"${archisolabel}\", SYMLINK+=\"archiso\"">> /lib/udev/rules.d/00-archiso-device.rules fi } I was thinking about dropping the special udev rule and using blkid to find the right device, it has an option for that. I also thought about a failsafe mechanism in case the label is incorrect. This sound interesting. Are you talking about blkid -t LABEL="xyz" ?
Oops, I tried without this rule, works but only when booting the iso as disk (/dev/sd) if you boot the iso as cdrom blkid does not list any device. if you force blkid /dev/sr0 will work. -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D