Linux: i can't stop dumb users (me) completely destroying everything with a bad console command
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- 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.
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, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
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 remove France.
I did this. Luckily, nothing was lost because I was only using it to learn at the time. It oddly boosted my confidence because if I could break the OS, I could learn how to use it.
I'm pretty sure that if you use elevated privileges to run commands you don't understand, you can break Windows just as much as you can break Linux. Windows might pop up an extra "Are you sure?" box or two though. It's been a while since I did anything on that OS.
You can, but on windows there is no need usually to run these kind of commands.
What happened was that years ago I was trying out Ubuntu but didn't like the UI, so I followed some steps from someone to replace the gnome or whatever with something else (kde?), but then the ui completely broke down.
Given how fickle that system is in Ubuntu, I was probably using legit sources for the commands, but they were not fully up to date and something went wrong.
Ironically, something similar happened lately on my Ubuntu virtual machine, where the file explorer has rendering issues, but tbh I think this time it was because the virtual machine disk space became full mid update, so kind of my bad too.
The only thing keeping me in windows these days is that I just really like the UI, but I think next time I need to format (which admittedly might be year or two from now) I might move to GraphyOS anyway.
A great learning experience to not copy paste commands yoj don't understand.
Breaking things is a valid way to start learning. Reading man pages is very often difficult and confusing for new users. And much of the documentation is crap anyway-- it's why distro forums exist. And I'm from a time when distro upgrades/updates were sometimes dicey, (they still can break things on occasions), and you complied your kernel and drivers from scratch.
Please, I don't understand a single command I'm putting in. I'm just copying whatever some nerd posted on a message board.
But that's in my experience sadly very necessary especially in the beginning when you are getting into Linux. So getting into Linux has quite a steep learning curve because not knowing what you are copy pasting can have terrible consequences, but understanding everything before you copy paste is very demanding.
When out comes to my main rig, i never had the experience of everything just working out of the box. There was always something that required me searching for obscure fixes, hoping for the best.
Installing old Linux applications IS a problem. They're available only if someone repackaged them for newer distros. If not they can't run anymore because of dependencies mismatch.
This is a good reason for static linking. All the dependencies are built into the binary, meaning it is more portable and future proof.
We don't need flatpak for this!
And harder to fix vulnerabilities in a linked library, and more bloat in both storage space and memory used.
Trade-offs!
I'll take a program that isn't getting updates anymore or simply wasnt working in my modified environment using slightly more ram and storage over it not working at all.
I have firsthand experience with videogames made for one flavor of Linux not working on my machine due to dependency hell.
For occasional programs, or things like games, I'll agree. For most software I use, no thanks.
Speaking of not being able to delete system apps, a friend of mine with a Pixel phone says Google Play cannot be uninstalled from it. Anybody know for sure?
You can via adb ( android debug bridge ) , no root needed, but you need a pc or shizuku. Although if he has a pixel device he should just install GrapheneOS imo. Edit: puxel -> pixel