Forem: Sana Muhammad Sadiq

Linux Myths vs Reality: What Beginners Should Know

Sana Muhammad Sadiq — Thu, 08 May 2025 19:06:14 +0000

Introduction

As I continue my 30-day Linux challenge in preparation for the RHCSA exam, today marks a milestone — the final day. And what better way to wrap up than by clearing the fog surrounding Linux itself?

Linux is often wrapped in layers of myth, hearsay and outdated assumptions — scaring off beginners and making even seasoned IT professionals second-guess exploring it deeper. Today, we’re busting the biggest myths and laying out the realities with clear explanations, practical examples, industry insights and real-time scenarios. Let’s get comfortable with the truth.

Index

Myth 1 Linux is Only for Programmers and Hackers
Myth 2 Linux Has No Good Applications
Myth 3 You Must Know Terminal Commands to Use Linux
Myth 4 Linux is Hard to Install and Configure
Myth 5 Linux is Not Suitable for Work or Enterprise
Myth 6: You Cannot Play Games on Linux
Recommendations
Quick Summary
Closing Thoughts Why This Matters

👨‍💻 Myth 1 Linux is Only for Programmers and Hackers

💡 Reality: Linux is for everyone — from writers to IT administrators.

Linux has matured dramatically over the years. Today, beginner-friendly distributions like Ubuntu, Linux Mint and Fedora Workstation offer intuitive graphical interfaces that rival Windows and macOS.

Example: My non-tech cousin (a content writer) — switched to Ubuntu for its speed and privacy. She uses LibreOffice, Firefox and GIMP daily without touching the terminal.

✅ Tip: Start with "Ubuntu" or "Linux Mint" if you’re a complete beginner. You’ll feel right at home with familiar menus and app stores.

💻 Myth 2 Linux Has No Good Applications

💡 Reality: Linux has thousands of powerful apps; often free and open-source.

Whether you’re designing, coding, writing or just browsing, Linux covers it all.

Examples:

LibreOffice → MS Office alternative

GIMP → Photoshop alternative

VLC Media Player → Media player

VS Code → Coding IDE

Kdenlive → Video editing

Industrial Insight: Major corporations like Google, Netflix and NASA use Linux-powered systems daily — often with customized tools and applications.

✅ Tip: Explore "Flathub" or your distribution’s app store to discover apps instantly.

📟 Myth 3 You Must Know Terminal Commands to Use Linux

💡 Reality: You can get by without the terminal — but learning a few commands boosts confidence.

Modern Linux distros provide GUI-based tools for almost everything: installing apps, managing files, adjusting settings.

Real-Time Scenario:
Installing VLC Media Player:

GUI: Open Software Center → Search "VLC" → Click Install
Terminal (optional): sudo apt install vlc

✅ Tip: Gradually learn essentials like ls, cd, cp and rm — they’ll make you feel empowered, not overwhelmed.

🔧 Myth 4 Linux is Hard to Install and Configure

💡 Reality: Most distros today have foolproof installers.

Ubuntu’s installer takes 15–20 minutes, with guided, step-by-step instructions and it is often faster than Windows installations.

Industrial Insight: System administrators globally spin up Linux servers in minutes using automated tools like Ansible, Terraform and cloud-init.

✅ Tip: Try Linux first using a Live USB or Virtual Machine — risk-free, no changes to your system.

🌐 Myth 5 Linux is Not Suitable for Work or Enterprise

💡 Reality: Linux powers most of the internet and Fortune 500 companies.

Real-Time Scenario:

Amazon Web Services (AWS) — runs on customized Linux AMIs

Android OS — based on the Linux kernel

Stock Exchanges — New York Stock Exchange (NYSE) uses Linux servers for high-frequency trading

✅ Tip: Learning Linux (even basic sysadmin skills) massively boosts career prospects in cloud computing, DevOps, data science, and cybersecurity.

🎮 Myth 6 You Cannot Play Games on Linux

💡 Reality: Gaming on Linux is exploding.

With Proton (by Valve/Steam), thousands of Windows games run smoothly on Linux.

Examples:

Counter-Strike: Global Offensive (CS:GO)

The Witcher 3

Rocket League

✅ Tip: Install Steam for Linux and enable Proton — you’ll be amazed.

🛡️ Recommendations

If You’re Still Hesitant:

Start small: Dual-boot Linux alongside Windows or run it in VirtualBox.
Join a community: Linux has vibrant support forums, Reddit threads and Discord servers.
Practice real-world tasks: Like installing apps, setting up Wi-Fi printers and browsing the web.
Consider certifications: RHCSA, LFCS or Linux+ can validate your growing skills.

🧠 Quick Summary

The Truth About Linux

Myth	Reality
Linux is just for hackers	It’s for everyone
No good apps	Thousands of powerful apps
Terminal is mandatory	Optional, but useful
Hard to install	Easier than ever
Not for work	Powers global enterprises
No games	Gaming ecosystem thriving

👩🏻‍💻 Closing Thoughts Why This Matters

Over the last 30 days of my Linux challenge, I realized Linux is less about commands and more about mindset:
Curiosity, community, and continuous learning.

Whether you're a non-tech professional, IT aspirant or business owner — knowing the truth about Linux can save money, boost security and open career doors.

Don’t let myths limit you. Explore with confidence.

Here’s to open-source, empowerment and lifelong learning. See you in the shell!

— Sana

I'd love to hear your thoughts, insights or experiences with Linux. Feel free to share and join the conversation [ Connect with me on LinkedIn www.linkedin.com/in/techwithsana ]💜

#30dayslinuxchallenge #redhat #networking #cloudcomputing #cloudengineer #cloudarchitect #cloud #RHCSA #RHCE #RHEL #WomeninTech #Technology

Linux for Non-Techies: A Simple Guide to Getting Comfortable

Sana Muhammad Sadiq — Thu, 08 May 2025 19:05:02 +0000

Introduction

As I continue my RHCSA journey with the 30-day Linux challenge. Today, I want to step back from the deeply technical commands and configurations and instead speak directly to the non-techies — the project managers, analysts, entrepreneurs, marketers and curious learners who’ve always heard about Linux but found it intimidating or irrelevant to their daily workflows.

Spoiler alert: Linux isn’t just for system admins and developers anymore.
It’s a powerful, stable and surprisingly user-friendly environment that can make you more productive, resourceful and confident — no matter your job title.

In this guide, I’ll break it all down simply with examples, helpful tips, real-world cases and industry insights so you’ll walk away saying:

“I can use Linux, and I’m comfortable doing it.”

Index

Why Non Techies Should Care About Linux
Linux Basics Made Easy With Examples
Helpful Tips to Get Comfortable
Industrial Insights and Real Time Scenarios
Recommendations for Non Techies
Quick Summary

🌍 Why Non Techies Should Care About Linux

“You don't have to be a developer to harness the power of Linux — you just need to know where to start.”

Fact: 96.3% of the world’s top 1 million web servers run Linux (source: W3Techs).

Even if you’re not managing servers, understanding Linux gives you an edge in modern workplaces where cloud platforms, containers, automation, and data pipelines are increasingly Linux-based.

Real-World Case Study

A marketing manager at a SaaS company started using Linux (via a virtual machine) to:

Access large CSV datasets faster.
Run simple scripts to clean mailing lists.
Automate reports from their CRM tool using basic Bash scripts. — Result: Less dependency on overbooked IT teams and quicker time-to-insight.

🛠️ Linux Basics Made Easy With Examples

Let’s take intimidating Linux concepts and translate them into everyday language.

Linux Concept	Simple Explanation	Example
Terminal	A command box, like a Google search bar — but for your computer.	`ls` = Show me what files are here
Home Directory	Your personal “Documents” folder.	`cd ~` takes you there
Package Manager	App Store for Linux software.	`sudo apt install firefox` installs Firefox
Permissions	Who can see/edit the file?	`chmod 755 file.txt` sets view/edit rules
Shell Script	A to-do list for the computer to follow automatically.	Automate “send email + backup files”

💡 Helpful Tips to Get Comfortable

1. Don’t install Linux on your main machine (yet)

Start with:

VirtualBox + Ubuntu ISO → Run Linux inside Windows/Mac.
WSL (Windows Subsystem for Linux) → Best for Windows users.
Live USB → Try Linux without installing (plug-and-play).

2. Stick to Graphical Interfaces first

Modern Linux desktops (like Ubuntu, Fedora, Zorin OS) look just like Windows or Mac.

Tip: You don’t have to use the terminal immediately. Click around first!

3. Google every error unapologetically

99% of Linux problems have been solved (and documented).

“Copy → Paste error → Google → Solution” — That’s the real Linux workflow.

🏢 Industrial Insights and Real Time Scenarios

Industry	Linux Use Case	How Non-Techies Benefit
Finance	Batch process reports, automate reconciliations	Faster reporting without IT bottlenecks
Healthcare	Secure data storage, encrypted file handling	Improved patient data privacy
E-commerce	Server maintenance, database queries	Better communication with dev/ops teams
Content Creation	Open-source creative tools (GIMP, Inkscape)	No need for costly licenses

Example:
A Product Manager who understands basic Linux commands can:

SSH into cloud servers to check logs.
Pull real-time sales data from SQL databases.
Communicate with DevOps teams more fluently.

In 2025, Linux literacy = career agility.

⭐ Recommendations for Non Techies

Start with Ubuntu → Easiest Linux flavor, most user-friendly.

Bookmark These Resources:

Linux Journey (Beginner-friendly)
Explainshell.com (Explains any Linux command)
OverTheWire: Bandit (Fun Linux game)

Practice 5 Commands Daily → ls, cd, cat, nano, grep
(That’s it. These cover 80% of basic needs!)

Shadow a Colleague → Ask a DevOps or IT teammate to show you one real task they do on Linux.

📝 Quick Summary

Linux isn’t just a playground for tech enthusiasts anymore — it’s an empowerment tool.
For non-techies, becoming “Linux comfortable” doesn’t mean becoming a sysadmin.
It means:

Speaking the language of modern IT and cloud.
Automating tedious tasks.
Unlocking tools that give you independence and speed.

I'd love to hear your thoughts, insights or experiences with Linux. Feel free to share and join the conversation [ Connect with me on LinkedIn www.linkedin.com/in/techwithsana ]💜

#30dayslinuxchallenge #redhat #networking #cloudcomputing #cloudengineer #cloudarchitect #cloud #RHCSA #RHCE #RHEL #WomeninTech #Technology

Configuring and Securing SSH Access in Linux

Sana Muhammad Sadiq — Thu, 08 May 2025 19:03:02 +0000

As I continue my RHCSA journey with the 30-day Linux challenge. Today’s topic is all about something that powers remote access and server administration in the Linux world SSH (Secure Shell). If you’ve ever connected to a remote machine securely, you’ve likely used SSH already. But configuring and securing it properly? That’s where many stop short and that’s exactly what we’ll tackle today.

🔍 What is SSH?

SSH (Secure Shell) is a protocol used to securely log into remote systems over a network. It encrypts all the traffic, preventing eavesdropping, connection hijacking and other attacks.

🛠️ Basic SSH Command

ssh username@remote_host

username: user on the remote machine
remote_host: IP or hostname of the server

📦 Installing SSH

On Ubuntu/Debian:

sudo apt install openssh-server

On RHEL/CentOS:

sudo dnf install openssh-server

🔐 Start & Enable SSH Service

sudo systemctl start sshd
sudo systemctl enable sshd

🔐 Securing SSH Access (Best Practices)

✅ Change the default port
Edit /etc/ssh/sshd_config:

Port 2222

✅ Disable root login

PermitRootLogin no

✅ Use SSH key authentication

ssh-keygen
ssh-copy-id user@remote_host

✅ Limit users who can login

AllowUsers sana ali devops

✅ Use Fail2Ban or firewall rules to block brute-force attempts.

📁 Real-Time Use Cases

🔹 DevOps teams use SSH keys for secure deployments.
🔹 Sysadmins monitor cloud instances without exposing passwords.
🔹 Developers connect to staging servers to test builds securely.

💡 Pro Tips

Always backup your ~/.ssh directory.
Use ssh -v to troubleshoot SSH issues.
Audit /var/log/auth.log for unauthorized attempts.

🧠 Quick Summary

Task	Command / Action
Connect to SSH	`ssh user@ip`
Generate SSH key	`ssh-keygen`
Copy key to remote	`ssh-copy-id user@host`
Change default port	Edit `/etc/ssh/sshd_config`
Restart service	`sudo systemctl restart sshd`
Disable root login	`PermitRootLogin no`

SSH is your gateway to the Linux world but with great power comes great responsibility. By taking the time to secure your SSH access, you’re not just connecting remotely; you’re building a safer system.

I'd love to hear your thoughts, insights or experiences with Linux. Feel free to share and join the conversation [ Connect with me on LinkedIn www.linkedin.com/in/techwithsana ]💜

#30dayslinuxchallenge #redhat #networking #cloudcomputing #cloudengineer #cloudarchitect #cloud #RHCSA #RHCE #RHEL #WomeninTech #Technology

Best Open Source Tools to Use on Your Linux Journey

Sana Muhammad Sadiq — Thu, 08 May 2025 19:02:16 +0000

Introduction

As I continue my RHCSA journey with the 30-day Linux challenge, today’s focus is on the powerful open-source tools that make the Linux experience smoother, smarter and way more productive.

Whether you're writing code, managing systems, working with data or just navigating Linux as a learner the right tools matter. And in the world of Linux, open-source tools aren’t just alternatives, they’re often the industry standard.

Index

Top Open Source Tools Every Linux User Should Know
Real World Use Case
Recommendation
Quick Summary

🛠️ Top Open Source Tools Every Linux User Should Know

Let’s explore the most commonly used and recommended ones, with practical uses:

🔍 1. htop

What it does: A user-friendly process viewer (like top, but better).
Why it matters: Gives real-time insights into system resources.
Try it:

  sudo apt install htop
  htop

📝 2. vim / nano

What they do: Terminal-based text editors.
Tip: Use nano for simplicity, vim for power once you’re confident.

🌐 3. curl & wget

Use Case: Download files, APIs, webpages from the command line.

  curl https://example.com
  wget https://example.com/file.zip

🧱 4. tmux

What it is: Terminal multiplexer—run multiple sessions in one terminal.
Scenario: Keeping a process running even when SSH is lost.

📦 5. Git

Use Case: Version control (and collaboration via GitHub/GitLab).

  git clone https://github.com/user/repo.git

💡 6. ncdu

What it is: Visual disk usage analyzer.
Why: Much clearer than du -sh * when exploring space-hogs.

🌍 7. nmap

Purpose: Network scanning and security auditing.
Used in: System/network administration and cybersecurity.

🧪 8. bash-it / oh-my-zsh

Why: Supercharge your terminal with themes, aliases and autocompletions.

📁 9. rsync

Why it matters: Efficient file syncing, backup, and migration.

🧰 10. GParted

GUI-based partition editor. Great for resizing, formatting or repairing partitions without command-line stress.

🔁 Real World Use Case

Let’s say you’re a junior sysadmin troubleshooting disk issues:

Use ncdu to find bloated directories,
rsync to back them up to another server,
tmux to run these long tasks in multiple sessions without disconnecting.

That’s the real Linux power—open source helping you work smarter, not harder.

🧠 Recommendation

Don’t try to master everything at once. Start with what solves your immediate need. Then keep adding as your comfort grows.

✅ Quick Summary

Tool	Best For
htop	System monitoring
vim/nano	File editing
curl/wget	Downloading data
tmux	Terminal multitasking
git	Version control
ncdu	Disk space exploration
nmap	Network diagnostics/security
bash-it	Enhanced CLI experience
rsync	File sync and backup
GParted	Partition management (GUI)

I'd love to hear your thoughts, insights or experiences with Linux. Feel free to share and join the conversation [ Connect with me on LinkedIn www.linkedin.com/in/techwithsana ]💜

#30dayslinuxchallenge #redhat #networking #cloudcomputing #cloudengineer #cloudarchitect #cloud #RHCSA #RHCE #RHEL #WomeninTech #Technology

File Searching Like a Pro: find, locate and which

Sana Muhammad Sadiq — Thu, 08 May 2025 19:01:11 +0000

Introduction

As I continue my RHCSA journey with the 30-day Linux challenge. Today’s focus is one of those everyday essentials that saves time, boosts efficiency and solves the age-old question: "Where did that file go?"

Let’s talk about file searching in Linux using the powerful trio: find, locate and which.

Index

What Are These Commands
Real Life Use Cases
Pro Tips
Industrial Insight
Quick Summary

🔍 What Are These Commands?

1. `find`

A versatile and powerful command to search for files and directories in real time.

find /home/sana -name "report.txt"

This searches for a file named report.txt starting from /home/sana.

2. `locate`

Faster than find because it searches through a prebuilt database.

locate report.txt

Bonus tip: Update the database with sudo updatedb before using.

3. `which`

Used to locate the executable path of a command.

which python3

It tells you where python3 is installed on your system.

💡 Real Life Use Cases

✅ Sysadmin Troubleshooting – Find misplaced logs or config files in seconds.
✅ Development Setup – Locate compilers, interpreters or toolchains installed.
✅ Audits & Backups – Combine find with mtime to identify old files for cleanup or backup.

🚀 Pro Tips

Search files by modification time:

  find . -mtime -2

(Finds files modified in the last 2 days)

Combine find with exec:

  find . -type f -name "*.log" -exec rm {} \;

(Deletes all .log files from the current directory down)

Want blazing fast results? Use locate but make sure to run updatedb first.

🛠️ Industrial Insight

In production environments, time matters.
Searching for the right config file or script quickly can reduce downtime.
Advanced users often combine these tools in automation scripts for health checks or audits.

✅ Quick Summary

Command	Best For
`find`	Deep, real-time file searches with powerful filters
`locate`	Super-fast searches with a prebuilt index
`which`	Finding executables in your system path

Mastering these tools means you’ll never lose track of a file again.

I'd love to hear your thoughts, insights or experiences with Linux. Feel free to share and join the conversation [ Connect with me on LinkedIn www.linkedin.com/in/techwithsana ]💜

#30dayslinuxchallenge #redhat #networking #cloudcomputing #cloudengineer #cloudarchitect #cloud #RHCSA #RHCE #RHEL #WomeninTech #Technology

Redirecting Output in Linux: >, >>, 2> and |

Sana Muhammad Sadiq — Thu, 08 May 2025 19:00:38 +0000

Introduction

As I continue my 30-day Linux challenge in preparation for the RHCSA exam and today’s command combo is the secret sauce that makes shell scripting truly powerful. These are the tools of the trade:

> — Overwrite output to a file
>> — Append output to a file
2> — Redirect error messages
| — Pipe output from one command into another

Index

Why Output Redirection Even Matters
The Essentials Explained with Examples
Real Time Use Cases
Pro Tips
Industry Insight
Quick Summary

✨ Why Output Redirection Even Matters

Linux is built on the philosophy of small programs doing one thing well and letting you chain them together. That’s where output redirection steps in.

Whether you're saving logs, chaining commands or managing errors like a pro, output redirection is the magic behind automation and terminal mastery.

🔧 The Essentials Explained with Examples

1. `>` – Redirect STDOUT (and overwrite)

echo "Hello Linux!" > greetings.txt

📌 Creates greetings.txt (or replaces it) with the message.

2. `>>` – Redirect STDOUT (and append)

echo "Another line" >> greetings.txt

📌 Adds content without wiping the file.

3. `2>` – Redirect STDERR

ls no_such_file 2> error.log

📌 Saves the error message to error.log instead of printing on the screen.

4. `|` – Pipe output to another command

cat /etc/passwd | grep root

📌 Sends the output of cat to grep — only shows lines with “root”.

⌛ Real Time Use Cases

🔹 System Logging:
Redirect logs while running cron jobs or scripts:

./backup.sh >> /var/log/backup.log 2>&1

— Appends both STDOUT and STDERR into a single log file.

🔹 Error Isolation:
Troubleshoot issues cleanly by separating errors from standard output.

🔹 Command Chaining in Automation:
Use | in pipelines to manipulate data without temporary files.

💡 Pro Tips

✅ Combine STDOUT and STDERR:

command > all_output.txt 2>&1

✅ Use /dev/null to silence output:

command > /dev/null 2>&1

✅ Pipes can be combined endlessly:

cat file.txt | grep "pattern" | sort | uniq

✅ Create logs with timestamps:

echo "$(date): Something happened" >> events.log

🏭 Industry Insight

In production systems, output redirection is non-negotiable. Whether it is:

Logging errors in backend scripts
Piping data between tools in CI/CD pipelines
Redirecting output for backup and restore automation

It’s the difference between amateur scripts and bulletproof sysadmin workflows.

✅ Quick Summary

Symbol	Purpose
`>`	Redirect STDOUT (overwrite)
`>>`	Redirect STDOUT (append)
`2>`	Redirect STDERR
`	`

Understanding how Linux handles input, output and error streams helps you take control of everything that happens under the hood. This is not just a technical skill, it is a core competency.

Master redirection and you are not just using Linux, you are orchestrating it.

I'd love to hear your thoughts, insights or experiences with Linux. Feel free to share and join the conversation [ Connect with me on LinkedIn www.linkedin.com/in/techwithsana ]💜

#30dayslinuxchallenge #redhat #networking #cloudcomputing #cloudengineer #cloudarchitect #cloud #RHCSA #RHCE #RHEL #WomeninTech #Technology

File Compression & Archiving with tar, gzip and bzip2

Sana Muhammad Sadiq — Thu, 08 May 2025 19:00:08 +0000

Introduction

As I continue my RHCSA journey with the 30-day Linux challenge. Today, we’re diving into tar, gzip and bzip2; your essential Linux toolkit for file compression and archiving.

Index

What is Archiving vs Compression
Why This Matters
Getting Started with tar
Adding Compression using gzip
A Bit Slower but Better Compression using bzip2
Pro Tips
Real World Use Cases
Industrial Insight
Quick Summary

📦 What is Archiving vs Compression?

Archiving = Combining multiple files/directories into a single file. (Think: .tar)
Compression = Reducing the file size using algorithms. (Think: .gz, .bz2)

✅ tar = Archive
✅ gzip, bzip2 = Compress

🚀 Why This Matters

If you’ve ever transferred, backed up or stored files in Linux, you’ve already encountered the need for compression or archiving.

Knowing how to reduce file size efficiently while preserving file structures is a must for:

DevOps Engineers 📁
System Admins 🛠️
Cloud Professionals ☁️
And even curious explorers like me! 🧭

🔧 Getting Started with tar

🎯 Create a `.tar` Archive:

tar -cvf archive.tar myfolder/

-c = create
-v = verbose
-f = filename

🎉 Now you have a neat archive named archive.tar.

🎯 Extract a `.tar` Archive:

tar -xvf archive.tar

💨 Adding Compression using gzip

🗜 Compress your archive:

tar -czvf archive.tar.gz myfolder/

-z = use gzip

📂 Extract it:

tar -xzvf archive.tar.gz

✅ gzip is fast and widely supported.

🐢 A Bit Slower but Better Compression using bzip2

tar -cjvf archive.tar.bz2 myfolder/

-j = use bzip2

To extract:

tar -xjvf archive.tar.bz2

✅ bzip2 compresses better than gzip, but it's a bit slower.

💡 Pro Tips

✅ Use gzip for speed, bzip2 for better compression.
✅ Always test your archives before deleting originals.
✅ Combine tar and compression in one line to save steps.
✅ tar maintains permissions and structure — super handy!

🏭 Real World Use Cases

🔁 Backup Automation: Run daily tar+gzip jobs for /etc, logs, databases.
🚀 Deployment Packaging: Package entire app directories for deployment.
📦 File Transfer: Compress logs before sending over networks.
📂 Archival: Monthly archives of reports, configs, etc.

💼 Industrial Insight

Large-scale cloud systems (think AWS EC2, GCP Compute) often use scripts that:

Archive logs regularly
Compress them with gzip/bzip2
Ship them off to S3/Cloud Storage buckets

Having full control over file size and structure is key in both storage cost and performance.

📝 Quick Summary

Tool	Purpose	Speed	Compression
`tar`	Archiving only	Fast	None
`gzip`	Compress faster	Very fast	Good
`bzip2`	Compress better	Slower	Better

Today, I didn’t just “learn Linux commands”, I mastered the art of tidy packaging and efficient storage. It’s empowering to know I can now prepare professional backups and deploy-ready archives like a pro!💪

I'd love to hear your thoughts, insights or experiences with Linux. Feel free to share and join the conversation [ Connect with me on LinkedIn www.linkedin.com/in/techwithsana ]💜

#30dayslinuxchallenge #redhat #networking #cloudcomputing #cloudengineer #cloudarchitect #cloud #RHCSA #RHCE #RHEL #WomeninTech #Technology

Disk Space Awareness: df, du and What is Filling Up Your System

Sana Muhammad Sadiq — Thu, 08 May 2025 18:59:28 +0000

Introduction

I’m continuing my 30-day Linux challenge as part of my preparation for the RHCSA exam, and today’s topic might just be a lifesaver for system admins and everyday users alike: understanding disk space usage with df, du and how to find what’s clogging up your system.

Index

Why Disk Space Awareness Matters
What is df
What is du
Real Time Scenario
Industrial Insight
Recommendations
Quick Summary

🧱 Why Disk Space Awareness Matters

Running out of disk space can silently break a system whether it's preventing new files from being written, blocking services or even crashing processes. Being proactive is key.

That’s where df and du come in, they give you a clear picture of what's full, why, and how to fix it.

🔍 What is df?

df (Disk Free) reports available and used disk space on file systems.

🔧 Syntax:

df -h

✅ Example:

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        40G   20G   18G  53% /

-h: Human-readable format (MBs, GBs)
Quickly helps you know which partition is getting full

✅ Pro Tip: Use df -Th to also show filesystem types like ext4, tmpfs, etc.

📦 What is du?

du (Disk Usage) shows how much space a directory or file consumes.

🔧 Syntax:

du -sh /path/to/folder

✅ Example:

$ du -sh /var/log
1.2G    /var/log

-s: Summary only (don’t dive into subfolders)
-h: Human-readable

🛠 Tip: Run du -sh * inside a directory to compare which folders are space hogs.

🧰 Real Time Scenario

You log into a server and see alerts about low disk space. You use:

df -h

to check overall usage — /var is 90% full.

Then:

du -sh /var/*

to locate the culprit — it’s /var/log.

Then:

sudo du -ah /var/log | sort -rh | head -n 10

to find which specific log files are bloating. You clear old logs or rotate them. Problem solved.

🧠 Industrial Insight

In cloud deployments and containerized environments (like Docker), disk bloat is common. Backups, logs, caches — they add up silently. Keeping df and du in your toolbox can save hours of debugging.

🛡️ Recommendations

🔁 Set up cron jobs to monitor disk usage weekly
📉 Automate cleanup with logrotate
🚀 Combine find, du and xargs to identify and clean files older than X days
🧪 Always use -h in scripts that will be reviewed by humans

✨ Quick Summary

Command	Purpose	Best Option
`df`	Check disk usage	`df -h` or `df -Th`
`du`	Folder/file size usage	`du -sh`

Today was all about staying in control, disk space issues don’t wait. Now I know exactly what’s filling up my system and more importantly, how to clean it up before it becomes a problem.

I'd love to hear your thoughts, insights or experiences with Linux. Feel free to share and join the conversation [ Connect with me on LinkedIn www.linkedin.com/in/techwithsana ]💜

#30dayslinuxchallenge #redhat #networking #cloudcomputing #cloudengineer #cloudarchitect #cloud #RHCSA #RHCE #RHEL #WomeninTech #Technology

Killing Processes Gracefully with kill, pkill and killall

Sana Muhammad Sadiq — Thu, 08 May 2025 18:58:51 +0000

Introduction

As I continue my 30-day Linux challenge in preparation for the RHCSA exam. Today is about something powerful yet surprisingly elegant: gracefully managing running processes in Linux. Each command, each concept is another step toward mastery.

Index

What Happens When a Process Misbehaves
kill
pkill
killall
Real World Scenario
Pro Tips
Quick Summary

🚨 What Happens When a Process Misbehaves?

Sometimes, a process freezes, eats up memory, or refuses to quit. That’s where Linux gives us three mighty tools to step in with authority but grace too.

kill
pkill
killall

Let’s understand how each works.

🧰 kill 🗡️

The Precision Tool
kill is used to send signals to specific processes using their PID (Process ID).

kill -SIGTERM 1234

This sends a polite request (SIGTERM) asking the process to stop. Want to force it?

kill -9 1234   # SIGKILL – Force kill if it's stubborn

✅ Tip: Always try SIGTERM before using SIGKILL. Be kind to your processes!

🔍 pkill 🔠

The Pattern Matcher
Don’t want to look up PIDs? pkill lets you target processes by name or pattern:

pkill firefox

This will gracefully terminate all processes with the name "firefox".

Need to be more specific?

pkill -u sana chrome

This targets only Chrome processes run by user sana.

🧼 killall 🧹

The Sweeper Broom
Use killall to kill all instances of a process by name.

killall -15 node

This sends SIGTERM to all "node" processes.

killall -9 node

Force kill them if they don’t cooperate.

🎯 Real World Scenario

Imagine you’re deploying a Node.js server and something goes haywire. Rather than finding the exact PID:

killall node

One command. All processes. Clean slate.

✨ Pro Tips

✅ Prefer SIGTERM over SIGKILL — it gives apps time to clean up.
✅ Use pgrep first to check what you're about to kill.
✅ Log process shutdowns in production environments.

🧩 Quick Summary

Learning to gracefully stop processes isn’t just about control — it's about respecting the system’s state, and ensuring stability with precision. And now you're confidently in control when it comes to managing Linux processes onwards and upwards.

I'd love to hear your thoughts, insights or experiences with Linux. Feel free to share and join the conversation [ Connect with me on LinkedIn www.linkedin.com/in/techwithsana ]💜

#30dayslinuxchallenge #redhat #networking #cloudcomputing #cloudengineer #cloudarchitect #cloud #RHCSA #RHCE #RHEL #WomeninTech #Technology

Viewing Processes with ps, top and htop

Sana Muhammad Sadiq — Thu, 08 May 2025 18:57:31 +0000

Introduction

As I continue my 30-Day Linux Challenge for RHCSA preparation with the #CloudWhistler community led by Ali Sohail. Today I’m diving into a topic that helps you see what's really happening inside your Linux system process monitoring. In this article, I’m exploring three powerful commands: ps, top and htop.

Index

What Are Processes in Linux
ps Process Snapshot
top Real Time Process Viewer
htop Enhanced Top
Real Life Use Cases
Recommendations
Quick Summary

🧠 What Are Processes in Linux?

Every running task or application in Linux is a process. These include services, system tasks and commands you run in the terminal.

Being able to view and manage processes is essential to troubleshoot, monitor system load and understand how your machine is performing.

🔍 ps Process Snapshot

The ps command gives you a snapshot of currently running processes.

Basic usage:

ps

Show all processes with detailed output:

ps aux

Filter by user:

ps -u sana

Search by process name:

ps aux | grep firefox

📊 top Real Time Process Viewer

The top command shows a dynamic, real-time view of system processes.

Just run:

top

Use keyboard shortcuts inside top:

k to kill a process
q to quit
P to sort by CPU usage
M to sort by memory usage

📌 Pro Tip: It’s already available on most Linux systems by default!

🚀 htop Enhanced Top

If you want a more interactive and colorful view, try htop. It offers a scrollable interface and allows you to manage processes with your keyboard.

Install htop:

sudo dnf install htop     # RHEL/Fedora
sudo apt install htop     # Ubuntu/Debian

Run it:

htop

🟢 Use arrow keys to scroll, F9 to kill a process and F10 to quit.

💼 Real Life Use Cases

🛠️ Troubleshooting slow systems
🧠 Identifying memory or CPU-heavy applications
🧹 Killing unresponsive background services
🛡️ Monitoring server performance in real-time

🌱 Recommendations

Use ps when you want a quick look at what's running.
Use top or htop when you want live monitoring.
Don’t kill processes unless you know what they do.

✅ Quick Summary

Command	Use Case
`ps`	Quick snapshot of processes
`top`	Live process monitoring
`htop`	Interactive and user-friendly process viewer

If you’ve ever wondered how to peek under the hood of your Linux machine, these tools are your go-to companions. And yes once you get used to htop, there’s no going back. 😄

I'd love to hear your thoughts, insights or experiences with Linux. Feel free to share and join the conversation [ Connect with me on LinkedIn www.linkedin.com/in/techwithsana ]💜

#30dayslinuxchallenge #redhat #networking #cloudcomputing #cloudengineer #cloudarchitect #cloud #RHCSA #RHCE #RHEL #WomeninTech #Technology

Switching Users with su and sudo (And When to Use Them)

Sana Muhammad Sadiq — Tue, 06 May 2025 18:38:05 +0000

Introduction

As I continue my 30-day Linux challenge in preparation for the RHCSA exam, today's focus is on something every Linux user needs to get comfortable with early on switching users securely and smartly using su and sudo.

Both commands give access to elevated privileges but they’re meant for different situations. And knowing the right way to use them can protect your system, your work and your team.

Index

What is the Difference
Basic Usage with Examples
Key Differences
Real World Scenario
Industry Tip
Quick Summary

🔍 What is the Difference?

su stands for substitute user. By default, it switches to the root user unless you specify another username.
sudo stands for superuser do. It allows temporary elevation of privileges to run a single command as another user (commonly root).

💡 Basic Usage with Examples

Command	Purpose
`su`	Switch to root (requires root password)
`su - username`	Switch to another user
`sudo command`	Run one command as root (requires current user's password)
`sudo -u username command`	Run a command as a specific user

🧪 Examples:

su
su - sana
sudo dnf check-update
sudo -u postgres psql

🔐 Key Differences

`su`	`sudo`
Requires root password	Uses current user's password
Starts a new shell	Executes a single command
Can be risky if left open	Safer, logs activity
Doesn’t require configuration	Needs user in `sudoers` file

🌱 Real World Scenario

Imagine you're managing a server and you need to edit a protected config file. If you use su and forget to exit, your shell stays elevated — risky. Using sudo for just that one command reduces the risk of accidental changes.

sudo nano /etc/ssh/sshd_config

This way, you're doing exactly what’s needed — nothing more, nothing less.

💼 Industry Tip

✅ Many sysadmins disable root login and rely entirely on sudo for tighter security and clearer audit logs.
✅ Always use sudo unless you must become another user with a full shell.

💬 Pro Tip: You can limit sudo access by role or command in /etc/sudoers, offering precision control in enterprise environments.

If you’ve ever been unsure when to use su vs sudo, I hope this cleared it up!

✅ Quick Summary

Use su to fully switch users (like debugging as another user).
Use sudo for privilege elevation without changing users.
Prioritize security and visibility.

I'd love to hear your thoughts, insights or experiences with Linux. Feel free to share and join the conversation [ Connect with me on LinkedIn www.linkedin.com/in/techwithsana ]💜

#30dayslinuxchallenge #redhat #networking #cloudcomputing #cloudengineer #cloudarchitect #cloud #RHCSA #RHCE #RHEL #WomeninTech #Technology

Navigate Linux Like a Pro: Understanding Absolute vs Relative Paths

Sana Muhammad Sadiq — Sat, 03 May 2025 17:57:01 +0000

Introduction

As I continue my RHCSA journey with the 30-day Linux challenge, today’s focus is all about mastering paths something that might seem small but it plays a huge role in working effectively within a Linux environment.

Understanding the difference between absolute and relative paths is essential for navigating the file system with confidence, writing scripts and managing tasks precisely. So let’s simplify this with examples, tips and real-world use.

Index

What Are Paths in Linux
Practice
Real Time Scenario
Recommendations
Quick Summary

🧭 What Are Paths in Linux?

A path is the address of a file or directory in the Linux filesystem. It tells the shell where a file or folder is located.

There are two types of paths:

🔹 Absolute Path

An absolute path starts from the root (/) and shows the full directory route to the file or folder.

📦 Example:

/home/sana/documents/report.txt

This points to the exact location no matter where you are in the system.

🔹 Relative Path

A relative path starts from your current directory. It doesn’t begin with /.

📦 Example:

documents/report.txt

This works if you are already in /home/sana.

📝 Use . (current directory) and .. (parent directory) to move within paths:

cd ../downloads

📂 Practice

🔍 Check where you are:

pwd

📁 Move using absolute path:

cd /home/sana/projects

🚶 Move using relative path:

cd ../projects

🛠️ Real Time Scenario

You’re writing a shell script to copy files. If you use a relative path and the script runs from a different directory it fails. Using an absolute path ensures reliability.

✅ Pro Tip: In automation (like cron jobs), always prefer absolute paths for consistency.

🧠 Recommendations

Practice moving around using both types of paths.
Try writing a script using absolute paths, then modify it with relative ones.
Combine this knowledge with cd, pwd, ls and find.

🚀 Quick Summary

Even the smallest habits like using the correct path can save you hours of confusion and debugging.

I'd love to hear your thoughts, insights or experiences with Linux. Feel free to share and join the conversation [ Connect with me on LinkedIn www.linkedin.com/in/techwithsana ]💜

#30dayslinuxchallenge #redhat #networking #cloudcomputing #cloudengineer #cloudarchitect #cloud #RHCSA #RHCE #RHEL #WomeninTech #Technology

Forem: Sana Muhammad Sadiq

Linux Myths vs Reality: What Beginners Should Know

Introduction

Index

👨‍💻 Myth 1 Linux is Only for Programmers and Hackers

💡 Reality: Linux is for everyone — from writers to IT administrators.

💻 Myth 2 Linux Has No Good Applications

💡 Reality: Linux has thousands of powerful apps; often free and open-source.

📟 Myth 3 You Must Know Terminal Commands to Use Linux

💡 Reality: You can get by without the terminal — but learning a few commands boosts confidence.

🔧 Myth 4 Linux is Hard to Install and Configure

💡 Reality: Most distros today have foolproof installers.

🌐 Myth 5 Linux is Not Suitable for Work or Enterprise

💡 Reality: Linux powers most of the internet and Fortune 500 companies.

🎮 Myth 6 You Cannot Play Games on Linux

💡 Reality: Gaming on Linux is exploding.

🛡️ Recommendations

🧠 Quick Summary

👩🏻‍💻 Closing Thoughts Why This Matters

Linux for Non-Techies: A Simple Guide to Getting Comfortable

Introduction

Index

🌍 Why Non Techies Should Care About Linux

Real-World Case Study

🛠️ Linux Basics Made Easy With Examples

💡 Helpful Tips to Get Comfortable

1. Don’t install Linux on your main machine (yet)

2. Stick to Graphical Interfaces first

3. Google every error unapologetically

🏢 Industrial Insights and Real Time Scenarios

⭐ Recommendations for Non Techies

📝 Quick Summary

Configuring and Securing SSH Access in Linux

🔍 What is SSH?

🛠️ Basic SSH Command

📦 Installing SSH

🔐 Start & Enable SSH Service

🔐 Securing SSH Access (Best Practices)

📁 Real-Time Use Cases

💡 Pro Tips

🧠 Quick Summary

Best Open Source Tools to Use on Your Linux Journey

Introduction

Index

🛠️ Top Open Source Tools Every Linux User Should Know

🔍 1. htop

📝 2. vim / nano

🌐 3. curl & wget

🧱 4. tmux

📦 5. Git

💡 6. ncdu

🌍 7. nmap

🧪 8. bash-it / oh-my-zsh

📁 9. rsync

🧰 10. GParted

🔁 Real World Use Case

🧠 Recommendation

✅ Quick Summary

File Searching Like a Pro: find, locate and which

Introduction

Index

🔍 What Are These Commands?

1. find

2. locate

3. which

💡 Real Life Use Cases

🚀 Pro Tips

🛠️ Industrial Insight

✅ Quick Summary

Redirecting Output in Linux: >, >>, 2> and |

Introduction

Index

✨ Why Output Redirection Even Matters

🔧 The Essentials Explained with Examples

1. > – Redirect STDOUT (and overwrite)

2. >> – Redirect STDOUT (and append)

3. 2> – Redirect STDERR

4. | – Pipe output to another command

⌛ Real Time Use Cases

💡 Pro Tips

1. `find`

2. `locate`

3. `which`

1. `>` – Redirect STDOUT (and overwrite)

2. `>>` – Redirect STDOUT (and append)

3. `2>` – Redirect STDERR

4. `|` – Pipe output to another command

🎯 Create a `.tar` Archive:

🎯 Extract a `.tar` Archive: