If you’re doing it from scratch, I’d recommend starting with a filesystem that has parity checks and filesystem scrubs built in: eg BTRFS or ZFS.
The benefit of something like BRTFS is that you can always add disks down the line and turn it into a RAID cluster with a couple commands.
Yep, the problem was that docker started before the NFS mount. Adding the dependency to my systemd docker unit did the trick!
isn’t it an annoyance having to connect to your home network all the time?
It’s less annoying than the gnawing fear that my network might be an easy target for attackers.
Proliant G9 is an EoL server that hasn’t been sold since 2018. Meanwhile, Debian bookworm released last year. I’d be surprised if the problem were that your installer gave you a kernel that’s too old.
What is the output of ip addr show?
It might also be worth ruling out low-level issues:
Surely this could be good, right?
If celebrities need to be accessible to their biggest fans, maybe it would induce them to leave the birdsite? And if this is as big a migration as the article suggests, it has the potential to snowball in network effects, giving other influential users one less reason to feel chained to a dumpster fire.
Yes, OP I highly recommend a GL.iNet device. It’s pocket sized and always does the job.
It’s also great for removedty wifi that tries to limit how many devices you can connect. The router will appear as one MAC and then all your other devices can route traffic through it.
As someone who has owned enterprise servers for self-hosting, I agree with the previous comment that you should avoid owning one if you can. They might be cheap, but your longterm ownership costs are going to be higher. That’s because as the server breaks down, you’ll be competing with other people for a dwindling supply of compatible parts. Unlike consumer PCs, server hardware is incredibly vendor locked. Hell, my last Proliant would keep the fans ramped at 100% because I installed a HDD that the BIOS didn’t like. This was after I spent weeks tracking down a disk that would at least be recognized, and the only drives I could find were already heavily used.
My latest server is built with consumer parts fit into a 2U rack case, and I sleep so much easier knowing I can replace any of the parts myself with brand new alternatives.
Plus as others have said, a 1U can be really loud. I don’t care about the sound of my gaming computer, but that poweredge was so obnoxious that despite being in the basement, I had to smother it with blankets just so the fans didn’t annoy me when I was watching TV upstairs. I still have a 1U Dell Poweredge, but I specifically sought out the generation that still let you hack the fan speeds in IPMI. From all my research, no such hack exists for the Proliant line.
The problem with chromebooks is that the base specs are pretty removed. A lot of them have 4 GiB of RAM and maybe 16GiB of disk if you’re lucky.
They were designed to be thin clients to connect students to the internet, and little else. Maybe they could be hacked into something useful, but I don’t think it’ll ever make a good PC. They were always destined for the landfill.
Meanwhile, the best thinkpads were quality machines back when they came out. IMO, that’s why they’re still so versatile today. Free software can’t fix bad fundamentals.
Not sure what motherboard you have: Most consumer boards only support “FakeRAID”, which requires a kernel driver to actually function. Good luck finding a vendor who wrote a driver for Linux.
I’d definitely recommend software RAID instead, as you’ll have better support. I like btrfs, so I’d recommend you set up your new drives to use a btrfs RAID configuration. mdadm is another option, if you really like ext4.
On Linux, I run fwupdmgr to periodically check for firmware updates. Not every manufacturer supports it yet, but I’ve had good results with a few laptops. Not sure if it supports BIOS.
Also though, I generally try to leave my BIOS alone if everything is working fine. Unless I hear of a reason to update, I’d rather stay on a stable version.
Are you an emacs user?
Try org-roam. It’s a similar system to obsidian, but fully open source. You have all the note taking techniques of org-mode, and all the scripting power of emacs.
I’d recommend BTRFS in RAID1 over hardware or mdadm raid. You get FS snapshotting as a feature, which would be nice before running a system update.
For disk drives, I’d recommend new if you can afford them. You should look into shucking: It’s where you buy an external drive and then remove (shuck) the HDD from inside. You can get enterprise grade disks for cheaper than buying that same disk on its own. The website https://shucks.top tracks the price of various disk drives, letting you know when there are good deals.
As an emacs user, I use M-x man. All my standard keybindings make finding what I need very easy.
Of course, it’s not so fast if you aren’t already in emacs.
I wouldn’t trust anything like that to the open internet. It would be better to access the system over a VPN when you’re outside the network.
How about writing a script to automate the deletion, thus minimizing the chance of human error being a factor? It could include checks like “Is this a folder with .git contents? Am I being invoked from /home/username/my_dev_workspace?”
In a real aviation design scenario, they want to minimize the bullremoved tasks that take up cognitive load on a pilot so they can focus on actually flying. Your ejector seat example would probably be replaced with an automatic ejection system that’s managed by the flight computer.
It would have to iterate over all saved keys, which sounds rather inefficient to me and potentially unsafe (timing attacks etc.)
sshd only checks for matches in the user’s authorized_keys file, not system wide.
I needed to find large directories on disk the other week, and found the tool btdu to be quite useful.
It could be a firmware update. I noticed on my machine that there was always one update in the discover program that appeared as ready but never got installed.
Turns out I had to manually run fwupdmgr update to install it.
If you want to move your containers to a different location, look into configuring docker’s
data-root: https://stackoverflow.com/questions/24309526/how-to-change-the-docker-image-installation-directoryYou copy
/var/lib/dockerto a new location and update/etc/docker/daemon.jsonI will say: Moving data-root to an NFS mount isn’t going to work well. I’ve tried it, and docker containers rely on filesystem features to run their overlays. On an NFS, this feature isn’t present, so your services will duplicate the container’s entire filesystem. This will tank your performance and is basically unusable for anything but trivial examples. Docker data-root basically needs to be a “physical” disk.
I’ve had no issues using NFS shares mounted as docker volumes. It’s just the data-root where it’ll fail.