Simple thing, but are you sure you mounted the NFS share as NFSv4? I don’t have access to a machine to check right now, but I think it might default to mounting NFSv3, even if both sides support v4.
<span style="color:#323232;">vineta.h.kfe.pt:/nfs/nas on /nfs/nas type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp6,timeo=600,retrans=2,sec=krb5p,clientaddr=2001:470:7391::ce,local_lock=none,addr=2001:470:7391::c0,_netdev)
</span>
Linux desktop will, most likely, fail for: Developers and sysadmins, because not everyone is using Docker and Github actions to deploy applications to some proprietary cloud solution. Finding a properly working FTP/SFTP/FTPS desktop client (similar WinSCP or Cyberduck) is an impossible task as the ones that exist fail even at basic tasks like dragging and dropping a file.
Linux desktop is great, I love it but I don’t sugar coat it nor I’m delusional like most posting about it.
It all comes down to a question of how much time (days? months?) you want to spend fixing things on Linux that simply work out of the box under Windows for a minimal fee. Buy a Windows license and spend the time you would’ve spent dealing with Linux issues doing your actual job and you’ll, most likely, get a better ROI.
Guess what happens whenever people popularize immutable distros as the next hype in tech that will make everything better? You get yourself into a totally unreasonable and avoidable ecosystem just because those systems won’t cut it for most use cases… same that happened with Docker/Kubernetes.
I’ve been saying it for year and nobody cares: nowadays those companies are all about re-creating and reconfiguring the way people develop software so everyone will be hostage of their platforms. We see this in everything now Docker/DockerHub/Kubernetes and GitHub actions were the first sign of this cancer. We now have a generation of developers that doesn’t understand the basic of their tech stack, about networking, about DNS, about how to deploy a simple thing into a server that doesn’t use some Docker BS or isn’t a 3rd party cloud xyz deploy-from-github service.
The latest endeavor in making everyone’s hostage is the new Linux immutable distribution trend. Immutable distros are all about making thing that were easy into complex, “locked down”, “inflexible”, bullshit to justify jobs and payed tech stacks and a soon to be released property solution.
We had Ansible, containers, ZFS and BTRFS that provided all the required immutability needed already but someone decided that is is time to transform proven development techniques in the hopes of eventually selling some orchestration and/or other proprietary repository / platform / BS like Docker / Kubernetes does.
“Oh but there are truly open-source immutable distros” … true, but this hype is much like Docker and it will invariably and inevitably lead people down a path that will then require some proprietary solution or dependency somewhere that is only required because the “new” technology itself alone doesn’t deliver as others did in the past.
As with CentOS’s fiasco or Docker it doesn’t really matter if there are truly open-source and open ecosystems of immutable distributions because in the end people/companies will pick the proprietary / closed option just because “it’s easier to use” or some other specific thing that will be good on the short term and very bad on the long term. This happened with CentOS vs Debian is currently unfolding with Docker vs LXC/RKT and will happen with Ubuntu vs Debian for all those who moved from CentOS to Ubuntu.
Those popularizing immutable distributions clearly haven’t had any experience with it before the current hype. Let me tell you something, immutable systems aren’t a new thing we already had it with MIPS devices (mostly routers and IOTs) and people have been moving to ARM and mutable solutions because it’s better, easier and more reliable.
There is always some solutionizm in tech, but I’m interested in containerzation as a solution to problems I’ve had with configure drift building up on my systems and make it easier to share and work with the community.
The immutable desktop work to me is specifically working on bridging the gap between the UX of a local admin (you know wanting custom configuration and fast reaction to user input) and the industrial expectations of being able to test and track every change and reduce the number of different pieces you need to operate a system.
Hopefully we can lose some of the industries bad habits though. Like “relying on this proprietary piece is ok because we can move faster” or making other excuses as if you are going to have to explain to your boss why some metric looks bad instead of just trying to make the best system or solution we can.
The amount of times my Windows installation(s) broke is just as high as the amount of times my Linux installations had issues. The article you quoted seems to be from someone with more Windows experience than Linux experience.
One example: FileZilla is a capable GUI SFTP and FTP client, but so is nearly every file manager. I can drag and drop files from Dolphin into a fuse mounted FTP, SMB or SFTP folder just fine. Skill issue?
EDIT: omg, I just realised they use WinSCP for deploying applications. It really seems like a skill issue since you can automate that even without proprietary clouds. I can probably replace this person with a PowerShell script, which is even more efficient than them doing their job on Windows.
All operating systems sadly need lots of maintenance nowadays. The main reason I use Linux is that I feel in control of the system and the vendor doesn’t actively try to fuck with my installation.
There’s a very nice (albeit somewhat outdated) talk here.
In a nutshell, both X11 and Wayland are protocols that define how software should communicate to (hopefully) display stuff on your screen.
Protocols as in there’s a bunch of documentation somewhere that says which function a program must call to create a window, without specifying how either program or function should be implemented.
This is great because it allows for independently written software to be magically compatible.
X11 is the older protocol, and was working fine good enough for many years, but has issues handling a bunch of modern in-deman technologies - issues which can’t be fixed without changing the protocol in a way that would make it incompatible with existing software (which is the entire point).
Plus its most used implementation - Xorg, consists of a huge and complex codebase that fewer and fewer people are willing to deal with.
Wayland is the newer protocol, that mostly does the exact same thing, but better, in a way that allows for newer tech, and completely breaks compatibility in order to do so.
The trouble with the whole situation was that in order to replace X with Wayland basically the entire Linux graphics stack had to be rewritten - and it was, with raging debates and flame wars and Nvidia being lame.
They also wrote a compatibility layer called Xwayland that lets you keep using older X-only apps which somehow manages to outperform Xorg.
Now we’re at the point where major distributions are not only switching to Wayland by default, but also dropping support for Xorg completely, and announcing that they’ll no longer maintain it, which is why posts about it keep popping up.
I don’t see a real „versus“ here. Wayland will definitely become the standard display server for Linux distributions. This is not sysV init vs systemd or something else. As pointed out by lots of ppl here X11 is old and insecure because it is from another time and does not fit into modern systems and requirements, thus it is way easier to start new and fresh instead of working around for any feature needed and maintain such a old code base. The only downside for me personally is that Wayland does not support always on top windows automatically. So either right click the window or use plugins for videos from Firefox for example. AFAIK this is also for security reasons. I run Wayland on my main machine for years now, no problems at all. If I got the choice I would always go for Wayland. Even Cinnamon has experimental Wayland support now and hopefully will make the switch soon.
unless you are a developer, there’s not a whole lot to worry about – you’ll switch from one to the other when your distro switches and, chances are, you’ll never notice
the drama comes from the fact that the Linux community loves choices (and arguing over those choices) and, as @skullgiverpoints out, most of the choices have fallen by the wayside over the years
Don’t really have an Idea, but to add to your problem…
I have a 4K TV and 2 1080p Monitors and switching beneath them. Using NVIDIA graphics card with up to date drivers. All I can say, I’ve tried using KDE multiple times now, but always ended up getting weird Bugs, Micro stutter, etc on my 4K TV with KDE. So I always reverted Back to Cinnamon, GNOME, etc, because there it is working fine.
There are distros that make it easy for non-techies to install and manage Linux, and if you have any computer aptitude at all, it should be pretty easy. The devil is in the details; if all your hardware is well supported, there’s no reason why you should ever have to open a shell. Trouble usually happens with peripherals like printers and some extremely protective vendor chips like Broadcom. In those cases, it’s usually still possible to make things work, but it can require researching, finding, reading how-tos, downloading, compiling and installing software.
I think 99% of trouble I’ve ever had in the past 20 years has been with printers+scanners or Broadcom chips - they’re very common. I read about people having issues with graphics cards, but that seems to be mainly Nvidia; I’ve only ever had Intel or Radeon, and haven’t had trouble with graphics cards in the past decade or so, myself.
Anyway, my advice is to do some distro hopping before you settle on one. Boot from a USB stick for a while; it’ll be a bit slower, but it’ll make playing with different desktop environments and distributions easier, before you commit.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.