LOL not sure if this is because Windows warns you about dumb shit or because Linux will totally just allow you to nuke your entire OS with a single command.
Windows constantly says "this could harm your computer." Just about any time you install software it does.
Remember when Linus Sebastian blew up Pop!_OS? As a Windows user, "This is likely to break your computer, do not do this unless you absolutely know what you're doing. To proceed, type "Yes, do as I say."" is something to walk right past.
Damn so thats why he ignored the warning... I never understood how he could write Yes, do as I say! by ignoring the obvious warning.
It seemed like he intentionally brick the system just to complain linux is bad
I've done big forensic write-ups of it in the past and mapped it to the FAA's accident chain model. It just so happened that he was using a distro with a weird forked DE (Pop!_OS) and just so happened that the version of the Steam package in the apt cache from when the install image was made was bugged in such a way that it would uninstall Xorg, and it just so happened that Pop!_OS didn't run an apt update when launching their GUI app manager.
When Linus saw "failed to install Steam" he turned the petulant child up to 11 and started bitching about how you always have to use the terminal in Linux, and instead of googling the error message to find out "do an update and try again" he found a page that told him how to sudo apt install steam. Most instructions like that tell you do to an apt update before an apt install, so I don't know if he either aggressively skimmed, deliberately ignored the update command because he's used to how painful Windows updates are, or if he found a source that didn't include it.
APT spat out a lot of stdout about all the packages it was going to remove, with a highlighted plaintext warning at the end which he failed to read or failed to heed.
Linus' bad attitude was a major contributing factor to the incident.
I too wrote something similiar here https://lemmy.dbzer0.com/comment/9956561
But didn't expect it was Windows mentality to ignore all hazardous warnings
I think it played a part.
To be fair, you can nuke your entire OS with a single command on Windows too.
Don't even need a command. I've seen people brick their windows install messing around with registry keys. Most of my coworkers and friends think I'm some sort of wizard because I follow the instructions to the letter if I have any reason to run regedit.
This is what got me started on linux lol
Yes?
Windows error messages are usually something to pay attention to if they generate a popup. But you can ignore most errors and warnings in the event viewer.
Linux is the same. If you get a popup, look into that, but if you see warnings or errors in a logfile then they can most likely be ignored if the app is working
Bailing out. You are on your own. Good luck!
Well fuck...
WARNING: /boot appears to be a separate partition but is not mounted. You probably just broke your system. Congratulations.
Is that a real error message in Linux?
Yes
This principle applies to the GNU C compiler also. Any other compiler is going to complain at you for not adhering to their stupid style guide, or for not using their proprietary "mEmOrY sAfE" libraries. But if GCC is giving you warnings, you darn well better fix something.
Yes, do as I say! đź—ż
uninstalls essential package
Why is my system broken? :O
LTT moment
the average brain on Windows...
"wdym a different OS doesn't behave exactly like Winsows? That just means it's bad!"
"It's Linux' fault that my proprietary software/configurator for overpriced hardware gimmicks isn't working and definitely not just the vendor not giving enough of a shit to provide support (or at least help with community drivers) on other platforms as well!!1!"
Windows warning is like the check engine light in your car, ignore till it starts being a problem lmao
For the record, if your check engine light is ever blinking, you need to immediately shut off your engine.
Shit is going very very wrong in your engine at that point, to the extent that it might cause an energetic catastrophic failure.
Interesting, I've never heard of that. What does it blinking signify?
In my case it meant the cilinders were scrapping against the block with zero lube
My wife hates it when that happens
It can mean a misfire too.
I had an old accord that basically lost a cylinder (blew a valve or something) but could still drive down the road with check engine blinking because that cylinder was “misfiring.”
It happened far away from home too. I drove several dozen miles with my unintentional 3 cylinder swap.
To be fair, it can also mean "one of my fucking radiator fans is not responding quickly enough to computer control"
Which was not a fun experience when that happened to me, full fucking BEEP BEEP BEEP MOTHERFUCKER with a check engine and a STOP sign blaring on the digital system display panel, made me panic out of my mind because a radiator fan was a removed
Imminent catastrophic failure.
Misfiring in my experience
So you're telling me I should just turn up the volume instead of fixing my install ?
My favorite error message of all times:
You don't exist, go away!
If you have a problem just sudo it away.
sudo rm debt
Throw in an '-rf' for good measure
My broken pipe on update error doesn’t come up often enough to properly deal with and every possible cause I have found hasn’t applied
One you actually care about while the other... blows wind.
Heck, I have errors in windows log that are just "sure, let's move on".
This post not written by someone who has ever run ‚systemctl -p3 —since today’
I use Arch btw
Sister communities:
Community rules
Please report posts and comments that break these rules!
