Hi, adrian15 wrote: > 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.
It's spelled x o r r i s o nowadays :)) There are use cases like Knoppix: An ISO partition, an EFI partition, and a writable ReiserFS partition which gets expanded up to the end of the USB stick or hard disk. > 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. Consider to stay at least with the idea of a dedicated marker file with a not-so-probable constant name. The double-job of vmlinuz and the existence of an identical path on another disk caused the problems in this bug report. If the searched path would have been /live/this_is_a_debian_live_iso then no change of kernel names could interfere. Any incidential path equality would be unlikely, unless multiple debian-live ISOs are involved. > Hopefully Thomas you are not too bad at me. You seemed to be very > excited with all of this earmark implementation ;) . I am a bystander and tool provider here. Some aspects of the current state of Debian ISOs appear sub-optimal to me. E.g. the EFI partition inside the ISO filesystem rather than after it. When the discussion comes to these, then i pop up with my pre-formatted opinion. Have a nice day :) Thomas
