this post was submitted on 07 Dec 2023
1131 points (98.4% liked)
memes
9615 readers
2690 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
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
As if *nix doesn't have file permissions? I see this more on my *nix systems than anything else lmao.
so 755 that muthafuck?
Just embrace heaven and 777 it.
Bold, I like it.
You see it because on GNU/Linux (and other *nixes) you have good reason to get at protected files if you administer the machine, and because you forget to sudo things
Where Windows rarely needs proof the current user is still authorised
I'm not going to lie that's never really been an issue for me. (I have root)
I sometimes get into some kind of fight, if I'm not really logged in as root and have to do things the sudo way. I'm not so deep in Linux, so I'll ask bluntly:
Is it always a user error if you have trouble doing things with sudo or is it possible that the way sudo was configured for your user makes your life hard?
Over the years i had lots of clients, where i would be given sudo rights and the experiences doing so were pretty diverse, ranging from "feeling at home and just typing away" to "am i fucking crazy? Nothing goes as expected"
I really depends on what you are trying to do. Most things should not need root so if you find yourself using sudo all the time you may be over using it.
Maybe you messed up permissions?
The machines were always set up by the client's team, mostly not being anymore onboard. I only got the server address + credentials, so i could check for web related issues on them. I am experienced enough to know how inexperienced i am with things other than my area of work.
Sometimes they had issues on machines they only had credentials to, but no one to fix. The main sudo trouble i sometimes had, was when trying to work on websites, that were all created by root ...
Yeah that's sounds like you need to onboard a proper sysadmin with Linux experience. I'm sure there is more to the story though