I now feel like giggling and throwing up at the same time. A rather confusing sensation.
I now feel like giggling and throwing up at the same time. A rather confusing sensation.
Chiropractor at work: Whatever is wrong with you, as long as I get to crack some joints, you will not die of anything, pinky promise!
The absurd waste of resources VMs bring… LXC and Docker a godsend in that regard.
Are VMs really simpler? I’d say no.
Most red dyes are bugs. Be it food or otherwise. https://en.wikipedia.org/wiki/Carmine
This goes for most LLM things. The time it takes to get the word calculator to write a letter would have been easily used to just write the damn letter.
I also know that I cannot tell the difference between two IPv6 addresses because they all merge into an indiscernible blur inside my head
I’d rather troubleshoot for days than try to reboot or check cables.
“but… I explicitly described this in the frickin’ ‘Business Case’ you had me fill out a thousand times!”
Dmarc/dkim/SPF/certs. Fun times!
I got a mall server running, yet it’s almost more as an inbox.
BEFORE you mess with your VNC, it is extremely important to have a backup connection. So either you have the ability to connect your pi to a monitor and a keyboard locally, or you really, really should setup SSH before you mess with your VNC server.
Use SSH with a Certificate, described here: https://raspberrypi-guide.github.io/networking/connecting-via-ssh (“passwordless”) This guide doesn’t show how to set up SSH, but how to install a key in a more detailed way: https://pimylifeup.com/raspberry-pi-ssh-keys/
The good thing: Once you got this working, you’re basically done. Just ditch VNC and go straight to SSH from now on. It’s more secure and has better performance usually.
Yet, if you like your VNC and want to continue using it, you first connect via SSH do not do this while using a VNC connection! Now, first, you do all this: https://www.tomshardware.com/how-to/install-vnc-raspberry-pi-os then you do a
sudo update-alternatives --list vncserver
sudo update-alternatives --list vncserver-x11
you should see tightvnc listed there. Don’t freak out if one of the two returns an error that the application was not found. That’s okay. Not all versions of Raspbian used the same application name in the past, so I listed them both. As long as one of them works, you’re fine.
Then, you do a
sudo update-alternatives --config vncserver
sudo update-alternatives --config vncserver-x11
and change it to tightvnc. now you can stop your running VNC:
sudo vncserver-x11 -service -stop && sudo vncserver -service -stop
sudo vncserver-x11 -service -start && sudo vncserver -service -start
Once you did that, connect to tightvnc as described in the article. If this works, do
sudo apt uninstall realvnc
You should now be able to connect via VNC without weird account bullshit.
Wait till Trump starts yapping about “cracking down on crime”
And once you have found your specific collection of plugins that happen not to put the exact features you need behind a paywall but others, you ain’t touching those either.
How is Microsoft related to a tool to scan Linux for malware?
This is almost certainly a montage
That’s a really weird take. Like… what even is the difference supposed to be?
This sounds more like “everything should be as it was back when <insert arbitrary point in time here>! When there were still Webpages, and we were frolicking about the internet! Until the fire nation attacked Web apps took over!”
Well, Google will probably optimize their shit for their own privacy invasion sniffing tool browser twice as hard as for Firefox and such
That one was a wild ride