news
Technical Articles About GNU/Linux and FreeBSD
-
XDA ☛ 5 tiny tweaks that make a new Linux install feel perfect in just a few minutes
You’ve just installed Linux, and everything looks shiny and new. The desktop is clean, the system is running, and you’re ready to dive in. But before you start using it day to day, there are a few simple steps you can take that can make the experience nearly perfect. Linux distributions like Ubuntu, Fedora, or Debian come ready to use right after installation, but with a little fine-tuning, you can take things from good to great.
-
TuMFatig ☛ Migrate a Peertube instance from Debian to FreeBSD
Not matter how hard I try, I can’t stand and learn those
systemdandipcensored swearingstuff on Linux. Call me an old fart with muscle memory amnesia but I just want to manage my servers usingrcscripts,ifconfigandroutecommands, and read my logs insyslogflat format. Anyway, my Peertube instance was running on Debian and I wanted to use some BSD instead of Linux. -
HowTo Geek ☛ 4 Signs You’re Becoming a Linux Power User
You may not be a power user yet, but you've undoubtedly grown since you started using Linux. Power user or not, by virtue of using Linux, you're on course to become one, and the symptoms will show. I have detailed my personal experience and symptoms; perhaps you have your own?
4 There's Always a Terminal Window Open
When I used Windows, I barely touched the command shell, except to run a shutdown timer or enter the odd command. The Windows command shell feels stuck in the 90s—it hasn't really changed. There's no autocomplete, it lacks useful utilities and practical scripting, and it uses backslashes in file paths. It was awkward, so I avoided using it.
When I switched to Linux, I didn't start using the terminal immediately. I assumed it would be difficult to learn, so I delayed. However, I soon discovered that installing software via the terminal was easy, and so I started using it frequently. Over time, I gradually expanded upon my skills. Now, for many years, the terminal has been the first thing I open after booting.
-
XDA ☛ 3 reasons I love my Proxmox cluster (even though the average home labber doesn't need one)
Before I dove into the home lab rabbit hole, I assumed server setups require high-end hardware that costs at least a thousand dollars, if not more. While there are certain distros that require a high-end workstation, Proxmox isn’t one of them, and it can deliver decent performance on even the most potato system. In case you're wondering, then yes, I speak from experience. After installing Proxmox on my N100 SBC and a decade-old laptop a while ago, I figured I should build a cluster out of these devices.
One thing led to another, and I ended up building a triple node PVE cluster after throwing an old Ryzen 5 1600 PC into the equation. Having used this weird but highly functional setup for more than a few weeks, I’ve grown to love my Proxmox cluster – even though it has some glaring issues.
-
XDA ☛ I added real-time temperature monitoring to my Proxmox dashboard, here's how
Despite working on wacky experiments all the time, I take my home lab management tasks seriously. As such, monitoring services, add-ons, and tools rank high on my list of mission-critical applications. I rely on Uptime Kuma to track the operational status of my container army, while Beszel keeps an eye on my server nodes. These days, I use Pulse to monitor my Proxmox workstations as well as the LXCs and VMs running on them from a neat dashboard.
Speaking of Proxmox, I also appreciate the extra graphs added to PVE 9, as they let me check the resource contention on my servers. But as someone who has set up system temperature monitoring via Conky widgets (on Linux systems) and Rainmeter plugins (on Windows PCs), I’m not fond of the fact that I can’t monitor the temps of the server nodes on Proxmox. So, one thing led to another, and I ended up trying out some packages and tools to bring temp sensors to my PVE workstations.