Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just upgraded my pop_os to 21.04 and I use refind bootloader for my dual boot laptop. I wanted to change my refind theme and was trying to access /boot/efi directory but was unable to do so, as I am getting an error. Check the screenshot.
I just upgraded my pop_os to 21.04 and I use refind bootloader for my dual boot laptop. I wanted to change my refind theme and was trying to access /boot/efi directory but was unable to do so, as I am getting an error. Check the screenshot.
I would guess from that screenshot that since the efi directory is vfat and not a standard linux file system, as well as being accessible only to root, that the command line access would be the better route.
I would guess from that screenshot that since the efi directory is vfat and not a standard linux file system, as well as being accessible only to root, that the command line access would be the better route.
Yes, the directory is accessible through CLI but not through the inbuilt File manager application in the latest pop_os, although it worked through the app in previous version.
Yes, the directory is accessible through CLI but not through the inbuilt File manager application in the latest pop_os, although it worked through the app in previous version.
The file manager should NOT have had access in the earlier version since the permissions only allow root access.
Using thunar as the root user can easily become a very bad idea since it would allow manipulation of system files and directories with a click of the mouse.
The file manager should NOT have had access in the earlier version since the permissions only allow root access.
Using thunar as the root user can easily become a very bad idea since it would allow manipulation of system files and directories with a click of the mouse.
Yes, I know. But I am not using root accessed thunar for everyday use.
I had to modify some system files for setting theme for refind.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.