On Sun, 2019-07-07 at 00:47 +0530, Suvayu Ali wrote: > I have never quite understood how UEFI worked. Initially I stayed > away from it because of secure boot issues. Do you think I should > put in the effort to move to UEFI? UEFI is the very basic operating system loaded into your motherboard, stored in firmware. It does a similar role to BIOS. It's how your OS uses the hardware, at least during the boot-up phase. You adjust it through the motherboard's interface, in a similar way that you would have changed any BIOS settings. But you probably completely ignore it, most people probably never even look at it. They plug in drives, run the installer, and the installer does what it wants to, and you get a running system. You probably mean, do you need to learn what's involved with booting up Linux using it. Well, BIOS is on the way out, UEFI is the way it's currently heading, until someone decides to reinvent the wheel, yet again. So, yes, you're better off to find out about it. But, if you don't dual boot, Linux will probably just install and run, without you having to do anything with UEFI. And if nothing fails, you probably won't have to do anything with it either. But you want to know some basics for the day you have to fix something. Securing boot, using the features of UEFI, is another thing. If you enable that feature, and you create custom kernels, etc., then you'll really need to know about it. -- uname -rsvp Linux 3.10.0-957.21.3.el7.x86_64 #1 SMP Tue Jun 18 16:35:19 UTC 2019 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
