linuxmemes

20880 readers

9 users here now

I use Arch btw

Sister communities:

LemmyMemes: Memes
LemmyShitpost: Anything and everything goes.
RISA: Star Trek memes and shitposts

Community rules

Follow the site-wide rules and code of conduct
Be civil
Post Linux-related content
No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago

MODERATORS

[email protected]

1414

That's LTT in the bottom (lemmy.dbzer0.com)

submitted 8 months ago by [email protected] to c/[email protected]

492 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 8 months ago* (last edited 8 months ago)

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.