Linux Basics Day 5: Shell Scripting and Automation

🚀 Day Progress Update – Linux & Bash Scripting Today I focused on strengthening my fundamentals in Linux and Bash scripting, and I’m starting to see how things connect beyond just commands. 🔹 Key concepts I practiced: File & directory management (mkdir, touch) Understanding relative paths (. and ..) Searching logs using grep Counting results with pipes (| wc -l) Output redirection (> vs >>) Script execution (chmod +x, ./script.sh) Understanding the purpose of the shebang (#!/bin/bash) Capturing command output into variables ($(...)) 🔹 Biggest takeaway: Instead of memorizing commands, I focused on understanding why things work: How the system interprets scripts How paths depend on your current directory How commands can be chained to solve real problems 🔹 Mini practical use-case: Built a simple log-checking flow to: ✔ Extract error lines ✔ Count them ✔ Prepare for conditional checks (next step) 📈 Moving forward: Next focus is on: Writing conditional logic (if statements) Automating tasks with loops Building small real-world scripts Consistency over intensity. One step at a time. #Linux #Bash #DevOpsJourney #LearningInPublic #Scripting #Automation

Most developers learn Linux commands. Very few actually use them to think better while working. I recently cleaned up my messy Linux notes, and one thing became clear: It’s not about remembering commands like ls, cd, or grep. It’s about understanding how everything connects. A few things that genuinely changed how I work: • find + -exec vs xargs → same goal, completely different execution behavior • source vs bash script.sh → one changes your current environment, the other doesn’t • permissions (rwx) → not theory, but literally controlling access at system level • pipes | → small commands, but together they become workflows • .bashrc → your terminal is not fixed, you can shape it The shift was this: I stopped treating Linux as “commands to memorize” and started seeing it as a system I can control. Still learning, but now it actually feels useful in real dev work instead of just interview prep. If you're a developer and still relying only on GUI tools, try spending a few days in the terminal. It’s uncomfortable at first, but worth it. #developers #linux #backend #devtools #softwareengineering #productivity #programming #learninpublic

📂 Understanding Absolute vs Relative Paths in Linux Navigating the Linux file system becomes much easier once you clearly understand the difference between absolute and relative paths. 🔹 Absolute Path Starts from the root (/) and gives the complete location of a file or directory. Example: /folder1/folder2/folder3 ✔ Works from anywhere in the system 🔹 Relative Path Defined based on your current directory. Uses: . → current directory .. → parent directory Example: From /folder1/folder2/folder3 → cd ../../f1/f2/f3 💡 Key Takeaway Absolute path = full address Relative path = directions from where you are ✅ When to Use What? Use absolute paths when you need reliability (scripts, cron jobs) Use relative paths for quick navigation and portability within projects Mastering both helps you move efficiently, write better scripts, and manage files like a pro in Linux 🚀 #Linux #DevOps #Programming #SystemAdministration #Learning

Most people use Linux… But very few automate with it. While going through Mastering Linux Shell Scripting, one thing became clear: 👉 Scripting is what separates users from engineers. 💡 What stands out: Shell scripting is not just about commands… 👉 It’s about automating repetitive tasks and saving time As highlighted early in the book: 👉 We don’t need to do repetitive tasks manually when scripts can handle them. 🔍 Realization: With simple scripts, we can: ✔ Automate system tasks ✔ Handle user input dynamically ✔ Build reusable workflows ✔ Debug and optimize processes Even a basic script can: 👉 Take input 👉 Process it 👉 Produce meaningful output ⚡ What this means for us: Instead of doing things manually every time… 👉 We should start thinking in terms of automation Because: 🔹 Scripts scale 🔹 Manual work doesn’t What’s one task you would automate if you had the chance? Credit: @Andrew Mallett #Linux #ShellScripting #Automation #DevOps #Engineering #TechSkills #Programming #SoftwareEngineering #Learning

Most people use Linux… But very few actually understand it. While going through Advanced Linux: The Linux Shell and Toolkit, We realized something important: 👉 Linux is not just an operating system 👉 It’s a powerful tool for automation and system control 💡 What stood out to us: From the early chapters: 👉 The shell is a command interpreter that allows direct interaction with the system 👉 It doesn’t just execute commands… 👉 It also acts like a programming language That means you can: ✔ Automate repetitive tasks ✔ Write scripts to manage systems ✔ Control processes and workflows 🔍 Real-world insight: According to the manual (page 14): 👉 Shell scripts are used internally by Linux for system operations like startup processes and services That means: 👉 The OS itself runs on automation ⚡ What makes this powerful? With just shell scripting, you can: 🔹 Automate deployments 🔹 Monitor servers 🔹 Manage users and permissions 🔹 Process files and logs And as highlighted in the book (page 24): 👉 If you can use the shell… you can program 💡 OUR TAKEAWAY If you’re in tech: 👉 Learn Linux 👉 Learn the shell 👉 Learn automation Because: 🚫 Clicking doesn’t scale ✅ Automation does What’s the most powerful thing you’ve done (or want to do) with Linux? Credit: Tobias Elsner @Anselm Lingnau #Linux #DevOps #ShellScripting #Automation #CloudComputing #Engineering #TechSkills #SoftwareEngineering #STEM #CareerGrowth

📅 Week 9 Learning Summary This week I focused on: ✔ Troubleshooting mindset ✔ Linux debugging ✔ SQL performance ✔ Incident handling Becoming better at solving real problems every day. #LearningInPublic #CloudEngineerJourney

In this lab, I build a user management script that prompts for a username, creates the account, sets a password, and adds the user to a group. It shows how Bash can take user input and turn it into automated system commands. This lab also helps me practice system administration while improving my Bash scripting skills. #Linux #Bash #ShellScripting #SystemAdministration #DevOps #Automation

🐧 Revisiting Linux Fundamentals After working with Docker and Jenkins pipelines, one thing became clear: All of it runs on Linux. So today, I stepped back and revised the fundamentals. 🔹 File System & Navigation Understanding /, /home, /var, /etc Knowing where things live = faster debugging 🔹 Permissions & Ownership chmod, chown, sudo Security and control start here 🔹 Process Management ps, top, kill Because something will break — and you’ll need to fix it 🔹 Package Management apt, install, update Managing dependencies at system level 🔹 Logs & Monitoring /var/log, tail -f, journalctl If you can read logs, you can solve problems 🔹 Networking Basics netstat, ss, ports Critical for debugging services and containers 💡 Key Realization Tools like Docker and Jenkins don’t replace Linux — they depend on it. 📌 Why This Matters When pipelines fail or containers crash, you’re not debugging Docker… you’re debugging Linux.

🚀Next step towards devops journey🚀 💻Used to type the same Linux commands again and again… until I learned Shell Scripting 💻 🌠At the beginning, Linux felt a bit confusing with so many commands to remember. But once I understood how shell scripts work, things became much simpler. Now I can: ♣Automate repetitive tasks ♣Write basic scripts ♣Use shebang (#!/bin/bash) properly ♣Display output with echo ♣Work with loops, conditions, and variables 🌠It’s a small step, but it really changed how I use Linux. 🌠I’ve created a simple PPT to explain these concepts in an easy way. 💻You can also check my scripts and resources here: 🔗 GitHub Repository: https://lnkd.in/dxzCa8uB If you're just starting with Linux or DevOps, this might help you 👍 #Linux #ShellScripting #DevOps #Learning #Automation #Beginner #GitHub

🚀 Boost Your Productivity in Linux Terminal The difference between a regular user and a pro is "speed". This image summarizes the top tools to save your time: 🔹 Master Shortcuts: Move lightning-fast with Ctrl + A/E for start/end, and delete lines instantly with Ctrl + K/U. 🔹 Smart Search: Stop retyping long commands. Use Ctrl + R to search history and Tab for auto-completion. 🔹 System Analysis: Monitor disk space clearly with df -h and check folder usage with du -sh. 🔹 File Management: Get full details on hidden files and permissions using smart ls filters. 📌 Key Takeaway: Mastering these simple tools multiplies your speed on dev and admin tasks. #Linux #DevOps #Terminal #Coding #SysAdmin #Bash #Productivity