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).
I won't argue about leftovers when uninstallig, some package managers do that as well, plus it's not really the registry's fault, that's just bad or badly configured installers/uninstallers.
Ah, if the thing has USB 3.0, then the NIC in the laptop is probably 100Mbit (lower end models had 100Mbit even if they were newer), that's your main issue, not SMB. SMB is a TCP/IP protocol, has nothing to do with hardware implementation and has no speed limits (at least none that I'm aware of). It goes as fast as the slowest part in the chain.
Cheapo built-in consumer motherboard RAID doesn't work great on Linux
That is what I actually meant.
I guess if you're dual booting, you'd have to do it that way since I don't think you can share software RAID between Windows and Linux. It's still not great.
That's why you don't do RAID at all on a daily driver. You make/buy a NAS for that kind of thing. Maybe just RAID1 in hardware, cuz that's easy to set up and generally just works, even with low end hardware solutions.
0x4E4F @ 0x4E4F @lemmy.dbzer0.com Posts 56Comments 412Joined 1 yr. ago
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.