On Mon, Sep 14, 2009 at 4:17 PM, Kay Sievers <kay.sievers@xxxxxxxx> wrote:
> On Mon, Sep 14, 2009 at 15:52, Pascal Terjan <pterjan@xxxxxxxxx> wrote:
>> 60-persistent-storage.rules contains :
>>
>> ENV{DEVTYPE}=="partition", IMPORT{parent}="ID_*"
>> KERNEL!="sr*", IMPORT{program}="/sbin/blkid -o udev -p $tempnode"
>>
>> This causes a bug in a very specific setup here :
>>
>> The full disk has iso9660 signature but contains 2 partitions, one of
>> them with a vfat FS, the other one without valid FS
>> Because of these rules, the partition without valid FS is listed as
>> iso9660 and apps try to mount it (and fail)
>>
>> I don't know any way to change IMPORT{parent}="ID_*" to exclude ID_FS_*
>> Is there a way to do it ?
>
> Why can an iso9660 volume have partitions?
As I said, this is very specific setup. This is an iso image than can
be dumped on either usb stick or a cdrom (made with isohybrid,
provided by isolinux).
There is enough space in the beginning of iso to put a partition table
which most BIOS will be able to boot while very few accept to boot an
iso image dumped on usb key.
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
