For this reason I opted to use hibernate coupled with wake-on-LAN.Ĭonfiguring the wake-on-LAN took a little while. I also wanted my x2go session to be persistent so I could pick up where I left off. Since this machine won’t be in use all the time, I wanted to shut it down and power it up remotely. If I ever come to reinstall on the desktop machine, I’ll look at Manjaro Architect further. I played with this a bit later when installing Manjaro on my Laptop, but opted to go with the default encrypted system option from the GUI installer. I could create volume groups, but it wouldn’t let me add partitions to them! As far as I understand Manjaro Architect lets you do this. One thing I noticed was that I wasn’t able to manually set up LVM from the GUI installer. The bare metal install of Manjaro was pretty boring (which is a good thing, installing a Linux distro should be boring and stable!). ![]() It wasn’t a complete loss, since I got a chance to try out the newly updated clustering in Proxmox, which will be relevant when I convert my existing Ubuntu server over. I decided to abandon the VM approach for now and go with a bare metal install to see if I can work with the remote desktop system. This causes lots of things to fail, including VM backups on the remaining host. As I added this machine in a cluster with my other host, the cluster would also lose quorum when the host went down. The second was that suspending the VM and shutting down the host was pretty clunky and prone to just hang for no reason. The first was that I couldn’t get the host machine to pass through the internal DVD drive to the VM which was a deal breaker. I spent quite a bit of time configuring this only to find a few issues. I also wanted the remote desktop to run as a VM on the machine, under Proxmox, so that I could potentially switch distros easily or create extra VMs for other purposes. I’d heard good things about Manjaro and the KDE edition works great with x2go (both client and server). Secondly, although the desktop worked fine I was unable to suspend the session due to some Systemd/D-BUS issue. First of all I couldn’t install the client on my laptop due to a dependency issue in APT. The bad news is that my preferred desktop distro – KDE Neon – didn’t work well. ![]() The good news is that it works pretty well (at least for basic remote desktop, I’ll come to some of the problems below). Initially I did a few tests with local VMs to see if x2go was going to work with KDE, since I’d seen mixed reports about this. I decided to do the same, since I had the hardware already available to make it work. That was until I came across a post about using x2go to create a remote workstation after musing whether this would be possible. So that computer sat gathering dust for the most part. ![]() I was also not enthused about spending my evenings sitting in the same office I’ve just been working in all day. I could have probably remedied this with a KVM switch, but somehow I never got around to it. This was mainly due to having to switch the mouse, keyboard and monitor over from my work machine in order to use it in the limited space which is my home office. I actually do have another desktop computer, but my use of it recently has been limited to the odd DVD rip. Clearly 4GB of RAM is not enough to run modern applications. However, every now and then I need to run a couple of apps which just bring it to a halt as it thrashes around trying to swap. Since my server performs the majority of my computing I haven’t really been limited by this. For my requirements this is mostly OK, since my workload mostly consists of a web browser and terminal windows and it runs my preferred desktop (KDE Plasma Desktop) just fine. It’s been upgraded over time with an SSD and a replacement battery. I’ve been running a very under-powered and increasingly ancient laptop, a ThinkPad X131e, for several years. Please see the disclaimer for more information.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |