Finally I have something to report. Very niche in it’s impact, but personally I’m very satisfied now.
Project: UTStats recovery
Installed Ubuntu 14.04 to a vm so that I have php5. Imported the databases to check if my stats were accessible and they are!
Now this is in vm, I had some issues during init and I didn’t verify whether it actually parses the logs, but seeing this after so many years makes me happy! Next phase is to update 3.06 to 3.09. The newer version is by a different developer, but should wotk with php7 and has some additional improvements too. Install guide does say that “If you are upgrading from UTStatsDB 3.06, a new installation is highly recommended, rather than attempting an update. If you do perform an update, rather than a new install, certain special event data like player headshot counts may not be transferred to the new database structures.”. So how to go on with this? Maybe I should install 3.09 to a new vm and see what’s different in the database structure. And write a simple export/import sql query. Maybe it could be on gitlab. Maybe I should fork this to gitlab (I have plans).
While installing Ubuntu on vm I also installed Terry Davis’ Temple OS (vm), quite the experience. It’s only 16M, so it can remain on my system, but I don’t know what do do with it. I might get a new synthesizer. I’ve been wanting one of those for a long time. It costs a lot so I have to sell some stuff before I can justify the purchase.
Now that I have a new rig, I need to figure out what to do with the old one. It’s not stable as it crashes after some time. Maybe a test machine of sorts? Following the official guide. I added the -g -flag. Hopefully it’s enough as the BIOS is really limited. I can only set time there!
Now the “SleepingRig” has: -g -flag. I also took it’s MAC-address and shut it down. On my “MainRig” I installed etherwake. It uses eth0 by default so I need to modify the command a bit.
$ sudo etherwake -i enp2s0 aa:bb:cc:11:22:33
And boom! It works! Amazing! Now I can automatically start a LAN-machine. It boots into the login-screen, and the -g -flag has reverted to -d.
The above guide shows how to set the -g -flag, but it’s from 2015 and doesn’t use the new netplan that’s default in Ubuntu nowadays. This might be a problem (upd: editing the /etc/interfaces worked for me).
Setting up TightVNC
Normally SleepingRig is running KDE, but the guide that I’m following needs xfce. While KDE has it’s own ‘krfb’, I can live with the bloat. I also want to know how this’ll work.
Everything went well until the section 3. The command doesn’t work! It does ask for the vnc password, but after that there’s just empty terminal. I also tried to use kde instead of xfce4, but that failed and vnc showed only x. Section 4 worked fine, it’s about creating a systemd service for vnc.
All in all I did good progress. There were few issues that still puzzle me, like why did startkde and secure-vnc fail? Well I can work with xfce4 and this machine wont be accessible online so fine. However Wake-on-LAN, ssh and vnc works so now I can power my devices with a simple terminal command and control them from a different machine!