Whatever you decide for your laptop, I’m a proponent of a barebones off-site setup if you’re trying for 3-2-1 backup or similar.
I use a raspberry pi 3 with a single HD (ZFS) retaining some number of daily/weekly/monthly snapshots. Daily rsync, everything over WireGuard+VPS (TailScale would work too).
Others mentioned virtualization — I have had issues with COW filesystems (btrfs), as COW does not always play nicely with VM drives (extreme fragmentation and very poor performance).
from stdlib.h import cout
Wait this looks wrong, shit…
Anything can use it, but I think by convention it’s used for http on a non-privileged port.
Maybe there’s some interplay between amd64 and x64 architectures.
AMD64 and x64 are the same thing. Do you mean AMD64 and x86? There is definitely interplay there, as AMD64 implements the x86-32 instruction set.
Same — rsync to a pi 3 with a (single) ZFS drive at family’s house. Retain some daily/weekly/monthly snapshots.
I have a (free) VPS with static IPv4 which is how I connect everything.
Both the VPS and the remote site have limited network speed (I think 50Mbps for VPS), so the initial sync was done sneakernet (well…“airplane net”). Nightly rsync is no problem bandwidth-wise, and is mostly just any new videos I’ve uploaded to my local Immich instance.
It is “backwards” from some other commands — usually you run copy/rsync/link from source to destination, but with tar the destination (tarball) is specified before the source (directory/files).
That, and the flags not needing dashes always just throws me for a loop.
And the icing on the cake is that I don’t use tar for tarring that often, so I lose all muscle memory (untaring a tgz or tar.bz2 is frequent enough that I can usually get that right at least…).
To each their own though? I can’t imagine why anyone would want something other than i3 (or similar), because almost by definition the DE is not the program I fired up my computer to interact with, and i3 “gets out of the way better” than most others in my experience.
But…that’s just my use case. It’s a horrible UX for most people, just happens to work well for me.
I feel old…when I was learning how to run Linux I started with an old 386 (maybe 486?) my dad wasn’t using. I think it had 32MB RAM, which was fancy for those machines.
We had dial up at the time, so only one machine could be on the Internet. So, I set up a modem on the x86, plugged into an Ethernet hub (switch?), and learned enough ipchains (this was before iptables) to share a connection. It also ran Samba, an AFP server, and probably FTP and HTTP (just for local access) — but it worked for filesharing.
It could also run MP3 streaming software which amused me because the machine itself was too slow to decode MP3 (but that’s not necessary to stream).
You mentioned ham radio — definitely fun! It’s a process to get into it though, as you need to study/pass an exam, and then you need a radio. Radios range from cheap ($25 or so) in the VHF/UHF (“walkie talkie”-style) to more expensive for an HF rig ($1000 range for 100W HF). If you want to get into low power (“QRP”) it can be much cheaper. You also need a fair amount of space for a good antenna setup…
There are tons of different communication modes, some without a computer and, like you mentioned, some that use computers. wsjtx and fldigi are popular programs.
Good luck!
D’oh, I’m a doofus — it’s search that I was thinking of (apt-cache search, not apt-get search).
Can apt-get refresh package list?
Edit: yes…yes it can. I was confused.
“…and there are no comments, because it’s Self Documenting™”
Modern bots are bad, but the old school IRC (maybe early Battle.net?) bots… I’m cool making an exception for them if you are.
Sounds like you’ve only ever used desktops and/or laptops…
Fail2ban config can get fairly involved in my experience. I’m probably not doing it the right way, as I wrote a bunch of web server ban rules — anyone trying to access wpadmin gets banned, for instance (I don’t use WordPress, and if I did, it wouldn’t be accessible from my public facing reverse proxy).
I just skimmed my nginx logs and looked for anything funky and put that in a ban rule, basically.
Windows is just as hard as linux, harder even with all the layers of obscurity.
With Windows, there is 1 current version of Windows (11), 1 “almost current” (10), 1 “outdated but you’ll maybe see it” (8.x) and only a few “you’ll probably only see this in obscure situations” versions. Linux has as many “parent” distros/package management systems (apt, rpm, pacman, etc.). This definitely complicates things, as each distro family does things slightly differently.
And we haven’t even touched the window manager/DE choices, of which there are a ton (as opposed to Windows). “Combinatorical explosion” maybe isn’t the right phrase, but you get the idea — Debian with i3wm is wildly different from Fedora Plasma.
This is all a good thing though, as Linux users tend to like the choice and flexibility — but it does mean that the “right way” to do something on Linux is very dependent on your particular setup, which isn’t the case with Windows.
(I have used Linux for the last 20+ years, and it’s definitely my preferred setup, and am lucky enough that I rarely use Windows for work, and never for personal use.)
And many folks have headless setups — raspberry pis, home servers, VPSs, etc. It’s kinda overkill to install a desktop environment on a headless box if the only reason you need it is so you can VNC into it for a simple task that could be done over ssh.
For some (most?) of us, we don’t have ssh access open to the world, so everything is over a VPN. So I can just use NFS over WireGuard which afaik is fairly secure, if you trust your endpoints, and works great over the Internet.
— Richard P. Feynman
I think the same is true for a lot of folks and self hosting. Sure, having data in our own hands is great, and yes avoiding vendor lock-in is nice. But at the end of the day, it’s nice to have computers seem “fun” again.
At least, that’s my perspective.