thias / glim

GRUB Live ISO Multiboot

GRUB2 Live ISO Multiboot

https://github.com/thias/glim | http://glee.thias.es/GLIM

Overview

GLIM is a set of grub configuration files to turn a simple VFAT formatted USB memory stick with many GNU/Linux distribution ISO images into a neat device from which many different Live environments can be used.

Advantages over extracting files or using special Live USB creation tools :

• A single USB memory can hold all Live environments (the limit is its size)
• ISO images stay available to burn real CDs or DVDs
• ISO images are quick to manipulate (vs. hundreds+ files)

Disadvantages :

• There is no persistence overlay for distributions which normally support it
• Setting up isn't as easy as a simple cat from the ISO image to a block device

My experience has been that the safest filesystem to use is FAT32 (surprisingly!), though it will mean that ISO images greater than 4GB won't be supported. Other filesystems supported by GRUB2 also work, such as ext3/ext4, NTFS and exFAT, but the boot of the distributions must also support it, which isn't the case for many with NTFS (Ubuntu does, Fedora doesn't) and exFAT (Ubuntu doesn't, Fedora does). So FAT32 stays the safe bet.

Screenshots

Installation

Once you have your USB memory with a single partition formatted as FAT32 with the filesystem label 'GLIM', mount it, clone this git repository and just run (as a normal user) :

./glim.sh

Once finished, you may change the filesystem label to anything you like.

The supported boot/iso/ sub-directories (in alphabetical order) are :

• almalinux - Live Media only
• antix
• arch
• artix
• bodhi
• calculate
• centos - Live was discontinued
• clonezilla
• debian - live & mini.iso
• elementary
• fedora
• finnix
• gentoo
• gparted
• grml
• ipxe - .iso or .efi
• kali
• kubuntu
• libreelec
• linuxmint
• lubuntu
• manjaro
• memtest - Only .bin/.efi, not .iso
• mxlinux
• netrunner
• openbsd
• opensuse - Live from Alternative Downloads only
• peppermint
• popos
• porteus
• rhel - Installation only
• rockylinux
• slitaz
• supergrub2disk
• systemrescue
• tails
• ubuntubudgie
• ubuntu
• void
• xubuntu
• zorinos

Any unpopulated directory will have the matching boot menu entry automatically disabled, so to skip any distribution, just don't copy any files into it.

Download the right ISO image(s) to the matching directory. If you require boot parameter tweaks, edit the appropriate boot/grub2/inc-*.cfg file.

Items order in the menu

Menu items for a distro are ordered by modification time of the iso files starting from the most recent ones. If some iso files have the same mtime, their menu items are ordered alphabetically.

Here is a generic idea how to keep it nicely ordered when you have multiple releases of some distro:

• touch your release iso files with the release date
• touch your point release iso files with the original release date plus a day per point. This is a way to ensure point releases never pop above the next release like Debian 10.13.0 (released 10 Sep 2022) would still be below Debian 11.0.0 (released 14 August 2021)
• in case there are multiple flavours of some iso but the version is the same, touch all of them with the same date for the whole group to be ordered alphabetically

Sample ordered menu:

	iso mtime
Debian Live 12.0.0 amd64 standard	10 June 2023
Debian Live 11.7.0 amd64 gnome	14 August 2021 + 7 days
Debian Live 11.7.0 amd64 kde	14 August 2021 + 7 days
Debian Live 11.7.0 amd64 standard	14 August 2021 + 7 days
Debian Live 11.0.0 amd64 gnome	14 August 2021
Debian Live 11.0.0 amd64 kde	14 August 2021
Debian Live 11.0.0 amd64 standard	14 August 2021
Debian Live 10.13.0 amd64 standard	6 July 2019 + 13 days
Debian Live 9.13.0 amd64 standard	17 June 2017 + 13 days

Special Cases

iPXE

The .iso files don't work when booting using EFI, you simply need to use .efi files instead.

LibreELEC

LibreELEC isn't provided as ISO images, nor is it able to find the KERNEL and SYSTEM files it needs anywhere else than at the root of a filesystem. But it's useful to enable booting the installer by just copying both files to the root of the USB memory stick. Live booting is also supported, and the first launch will create a 512MB file as /STORAGE.

Memtest86+

The .iso file doesn't work. Use either the .bin or the .efi depending on the boot mode used.

Ubuntu

Recent Ubuntu desktop iso images bundle multiple versions on the Nvidia driver. With that, the images are over 4GB, the FAT32 max file size. For example ubuntu-20.04.6-desktop-amd64.iso is 4.1GB, ubuntu-22.04.2-desktop-amd64.iso is 4.6GB. The driver is not required in a live system, it can be removed to make an image fit into 4GB. For example, with 22.04.2 image in the current dir:

mkdir slim
iso=ubuntu-22.04.2-desktop-amd64.iso

xorriso -indev "$iso" -outdev slim/"$iso" \
    -boot_image any replay -rm_r /pool/restricted/{l,n} --

Now you can copy slim/ubuntu-22.04.2-desktop-amd64.iso to your FAT32 formatted GLIM USB stick.

Some Ubuntu flavours also bundle the Nvidia driver (like Kubuntu), some don't (like Xubuntu). The same trick can be used with the former.

Testing

With KVM it should "just work". The /dev/sdx device should be configured as an IDE or SATA disk (for some reason, as USB disk didn't work for me on Fedora 17), that way you can easily and quickly test changes. Make sure you unmount the disk from the host OS before you start the KVM virtual machine that uses it. For UEFI testing, you'll need to use one of the /usr/share/edk2/ovmf/*.fd firmwares.

Troubleshooting

If you have any problem to boot, for instance stuck at the GRUB prompt before the menu, try re-installing. If you have other exotic GRUB errors, such as garbage text read instead of the configuration directives, try re-formatting your USB memory from scratch. I've seen weird things happen...

Contributing

If you find GLIM useful but the configuration of the OS you require is missing or simply outdated, please feel free to contribute! What you will need is to create a GitHub pull request which includes :

• All changes properly and fully tested.
• New entries added similarly to the existing ones :
  • In alphabetical order.
  • With all possible variants supported (i.e. not just the one spin you want).
• An original icon of high quality, and a shrunk 24x24 png version. Using convert -size 24x24 -background 'rgba(0,0,0,0)' original.svg small.png may work.
• An updated supported directories list in this README file.

---

Copyleft 2012-2023 Matthias Saou http://matthias.saou.eu/

All configuration files included are public domain. Do what you want with them. The invader logo was made by me, so unless the exact shape is covered by copyright somewhere, do what you want with it. The background is "Wallpaper grey" © 2008 payalnic (DeviantArt) The ascii.pf2 font comes from GRUB, which is GPLv3+ licensed. For more details as well as the source code, see http://www.gnu.org/software/grub/

glim's Issues

Grub config handler or distro image downloader

Update ISO for each release is required to keep glim updated; so if I download the latest version of Arch Linux, I will have to manually update all other ISO.
It is possibile to update manually the single config file, but it would get worse in the long-term.
I don't think this is a suitable behavior.

I thought of two ways to improve this behavior:

• provide a script to download and update all supported ISO
• provide a base grub configuration file for each distro and a patch file for each distro release; a script will checkout provided distro in the drive and apply all the needed patches.

I can work on this, but i want to discuss the implementation first.

Windows 10 ISO

It seems like there's no easy way to boot Windows 10 ISOs from USB sticks in 2018, I found this article and may have to try it today, but the question that I have is if grub2 could boot W10 ISOs the way it does so with Linux-based distros?

Ref: https://willhaley.com/blog/windows-installer-usb-linux/

Fedora 37 & 38, RHEL 9 clones don't work

See https://bugzilla.redhat.com/show_bug.cgi?id=2181989

Add support for NixOS

Creating this for reference, since I've just tried and failed. Maybe someone else will have better luck than me...

This almost works, but gives an error about not being able to mount the GLIM filesystem on /findiso because of "device of resource busy":

# NixOS
function add_menu {
  isofile="$1"

  regexp \
    --set 1:isoname \
    --set 2:variant \
    --set 3:version \
    "^${isopath}/nixos/(nixos-([^-]+)-([0-9]+\.[0-9]+).*-([^-]+)-linux\.iso)\$" "${isofile}"
  menuentry "NixOS ${version} ${variant}" "${isofile}" "${isoname}" --class nixos {
    set isofile=$2
    set isoname=$3
    use "${isoname}"
    loop $isofile
    probe --set isolabel --label (loop)
    linux (loop)/boot/bzImage findiso=${isofile} init=/nix/store/3d6j0n5fjw1yrdpfdyy70072zm8iq04v-nixos-system-nixos-23.05.4407.80c1aab72515/init  root=LABEL=${isolabel} # boot.shell_on_fail video=hyperv_fb:1152x864 elevator=noop nohibernate splash loglevel=4 nomodeset
    initrd (loop)/boot/initrd
  }
}

for_each_sorted add_menu "$isopath"/nixos/nixos-*-linux.iso

Since the above has a very unique init= parameter, I also tried using the provided grub2 loobpack configuration. That loads the provided grub menu, but entries freeze for me:

# NixOS
function add_menu {
  isofile="$1"

  regexp \
    --set 1:isoname \
    --set 2:variant \
    --set 3:version \
    "^${isopath}/nixos/(nixos-([^-]+)-([0-9]+\.[0-9]+).*-([^-]+)-linux\.iso)\$" "${isofile}"
  menuentry "NixOS ${version} ${variant}" "${isofile}" "${isoname}" --class nixos { 
    set isofile=$2
    set isoname=$3
    use "${isoname}"
    loop $isofile
    change_root (loop)
    set iso_path=$isofile
    export iso_path
    configfile /boot/grub/loopback.cfg
    restore_root
  }
}

for_each_sorted add_menu "$isopath"/nixos/nixos-*-linux.iso

Possibly something that needs to be sanitized better.

Don't show 64-bit ISOs in menu if CPU is 32-bit

Since grub2 knows the CPU architecture, you could add a test before each menuentry to check that the $arch is compatible?
e.g. currently if I boot to UEFI-32 or MBR-32, the menus lists all 64-bit ISOs.

Suggestion: Adding functionality from Super Grub2 Disk

Hi,
This is just a suggestion: I have been using Super Grub2 Disk recently, and it has some great functionality to auto detect installed OSs, grub.cfg files, and other possible ways to boot your machine. It seems to all be just some clever scripts, but it could be extremely useful.

I have been able to add the ISO to my GLIM usb, and added this as inc-sgd.cfg

# Super Grub2 Disk
set isoname="super_grub2_disk_hybrid_2.02s9.iso"
set isofile="${isopath}/sgd/${isoname}"
menuentry "Super Grub2 Disk" --class arch {
  echo "Using ${isoname}..."
  loopback loop $isofile
  source (loop)/boot/grub/grub.cfg
}

but I suspect it would be a better idea to integrate the scripts in GLIM itself. Here is the Github code:
https://github.com/supergrub/supergrub/

Add support for xcp-ng

I use xcp-ng for my VM infrastructure so it would be fitting to allow installation with glim.
xcp-ng is currently at version 8.2.1

How/what to sign so that secure boot can be enabled

Do you have a recommended procedure for signing GLIM's bits so that secure boot can stay enabled on systems that I control?

Feature request : Windows ?

Nowadays Microsoft provides ISO files https://www.microsoft.com/en-au/software-download/windows10ISO and these can come in very handy if you happen to loose your EFI boot partition, or somehow make your current windows installation unbootable...

By booting on these ISO you can use Microsoft tools to troubleshoot and fix your computer.

Super grub disk still stands out

Jan 3, 2019:

.. this is the first ISO image that doesn't require a sub-directory inside "iso", as I plan to change all of them to be like this soon

Super grub disk is still the only distro without a subdir. What is the current development direction on the matter?

Include support for rescuezilla

I created a inc-rescuezilla.cfg for Rescuezilla
I based on the nixos example using loopback.cfg given by thias.

# Rescuezilla
function add_menu_rescuezilla {
isofile="$1"

regexp
--set 1:isoname
--set 2:version
--set 3:arch
"^${isopath}/rescuezilla/rescuezilla-([0-9.]+)-([^-]+).iso"$ "${isofile}"

menuentry "Rescuezilla Live ${version} ${arch}" "${isofile}" "${isoname}" --class rescuezilla {
set isofile=$2
set isoname=$3
use "${isoname}"
loop $isofile
# Change root might not be necessary, depending on Rescuezilla's boot process
change_root (loop)
set iso_path=$isofile
export iso_path
# Point to the actual loopback configuration file for Rescuezilla (if it exists)
configfile /boot/grub/loopback.cfg
# Restore root might not be necessary
restore_root
}
}

for_each_sorted add_menu_rescuezilla "$isopath"/rescuezilla/rescuezilla-*.iso

To grub.cfg I have added:

if any_exists ${isopath}/rescuezilla/rescuezilla*.iso; then
menuentry "Rescuezilla >" --class rescuezilla {
configfile "${prefix}/inc-rescuezilla.cfg"
}
fi

I rebuilt the USB and have it working. I did have some issue with files being overwritten when running the script but I have things going now.

I also had to add an entry in the README.md file so it would create a folder for the iso when running the script:

• rescuezilla`

Write a GRUB module to detect the ISOs

Would it be possible to write a GRUB module to do detect the ISOs rather than hardcoding certain versions? I might be interested in this for the SystemImageKit project, too.

Hybrid USB ?

Having a look at https://wiki.archlinux.org/index.php/Multiboot_USB_drive, making a Hybrid UEFI GPT + BIOS GPT/MBR boot requires multiple partitions.

However currently the install script support only one partition :

alexv@alexv-XPS-Tablet:~/Projects/glim$ ./glim.sh 
Found partition with label 'GLIM' : /dev/sdb1
Found block device where to install GRUB2 : /dev/sdb
ERROR: /dev/sdb1 isn't the only partition on /dev/sdb

Is this really an error ?
Can we somehow improve the installation process to not complain about this, if it s not required ?

We could also have a part of the installation that is about formatting the drive in a proper, known, hybrid configuration, but I guess this can be some extra work for another issue.

Serial console support?

hi there, really nice project;) I was just curious if serial console output would/could be supported by default, for headless installations where only serial console is available? Something like https://github.com/eengstrom/multiboot/blob/master/grub/grub-m1000e.conf#L15-L20 -- thanks in advance for feedback

Typo in file glim/grub2/inc-linuxmint.cfg

Hi!

There is a typo in the glim/grub2/inc-linuxmint.cfg file. The name of Debian based «Linux Mint» live cd images begins with “lmde”.

Best regards
inc-linuxmint.diff.txt
.

`rsync` fails because it cannot change permissions on FAT filesystem

$ set -x; ./glim.sh
+ ./glim.sh
Found partition with label 'GLIM' : /dev/sdb1
Found block device where to install GRUB2 : /dev/sdb
Found mount point for filesystem : /run/media/jonas/GLIM
Install for EFI in addition to standard BIOS? (Y/n) y
Ready to install GLIM. Continue? (Y/n) y
Running grub-install --target=i386-pc --boot-directory=/run/media/jonas/GLIM/boot /dev/sdb (with sudo) ...
[sudo] password for jonas: 
Installing for i386-pc platform.
Installation finished. No error reported.
Running grub-install --target=x86_64-efi --efi-directory=/run/media/jonas/GLIM --removable --boot-directory=/run/media/jonas/GLIM/boot /dev/sdb (with sudo) ...
Installing for x86_64-efi platform.
Installation finished. No error reported.
Running rsync -rpt --delete --exclude=i386-pc --exclude=x86_64-efi --exclude=fonts --exclude=icons/originals ./grub2/ /run/media/jonas/GLIM/boot/grub ...
rsync: [generator] failed to set permissions on "/run/media/jonas/GLIM/boot/grub/.": Operation not permitted (1)
rsync: [generator] failed to set permissions on "/run/media/jonas/GLIM/boot/grub/themes": Operation not permitted (1)
rsync: [generator] failed to set permissions on "/run/media/jonas/GLIM/boot/grub/themes/invader": Operation not permitted (1)
rsync: [generator] failed to set permissions on "/run/media/jonas/GLIM/boot/grub/themes/invader/icons": Operation not permitted (1)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1330) [sender=3.2.3]
ERROR: the rsync copy returned with an error exit status.

I think -p (--perms) should not be specified since this is not allowed on a FAT32 file system.

Kernel panics on multiple distros

Hello
Thanks for useful tool :)
I've tried to use it and got kernel panic: unable to mount root for following distros:

• fedora-workstation,
• debian
• elementary

SystemRescueCD is working fine
I was testing all above in qemu virtual machine.
Do you have any clues what can cause this?

Thanks
P.S. if all goes well i would be happy to add config for Gentoo :)

Recent ubuntu desktop isos require extra boot args

Since 21.10 ubuntu live-server iso uses multi-layered squashes (compare contents of /casper/ before and after 21.10). It doesnt affect anything because the images can boot without any kernel args. Ubuntu desktop uses the same multi-layered scheme since 23.04 but without explicit layerfs-path=minimal.standard.live.squashfs kernel arg it does not boot as supposed.

Ubuntu flavours are likely to move towards the new installer as well, but not there yet (aside for Budgie) as of release 23.10.

Btw with 23.04 they've introduced desktop-legacy images which are based on the old installer.

make an exe for windows , boot LIVE CD ISO

run exe
select LIVE CD ISO . create and add windows's boot menu .
reboot
timeout 10 boot LIVE CD , else boot windows .
start LIVE CD .

Make inclusion in other projects easier

I've been using Super UEFIinSecureBoot Disk which includes glim in its default full installation.

The version there is a bit outdated (see ValdikSS/Super-UEFIinSecureBoot-Disk#26), and it turned out to be a bit tricky to upgrade it (see ValdikSS/Super-UEFIinSecureBoot-Disk#27), especially due the assumption that inc-*.cfg files are in the same directory as the root GRUB configuration. This is not true in Super-UiSB-Disk since its root grub.cfg loads glim from a subdirectory using configfile "$prefix/glim/main.cfg" and puts inc-*.cfg in that subdirectory as well.

I'm not sure about on which side it makes more sense to tweak the approach, so I wanted to give a heads up of this problem in both and cross-reference the issues.

Thanks for the amazing work on glim @thias!

Can't get past "Welcome to GRUB" screen

Tested on two different physical machines, with two different USB sticks.
The installation process completes with no errors, but I never get to the actual boot menu.

Most likely there's something wrong with the configuration.
The host system where I run grub2-install is OpenSUSE 42.x.

Tried both FAT32 and ext4 partition type (MBR, of course).

I've been ready to start my own project with a similar concept, but was happy to find your work
Thank you for sharing it. I would like to help you fix and improve it.

Fedora ISOs not working properly

Booting Fedora images is not working because the boot process stops during the initram execution. Additionaly, only live images of Fedora Workstation can be booted because the regex pattern does not match "netinstall" for the network installer and "dvd" for the server ISO.

A working example (including boot options for image check and recovery) would look like this:

# Fedora
for isofile in $isopath/fedora/Fedora-*.iso; do
  if [ ! -e "$isofile" ]; then break; fi
  regexp \
    --set 1:isoname \
    --set 2:variant \
    --set 3:type \
    --set 4:arch \
    --set 5:version \
    "^${isopath}/fedora/(Fedora-([^-]+)-([^-]+)-([^-]+)-([^-]+)-[^-]+\.iso)\$" "${isofile}"
    menuentry "Fedora ${version} ${arch} ${variant} (${type})" "${isofile}" "${isoname}" --class fedora {
      set isofile=$2
      set isoname=$3
      echo "Using ${isoname}..."
      loopback loop $isofile
      probe --set isolabel --label (loop)
      linux (loop)/isolinux/vmlinuz inst.stage2=hd:LABEL=${isolabel} iso-scan/filename=${isofile} quiet
      initrd (loop)/isolinux/initrd.img
    }
    menuentry "Fedora ${version} ${arch} ${variant} (${type}) (test media)" "${isofile}" "${isoname}" --class fedora {
      set isofile=$2
      set isoname=$3
      echo "Using ${isoname}..."
      loopback loop $isofile
      probe --set isolabel --label (loop)
      linux (loop)/isolinux/vmlinuz inst.stage2=hd:LABEL=${isolabel} iso-scan/filename=${isofile} rd.live.check quiet
      initrd (loop)/isolinux/initrd.img
    }
    menuentry "Fedora ${version} ${arch} ${variant} (${type}) (rescue)" "${isofile}" "${isoname}" --class fedora {
      set isofile=$2
      set isoname=$3
      echo "Using ${isoname}..."
      loopback loop $isofile
      probe --set isolabel --label (loop)
      linux (loop)/isolinux/vmlinuz inst.stage2=hd:LABEL=${isolabel} iso-scan/filename=${isofile} rescue quiet
      initrd (loop)/isolinux/initrd.img
    }
done

Feel free to optimize it (i'm not an expert with GRUB so I don't know if all this stuff like loopback or probe needs to be in every menuentry) or to strip out the last two menu entries if you think it doesn't fit the simplicity of glim.

Failure grub-install: device.map missing - but this is unavailable in Arch Linux

Hi,
the script is executing this command to install Grub2:
sudo ${GRUB2_INSTALL} ${GRUB_TARGET} --boot-directory=${USBMNT}/boot ${USBDEV}
or
sudo grub-install --target=x86_64-efi --efi-directory=/mnt/tmp --removable --boot-directory=/mnt/tmp/boot /dev/sdd1

However, there's no device.map in /boot/grub/ on Arch Linux.
And there's no grub-mkdevicemap to create it.

Please advise how to fix this issue?

THX

Is a storage partition possible?

For example: a 128GB stick divided into two partitions, 64gb FAT32 for GLIM and 64gb ext4 for transferring and storing files. Is this possible?

could you add support of Manjaro?

it stays in the distrowatch popularity top3 for a long time already, hope you can include here

1. http://distrowatch.com/dwres.php?resource=popularity
2. https://manjaro.org/

it's ArchLinux based, since you support Arch already, add Manjaro should be easy?

The installation procedure is too complicated

I believe there's a bottleneck in making glim a more popular way of booting distros due to the overly complex way of installing it on a USB drive when compared to using dd to "cat" the image of hybrid ISOs onto the drive. It's a real shame, as it's in my opinion, could be a safer, faster, and more convenient way of booting ISOs from USB drives if only more people could take advantage of it by having a more basic way of getting glim onto their USB drives.

I'd like to suggest to introduce these features, which some of I could take care of myself if the idea is welcome:

• start issuing releases of glim which can be dd'd and then expanded to the full size of the USB stick/drive as the primary way to install glim
• include a script inside of the boot partition which could be used to git pull the latest set of config files from the GitHub repo to keep things up-to-date
• if possible, make the menu display information regarding which ISOs can be booted from the boot menu upon load (e.g. greying out missing ISOs)
• using a wildcard-based mechanism of locating ISO images to boot, to make glim more version-agnostic when it comes to releases of various distros

Add testing info

Can you please add testing information so that even people not familiar with kvm can test grub configuration easily?

Support for FreeBSD / Opnsense

Hi! Thank you for creating glim, what a gem :)

Can I use glim to boot FreeBSD distribution like Opnsense? I'd appreciate any help

archlinux doesn't work

here worked solution.

EFI install fails on Fedora

Running grub2-install --target=x86_64-efi --efi-directory=/run/media/dude/GLIM --removable --boot-directory=/run/media/dude/GLIM/boot /dev/sdc (with sudo) ...
grub2-install: error: this utility cannot be used for EFI platforms because it does not support UEFI Secure Boot.
ERROR: grub2-install returned with an error exit status.

Reported upstream in January 2021: https://bugzilla.redhat.com/show_bug.cgi?id=1917213

Happening since Fedora 34. The reason is somewhat valid: Users with secure boot enabled will be rendering their OS unbootable if they use grub2-install to reinstall their boot disk EFI files, as the signed efi files will get replaced with grub's unsigned ones.

For my own usage, I have rebuilt Fedora 37 & 38 grub2 packages with the 0144-grub-install-disable-support-for-EFI-platforms.patch excluded: http://dl.marmotte.net/rpms/fedora/

ERROR: grub2-install or grub-install commands not found.

Hello there! I got this message when I ran it on my debian machine.

Add support for Mageia

I just tried, and failed. Their dracut doesn't include any mechanism to loopback mount the iso image (such as iso-scan/filename and similar). This has already been reported upstream: https://bugs.mageia.org/show_bug.cgi?id=30206
Once support gets added, it'll be possible to add Mageia to GLIM.

Suggestion: Use loopback.cfg for Ubuntu ISOs

Most Ubuntu ISOs have a loopback.cfg menu file which should contain the correct kernel parameters to boot from the ISO. A typical grub2 menu used 'configfile /boot/grub/loopback.cfg' to use it. e.g.

menuentry "Ubuntu" {
        set iso_path=/_ISO/Ubuntu64.iso
        export iso_path
        search --set=root --file $iso_path
        loopback loop $iso_path
        set root=(loop)
        configfile /boot/grub/loopback.cfg
        loopback --delete loop
}

This means that the correct kernel parameters will always be used and you don't need to maintain the menu code,
I suggest you modify the Ubuntu inc menu so that it looks for the loopback file and uses it if it exists - if it does not exist then use the default linux and initrd commands as usual?

Windows 10 Loader Install Mode trough of Grub 2 -ISO File Path

It's possible adition attaching of windows on Grub2 Glim ISO Loader Installation for windows 7.8,10?
Can you make it ?

Void Linux support

Latest System Rescue CD ISOs have a different naming convention

The latest System Rescue CD ISO name is systemrescuecd-6.0.2.iso which isn't expected by https://github.com/thias/glim/blob/master/grub2/inc-sysrescd.cfg .

Could inc-sysrescd.cfg be updated?

EFI boot on macbook air

I was running my usb boot disk on a MacBook air that recognized the EFI boot partition.

After starting, there was only a black screen with a blinking cursor. We thought it crashed, but actually, the thing works in the background, so we could boot iso's, we just had no menu visible while in glim.

Iconsistancies with sysrescd (and possibly elsewhere)?

glim/grub2/grub.cfg refers to sysrescd as systemrescuecd-*.iso to check
but, for some reason, glib/grub2/inc-sysrescd.cfg refers to it as systemrescuecd-x86-*.iso
This can lead to issues where an iso like systemrescuecd-amd64-*.iso can make an entry appear, but not actually be openable

Possible to add EFI 32 bit?

Is it possible to add 32 bit EFI boot?

it is just add a new new efi grub install line with --target=i386-efi

alpine linux support

it would be nice to support alpine linux

[Request] Provide inc-*.cfg for debian-<version>-<arch>-netinst.iso

Hi,
I've tried to create a inc-*.cfg for debian---netinst.iso, however I failed badly.

Could you please advise how to create a working cfg for this iso?

THX

How to have iso folder on a different partition?

I want to store ISOs on a 2nd NTFS partition.

If I change the main.cfg to use:

set isopath=(hd0,msdos2)/iso

then the menuentry's do not work because of regexp failing to get variables

  regexp \
    --set 1:isoname \
    --set 2:version \
    --set 3:arch \
    "^${isopath}/clonezilla/(clonezilla-live-(.+)-([^-]+)\.iso)\$" "${isofile}"

Sintax error just on launching glim.sh

glim.sh fails just executing:
./glim.sh: línea 7: error sintáctico cerca del elemento inesperado newline' ./glim.sh: línea 7: '

It's a syntax error.

Can not install glim on my USB anymore, and it is not recognised anyway by my computers, if it works

I had installed GLIM on one of my USB sticks, but I could not boot from it. Either I got a grub rescue shell or I got only a blinking cursor, before the selection, which iso to boot.
I tried reinstalling. not possible:

Found partition with label 'GLIM' : /dev/sdh1
Found block device where to install GRUB2 : /dev/sdh
Found mount point for filesystem : /mnt
Install for EFI in addition to standard BIOS? (Y/n) y
Ready to install GLIM. Continue? (Y/n) y
Running grub-install --target=i386-pc --boot-directory=/mnt/boot /dev/sdh (with sudo) ...
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
grub-install: error: will not proceed with blocklists.
ERROR: grub-install returned with an error exit status.

So these are two issues in one, yes, but I tink they are kind of related to each other, so I keep them as one. No differences, if I enable or disable EFI support during the installation.
I will use another program until this works again.

Booting fedora server

Hi. Great stuff you have here.

The only thing I could not get to boot so far is fedora server.
After a period in a stalled state, I'm dropped to dracut.
Error messages complain about missing /dev/mapper/live-rw

Any ideas how to solve this?

Thank you.