I was always curious about this feature, and I am willing to implement it within the foreseeable future. Still, if someone, probably from the core team, wants to come ahead of me, I welcome this:
The tutorial is a bit wonky, suggesting it would not be possible from btrfs, but you get the idea:
Some way, optimally via GUI, to install an ISO of us into the filesystem, so that GRUB can read it.
All the ‘finding an USB stick lying around, writing the ISO to it, restarting, missing the input to boot from USB, restarting again, and so on…’ would be over.
I specifically think, this could increase the amount of people, who want to test a new ISO (and makes it more comfortable for the core team in the first place)
As said, I would look into this in like a week or so.
There is something similar which has been suggested or mentioned here in the forum several times.
I learned it from @SGS and liked it a lot , so I’m picking a random post from him at a quick search for “custom.cfg”:
Changes to /boot/grub/custom.cfg do not require re-running grub-mkconfig, since /etc/grub.d/41_custom adds the necessary source statement to the generated configuration file.
You can also boot ISO’s directly from the internal hard disk with custom.cfg.
Is everything here in the forum, somewhere
But a big time advantage does not arise from this for me to be able to test all Garuda DE’s now.
The Garuda download tool seems to be not in use anymore, otherwise would I have said, that it could put ISOs into that directory as well, so we could just download and reboot into live mode with a handful of clicks.
Its not a solution for me. Its not even what I have asked for.
I am looking for a newbie friendly way, not something that needs tinkering.
And this definitely needs.
custom.cfg did that.
Feel free to add this to the gitlab as MR.
I do not think so, Garuda is arch based, in the end the user is his own admin.
We are user-friendly, and newbies have to learn and not waiting for spoon-feed , at some point we do not have enough developer for all your wishes.
I understand your point of view, but new tools should be for important system functionality.
This seems to me to be something that makes life easier for those who test new isos (or other things…), and those who want to test should be able to edit a text file by just changing the name of the iso.
It’s nice-to-have as far as I’m concerned, but I really wouldn’t ask developers to invest time on this if they have other priorities (within the time they can dedicate).
Booting an ISO off the disk is a neat parlor trick, but less useful than a proper Ventoy stick for ISO testing. With Ventoy you can just throw ten ISOs on there if you want to, and get to work without having to redo the setup in between.
What would be really neat would be to have a Ventoy option built in to the disk. That way you could throw some ISOs into the Ventoy partition (right from the GUI file manager if you want to) and boot to Ventoy from Grub, or whatever boot manager.
It seems like it would be possible if Ventoy can share the regular EFI partition, but I have not tested or even looked at it closely. disk_layout_gpt . Ventoy
Well, I totally understand, that we might not have the people, who are willing to implement this.
And I am wondering, why people did skip the very line of my original comment, in which I suggested, that I will look into this, and if others may find this interesting, they could join.
At no point did I argue, this should take some form of priority, or that I deem anyone responsible for this, other than myself.
, so I’m picking a random post from him at a quick search for “custom.cfg”:
, at some point we do not have enough developer for all your wishes.