Follow-up Comment #6, bug #39306 (project grub):
re: comment #3 - yes, i understand how they're generated.
however if you run 'grub-set-default
gnulinux-3.8-2-amd64-advanced-db4cb9bd-e5e9-40c6-ac22-2267fd41084d' and then
later delete the kernel, the default in grubenv will point to a kernel that is
no longer installed. same as if you use the index and then delete the
kernel.
in other words, you need to check that your saved_entry or prev_saved_entry is
valid every time you run update-grub/grub-mkconfig whether you use a numbered
index or a $menu_id_option.
which, again, is the point of my script. it makes that task much less of a
hassle.
BTW, if menuentry_id_option was mandatory for every menuentry, it would be
trivial to modify the grub-list-kernels.pl script so that it printed them
instead of a numeric index...but it's not mandatory, it's optional, so you
can't rely on it being there.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?39306>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-grub mailing list
Bug-grub@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-grub
