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.
That's the second bad spinoff from using as ISO earmark a file which
already has a different job.
(First in my counting is that a change in kernel naming inadvertedly
could spoil the recognition of the ISO.)
> 3) I'll try to code this dedicated unique identification file path that
> you are proposing and see if it works better.
I am pondering whether the name should be long and human readable
like "d-live_9.4.0_xf_amd64" or short and bootloader agnostic like
"0F63AE66.87F" (*).
The former needs Rock Ridge support to be recognizable (GRUB2 has it,
afaic), the latter would show up the same in all naming systems of
the ISO. Be it plain ISO 9660 level 1, Rock Ridge, or Joliet.
(*) The short name was derived by:
x=$(echo -n 'd-live 9.4.0 xf amd64' | md5sum | tr 'a-z' 'A-Z' | dd bs=1
count=11)
name=$(echo "$x" | dd bs=1 count=8)"."$(echo "$x" | dd bs=1 skip=8 count=3)
(I am sure it can be done more elegantly.)
Have a nice day :)
Thomas
