Re: isues with f40 install

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 7/4/24 11:37, Tim via users wrote:


If you install other OSs, they should do something similar.  You'd have
something like:

    ... EFI/debian
    ... EFI/fedora

Which should keep all the OSs separate from each other.

If you wanted dual booting different versions of Fedora, without one
stomping on the others files, it might be worth naming the directories
more uniquely.  I'm not sure if there's any straightforward way to do
that.

e.g.  ... EFI/fedora39
       ... EFI/fedora40


At first I thought something similar but that the 36, 40, etc would be subdirs of fedora. Not so...

After some (a lot) searching I found bits that help understand what is going on. The efi spec is not helpful in describing the EFI structure but is more about the byte/bit layout of the motherboard's NVRAM.

/boot/efi/EFI contains vendor directories and one generic called boot. Names are case insensitive. I've seen MICROSOFT, fedora, Fedora, Debian, debian, DEBIAN, boot, BOOT, and so on.

Within each of the vendor directories there are efi binaries, and a bootx64.csv which tersely describes what is there. E.g. here's one for debian:

  shimx64.efi,debian,,This is the boot entry for debian

Lastly, there is a config file specific to what each vendor uses. Most of the linux distros use grub so for those you will find grub.cfg.

Whenever a vendor's product is installed successfully the system runs the os-prober and rebuilds, in our case, the grub.cfg, with menuentries for each that it finds. That is how multiple version co-exist: not as entries in EFI but as entries in the appropriate config file.

There are a couple of levels in the boot process. First one is the BIOS which offers different devices, then proceeds to the loader that handles the selected device, which then runs that loader. That is the one that offers e.g. fedora36, fedora40, etc.
--
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux