Norgur

That’s what happens around any toilet in a 2km radius when Taco Bell has a major sale.

Oh, you actually believed that story? Whoops. Sorry! It was actually me who ate your Cheetos and downed your Vodka.

It doesn’t. It will require you to reboot for every god-damned line of code that has changed.

Na, nothing. Did an update today. Nothing bad happened at al, Because why would it?

Back in the day, when I installed my very first Linux OS, I had a wireless stick from Netgear. Wireless Drivers back then were abysmal, so I had to compile them from source (literally 15 mins after seeing a TTY for the first time). After I had found out how build-dependencies and such worked somehow and ./configure completed successfully for the first time, the script ended with the epic line:

configure done. Now type 'make' and pray

The enemy of my enemy, eh?

glibc 2.36 is all you’ll ever need, okay? Go away with those goddamn backports!

I don’t. So… uhm… you’re wrong I guess.

You know how Linux killed the chef?

With a fork bomb

The absurd waste of resources VMs bring… LXC and Docker a godsend in that regard.

Are VMs really simpler? I’d say no.

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’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.

Well, you can try, but I bet you’ll encounter unmet dependencies, namely “host-good-looks” and “nice”

Well, not everyone will let you recompile their kernel, if you catch my drift.

Have you looked in the Wiki?

Nah, that way, I can be the Alpha-Nerd in my circle, getting all the clout when I help them out with a command-line-command that contains awk.