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.
I know instantly how to get the packages I need in Linux but I had to do some research to enable the webcam in Windows 10.
The idea that one OS is easier than the other is misattributed familiarity.
To enable the webcam on windows you just…open teams and start a call or use one of the apps that use the camera…
It is almost like those Linux users are not really as technologically capable as they claim to be.
Or they are just lying and haven’t used Windows in over a decade.
Even on Linux, to use the webcam you just plug it and open gnome cheese or Google meets…
Ok great so the webcam works easy without researching on both OSes.
Unlike what arthurpizza claims.
Unless the vendor decided to lock it down until you manually unlock it with the administrator account. Then even Teams can’t see it.
How do you know if you don’t already know the package name?
I have to always Google for the package name, which similarly is what I do to find a Windows installer but instead of the name it’s download link.
Or
Or
Thanks!
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.