Just getting a feel for Solus - installed a copy of 4.0 on a ProxMox server as a KVM VM and am finding it extremely nice. I tend to be partial to Debian based distros, but this may have pulled me away from MX - the MX developers have chosen to use sysvinit rather than systemd which tends to blow up a few things (like VNC Connect).
After the initial creation of the VM - the system would not detect a SCSI HDD for some reason - switched it over to IDE and it worked great - would be nice if it did detect the SCSI VirtIO disk rather than having to use IDE, but certainly not a show stopper.
Installing Chrome - easie piesie - Third Party apps, done and done. Accidentally installed the Beta, was a bit cumbersome to figure out how to uninstall it (searched for Chrome did it for me) but aside from that again - no show stopper.
Installing VNC Connect, pretty simple to use the install script - ran it as root (wanted it installed system wide) and installed fine and after a reboot my little VNC icon was already on the taskbar with a big red X. When I went to logon to my VNC connect account it failed asking me for Administrator permissions, Google searched and found I needed to open terminal and perform a sudo vnclicensewiz then everything worked like a top.
So far so good, very nice, clean install modern looking desktop - I could see continuing to use original stock Debian for server tasks and this possibly as a new desktop replacement for MX. MX just feels a bit long in the tooth and that systemd sysvinit things gets me a couple of times. Great work fells, please do keep it up!!
