then the only way to do that is with a /etc/grub.d/40_Custom file
but those directives need to be hand-edited after every update in
any of the systems.
On Thu, 24 Sep 2026 16:49:41 -0400, bad sector wrote:
then the only way to do that is with a /etc/grub.d/40_Custom file
but those directives need to be hand-edited after every update in
any of the systems.
<https://www.gnu.org/software/grub/manual/grub/grub.html> section 6.1, rCLSimple configuration handlingrCY:
`grub-mkconfig` does have some limitations. While adding extra
custom menu entries to the end of the list can be done by editing
`/etc/grub.d/40_custom` or creating `/boot/grub/custom.cfg`,
changing the order of menu entries or changing their titles may
require making complex changes to shell scripts stored in
`/etc/grub.d/`. This may be improved in the future. In the
meantime, those who feel that it would be easier to write
`grub.cfg` directly are encouraged to do so ... and to disable any
system provided by their distribution to automatically run
`grub-mkconfig`.
Devs want tools, users want utilities.
On 9/24/26 7:39 PM, Lawrence DrCOOliveiro wrote:
On Thu, 24 Sep 2026 16:49:41 -0400, bad sector wrote:
then the only way to do that is with a /etc/grub.d/40_Custom file
but those directives need to be hand-edited after every update in
any of the systems.
<https://www.gnu.org/software/grub/manual/grub/grub.html> section 6.1,>> rCLSimple configuration handlingrCY:
-a-a-a-a `grub-mkconfig` does have some limitations. While adding extra
-a-a-a-a custom menu entries to the end of the list can be done by editing >> -a-a-a-a `/etc/grub.d/40_custom` or creating `/boot/grub/custom.cfg`,
-a-a-a-a changing the order of menu entries or changing their titles may
-a-a-a-a require making complex changes to shell scripts stored in
-a-a-a-a `/etc/grub.d/`. This may be improved in the future. In the
-a-a-a-a meantime, those who feel that it would be easier to write
-a-a-a-a `grub.cfg` directly are encouraged to do so ... and to disable any >> -a-a-a-a system provided by their distribution to automatically run
-a-a-a-a `grub-mkconfig`.
Devs want tools, users want utilities. I'm working with 40_custom but
there are issues, more about this tomorrow night. There is nothing wrong
with auto updates, most of the complaints revolve around menu
PRESENTATION and easy/simple user control of THAT.
It doesn't necessarily have to be 40_custom, if you want your entry
higher on the list you can use a lower number. I have currently 5
custom entries, each in its own file: 14_custom through 18_custom.
At best it's a tool made for developers (tail wagging the dog) and
doesn't even resemble a user-oriented boot loader. If all I want in
my menu for (currently) 6 onboard OSes is the partition number and the
distro name ending with a UEFI boot
11 Artix
12 Devuan
13 Slackware
14 Tumbleweed
15 Debian
16 Leap
UEFI
bad sector <forgetski@_INVALID.net> writes:
At best it's a tool made for developers (tail wagging the dog) and
doesn't even resemble a user-oriented boot loader. If all I want in
my menu for (currently) 6 onboard OSes is the partition number and the
distro name ending with a UEFI boot
11 Artix
12 Devuan
13 Slackware
14 Tumbleweed
15 Debian
16 Leap
UEFI
Booting six different Linux installs is an extremely niche use case, not supporting it automatically doesnrCOt make it a rCyPOSrCO.
On Thu, 24 Sep 2026 16:49:41 -0400, bad sector wrote:
then the only way to do that is with a /etc/grub.d/40_Custom file
but those directives need to be hand-edited after every update in
any of the systems.
<https://www.gnu.org/software/grub/manual/grub/grub.html> section 6.1, rCLSimple configuration handlingrCY:
`grub-mkconfig` does have some limitations. While adding extra
custom menu entries to the end of the list can be done by editing
`/etc/grub.d/40_custom` or creating `/boot/grub/custom.cfg`,
changing the order of menu entries or changing their titles may
require making complex changes to shell scripts stored in
`/etc/grub.d/`. This may be improved in the future. In the
meantime, those who feel that it would be easier to write
`grub.cfg` directly are encouraged to do so ... and to disable any
system provided by their distribution to automatically run
`grub-mkconfig`.
On 9/25/26 4:02 AM, Richard Kettlewell wrote:
bad sector <forgetski@_INVALID.net> writes:
At best it's a tool made for developers (tail wagging the dog) and
doesn't even resemble a user-oriented boot loader.-a If all I want in
my menu for (currently) 6 onboard OSes is the partition number and the
distro name ending with a UEFI boot
11 Artix
12 Devuan
13 Slackware
14 Tumbleweed
15 Debian
16 Leap
UEFI
Booting six different Linux installs is an extremely niche use case, not
supporting it automatically doesnrCOt make it a rCyPOSrCO.
Natural stability requires three or more legs, I just brought it down
from ten and the current mix is 3 with systemd and three without to
focus on the looming gore.
On Thu, 24 Sep 2026 23:16:17 -0400, bad sector wrote:
Devs want tools, users want utilities.
Not sure what the difference is. Sounds like yourCOre bringing across a mindset from the world of proprietary platforms, where ordinary users
are not supposed to have access to any functionality that has to do
with rCLdevelopmentrCY.
In the open-source world, there are no hard-and-fast barriers; itrCOs
all a spectrum.
At best it's a tool made for developers (tail wagging the dog) and
doesn't even resemble a user-oriented boot loader. If all I want in my
menu for (currently) 6 onboard OSes is the partition number and the
distro name ending with a UEFI boot
11 Artix
12 Devuan
13 Slackware
14 Tumbleweed
15 Debian
16 Leap
UEFI
then the only way to do that is with a /etc/grub.d/40_Custom file but
those directives need to be hand-edited after every update in any of the systems.
As it is, the only alternative is some cron that runs the installed
systems and verifies existing or creates standard links which can then
be used in an /etc/grub.d/40_Custom file.
On 9/25/26 4:02 AM, Richard Kettlewell wrote:
bad sector <forgetski@_INVALID.net> writes:
At best it's a tool made for developers (tail wagging the dog) and
doesn't even resemble a user-oriented boot loader. If all I want in
my menu for (currently) 6 onboard OSes is the partition number and the
distro name ending with a UEFI boot
11 Artix
12 Devuan
13 Slackware
14 Tumbleweed
15 Debian
16 Leap
UEFI
Booting six different Linux installs is an extremely niche use case,
not supporting it automatically doesnrCOt make it a rCyPOSrCO.
Natural stability requires three or more legs, I just brought it down
from ten and the current mix is 3 with systemd and three without to
focus on the looming gore.
On 24/09/2026 22.49, bad sector wrote:
At best it's a tool made for developers (tail wagging the dog) and
doesn't even resemble a user-oriented boot loader. If all I want in my
menu for (currently) 6 onboard OSes is the partition number and the
distro name ending with a UEFI boot
11 Artix
12 Devuan
13 Slackware
14 Tumbleweed
15 Debian
16 Leap
UEFI
then the only way to do that is with a /etc/grub.d/40_Custom file but
those directives need to be hand-edited after every update in any of
the systems.
Let each distribution to handle their own grub.cfg as they see it fit,
just don't install the grub loader on disk.
You then have one master grub stored in mbr/gpt/efi, which has only your custom configuration, it points to the grub in the partition, for example:
-a-a-a menuentry '11 Artix' {
-a-a-a-a-a-a insmod chain
-a-a-a-a-a-a set root=(hd0,11)
-a-a-a-a-a-a configfile /boot/grub/grub.cfg
-a-a-a }
This makes you to have to edit the master grub install only each time
you install a new distro. Each time a distro updates kernels it will
update it's own grub configuration.
"...queries involving GRUB2 menu problems consistently yield
millions of results, indicating it is one of the most common
troubleshooting areas in Linux administration."
I rest my case.
On 9/24/26 11:43 PM, Lawrence DrCOOliveiro wrote:
In the open-source world, there are no hard-and-fast barriers; itrCOs
all a spectrum.
What I want is
*blindfolded in 3 seconds with one hand*
On 24/09/2026 22.49, bad sector wrote:
At best it's a tool made for developers (tail wagging the dog) and
doesn't even resemble a user-oriented boot loader. If all I want in my
menu for (currently) 6 onboard OSes is the partition number and the
distro name ending with a UEFI boot
11 Artix
12 Devuan
13 Slackware
14 Tumbleweed
15 Debian
16 Leap
UEFI
then the only way to do that is with a /etc/grub.d/40_Custom file but
those directives need to be hand-edited after every update in any of
the systems.
Let each distribution to handle their own grub.cfg as they see it fit,
just don't install the grub loader on disk.
You then have one master grub stored in mbr/gpt/efi, which has only your custom configuration, it points to the grub in the partition, for example:
-a-a-a menuentry '11 Artix' {
-a-a-a-a-a-a insmod chain
-a-a-a-a-a-a set root=(hd0,11)
-a-a-a-a-a-a configfile /boot/grub/grub.cfg
-a-a-a }
This makes you to have to edit the master grub install only each time
you install a new distro. Each time a distro updates kernels it will
update it's own grub configuration.
As it is, the only alternative is some cron that runs the installed
systems and verifies existing or creates standard links which can then
be used in an /etc/grub.d/40_Custom file.
Ouch, why over complicate something that Grub already have solved...
chose <chose@INVALID_.gov> (but really a nym-shifted bad sector) writes:
On 9/25/26 4:02 AM, Richard Kettlewell wrote:
bad sector <forgetski@_INVALID.net> writes:
At best it's a tool made for developers (tail wagging the dog) and
doesn't even resemble a user-oriented boot loader. If all I want in
my menu for (currently) 6 onboard OSes is the partition number and the >>>> distro name ending with a UEFI boot
11 Artix
12 Devuan
13 Slackware
14 Tumbleweed
15 Debian
16 Leap
UEFI
Booting six different Linux installs is an extremely niche use case,
not supporting it automatically doesnrCOt make it a rCyPOSrCO.
Natural stability requires three or more legs, I just brought it down
from ten and the current mix is 3 with systemd and three without to
focus on the looming gore.
I have no idea what this is supposed to mean. One Linux per computer has
been perfectly adequate for me (and I suspect almost all other Linux
users) for 30 years. At any rate whatever the reasons for your choices,
the configuration is distant outlier compared to the rest of the world.
On 24/09/2026 22.49, bad sector wrote:
At best it's a tool made for developers (tail wagging the dog) and
doesn't even resemble a user-oriented boot loader. If all I want in my
menu for (currently) 6 onboard OSes is the partition number and the
distro name ending with a UEFI boot
11 Artix
12 Devuan
13 Slackware
14 Tumbleweed
15 Debian
16 Leap
UEFI
then the only way to do that is with a /etc/grub.d/40_Custom file but
those directives need to be hand-edited after every update in any of
the systems.
Let each distribution to handle their own grub.cfg as they see it fit,
just don't install the grub loader on disk.
You then have one master grub stored in mbr/gpt/efi, which has only your custom configuration, it points to the grub in the partition, for example:
-a-a-a menuentry '11 Artix' {
-a-a-a-a-a-a insmod chain
-a-a-a-a-a-a set root=(hd0,11)
-a-a-a-a-a-a configfile /boot/grub/grub.cfg
-a-a-a }
This makes you to have to edit the master grub install only each time
you install a new distro. Each time a distro updates kernels it will
update it's own grub configuration.
At best it's a tool made for developers (tail wagging the dog) and
doesn't even resemble a user-oriented boot loader. If all I want in my
menu for (currently) 6 onboard OSes is the partition number and the
distro name ending with a UEFI boot
11 Artix
12 Devuan
13 Slackware
14 Tumbleweed
15 Debian
16 Leap
UEFI
then the only way to do that is with a /etc/grub.d/40_Custom file but
those directives need to be hand-edited after every update in any of the systems. Thousands of users including myself have been asking for STANDARDIZED vmlinuz and initrd links pointing to the latest kernel!!! openSuse have listened and do this but most others do not. This would
make it possible to have a simplified custom menu that uses the links
and does not have to be edited each time.
As it is, the only alternative is some cron that runs the installed
systems and verifies existing or creates standard links which can then
be used in an /etc/grub.d/40_Custom file.
I have no idea what this is supposed to mean. One Linux per computer has
been perfectly adequate for me (and I suspect almost all other Linux
users) for 30 years. At any rate whatever the reasons for your choices,
the configuration is distant outlier compared to the rest of the world.
On 2026-09-25 13:59, Richard Kettlewell wrote:
I have no idea what this is supposed to mean. One Linux per computer has
been perfectly adequate for me (and I suspect almost all other Linux
users) for 30 years. At any rate whatever the reasons for your choices,
the configuration is distant outlier compared to the rest of the world.
But of course there are always exceptions. My computers all have at
least 2 Mageia installs on them, and half of them have 3.
One desktop and one laptop each have systems used for production, and
the rest are used for testing purposes. As an active member of the
Mageia Quality Assurance team, I test updates to Mageia 10 before they
are sent out into the wild.
For the last three months I've also been testing updates to Mageia 9.
That goes EOL today, so I will change them to Mageia 10 soon. Later,
after some more development, they will become "Cauldron" installs,
testing our development version under daily use.
TJ
On 2026-09-25 13:59, Richard Kettlewell wrote:
I have no idea what this is supposed to mean. One Linux per computer has
been perfectly adequate for me (and I suspect almost all other Linux
users) for 30 years. At any rate whatever the reasons for your choices,
the configuration is distant outlier compared to the rest of the world.
But of course there are always exceptions. My computers all have at
least 2 Mageia installs on them, and half of them have 3.
One desktop and one laptop each have systems used for production, and
the rest are used for testing purposes. As an active member of the
Mageia Quality Assurance team, I test updates to Mageia 10 before they
are sent out into the wild.
For the last three months I've also been testing updates to Mageia 9.
That goes EOL today, so I will change them to Mageia 10 soon. Later,
after some more development, they will become "Cauldron" installs,
testing our development version under daily use.
So now with an investment of hours and hours I got a decent menu out
of grub2,
On Wed, 30 Sep 2026 19:41:37 -0400, bad sector wrote:
So now with an investment of hours and hours I got a decent menu out
of grub2,
You could have written a script to automate it for you.
You *do* know those files in /etc/grub.d are nothing more than shell
scripts, donrCOt you?
You *do* remember when x11 (or even grub legacy) was set up in a
single config file and no one had any problems with it?
All that I really need is the sequential partition number and an
unversioned or even abbreviated distro name.
On 01/10/2026 18.40, bad sector wrote:
All that I really need is the sequential partition number and an
unversioned or even abbreviated distro name.
grub begins partition numbers on 0, Linux begins with 1...
On 9/30/26 8:11 AM, TJ wrote:
On 2026-09-25 13:59, Richard Kettlewell wrote:
I have no idea what this is supposed to mean. One Linux per computer has >>> been perfectly adequate for me (and I suspect almost all other Linux
users) for 30 years. At any rate whatever the reasons for your choices,
the configuration is distant outlier compared to the rest of the world.
But of course there are always exceptions. My computers all have at
least 2 Mageia installs on them, and half of them have 3.
One desktop and one laptop each have systems used for production, and
the rest are used for testing purposes. As an active member of the
Mageia Quality Assurance team, I test updates to Mageia 10 before they
are sent out into the wild.
For the last three months I've also been testing updates to Mageia 9.
That goes EOL today, so I will change them to Mageia 10 soon. Later,
after some more development, they will become "Cauldron" installs,
testing our development version under daily use.
TJ
Nowadays with all the zukerboogers and gatekeepers jockeying for
monopoly and total $tranglehold on humanity we never know which OS gets 'compromized' next so as far as I'm concerned using a single whatever is imprudence cubed.
On 2026-09-30 11:35, bad sector wrote:
On 9/30/26 8:11 AM, TJ wrote:A few years back a (probably) bad actor tried to compromise the Mageia
On 2026-09-25 13:59, Richard Kettlewell wrote:
I have no idea what this is supposed to mean. One Linux per computerBut of course there are always exceptions. My computers all have at
has
been perfectly adequate for me (and I suspect almost all other Linux
users) for 30 years. At any rate whatever the reasons for your choices, >>>> the configuration is distant outlier compared to the rest of the world. >>>
least 2 Mageia installs on them, and half of them have 3.
One desktop and one laptop each have systems used for production, and
the rest are used for testing purposes. As an active member of the
Mageia Quality Assurance team, I test updates to Mageia 10 before
they are sent out into the wild.
For the last three months I've also been testing updates to Mageia 9.
That goes EOL today, so I will change them to Mageia 10 soon. Later,
after some more development, they will become "Cauldron" installs,
testing our development version under daily use.
TJ
Nowadays with all the zukerboogers and gatekeepers jockeying for
monopoly and total $tranglehold on humanity we never know which OS
gets 'compromized' next so as far as I'm concerned using a single
whatever is imprudence cubed.
QA team. He (could have been a she I suppose, but read like a guy) tried
to appeal to our greedy side, asking why we were doing this as
volunteers when we could be lining our pockets somehow. I was deputy
leader of the team at the time, and when appealing to greed failed he changed the bait to the desire for power. He tried to convince me that I should stage a coup and take over the stranglehold of the then-leader.
It didn't work. We remain a community-based distro, staffed by all volunteers working in our spare time.
TJ
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:46:59 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,582 |