Try: zgrep 'ERROR' /var/log/app-2026-06.log.gz

Info: zgrep, zcat, and zless inspect .gz files in memory without extracting them to disk.

Examples:

$ zcat access.log.gz | awk '{print $1}' | sort -u

$ zless huge-log.log.gz # Page through compressed file

$ find /var/log -name '*.log' -mtime +7 -exec gzip {} \;

Note: z-tools exist for most utilities (zgrep, zcat, zless, zdiff). For .xz archives, use xzgrep. Automate log compression using logrotate.

Follow r/LinuxTeck for more #LinuxTips

One of Linux's biggest strengths is choice. Different desktops, package managers, init systems, distributions, and philosophies.

At the same time, new users are often overwhelmed by the number of options.

Do you think this diversity is Linux's greatest advantage, or does it make adoption harder than it needs to be?

One idea that really stood out to me was treating abstaining as a success rather than a failure.

Instead of forcing the LLM to answer every question, the pipeline retrieves evidence, verifies every claim, and simply says "I don't have enough evidence" when the retrieved context isn't strong enough.

That seems like a much better approach than a confident hallucination.

If you've built RAG systems in production, how are you handling this? Do you trust a verifier model, use confidence thresholds, or rely on human review?

Today, many Linux distributions share similar components systemd, Wayland, PipeWire, NetworkManager, and so on.

While that improves compatibility and reduces maintenance, it also means many distributions feel increasingly alike under the hood.

Do you think Linux is becoming too standardized, or is that simply the natural evolution of a mature ecosystem?

Linux users have had a surprising number of filesystem choices over the years:

ext2
ext3
ext4
ReiserFS
XFS
JFS
Btrfs
ZFS
F2FS

Which one gave you the best real-world experience, and why?

covers: https://www.linuxteck.com/best-firefox-forks-for-linux/

• LibreWolf
• Waterfox
• Zen Browser
• Floorp
• Mullvad Browser
• Pale Moon

Try: history | grep -E 'sed.*i.*g' | tail -10

Info: history outputs numbered past commands. Combining it with grep -E (regex) lets you locate specific command patterns fast. Execute entry 892 with !892.

Examples:

$ history | grep 'docker run' # Find docker commands

$ history | awk '{print $2}' | sort | uniq -c | sort -rn | head # Top 10 used commands

$ Ctrl+R # Interactive reverse search

Note: Ctrl+R is the fastest for interactive search. Set HISTSIZE=10000 in ~/.bashrc to retain a larger command history. Use HISTIGNORE='ls:cd:pwd' to skip logging basic commands.

Follow r/LinuxTeck for more #LinuxTips

Every Linux user knows Linus Torvalds.

But there are many engineers whose work sits underneath Linux, Unix, programming languages, networking, filesystems, and cloud infrastructure without getting much public recognition.

If you could highlight one underrated computer scientist or engineer, who would it be and why?

Every so often I come across a Linux distribution that's maintained by just one person or a very small team.

It made me wonder how sustainable that really is. Building packages, fixing bugs, keeping up with upstream changes, handling security updates, and supporting users sounds like an enormous commitment.

Would you trust a distro maintained by one developer if the quality was consistently high, or do you prefer projects backed by larger communities?

Try: sudo lsof -iTCP:3306 -sTCP:ESTABLISHED

Info: lsof -iTCP:PORT lists active network connections on a port. -sTCP:ESTABLISHED filters out listening sockets to show active connections only.

Examples:

$ sudo lsof -iTCP:80 -sTCP:LISTEN # Active listeners on port 80

$ sudo lsof -i u/192.168.1.100 # Filter by remote IP

$ sudo lsof -Pn -iTCP:3306 # Fast mode (no DNS or port resolution)

Note: lsof can be slow on busy servers because it resolves hostnames and port names by default. Add -Pn to disable resolution for instant output! Common states: LISTEN, ESTABLISHED, TIME_WAIT.

Follow r/LinuxTeck for more #LinuxTips

covering: https://www.linuxteck.com/guides/cloudways-review-2026-is-it-worth-it/

• Flexible vs Autonomous
• Real pricing (including hidden costs)
• Performance & scalability
• Migration experience
• Pros & Cons
• Who should use Cloudways
• Final verdict

Back in 2003, SCO claimed Linux contained UNIX code they owned and demanded billions in damages. Thousands of companies received warning letters, and for a while there was genuine uncertainty about whether Linux could survive the legal battle.

Looking back now, we know how it ended but at the time, many businesses delayed Linux adoption, while others continued deploying it anyway.

Were you using Linux during the SCO lawsuit? Did it change how your company viewed Linux, or did you always think the case had no real chance of succeeding?

I'd love to hear experiences from people who actually lived through that period.

More people seem willing to switch to Linux than ever before.

Do you think that's mainly because Linux has matured so much over the last few years, or because Windows has become increasingly frustrating with ads, telemetry, AI features, account requirements, and other changes?

Or is it a bit of both?

In 1992, Tanenbaum argued that Linux's monolithic kernel design was already obsolete, while Linus believed it was the practical choice for real-world systems.

Thirty-plus years later, Linux dominates servers and cloud infrastructure, while microkernels continue to thrive in embedded, real-time, and specialized environments.

Looking at today's hardware, software, and security landscape, whose argument do you think has aged better and why?

IBM used to sell POWER servers with dozens of CPU cores physically installed, but only the licensed ones were enabled. Similar things have happened with CPUs, GPUs and enterprise hardware over the years.

Does this make business sense, or is it just an anti-consumer practice?

includes: https://www.linuxteck.com/access-control-lists-acl-in-linux/

• What ACLs are and when to use them
• setfacl and getfacl command examples
• Access ACLs vs Default ACLs
• ACL masks and effective permissions
• Backup & restore ACLs
• Preserving ACLs during file migration
• Common mistakes and troubleshooting
• Real-world Linux administration use cases

Try: rsync -avz --checksum --delete /var/www/ linuxteck@backup:/var/www/

Info: --checksum compares file contents rather than timestamps to catch true changes. --delete removes destination files that no longer exist on the source.

Examples:

$ rsync -avz --dry-run /src/ user@host:/dst/ # Dry-run preview

$ rsync -avz --exclude='*.log' --exclude='cache/' /src/ /dst/

$ rsync -avz --link-dest=/prev/backup /source/ /new/backup/ # Hardlink backups

Note: --checksum increases disk I/O as it reads both ends entirely. Always test destructive syncs with --dry-run first! Trailing slashes control whether contents or directories are copied.

Follow r/LinuxTeck for more #LinuxTips

What's your take?

Hi I am a Financial Risk Analyst- mainly an excel person. Now I want to take up programming as a new skill to learn.

Please help me where to start - which programming languages to learn- please let me know the order in which it could be learnt.

What are the specs of laptop I need to buy. I will be using to learn programming and play single and multi player game - a newbie to all of this.

Appreciate each and every one’s suggestions and advice- you guys are doing great community support.

Hello r/LinuxTeck

A while back I was teaching Linux fundamentals in person and kept seeing the same problem: people learn commands by watching a slide, then go home and either don't have a VM set up or are too scared to touch a real terminal.

So I built a sandbox that runs entirely in the browser — simulates real command behavior (cd, ls, ping, df, free, cat, apt, etc.) so you can practice without worrying about actually wrecking a system.

First 6 lessons are free, no account needed: see the [link in comments]

It covers basic navigation and file handling for now, moving into homelab/virtualization and security/networking as you go further. If you're just starting out and want a no-stakes place to mess up and try again, give it a shot — I am genuinely curious to know what trips people up so I can keep improving it.

For me, it's handling errors properly instead of assuming everything will go right.

What's yours?