On 2016-07-24 16:33, Andrei Borzenkov wrote:
24.07.2016 14:10, Carlos E. R. пишет:
On 2016-07-24 07:10, Andrei Borzenkov wrote:
24.07.2016 04:47, Carlos E. R. пишет:
On 2016-07-22 17:25, Andrei Borzenkov wrote:
Of course not. This only affects code that is emitted by grub-mkconfig, so if you do not use grub-mkconfig, no reason to mess with this file (there is currently single exception of encrypted /boot/grub).
Ok... then I can not set the default entry of my choice via grub :-(
Sorry? You trimmed exactly my answer how to do it via grub.
Huh? You mean: |> Then just use |> |> set default=whatever-is-your-default |> |> in grub.cfg But I did that and it did not work, it was ignored. I said: In file "/etc/default/grub" I have: GRUB_DEFAULT=cer-main-001 GRUB_SAVEDEFAULT=true and in file "/boot/grub2/custom.cfg": menuentry 'Main (por uuid)' --id cer-main-001 { insmod part_gpt insmod ext2 set root='hd0,gpt5' if search --no-floppy --fs-uuid --set=root e99d9dcb-869d-4a24-94cf-cba32f169b8d ; then chainloader +1 else echo Could not find this OS instance, will not boot (3) sleep 1 fi } The intention is to boot by default an entry in the *custom.cfg* file. And it does not do that. It boots the first entry in "/boot/grub2/grub.cfg". You concurred that this does not work: |> Of course not. This only affects code that is emitted by grub-mkconfig, |> so if you do not use grub-mkconfig, no reason to mess with this file |> (there is currently single exception of encrypted /boot/grub). I don't see what I can do to boot "cer-main-001" by default. It is not in the grub-cf file, it is not touched by grub-mkconfig. If I misunderstood, please explain -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)