• Dr_Willis@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    15
    ·
    edit-2
    10 months ago

    I am reminded of the ability MANY years ago to write the kernel file directly to a floppy disk, or start of a hard drive and somehow being able to boot that way.

    I just can’t recall how I did it, or WHY I did it.

    Back when the kernel would fit on a floppy disk. I am truly showing my age.


    6 yr old grandson found a box of old floppy disks and was asking what they were. He started stacking them up making card houses and roads for his matchbox cars. Glad he got some use out of those recycled AOL floppies.

  • AutoTL;DR@lemmings.worldB
    link
    fedilink
    English
    arrow-up
    6
    ·
    10 months ago

    This is the best summary I could come up with:


    Fedora 40 is eyeing the next phase of its unified kernel (UKI) support within the distribution that will include the ability to support booting to unified kernel image files directly without having to go through a traditional bootloader like GRUB or SD-Boot.

    The second phase of Fedora’s unified kernel support is looking at a boot path from the EFI SHIM to UKI directly without any bootloader present.

    The UEFI boot configuration will get an entry for each kernel installed, newly-installed kernels are configured to be booted once but will then be made permanent after a successful boot, and also enabling UKI support for 64-bit Arm (AArch64).

    This latest UKI work for Fedora will lead to better UEFI Secure Boot support, better supporting TPM measurements and confidential computing, and a more robust boot process.

    Those interested in the latest UKI efforts for Fedora 40 can see this Fedora mailing list thread with more details.


    The original article contains 153 words, the summary contains 153 words. Saved 0%. I’m a bot and I’m open source!

    • Flaky@iusearchlinux.fyi
      link
      fedilink
      English
      arrow-up
      24
      ·
      edit-2
      10 months ago

      It basically means instead of relying on a bootloader (e.g. GRUB or systemd-boot) the computer boots the kernel directly. Generally there should be no change besides having to use the BIOS menu to manually select a kernel.

        • Flaky@iusearchlinux.fyi
          link
          fedilink
          English
          arrow-up
          8
          ·
          10 months ago

          No problem! :)

          FWIW, a lot of the DIY distros (Arch and Gentoo being the ones on most minds) allow this already so it’s nothing new. It’s just Fedora implementing it that’s new I guess. If you’re curious, the term to search is “EFISTUB”.

        • Flaky@iusearchlinux.fyi
          link
          fedilink
          English
          arrow-up
          0
          ·
          10 months ago

          Presume so, that’s what the article claims:

          This latest UKI work for Fedora will lead to better UEFI Secure Boot support, better supporting TPM measurements and confidential computing, and a more robust boot process.

            • Flaky@iusearchlinux.fyi
              link
              fedilink
              English
              arrow-up
              1
              ·
              10 months ago

              I’d imagine that if you want a bootloader, the option is there as well. I can’t imagine Fedora just doing away with that unless the bootloaders themselves are unmaintained.

    • V ‎ ‎ @beehaw.org
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 months ago

      Yes, in my opinion. The configuration of grub (boot loader) is just another step to go wrong, and this will eliminate that possibility. Additionally, it will prevent stupider operating systems (cough Windows) from accidentally overwriting the boot loader during an update.

  • ikidd@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    10 months ago

    Is there not issues with filling up the NVRAM with efi entries, even if you’re deleting old ones? I’ve bricked a computer by distrohopping so many times it couldn’t write new entries.