Oh yes. Much better since the KDE4 branch / debacle.

Go ahead, this is a safe space. Get it out of your system.

That’s great! Thanks for sharing.

https://i.kym-cdn.com/photos/images/newsfeed/000/428/075/30a.jpeg

I fucking love Oh Brother, Where Art Thou

Omg, it’s Taako from TV

See also: My brother, my brother, and me

Uhhh

The hunt for red lemmytober

Immediately thought of jojamart.

Right? Immediately made me think of the Arkema chemical plant in Texas episode

I loved the Ernest movies. How about a bumper sandwich booger lips?

You’d have to be really committed. There’s more admin work than you think to make sure you’re not insecure or getting blocked.

With the exception of any major games that have anti-cheat. I miss League of Legends.

Assuming you’re asking in good faith, the “/s” is usually added to denote sarcasm online.

/s I’m assuming.

Proxmox isn’t an option for vmware fusion replacement. Fusion is a type 2 hypervisor running on Mac. The options are paid parallels desktop and free virtualbox.

As an FYI to anyone trying this, I ran into the following problems and solved them.

1. Port 53 (DNS) was already bound to systemd-resolved. This caused the Adguard container to fail. https://hub.docker.com/r/adguard/adguardhome From their documentation, do this. I added the commands I did below.

sudo mkdir /etc/systemd/resolved.conf.d sudo touch /etc/systemd/resolved.conf.d/adguardhome.conf sudo nano /etc/systemd/resolved.conf.d/adguardhome.conf #Copy this in and save [Resolve] DNS=127.0.0.1 DNSStubListener=no

2. DHCP on the interface I was using on my VM was already bound to DHCP. To resolve this, set a static IP. I used the following. sudo nano /etc/netplan/00-installer-config.yaml

#Overwrite with the following. Make sure if your adapter isn’'t labeled ens33, you change it appropriately. network: renderer: networkd ethernets: ens33: addresses: - 192.168.1.200/24 nameservers: addresses: [192.168.1.1] routes: - to: default via: 192.168.1.1 version: 2