Recent content by clickwir

Sadly, I haven't found a solution yet. IMO, systemd is overstepping it's bounds by a lot. Was meant to be an init system replacement and it's morphed into a lot more than that and is slowly replacing everything in a linux system with a systemd method/application/service/way of life. And I...

Has no one else tried to run screen on a container? This is still a problem. Screen is entirely broken when you logout.

Was talking about this with a co-worker today. To recreate, it should be this simple: Install Debian bullseye container. Within that container, install screen. Run screen. Within screen, run something like 'top' that will keep running. Ctrl+A, D to detach screen. Logout. Login. Run 'screen...

I just installed 7.1-2 on a 3400G system a week or so ago and it worked fine-ish... The graphical installer did take about 10 minutes to come up. But once it came up, it was fine. I have no explanation as why this happened, but after a few attempts at rebooting and redoing my USB drive, I found...

So I've been struggling with this for a few hours and everything I've found online leads to huge arguments about how systemd (back in 2016?) changed a default to kill all user processes on logout. Well that sounds ok, but it kills things like screen. screen has been used for many many years...

Have been using disk passthrough on Proxmox 6 with 512 byte drives for a few years now, no problems. Tried doing the same thing to 4k drives and got lots of errors. Everything seemed to work fine at first, but after a few hours of using them I noticed there were errors. None of it was important...

Noticed a dstat crash while shutting down a VM. Just upgraded from Proxmox 6 to 7 yesterday, this was a fresh install of Proxmox 6 just a few days ago. No VM's had been made yet. Made a new VM today, Ubuntu Server 20.04. Used it for about an hour and then installed the qemu agent and did a...

FWIW, I was having problems with the initial Proxmox 5.1 page not loading at all. Just blank. Disabled all my addons and made no difference. Found I had dom.storage set to FALSE and that appears to be something Proxmox needs unfortunately. Enabled all my addons, restarted FF 57.0.1 with...