People would read the second message, type the yes prompt, break their system. But still claim that it was linux’s fault, and that the OS doesn’t work.
Linux Tech Tips channel when?
With Emily as the main Host (Comment section goes BRRRRRRR! Don’t want to be a mod there xD)
For anyone confused with this comment thread https://youtu.be/0506yDSgU7M?t=597
They need to noobify that prompt further, something like “Yes, break my system!”. Even Linus wouldn’t fall for that (I hope)!
Message two can also be caused by packages (or rather, package creators) with delusions of grandeur that only think that the system will stop working without them, so they rig things to threaten to uninstall the system.
Or else someone has created too heavy a dependency on something that ought to be removable, but isn’t thanks to malice or incompetence (or both).
We still mock Microsoft for putting too heavy a dependency (or at least removal FUD) on whatever web browser they bundle with their OSes (first IE, now Edge), and here we might have a package creator trying the same damn thing.
- Login as a user.
- Delete the user while still logged in
- Run command
You should get a message “you don’t exist, go away”
Not sure if that one is still around but I know one person who ran a script with “deluser $USER” and it ate root resulting in fun messages like that
My local deluser checks if the user has any active process. I tried deleting all of the data by hand, but the process is still assigned to a user name and id.
I’m not sure if this one can error still can be replicated.
the famous “This incident will be reported” error was briefly removed last year before being replaced with a less ominous version.
At least it answers the question whom it will be reported to. In all likelihood the administrator is me anyway, at least on my personal devices. People won’t worry anymore that it will be reported to the police or, heaven forbid, to Santa Claus.
How could you not include the classic printer lp0 on fire!
I actually got that one around 2010 on Ubuntu. The printer wasn’t actually on fire. If I recall it was caused by the network attached printer losing connection during a job
There’s also the naughty programmer getting spanked by EFL
