

2·
9 days agoHooooowwwwddy ho!
Hooooowwwwddy ho!
‘If God isn’t real, why do you say oh my God?’
That was from the deputy head of my school…
That’s good to know, thanks :)
I’ve got a few services running on my aging media server, so I want to start doing it properly, and getting a proper home sever going. I’ve used ssh for some of the basics in the past, but I need to start using that more too :)
I might be wrong, but I remember reading that they removed the objectionable content after the fuss that was kicked up.
If it makes you feel any better, I did something just as infuriating a few years ago.
I had set up my home media server, and had finally moved it to my garage with just a power cable and ethernet cable plugged in. Everything was working perfectly, but I needed to check something with the network settings. Being quite new to Linux, I used a remote desktop tool to log in and do everything through a gui.
I accidentally clicked the wrong item in the menu and disconnected the network. I only had a spare ps/2 keyboard and mouse, and as the server was an old computer, it would crash if I plugged a ps/2 device in while it was running*.
The remote desktop stayed open but frozen, mocking me for my obvious mistake and lack of planning, with the remote mouse icon stuck in place on the disconnect menu.
*I can’t remember if that was a ps/2 thing, or something specific to my server, but I didn’t want to risk it