Explore the world of Linux with clear, approachable guides. Whether you’re just starting out or looking to sharpen your skills, you’ll find something to brew your interest here.
I’ve been on the hunt for a reliable backup solution that can handle my laptop’s limited disk space for ages. When I stumbled upon Borg Backup in 2025, I thought I’d finally found the answer. This deduplicating backup program has been a game-changer, but I soon realized that its default settings weren’t exactly optimized for my laptop’s storage constraints. So, I set out to tame the beast and get Borg Backup to respect my laptop’s limited disk space.
[Read More]I’ve found that managing resources on Linux systems can be a real challenge, especially when dealing with resource-intensive desktop apps. That’s where cgroups come in - a powerful tool that allows you to allocate and manage system resources such as CPU, memory, and I/O for a group of processes. In my experience, cgroups can be a game-changer for keeping your system running smoothly.
To get started with cgroups, you’ll need to create a new group using the cgcreate command. This command not only creates the group but also specifies the subsystems that will be controlled. For example, to create a cgroup that controls CPU and memory usage, you can use the following command:
I’ve gotten pretty used to relying on my terminal history to recall previously executed commands. But let’s be honest, over time this history can become a mess with unnecessary entries, making it tough to find what I need. In this article, I’ll cover how to customize Bash history behavior to reduce clutter and improve productivity.
Bash history is stored in a file specified by the HISTFILE environment variable, which defaults to ~/.bash_history. Each time a command is executed, it gets appended to this file. The HISTSIZE variable determines the maximum number of commands stored in memory, while HISTFILESIZE sets the maximum number of commands written to the history file.
To view your current Bash history settings, you can use the following commands:
I’ve always been concerned about my laptop’s power consumption, and in 2025, I noticed my battery life was decreasing significantly. After some research and experimentation, I was able to get my laptop’s power consumption under control. I’ll share my experience and the steps I took to achieve this.
The first step was to identify the main power-hungry components of my laptop. I used the powertop tool to monitor my laptop’s power consumption in real-time. This tool provides a detailed breakdown of power usage by component, allowing me to pinpoint the areas that needed improvement.
I’ve been using Linux for years, and one of the things that’s really helped me streamline my workflow is using aliases and functions in Bash. These tools let you simplify long commands, reducing typos and making your life easier. In this article, I’ll share some of my favorite aliases and functions for taming long commands in Bash.
Aliases are basically shortcuts for longer commands. You can create an alias using the alias command followed by the name of the alias and the command it should execute. For example:
As someone who’s spent years running a homelab, I’ve found that managing background tasks is crucial. These tasks need to keep running even after I’ve logged out of my system, and they’re essential for things like backups, system monitoring, and maintenance scripts. I used to rely on screen and tmux to keep these tasks running, but I’ve recently switched to using nohup and systemd. In this article, I’ll share my experience with these tools and provide some practical examples.
I’ve been noticing that my desktop Linux system has been taking a painfully long time to boot - we’re talking around 5 minutes, which is way longer than I’m used to. As someone who values a fast and responsive system, I decided to dig in and see what was causing the slowdown. In this article, I’ll walk you through the steps I took to identify and fix the issue, and share some practical tips for optimizing your own Linux system’s boot time.
[Read More]I’ve lost count of how many times I’ve encountered “dependency hell” as a Linux user. You know, that frustrating situation where package dependencies conflict, causing installations or updates to fail. On Debian-based systems, I’ve found that apt pinning can be a lifesaver. In this article, I’ll share my experience with apt pinning, including its benefits, usage, and potential pitfalls.
Apt pinning is a feature of the Advanced Package Tool (apt) that allows you to assign priorities to packages. This priority system enables you to control which package versions are installed or updated, helping to avoid dependency conflicts. By assigning a higher priority to a specific package version, you can ensure that it’s installed instead of a newer version that might cause conflicts. I’ve seen this go wrong when you don’t use apt pinning, and it’s not fun to deal with.
[Read More]As someone who’s spent years running Linux systems, I can tell you that log management is crucial. Logs provide valuable insights into system activity, helping you troubleshoot issues and identify potential security threats. However, log noise can quickly become overwhelming, making it difficult to find relevant information. In my experience, journalctl and logrotate are two essential tools for managing logs on a small home server setup.
I’ve seen this go wrong when my system takes an eternity to boot up or start services. Usually, the culprit is a systemd service issue. systemd, being a core component of most modern Linux distributions, manages system services, boot processes, and more. When troubleshooting these delays, systemd-analyze is my go-to tool.
The real trick is to use systemd-analyze to get insights into the boot process and service startup times. Don’t bother with complicated commands - just use the plot option to generate a graphical representation of your system’s boot process: