On Friday 19 December 2014 14:56:08 Karel Zak wrote: > On Tue, Dec 09, 2014 at 11:35:20AM +0100, Karel Zak wrote: > > > I looked into grub2 code and it is identifying UDF label > > > also from LogicalVolumeIdentifier. So if you want to boot > > > something from UDF FS via grub you probably see label > > > problems... > > > > > > So I think that rather than using broken linux > > > implementation is better to fix it (which could bring > > > problems with different label names in new version). And > > > I would like to see human readable label as "555e3160". > > > > It's more important to not introduce regression, if you have > > LABEL= in your fstab then you don't want to see that after > > util-linux update your setting is obsolete and filesystem > > unmounted. > > You have convinced me that fix the problem (and improve > compatibility) with UDF LABEL= is a good idea. > > Not sure, but I guess that for many users the change will be > invisible because preferred way is to read the LABEL from > ISO9660 header and UDF specific LABEL is just fallback > solution only. > > The latest Pali's patches are at: > https://github.com/karelzak/util-linux/pull/135 > > Karel Now I played with Windows format.exe command and it set UDF ids: Volume identifier: "UDF Volume" Logical volume identifier: "<label_from_user>" Volume set identifier: "<8_hex_numbers> UDF Volume Set" Windows shows in My Computer label from Logical volume identifier -- Pali Rohár pali.rohar@xxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part.
