this post was submitted on 06 Jan 2024
113 points (100.0% liked)
linuxmemes
21263 readers
1238 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
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, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
Some file managers might add the +x automatically if you choose to run the binary through the desktop environment (not the terminal)... or ask you if you'd like to mark the file as an executable (i.e. add +x to permissions).
You can't do it the same way with tar, what are you gonna execute, tar is neither a script or an ELF binary. It's like asking for a zip file to be executable, doesn't make sense. You can change the extension to .exe, but it won't run, it's not an exe, no MZ header, nothing 🤷.