this post was submitted on 07 Mar 2024
1412 points (92.9% liked)
linuxmemes
21355 readers
1402 users here now
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 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
sudoin 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Exactly. OP's meme makes no sense to me. My experience has been that using Linux is a never ending series of file not found and access denied errors.
And you never dug any further to see WHY you're being denied access or WHY that file is not found.
Simple example, some distros will block regular user access to
/root. That doesn't mean that you can't access those files, it just means that YOUR user can't see them WHILE you're logged in with that user... which is why bash file/dir completion will not work if you cd to/root/path/to/dir. Log in as root in the terminal and it works just fine. Some even might out right not see the files if you're logged in as a user, instead of root, regardless if that user in the sudoers file or not (you type in the exact path to a dir/file in the terminal and it won't open/cd to it). In those cases, even sudo won't work for some things, you just HAVE TO work with root.To be honest, this is very rare and has happened to me like once or twice (on some distros). In most situations/distros, sudo will work just fine.