El 09/03/19 a las 15:03, Thomas Schmitt escribió: > Hi, > > adrian15 wrote: >> Well, guess what happened... my obvious patch: >> if ! search --set=root --file /live/vmlinuz ; then > search --set=root --file /live/vmlinuz1 >> does not boot in my computer because it's still finding /live/vmlinuz in >> the internal hard disk.
So, I have been taking a look at Debian official Live build images (which are built with lwr) and they happen to search for: search --set=root --file /.disk/info So there are two scenarios where this might arise as a problem: 1) Two live USB images being plugged in at the same time. And somehow the UEFI firmware is so good that it shows both of them to grub. I think we shouldn't care too much about this scenario because it's too unlikely. 2) One live USB image plugged in. And some computer manufacter having installed a possibly lwr based live build on an internal hard disk partition. I think this is highly unlikely because when you build an image designed to be used in a hard disk you do not use mkisofs. Why? Because you want the partition to be writable. Isn't it? So if mkisofs is not used then there won't be a /.disk/info file. So there is not a problem. What I'm saying with all of this is that I'm going to propose a fix that involves not using any earmark (which involves too much work) but just searching for /.disk/info instead. Hopefully Thomas you are not too bad at me. You seemed to be very excited with all of this earmark implementation ;) . adrian15 -- Support free software. Donate to Super Grub Disk. Apoya el software libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
