this post was submitted on 05 Dec 2023
955 points (100.0% liked)
linuxmemes
21263 readers
503 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
But, in that example:
If I'm the admin it doesn't matter I use it.
If I'm not it's not my problem that I could get more privileges than allowed. I'd probably even use the possibility then. ๐
So it poses a risk if you allow none-admin users to do that on your system, but I still don't see why I must choose to not use nano as root myself. ๐
Anyway, good practice to me is ease-of-use instead of with 7 protections against things that rarely happen.
Like, I'm pretty sure you are better protected from burglars if you also lock all doors inside your house, but I'm definitely not doing that either. ๐
Edit: Also, if you have users on your system, just chroot/vroot/lxc them, so they be free to 'sudo nano' too... ๐
I appreciate all the answers on what started out to mostly be a joke (the first comment, I'm not saying the rest was, I actually do mean my follow-up discussions and am enjoying them more than I should). ๐
Anyway, first I must disagree with sudo being useless in a single-user environment since some services have non-user (nologin) accounts as which you still need to run things sometimes, so sudo is commonly useful in single-user environments (though you could technically go set bash for those, I suppose.)
But yeah, I'm already used to "bad practices" as I have been using linux for 24 years now (when it still was it's predecessor 'pico' ๐ ) (I said over '10' years in an earlier comment, but I just realized I'm 40 and still calculated from 30. ๐ Wishful thinking. ๐ ) in what is assumed a bad practice, not only without any problems, but even because it never gave me problems.
Might be an age thing too, but I hold on to ease of use over best-practice, especially if it hasn't failed me in two decades and a half. I think it would take an actual attack on me abusing this behavior for me to stop doing it by now... And even then, I installed linux so many times in my life, even that seems more musclememory and not such a hassle anymore... ๐ At least I could make use of my backup system for once then... ๐