this post was submitted on 10 Jan 2025
393 points (95.8% liked)

linuxmemes

21801 readers
390 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 2 years ago
    MODERATORS
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Kazumara@discuss.tchncs.de 17 points 4 days ago* (last edited 4 days ago) (1 children)

    In A UEFI World, "rm -rf /" Can Brick Your System

    efivars are made read only by the kernel. That firmware bug (!) was worked around in the kernel years ago.

    https://github.com/torvalds/linux/blob/master/Documentation/filesystems/efivarfs.rst

    Specifically in 2016: https://github.com/torvalds/linux/commit/ed8b0de5a33d2a2557dce7f9429dca8cb5bc5879

    [–] Jumuta@sh.itjust.works 3 points 3 days ago (1 children)

    uefi is cringe anyway, reject uefi and return to grub in the system firmware

    [–] Kazumara@discuss.tchncs.de 2 points 3 days ago (1 children)

    Firmware is one step before.

    BIOS, UEFI, coreboot, or whatever weird code runs on a Raspberry Pi's GPU to load your system, those are firmwares.

    The firmware is what starts your bootloader; grub, BOOTMGR, u-boot, etc

    [–] Jumuta@sh.itjust.works 1 points 3 days ago (1 children)

    even if my grub is in the system eeprom?

    [–] Kazumara@discuss.tchncs.de 1 points 2 days ago (1 children)

    Oh I've never heard of such a setup. But that does muddy the lines a bit, I can see the argument for calling it part of firmware then.

    [–] Jumuta@sh.itjust.works 1 points 2 days ago (2 children)

    yeah it's goofy, you can embed grub in coreboot cbfs and load straight into it, skipping the bios/uefi stage. it's a bit difficult to set up (and you need coreboot supported hardware) but when you get it working the boot times become really quick

    i just realised though that you can embed Linux into cbfs as well, does that then mean that Linux could be my kernel and firmware at the same time?

    [–] uranibaba@lemmy.world 1 points 1 day ago

    you can embed grub in coreboot cbfs and load straight into it, skipping the bios/uefi stage.

    Why would someone do that? *keeps reading*

    boot times become really quick

    Now I almost want to try it out.

    [–] Kazumara@discuss.tchncs.de 1 points 1 day ago

    Wow very cool. Thanks for that link, I had no idea coreboot was so flexible!