On Sun, Aug 28, 2022, at 7:38 PM, Stephen Morris wrote: > Hi, >     /etc/extlinux.conf is flagged as missing flagged as missing by what? This file is normally not created on any Fedora variant I'm aware of. It could be a legacy file. >     /etc/grub2.cfg and /etc/grub2-efi.cfg both of which point to the > same file also display the same way as /etc/extlinux.conf, but in this > case the file pointed to actually does exist, and is linking to > /boot/grub2/grub.cfg, which I regularly write to with sudo and > grub2-mkconfig, There is no reason to regularly replace grub.cfg, it's a static file these days. The files that change are drop-in files found in /boot/loader/entries and can be modified with grubby per examples at: https://fedoraproject.org/wiki/GRUB_2#Changing_kernel_command-line_parame...

sudo/root is required to access the grub subdirectory because the permissions are locked down. I would guess since there can be encrypted grub passwords (and possibly other similar stuff) in there that is why it is locked down.

On Sun, Aug 28, 2022 at 6:38 PM Stephen Morris <samorris(a)netspace.net.au&gt; wrote: > Hi, > /etc/extlinux.conf is flagged as missing, the file is displayed in > red and the link is shown in white text on a red background. As > mentioned in another thread on this list that file actually is missing. > /etc/grub2.cfg and /etc/grub2-efi.cfg both of which point to the > same file also display the same way as /etc/extlinux.conf, but in this > case the file pointed to actually does exist, and is linking to > /boot/grub2/grub.cfg, which I regularly write to with sudo and > grub2-mkconfig, but I have also found that I need to use sudo to browse > /boot/grub2. Is it normal for links to be flagged as missing when sudo > is required to list the contents of the directory and why is sudo > required to list the contents of /boot/grub2 when I don't need sudo to > list the contents of /boot? /boot/efi seems to be in the same situation. > > regards, > Steve > _______________________________________________ > users mailing list -- users(a)lists.fedoraproject.org > To unsubscribe send an email to users-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

On Wed, Aug 31, 2022 at 6:02 PM Stephen Morris <samorris(a)netspace.net.au&gt; wrote: > On 30/8/22 01:16, Roger Heflin wrote: >> sudo/root is required to access the grub subdirectory because the >> permissions are locked down. >> >> I would guess since there can be encrypted grub passwords (and >> possibly other similar stuff) in there that is why it is locked down. > I did check the acl on the folder and noticed it was locked down to > root. I could put an acl on the folder to make the folder readable by me > without enabling reading of the contents of the files in that folder, > but is that the only way to stop ls from flagging a file as deleted when > the parent folder is locked down? > > regards, > Steve Pretty much. From the command run as a real user the file does not exist because of permissions, but the command has no way to know that so it is simply missing.

_______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue