Closed lemmyg closed 1 year ago
@lemmyg , may I know the reason I've been asked for a review again, since I don't find any commits after my previous review.
It was to check my reply. My /etc/fstab is mounted in /boot/efi with umask 0777 by defauft. User cant navigate unless is the root user. I think it make sense. So Im expecting your approval.
It was to check my reply. My /etc/fstab is mounted in /boot/efi with umask 0777 by defauft. User cant navigate unless is the root user. I think it make sense. So Im expecting your approval.
Sorry but I didn't get your reply on my send. Anyways, could u clarify the need of making /boot/efi readable.
added some changes, could you please have a look?
The whole guide assumes that you are installing refind in a separate partition named REFIND
. So this actually doesn't fit here.
The sole reason is that we don't want refind to clash with Windows and Grub/systemd, and it works perfectly on a separate partition.
we are not understanding each other. EFI REFIND is in a separate partition but when is mounted by Ubuntu with /etc/fstab is not navigable for any user. This is not handy is you need to do some edits in the refind config for example.
This is what Ubuntu does:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p4 during installation
UUID=18230753-2d37-4b32-96b4-a9eeca87d310 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p3 during installation
UUID=9415-19E6 /boot/efi vfat umask=0777 0 1
we are not understanding each other. EFI REFIND is in a separate partition but when is mounted by Ubuntu with /etc/fstab is not navigable for any user. This is not handy is you need to do some edits in the refind config for example.
This is what Ubuntu does:
cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/nvme0n1p4 during installation UUID=18230753-2d37-4b32-96b4-a9eeca87d310 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p3 during installation UUID=9415-19E6 /boot/efi vfat umask=0777 0 1
This screenshot shows my fstab, the UUID of all my partitions, which includes my REFIND partition, nautilus showing the refind partition as a separate one and the text editior open allowing me to edit refind.conf
I had followed the guide on the wiki and I haven't modified the fstab as per your PR, still I am able to edit the file, that too WITHOUT ROOT.
Not for me. If I set to 0777. I can't see anything from /boot/efi. It force me to become a root and then navigate. Kate for example does not allow to be opened as root.
On Mon, 15 May 2023, 5:34 pm Aditya Garg, @.***> wrote:
I had followed the guide on the wiki and I haven't modified the fstab as per your PR, still I am able to edit the file, that too WITHOUT ROOT.
— Reply to this email directly, view it on GitHub https://github.com/t2linux/wiki/pull/424#issuecomment-1548184613, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEFKRHFGSRFN6I6EMEFJBJTXGJLHVANCNFSM6AAAAAAYBGB2QU . You are receiving this because you were mentioned.Message ID: @.***>
Not for me. If I set to 0777. I can't see anything from /boot/efi. It force me to become a root and then navigate. Kate for example does not allow to be opened as root. … On Mon, 15 May 2023, 5:34 pm Aditya Garg, @.> wrote: I had followed the guide on the wiki and I haven't modified the fstab as per your PR, still I am able to edit the file, that too WITHOUT ROOT. — Reply to this email directly, view it on GitHub <#424 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEFKRHFGSRFN6I6EMEFJBJTXGJLHVANCNFSM6AAAAAAYBGB2QU . You are receiving this because you were mentioned.Message ID: @.>
But why do you want to navigate /boot/efi
, rEFInd doesn't exist there. GRUB exists there. I believe you have installed rEFInd in the traditional way.
my refind is installed in /dev/nvme0n1p3 /boot/efi/EFI/BOOT/refind.conf maybe I didn't create the EFI partition correctly?
my refind is installed in /dev/nvme0n1p3 /boot/efi/EFI/BOOT/refind.conf maybe I didn't create the EFI partition correctly?
You basically used your Linux EFI partition itself for refind as well and replaced grub. That’s also something you can do, but the guide on the wiki makes user another partition for REFIND. In short, there are many ways to get Refind working.
You probably must have used Linux itself to install Refind instead of involving macOS.
So your use case differs from those who follow the guide and thus this addition isn’t required imo.
no, I installed refind from MacOS. Im going to remove this bit if is not clear and we move on. I though other users have same issue
done
@Redecorating , lgtm now
adding some useful tricks new buildin microphones dsp config