Customized user_commands.bash and issues with boot loader choice, and fstab mount order

Considering this code I’m currently using:
https://0x0.st/XGTB.sh

I’m having issues where the boot loader choice chosen by default still isn’t grub, but systemd-boot. Even though, line 48 of the user_commands.bash is changing the line for packageChoice accordingly. I’ve tried values like grub and Grub, so far, with no success in defaults changing.

Secondary issue is, you may notice in the same script, I have updated the partitionLayout to include my own /boot as ext4, and efi on /boot/efi, but I noticed a post-install problem once I did this, in /etc/fstab.

/boot/efi was being mounted before /boot. I can manually fix this, and I can even consider making this change in my 1strun script also incorporated into the script to automate this fix, but, I’m wondering why, exactly, this is happening, and if it can be fixed, properly.

The qml modules are interesting. While there are generic configs for the qml modules, they are mostly customized by modifying the code directly. So, that value isn’t being read by anything.

You need to modify this file on the ISO: https://github.com/endeavouros-team/calamares/blob/calamares/src/modules/packagechooserq/UEFI.qml

By changing the checked booleans for each option.

Hmmm… Interesting. Yeah, not something I want to modify then. Though I do wish I could.

On a different note then. There’s sometimes packages, like iio-sensor-proxy, and maybe some specific modifications I’d like to do on a per “Computer Name” or hostname bases. In the post-install script somewhere, is it easily available to get the target hostname of the system being installed, so I can potentially add those types of things to my script, or would that be better off in my 1strun script?

That script runs in the target system at the end of the install. You should be able to grab the hostname via normal means at that point.

Yep! I was able to pull it straight from /etc/hostname, a reasonable method indeed.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.