4·
22 days agoThe hunt for red lemmytober
- 0 Posts
- 17 Comments
Joined 1 year ago
Cake day: August 3rd, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Immediately thought of jojamart.
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.
2·7 months agoI miss when it was called Fedora Core.
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.
3·7 months agoI don’t have any recommendations to make here, I just wanted to chime in and say I am looking for the same tool and I’m glad someone could put into words what I wanted.
I think the problem is that this will likely lead to more driving instead of flying.
In my size of company, it’s simple. I simply don’t want the overhead of running an email system. It’s not just running a server, it’s running a server farm for HA, dealing with domain blacklisting, retention systems, storage and firewalling to name a few.
Oh my God. I forgot about real player. Plus DivX.
This comment reminds me of the early days of KDE4. Fun times.
I’m not the only one!
And make the EVs affordable so they can be demanded?
4·1 year agoAs an FYI to anyone trying this, I ran into the following problems and solved them.
- 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
- 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
Uhhh