There are plenty of distros out there that fit that criteria, Mint, Manjaro, EndeavourOS. You can do everything a normal user would do from a GUI.
0x4E4F
That is impossible. It's like saying for Windows "can you do everything that you can do in a GUI, in PS or cmd". That can never come true because the OS was just never designed that way.
Likewise, in Linux or any other POSIX compatible OS, you can't expect that. Everything UI related is designed to just be a wrapper around the shell. You can't expect everything to be configurable through a UI when everything in that OS is designed to run in the terminal (a few exceptions, but generally, yes, this is true).
Even something simple like having keyboard focus follow mouse is a giant pain and doesn't work well
Ah, I see you have seen the UAC prompt as well.
It's their choice. I'm sure they also had this in the works as well, but it eventually didn't work out (why pay another dev when we can have the ones already working for us do this as a side project... they basically just have to clone the repo and change a few things, that's it).
As I said, he can sue for not mentioning the original project, but not much more... maybe he'll think a bit more about what license to choose when publishing big projects like this publically.
We do know about stuff like this... we just decide to turn a blind eye about it since we know who is using it and why they're using it.
But if things get out of hand and we notice weird things happening, then yes, we will act on it and will "know about it".
My usual reply to said employees is "if you know how to install and configure a Linux distro, you probably also know how to solve your own problems". Everything else is pretty much deployed over AD, so if you can get to the point where you need admin creds to hook to the DCs, then do whatever you like.
Eventually, all of them failed to even get close to being a part of the AD DC and that is where the story ended.
I actually thought PS was gonna be better than cmd... turns out consistency is a lot better in cmd... can't make heads or tails in PS. I still use cmd to invoke stuff in PS, but only if there is no other way.
Well, it's under a permissive license, so there is little he can do legally, except maybe sue them for not mentioning the original project, which I'm sure they will add and that will be that eventually.
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.
Though, yes, I do recommend LTSC as well (high seas and all that, since they cost a small fortune) vs. a Pro license. It's basically what Windows users were used to, a Windows install that's stuck in time, no new features, only security updates.
Oh, and no store and all that app crap, the only app installed is the settings app and there is no way to install any other store app (well, there is, but it's complicated and I would do it only of there is absolutely no other way).
Use LTSC and this and never worry about Windows deleting shit in Home or updates breaking something, do it ONLY when YOU want to update.
To be honest, yes, I use a single monitor setup... though I don't think many Linux users use a single monitor setup, they just use matched monitors (buy 2, 3 of the same kind).