conorab @ conorab @lemmy.conorab.com

Posts

8

Comments

172

Joined

2 yr. ago

And attempting to vault through makes your legs snap, gets you stuck in the wall or both.

The website looks like a blast from the past. The keys remind me of the keyboard on the GPD Pocket 2.

Did you originally buy it for emulation, or did you have something else in mind at the time? Judging from gPodder and SMPlayer, it looks like you were using it like a bit like an iPod touch.

Given this is for running a server for self-hosted, I would second what others have said here about using a VPS instead, provided you don’t mind self-hosting on a VPS rather than on your own gear at home.

You may be able to find a VPN provider that gives you a static IP and the ability to port forward. PureVPN offer this in limited locations and it’s what I use, but it’s jank since you can’t use their dedicated IP service with OpenVPN (their normal product does let you use it).

You may also be able to do something like run pfSense on a VPS, then run a site-to-site VPN to pfSense at home, using the pfSense in the cloud as your router. Then you can port forward from your pfSense VPS to your LAN. You’re getting very deep into the weeds with networking there though.

For me, the default wallpaper throws me back to the period it was made and reminds me of what it was like to use that version. This GNOME one feels a little generic and I swear I’ve seen it before. Feels like the right style to use in a dynamic wallpaper where colours randomly shift.

I have a bunch of container images I build for Kubernetes using Debian as the base. With the recent release of Debian 12, maybe it’s a good time to look at re-basing on Alpine for the simpler stuff.

Correct! I have Sanoid take daily and monthly snapshots on the source server, which replicate to the destination. Every now and then, I run a diff between the last known-good monthly snapshot and the most recent one which has been replicated to the destination. If I am happy with what files have changed, I delete the previous known-good snapshot and the one I diff’d becomes the new known-good. That helps keep me safe from ransomware on the source. The destination pulls from the source to prevent the source from tampering with the backup. Also helps when you’re running low on storage.

I run ZFS on my servers and then replicate to other ZFS servers with Syncoid.

An Ars commenter noted that the patch fixing a CVE that was originally rejected has now been accepted: https://arstechnica.com/information-technology/2023/07/almalinux-says-red-hat-source-changes-wont-kill-its-rhel-compatible-distro/?comments=1&post=42051274

Link to the patch being accepted: https://gitlab.com/redhat/centos-stream/rpms/iperf3/-/merge_requests/5#note_1481235739

Not like it's a real solution since it's quite unchangeable and forces everything through Tor, but Tails is probably as privacy-oriented as you can get.

EDIT: Also +1 for Debian.

It's been quite nice as a Debian user (primarily on servers) watching all this play out. On the other hand it's been infuriating watching the debacle unfold and then the solution has always been to switch to RedHat derivatives and just push the issue further down the road, only to be screwed again.

System 76 laptops are probably a bit better for Linux considering they were built specifically for it. TL;DR: Research the model of computer you're looking to buy with the distro you want before making the purchase no matter who you're buying from.

I have a bit of a chip on my shoulder about this. In 2018 I bought an Oryx Pro specifically because of this and because at the time JB was advertising them as "machines born to run Linux". However, this was not the case. The machine would constantly fail to resume from sleep and when it did, the wired network adapter would sometimes stop working until you rebooted the machine. This was on Pop!OS. The wired network adapter issue did not occur on Debian Testing at the time, but at this point I was just doing all the same workarounds on a System76 machine that I would have to do on any other machine, which completely defeated the point of buying a machine "born to run Linux". I ended up returning the machine despite this meaning that I would lose $1000 AUD in shipping (roughly $500 AUD each way). System76 did refund the cost of the machine as promised though and I appreciated the honesty and professionalism from their support. I believe the network issue was due to a regression in the kernel which had not yet trickled all the way down. To be fair, maybe System76 have ironed these issues out on their new machines.

Don't buy a machine from a manufacturer because they specifically sell Linux laptops hoping that it means you won't run in to any issues. Do some research on the model you're looking to buy for any issues with the distro you want to run and make your decision from there. The Ubuntu computer certifications are really useful here. I believe Ubuntu tested the ThinkPad P52 I bought afterwards and said everything but the fingerprint sensor worked, but to NEVER turn on one of the BIOS options because I would brick the machine, so I knew this before buying the ThinkPad and could make an informed decision.

The one advantage you might get with a Linux manufacturer is that they might be able to help if there is an issue, where-as you might have to hide the fact you run Linux from other manufacturers.