So, not knowing the syntax of Linux at all, how do I set the permission to be able to view and edit a certain file withint the boot/efi folder?
The file is refind.conf - and is the config file for the refind boot OS selector application.
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It only takes a minute to sign up.Sign up to join this community
I'd like to collect some information from the comments, and add more information, in a formal answer:
refind.conf. It exists in the same directory as the rEFInd EFI binary, which is normally
refind_x64.efi(or variants for non-AMD64 architectures; or
bootx64.efior variants if it's installed using the fallback filename). This configuration file will normally be
/boot/efi/EFI/refind/refind.conf, or sometimes
/boot/efi/EFI/BOOT/refind.conf, from Ubuntu.
/boot/efi/EFI/BOOTis the fallback location, which is used when installing rEFInd to a USB flash drive, if the installation script runs in BIOS mode, or if
mvrefindis used to move rEFInd to the fallback filename. The fallback filename is used if the EFI's NVRAM-based variables don't exist or if they all point to non-existent boot loaders or boot loaders that fail. In theory, rEFInd can be installed anywhere on the ESP, so it could exist in other oddball locations.
EFI/BOOT; you'd add the standard Ubuntu ESP mount point of
/boot/efi/to the start of these values to get
/etc/fstab. See this question and its answers for an introduction to how this is done.
/boot/efi, that means that any directory or filename component after that point is case-insensitive. Thus,
/boot/efi/EFI/refindis equivalent to
/boot/efi/efi/rEFInd; but these two are not equivalent to
/boot/efiis normally on a Linux-native filesystem like ext4fs, and Linux-native filesystems are case-sensitive.
lslistings identifies executable files. Files on an ESP are not normally executable in Linux, although rEFInd and other EFI binaries are executable in EFI. Ubuntu mounts the ESP in such a way that all files appear to be executable. I suspect that's because the executable bit does double duty as a way to identify directories that can be searched/entered, so it's required to make directories useful. The easy thing to do is to ignore this. If you're annoyed by it, you can edit the mount options in
/etc/fstab, using separate
fmaskoptions, which set directory and file permissions separately, rather than a single
umaskoption, that applies to both directories and files.
lslistings. Note that you can get more detailed information on individual files' permissions and ownership by doing long listings, as in
ls -l ~/foo; however, on a FAT partition, all files will have identical ownership, and permissions will be identical with the possible exception of write permission being denied on some files. (Directories might or might not have identical permissions, depending on the mount options.)
refind.confcould conceivably be a security threat, particularly on a multi-user computer. To access this partition, you can use
sudo, as in
sudo ls /boot/efi/EFI/refind. If you're not so concerned with security, you can edit
/etc/fstabto give yourself greater access to the partition; but even then, I strongly recommend against giving universal read/write access to it. The risk of accidentally trashing a directory is too great.
/etc/fstab, you can unmount the ESP (with
sudo umount /boot/efi), make the changes, and then re-mount the ESP (with
sudo mount -a).