this post was submitted on 22 Nov 2024
227 points (94.5% liked)

linuxmemes

21601 readers
561 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 2 years ago
    MODERATORS
     
    top 25 comments
    sorted by: hot top controversial new old
    [–] superkret@feddit.org 44 points 1 month ago* (last edited 1 month ago) (2 children)

    WARNING:

    Don't ever do this on a current bare metal system!
    Even if you have everything backed up, plan on re-installing anyway, and just want to see what happens.

    On a modern EFI system, recursively deleting everything (including the EFI path) has a chance of permanently hard-bricking your computer!
    https://github.com/systemd/systemd/issues/2402

    [–] 30p87@feddit.org 11 points 1 month ago (1 children)

    But Windows 95/XP does not run on EFI systems, so they aren't used in the BRD. We're save!

    [–] SanctimoniousApe@lemmings.world 5 points 1 month ago (1 children)

    Plus no ads, and MUCH more efficiently written code to boot - win-win!

    Just don't hook it up to the Internet...

    [–] 30p87@feddit.org 5 points 1 month ago

    We only need fax anyway. So we print stuff out, and fax it.

    [–] A_Very_Big_Fan@lemmy.world 9 points 1 month ago (1 children)

    Why would it be a permanent brick? Shouldn't a flashdrive and access to BIOS be enough to get your PC working again?

    [–] superkret@feddit.org 24 points 1 month ago* (last edited 1 month ago) (2 children)

    In a properly implemented EFI, this should be possible. But there have been cases with improperly implemented EFI in some laptops/motherboards where the computer won't POST after /sys/firmware/efi/efivars/ was nuked. In that case, accessing BIOS or booting from a flashdrive isn't possible anymore.

    [–] Acters@lemmy.world 5 points 1 month ago* (last edited 1 month ago)

    I have a little flash chip reader and backed up my bios and can flash it on the laptop. Even modified it to unlock the advanced menus Lol

    But th rm rf thing didn't nuke it so I guess I'm safe either way

    [–] trespasser69@lemmy.world -1 points 1 month ago (1 children)

    Bro, BIOS is located on motherboard and EFI variables only needed to boot an OS.

    Just install bootloader and OS in drive

    [–] superkret@feddit.org 7 points 1 month ago

    Bro, several people bricked their pc that way. I'm no expert, just throwing out a warning not to do dumb shit.

    [–] boredsquirrel@slrpnk.net 34 points 1 month ago (1 children)
    [–] SpaceCadet@feddit.nl 2 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

    In Linux, everything is a file.

    So if you have a problem, it will be in a file somewhere.

    So logically every problem can be equalled to one or more files.

    Therefore it follows: no files = no problems. And no problems = no headache.

    [–] boredsquirrel@slrpnk.net 2 points 3 weeks ago

    Everything that does something is a file. No files, no existence ;)

    [–] steventhedev@lemmy.world 15 points 1 month ago (1 children)

    Once upon a time, I accidentally created a folder named "~" in my home folder (the company provided scripting framework would inconsistently expand variables, so the folder had a ton of stuff inside it).

    I ran "rm -rf ~" and only panicked when I started to wonder why it wasn't taking too long.

    Good news is that it only managed to get halfway through my local checkout of aosp before I stopped it. Bad news was that it nuked most of my dotfiles.

    [–] Ziglin@lemmy.world 1 points 3 weeks ago

    You forgot the -r just like always.

    [–] Infernal_pizza@lemmy.world 8 points 1 month ago (3 children)

    Why doesn’t rm -rf /* also require —no-preserve-root? That seems just as easy to type accidentally and will just nuke your system without asking

    [–] savvywolf@pawb.social 16 points 1 month ago (1 children)

    It's actually harder to detect that. The * is expanded before the arguments are sent to rm, so it just sees a list of directories like /bin /usr /dev /sbin /home and so on.

    You could implement logic to detect that case, but at that point you're just playing whackamole.

    [–] zea_64@lemmy.blahaj.zone 2 points 1 month ago* (last edited 1 month ago)

    I believe zsh catches this and makes you confirm.

    Well, that or one of my plugins, I'm not sure.

    [–] superkret@feddit.org 8 points 1 month ago* (last edited 1 month ago)

    If you try to put in safeguards for every possible system-nuking command someone with root rights might type, you'll never get done.
    When you're typing "rm -rf" as root, you should immediately stop and triple-check what you're doing.
    Cause either there's a safer way to do what you want to do, or what you're trying isn't a good idea in the first place.

    (Even when you want to delete lots of stuff in root space, a better way is to use find. You can use it to look for and list the files you want to delete. After you've checked its output and verified that those are the correct files, just cursor-up to get the same find query again and add --delete at the end)

    [–] nichtburningturtle@feddit.org 2 points 4 weeks ago (1 children)

    Can confirm. Accidentally did that a few weeks ago.

    [–] Ziglin@lemmy.world 2 points 3 weeks ago (1 children)

    I am curious how. If you were deleting everything in the local directory you wouldn't need the ./ before the asterisk, so was it some sort of piping that messed it up?

    [–] nichtburningturtle@feddit.org 1 points 3 weeks ago

    I was cleaning a usb and didn't want to reformat it.

    [–] fmstrat@lemmy.nowsci.com 3 points 1 month ago (1 children)

    Obligatory trash-cli alias.

    [–] patrlim@lemmy.blahaj.zone 1 points 1 month ago (2 children)
    [–] illectrility@sh.itjust.works 3 points 1 month ago

    rm is like "delete permanently", trash-cli is like regular delete - it moves to the trash bin. Many people like making an alias so rm runs trash-cli to prevent accidentally permanently deleting data

    [–] autonomous@lemmy.ml 1 points 1 month ago

    rm deletes files the normal way everyone who actually knows unix expects it

    trash-cli tries to bring the comfort of windows to linux for the crybabies who like to delete files so recklessly that they end up screwing themselves later. (the same people who don't ever take backups or snapshots)