i would live to see the boot-repair tool added to the iso so it could be used in the live cd to repair the boot if someone neede to boot-repair / Home / Home
I don’t really see what the point of putting a tool to fix legacy boot situations with GRUB and MBR for the most part would be. (yes I do see that it does do some EFI repair/backup features), however, they have a bootable iso if you want to use that tool. Kind of like if you wanted to use any a particular tool for data recovery or disk imaging, etc. Most of those types of “tools” have you boot off their ISO that they have tested and designed to work with whatever OS they chose to develop and test it with. I’m not sure what the benefit of adding the bloat to be part of a Arch based linux distro that (per the website homepage) is designed to deliver lightning-fast speeds and stability.
You should check out Ventoy to create a bootable USB stick that you can then just drop the various ISOs you want in it and be able to have a single USB stick that can boot various ISO files, then you can have all the tools that you want to be able to use all on one USB stick and keeping it up to date is as simple as downloading the latest ISO and copying it to the USB Stick.
But hey I’m just the peanut gallery here so take my 2 cents for what it’s worth, it’s just my 2 cents.
From the live cd, you can open terminal and use chroot
OK no problem I just thought this be a good think to add since you guys added a benchmark we’ll I gess not shame
I like the idea of this, especially after I recently made a motherboard setting change and lost all my EFI entries; I ended up having to use cachy-chroot to reinstall rEFInd on the system. I could see a Cachy Hello button for “Reinstall Boot Loader” being really handy; perhaps the same three-option menu used for the beginning of the Calamares install process.
Some filesystems require unique mounting, though, thinking ZFS here; I don’t know how reasonably feasible it is to have a script be able to do this quickly and cleanly for each supported filesystem and setup. (I’m not a programmer; I got lost after being able to write simple batch files as a kid on DOS, as three separate Java 101/1001 instructors would agree after I failed each course attempt 
)
oh yeah that why i suggested it
also i dont like Ventoy i now i’ll get flack for that but i dont like it
Not sure why you’d get flack, you do you. I just personally don’t like carrying around 20 flash drives for different boots. Prefer to have one 256gb flash drive that does it all.
It’s probably because there’s been a issue with a crap-load of binary blobs in the source, with a lack of transparency (and communication) from the dev. Basically, if you wanted to install a boot-loader level rootkit on a bunch of machine, then Ventoy is the perfect vector 
I’ts probably nothing, but the dev’s refual to even comment on the matter (last that I checked) is a bit concerning to some.
True that is fair, it is always wise to determine your level of trust with a piece of software you are putting on your machine. They are actively working on a plan to start removing all the blobs. However, in the mean time all of the blobs have been identified with their source and checksums. Ventoy has pinned this open issue to discuss and track the issue: