Re: os-prober detects in wrong order and GRUB doesn't have enough options
On Wed, Jan 31, 2024 at 05:29:56AM -, David Chmelik wrote: > Earlier this or last year I tried to use Devuan to report os-prober > detects in wrong order. It may detect current OS partition first, but if > you have more than 10, then it continues from 10, and (if this is all you > have) goes to the last in the tens but then continues somewhere in single- > digit partitions, Sounds like someone's doing an alphanumeric sort on numbers. unicorn:~$ printf '%s\n' 1 2 3 11 12 13 | sort 1 11 12 13 2 3 It could be a result of filename globbing, e.g. /dev/sda[0-9]* which would give that kind of ordering. In any case, this isn't a Devuan mailing list. If you've reported a bug to Debian, then you should have the bug number, and the URL to its web page. If you've reported it to Devuan, then we can't help.
os-prober detects in wrong order and GRUB doesn't have enough options
Earlier this or last year I tried to use Devuan to report os-prober detects in wrong order. It may detect current OS partition first, but if you have more than 10, then it continues from 10, and (if this is all you have) goes to the last in the tens but then continues somewhere in single- digit partitions, so then puts your OS all in wrong order in GRUB2, which should have more options about menu order like is easy to configure LILO exactly the way you want. I have some entries I wrote myself, because even after a bug report over 10 years ago, os-prober didn't detect FreeBSD & NetBSD (reported) & DragonFlyBSD UNIXes, nor OpenSolaris/IllumOS UNIXes, nor does GRUB2 do some GNU/Linux right like SystemRescue and some obscure boot options some RedHat variants need or won't boot. Seems like the bug maybe didn't get reported to the os-prober programmers. Did it not get through or is there another way I could report this?
