this post was submitted on 19 Aug 2023
542 points (92.0% liked)

linuxmemes

21304 readers
994 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, 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 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] jimmycrackcrack@lemmy.world 33 points 1 year ago (7 children)

    But you could delete system32 if you wanted, it just broke everything, I can't imagine deleting the bootloader would go particularly well for you either.

    [–] user224@lemmy.sdf.org 32 points 1 year ago (1 children)

    Deleting bootloader at least won't kill your system. You can always reinstall it.

    Also some dude on Reddit shared neofetch screenshot showing 3+ years of uptime. He doesn't need a bootloader.

    [–] frippa@lemmy.ml 5 points 1 year ago

    Bootloaders are bloat! Always thought it

    [–] octobob@lemmy.ml 17 points 1 year ago

    Well remember when that Arch update broke grub?

    I couldn't boot into my PC at all. And for whatever reason, the fix they posted on the Arch wiki wasn't working for me.

    I deleted my bootloader in a live ISO environment and installed a different one (rEFInd). It was actually very easy.

    Having the flexibility and power to do whatever you want to your system is truly something I deeply appreciate with Linux.

    [–] kautau@lemmy.world 13 points 1 year ago* (last edited 1 year ago) (1 children)

    Yeah this is sort of funny because Linux used to let you delete EFI vars, bricking motherboards, since it mounted them to the root filesystem. It’s since been patched in every motherboard, but sometimes full control is more dangerous than “haha I can just reinstall”

    https://lwn.net/Articles/674940/

    [–] original_ish_name@lemm.ee 2 points 1 year ago (1 children)

    Are there not physical ways to reset efi vars? I'm pretty sure there are

    [–] kautau@lemmy.world 3 points 1 year ago (2 children)

    There are now. In 2016, there were motherboards that didn’t properly implement the UEFI standard, outlined in the link I provided, and those motherboards would be bricked were someone to delete the EFI vars. The motherboard would never reach POST on boot

    [–] original_ish_name@lemm.ee 2 points 1 year ago

    Those motherboards have no excuse to do that. I hope people at least got their money back if they were under warranty

    Not really bricked, you could always use an external flashing tool, and they are cheap

    [–] d3Xt3r@lemmy.nz 4 points 1 year ago* (last edited 1 year ago)

    Actually, you can't, not by normal means anyway. For starters, there's the Windows File Protection (WFP) which automatically restores any deleted essential system files, and there's also the Windows Resource Protection (WRP), which prevents you from even attempting to delete those files. There are ways you can get around it of course, but even still, you can't delete files which are in use, which means you still wouldn't be able to delete the system32 folder.

    The only way to actually delete it completely, would be to boot from a second OS or a rescue environment and then delete the folder.

    [–] adamnejm@programming.dev 4 points 1 year ago

    Deleting a bootloader is a perfectly valid thing to do.

    [–] MaxMouseOCX@lemmy.world 2 points 1 year ago

    In modern installs you've got to jump through a few hoops to be able to delete system32, because normally it simply won't let you or anything running do that.

    [–] zephr_c@lemm.ee 2 points 1 year ago

    I deleted my bootloader recently. You can actually just boot the Linux kernel directly by using efibootmgr to write a custom UEFI boot entry.