How to record and replay your terminal session with Linux

🐚 Under the Shell — Day 1: The Hidden Mind of the Shell Most people think the shell just “runs commands”. But the shell doesn’t run commands — The shell is the brain that interprets your commands. When you type something like: echo $HOME/*.txt Linux doesn’t see this command the way you typed it. Before sending it to the kernel, the shell secretly performs a series of transformations: 🔹 Variable expansion 🔹 Pathname expansion 🔹 Word splitting 🔹 And finally, execution Miss one step — and your command behaves completely differently. Ever wondered why echo "$HOME/*.txt" and echo $HOME/*.txt give different results? That’s shell expansion at work — the invisible logic most people never notice. And here’s another one: $(command) actually runs in a sub-shell — a new shell instance inside your current one! That’s why environment variables you set inside it don’t persist afterward. So next time you run a command, remember — the shell is not a messenger. It’s a mind that rewrites your command before Linux even sees it. #Linux #SysAdmin #DevOps #RHCSA #Bash #ShellScripting #LearningInPublic #UnderTheShell

The Linux Foundation just released on YouTube the yearly talk with Mr. Torvalds, which is essentially the only time he speaks in public during the year. As someone who burns with passion for software and product, I always find it very educational to watch. The concept that caught my attention most in this talk is transcribed below. I cannot stress enough that building "boring code" is one of the most intelligent practices you can enforce as a software architect, because boring means: stable, predictable, deterministic, easy to maintain and easy to expand. Moreover, being able to say "No" helps tremendously in creating software that grows organically and in preventing enthusiasm spikes from turning into impulsive technical decisions. "If I look at the process, we have had a very consistent process in the Linux kernel development for 15 years now. And one of the things that's so interesting is that to the press, this is too boring. [...] I used to say that my job is often to say no that people come and uh have some radical new idea that maybe it's really interesting but at the same time it it sounds like a maintenance nightmare and I go No, you go off, you prove this new feature in your own sandbox and you do this and then you come back with numbers and show that I was wrong." #linux #softwarearchitecture #development #productmanagement https://lnkd.in/d4F5gS9X

Why Zig for the new _rzilient CLI tool? Over time, I built a chunky Bash script to handle internal workflows , pulling logs, running tests, deploying environments with #Kamal. It started as a quick helper, but like most “quick” scripts, it turned into a mess, OS dependent tangle tied only to my own machine or Linux OS. We needed something cleaner and more portable. I wanted a tool that any dev could use, whether on Linux, macOS, or Windows as well as without struggling with dependencies or shell tricks. That’s where #Zig came in. It gave me just the right balance: low-level control, fast performance, and seamless cross-compilation. No macros that I'm not familiar with, no surprise behavior, just "simple", readable code that builds everywhere. So I’m turning that Bash beast into a proper Zig-based CLI. Same features, but easier to maintain and share across the team. As a plus, honestly, the Zig community is great, I’d say on par with the Rails community. Even though I’m not highly proficient with it, I’ve never gotten a bad answer to a question, even when the solution was right in front of me. If you're experimenting with Zig and wondering where to start, building internal command-line tools like this is a great entry point. Your teammates will thank you. #ZigLang #DevTools #CrossPlatform #InfraAutomation #rzilient #Zig

Tired of your Linux system feeling slow and cluttered? 🤔 A clean machine isn't just faster—it's more secure and easier to manage. Here are a few simple commands to give your Linux environment a spring clean: 🧹 Clean package cache: Use `sudo apt-get autoclean` or `sudo dnf clean all` to remove old package files. 🗑️ Remove orphans: Run `sudo apt-get autoremove` or `sudo dnf autoremove` to uninstall dependencies that are no longer needed. 📜 Manage logs: Check `/var/log` for old log files. Use `journalctl --vacuum-time=2weeks` to clear old systemd journal logs. 🧠 Free up memory: Clear your page cache, dentries, and inodes with `sudo sync && echo 3 | sudo tee /proc/sys/vm/drop_caches`. Regular maintenance keeps your system running at peak performance and prevents small issues from becoming big problems. What are your go-to commands for Linux maintenance? Share them below! 👇 #Linux #LinuxGuide #ServerManagement #SysAdmin #ITtips #ComputerTips #TechWithVelkaja #VALLUNAR #VallunarGroups #DevOps

💻 Automating Backups with a Simple Bash Script! I recently created a small but powerful Linux automation script that performs system backups and even allows easy restoration — all in just a few lines of code. Here’s what it does: ✅ Compresses important files into a dated .tar.gz archive ✅ Verifies successful backup creation ✅ Provides a one-line restore command for easy recovery This kind of automation is a real time-saver for developers and system admins who regularly manage multiple directories or projects. I’ve shared it on GitHub under the name backup_restore.sh, showcasing how simple scripting can make everyday tasks smarter and more reliable. 🔗 https://lnkd.in/gs3MBb5K #Linux #Automation #ShellScript #Bash #DevOps #Backup #OpenSource #GitHub #Scripting #Tech

Ever been surprised by how much disk space a package actually eats up after installation? I've been there—especially when working on systems with limited storage. That's why I've started checking install sizes for packages before pulling the trigger on both my Arch (Pacman) and Debian/Ubuntu (Apt) systems. What's really useful is seeing both the package size alone AND its total size with dependencies. It's wild how sometimes a small utility ballooons into hundreds of megabytes once you factor in everything it needs to run. This quick check has saved me from bloating my system more times than I can count, especially on development containers where every megabyte counts. It's one of those small habits that makes a big difference over time. Being mindful about what we install isn't just about disk space—it's about understanding our tools better and building more efficient systems. Sometimes the simplest commands teach us the most about our environment. If you're working with Linux, this is definitely a trick worth adding to your toolbox. https://lnkd.in/etHivNJh #Linux #Development #DevOps #SystemAdministration #FullStackDeveloper

Superblock: In every Linux filesystem (like ext4,xfs) has a Superblock, It contains complete details or metadata about that specific filesystem, its similar like "Linux inode" but here instead of storing metadata about file , Superblock store metadata about a entire filesystem. Eg:- file system metadata's: Filesystem type (ext4, xfs, etc.), total size, free and used Inodes, last mount time, and more. Without "SuperBlock" , Linux won’t know where your files are and how to interpret a file system so its very very important linux design feature to keep in your mind. If we learn something theoretically our tech mind always want to see it in practical, is n't it? lets see how can I see superblock details? sudo dumpe2fs /dev/sda1 --> this command will list all info about that file system. If the file system gets corrupted we can use this feature to restore it, even linux stores duplicate copies of superblock in different locations as backup. #DevOps #Linux

Recently, I needed to copy the largest video files from my phone to my PC, something that could’ve been done with some GUI steps, but not as fun (or efficient). So, I turned it into a quick scripting challenge instead, a chance to practice logic, pipelining, and automation in Linux. A small script combining 𝗳𝗶𝗻𝗱, 𝗱𝘂, 𝘀𝗼𝗿𝘁, and 𝘄𝗵𝗶𝗹𝗲, connected through Linux 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗶𝗻𝗴 handled it perfectly. Everyday tasks could be great opportunities to practice scripting and automation in Linux, building the same problem-solving mindset that drives real projects, until efficiency simply becomes part of how you think. #Linux #ShellScripting #Automation #DevTools #LearningByDoing

Have you ever tried to automate a script that requires input, but does not take input via cli flags like, `-y` or `--yes` or something? I was stuck there and found out that there is a command named `yes`, yes, literally yes. Here is how you can use it. yes this_post_is_awsome | ./your_script Or if the script requires multiple inputs, and you know how many inputs it will require, I hope you know the script you are running and not some random script from the internet. So you can use something like printf '0\n1\n2\n3' | ./your_script #linux #scripting #automation

Linux Tip: Copy a File to Multiple Directories in One Command. Ever needed to copy the same file to multiple locations? Here's an elegant solution using echo, xargs, and cp: echo /home/user/Videos/ /home/user/Downloads/ | xargs -n 1 cp -v /home/user/test.txt How it works: 1. echo lists your target directories. 2. xargs -n 1 processes each directory one at a time. 3. cp -v copies the file with verbose output. Why this matters: → Saves time on repetitive tasks → Perfect for deployment scripts → Cleaner than writing multiple cp commands → Easily scalable to dozens of directories Pro tip: Add more directories to the echo command to scale this to as many locations as you need! #Linux #DevOps #SysAdmin #Terminal #TechTips #Automation #Productivity