fokihotline.blogg.se - No one has ever been poor by giving quiterss like

No one has ever been poor by giving quiterss like install#
No one has ever been poor by giving quiterss like drivers#
No one has ever been poor by giving quiterss like windows 10#

No one has ever been poor by giving quiterss like drivers#

I spent a day messing about with different printer drivers and trying to coerce otherwise functional programs to behave rationally.

Printing proved to be a right royal pain in the posterior.

I mounted my network resources using nfs in the fstab.

Linux apps, in general, do not talk to data on the network directly.

If I relied on the values supplied by my DHCP server, the OS would occasionally reset itself so that it resolved only external names, and sometimes didn’t work at all. I disabled Network Manager and used netplan (rendered by networkd) to define a bridge (needed by the virtual machines) with static IP and DNS settings.

Ubuntu 20.04 domain name resolution is a right pain too if you have a local DNS server.

No one has ever been poor by giving quiterss like install#

However, I did not use the OS option to install on zfs because I have found zsys to be buggy, and in the past it failed me when I needed it most. I kind-of followed some of the ideas in the Ubuntu ZSYS project, having separate datasets for the root, and each user. I initially installed Zorin 16 to a SSD using ext4 as the filesystem, then I moved the installation to my nvme using the zfs filesystem (separate boot and root pools).It’s based on Ubuntu 20.04 LTS, which is also well maintaned. The Core version is free, but the existence of paid versions means the features in Core get professional attention. I selected Zorin 16 Core (based on Ubuntu 20.04) as my OS.Here is a list of observations from this work: There I was able to continue to use VideoPsalm and Microsoft Access (Office). Eventually I gave up and bought a one-time install license for Windows 10, and for Microsoft Office, which I was able to install in a fresh VM. I could boot it in safe mode, but not in normal mode.

No one has ever been poor by giving quiterss like windows 10#

Booting the Windows 10 installation image and attempted to repair the installation failed. The boot up in the virtual machine (VM) gave an error on a fetchingly attractive light blue background (gone are the bad old days of dark blue). I moved my installation to an SSD (where it still booted) and then virtualized this as a raw block device. I tried virtualizing the nvme PCI hardware in qemu-kvm.

I would really like to have moved my existing Windows 10 installation into the virtual domain. These are VideoPsalm (which is used to present in Church) and Microsoft Access (which I use to maintain multiple databases, e.g., for a publication I edit). A couple of the apps I depend on run only in Windows. Finally, I wanted to use ZFS to provide management and protection of my filesystem.īut can I drop Windows entirely? Unfortunately not. Thirdly, I am familiar with running Linux, which I use on my home server.

The second reason (and perhaps an equal first) is that I like to tinker, and Linux has plenty of scope for tinkering. Perhaps the most important is that Microsoft has branded most of my hardware unfit to run its next revision of Windows at some point Windows 10 will cease to be supported and vendors of the various Apps I depend on will stop supporting it. Why then should I want to migrate to Linux? There are multiple reasons.

I have 4 computers at home quite happily running Windows 10, and with very little frustration. I started developing an application under Windows 1 (a disaster due to memory leaks in the OS), I developed device drivers under Windows 3.1.