ZWQbpkzl [none/use name]

You set everything to /boot because that’s the mount point of your boot partition. /dev/sda1 or whatever gets mounted to /boot

• Grub will make /boot/EFI/<NAME>/grubx64.efi and will dump a bunch of files to /boot/grub.
  • For grub you edit configs in /etc/default/grub and generate the actual configs with grub-mkconfig
• Bootctl will make /boot/EFI/systemd/systemd-bootx64.efi and loader configs to /boot/loader
  • Configs for bootctl are edited directly in /boot/loader/
• Mkinitcpio will dump .img files to /boot/

If you mount your boot partition to /boot/efi instead of just /boot, you’ll have to specify that with command line flags for each of those commands. At first that’s easy enough. grub-mkconfig and grub-install only need to be run once. I believe that the same for bootctl. mkinitcpio however runs via a pacman hook whenever you update your kernel. You’ll have to ensure that the hook doesn’t default to /boot. I don’t know how to do that though.

Better off to just accept the difference IMO. Things will “just work”.

Can’t explain why your file browser doesn’t work and I don’t suggest logging into your desktop as root. You should take steps to make that impossible, in fact.

Now you said this doesn’t work

sudo chmod -v +x filename.sh

And that’s baffling. What is the exact error message and output of that command? Also is the file in question in a weird place or on a weird filesystem?

Remember how Landlords did price fixing by outsourcing their pricing to a third party algorithm? Well now we’re doing that with groceries.

RealPage for grocery stores