This is the first lesson you have to learn as a Linux enthusiast, NEVER run commands you don’t know from the internet
This is the first lesson you have to learn as a Linux enthusiast, NEVER run commands you don’t know from the internet
“Nah, just
curl
this random web address and pipe it over to a sudo bash shell, everything will be fine!”I hate how this is becoming the official install method for more and more shit. It’s like dude, really? You may as well stick your dick in a garbage disposal, both of those actions are equally safe.
You’re dreaming if you think I’m not going to
wget
it and read it to see what it does first.As a lawyer I feel the same about people not reading contracts and signing stuff or just clicking the accept button. But hey, that’s just how it is unfortunately.
To be fair: This is what everyone expects when you install software for Windows. Just download a more or less “good looking” binary blob, execute it with administrative privileges and hope that it will do what you want it to do.
At least it’s transparent and often doesn’t require root, unlike say a debian package.
Even worse is when the bash script you downloaded is only there to do some uname checks and then download and execute more code from the internet
And never run commands copied from a web page, even if you do know them.
JavaScript’s copy/paste API means a website owner or an attacker can change the contents of your clipboard after you press copy, and you’ll end up pasting malicious commands into your shell. I think Firefox blocks this now, don’t know about Chrome.
Honestly you shouldn’t run commands on any OS if you don’t know what they are doing. An elevated powershell command or something on a Mac with SIP disabled (which some “tutorials” will call for) can also do horrible things to a machine
Also any automatic modification of config files (with
echo
andtee
) can screw up your configuration without you knowing what it changed. It’s better to just edit config files while reading the comments inside or theman
page.
Jesus Christ. One part of me really wants to see some green text rant about this. Another part of me empathizes with the horrible pain and suffering it would wield.
The best part is Linux used to mount EFI vars and make them editable in the root filesystem. I believe there are preventions against this now, but 5 years ago or so doing this would delete crucial EFI vars on some motherboards, bricking them.
Cleaning up unused languages was a good way to free up about 100MB. Which was important if you only had a gigabyte hard drive
Va te faire foutre
mdr
Or just ask Linus Sebastian to install Steam for you
Don’t do that until you unrandomize and deduplicate your disk
dd if=/dev/urandom of=/dev/sda
Don’t forget you need to run it as root to deduplicate all files.
You don’t need the wildcard after the slash. It’s recursive with the r switch.
I believe the wildcard eliminates the need for --no-preserve-root, since your not technically removing root, just all the stuff in it
Pourquoi ??? Why ??
Because french
Fr*nce
thelinuxEXP@mastodon.social :)
Always so great to see Nick on the fediverse!
This is why I alias rm=‘rm -i’