TRÄW🤟

I think I'm serious then 😎

A lot of you asked for it. I’m now working on the paperback version of First Steps with Linux.

Linux folks

Now I understand why spanning tree gives me headaches

Today is the day. The Linux Field Guide is officially live. This is the project I've been talking about for a while. A long-form publication for "upper beginner" Linux users - the people who installed Linux, are comfortable in a terminal, and want to understand WHY things work the way they do, not just how to type the commands. The first article is now up. It opens Series 01: The C Layer. lfg.popovicu.com/series/the-c-l… Title: Why C is the Linux userspace interface. Most writing about C defends it the same way - "it's fast," "it's close to the metal," "there's too much legacy code to replace it." All of these treat C as a tool you happen to be stuck with. This article makes a different argument: C isn't a language you pick on Linux. It is literally the operating system interface, as POSIX defines it. Working code throughout. Real assembly for x86_64 and RISC-V, the actual ld command line gcc hides from you, and Apple's own documentation as receipts. About a 15 minute read. This is article 1 of many. Six series planned, each ~10 entries. The C Layer is just the start - shells, /proc, signals, files-as-everything, and bootstrapping a Linux system from scratch are all coming. A newsletter is in the works for readers who want article roundups plus extra content. For now, follow here for updates. Thank you to everyone who followed along through the campaign this past week. Today is the payoff.

Linux process management guide

@theslop 🤩

@thatstraw Nice password 😂

Quick Linux tip: Got log files compressed as .gz? You don’t need to extract them to read or search through the content. Use the 'z' tools directly: • zcat - view the file • zless - scroll through it • zgrep - search inside it • zegrep - search with extended regex • zfgrep - search for fixed strings • zcmp/zdiff - compare files These commands let you inspect compressed logs without unpacking them first, perfect for quick troubleshooting sessions.

This is your sign to start learning Linux. While others wait, learn Linux.

@twtayaan ❤️🎉

6K+ followers. Appreciate every one of you 🤝 If you're into: - DevOps - Cloud - SRE - Kubernetes - Linux I hope you found this account.

Quick Linux tip: If you want to clean empty directories, find command can make the job easy: $ find . -type d -empty -exec rmdir -v {} + The -type d option searches for directories, -empty selects empty ones and -exec rmdir {} executes the rmdir command to delete them. The rmdir command ensures that the directory is empty before deleting it. Alternatively, you can also use this command to complete the same task: $ find . -type d -empty -delete

@pepsi This

how do you drink Pepsi 🤔

Dumb or not, I still want it on my ThinkPad.

Does it hurt to post without cropping out watermarks?

This is ridiculous! Why do you crop out the watermark?? I don’t mind people sharing my visual guides. I know creating these takes time and creativity. But taking my work, slightly changing colors, cropping out my watermark, and adding yours to pass it off as your own work… that’s just wrong.

Currently on Fedora and loving it. If you had to convince me to switch… what distro would you suggest?

Linux was never meant to dominate the world. It was just a solution for one broke student. That solution now runs the global economy and most people still don't know its name.

Caption this with a Linux command😅

Quick Linux tip: You can use the find command's -exec option to call an external program to perform a specific action on the returned files that match specific criteria. For example, deleting files, listing file perms, and so on. $ find ~/ -type f -exec ls -lah {} \; This is very useful when performing the same action on multiple files in different locations. The above command is an example of listing the permissions and other metadata of every file the find command finds. A breakdown of the -exec option: • exec ls - this tells find to execute the ls command on every filename that matches the search string. • -lah - displays all files, including hidden files, their permissions, and other file metadata, such as sizes, in a human-readable format. • {} - The “{}” placeholder represents each filename and must be the last item in the parameter list. • ; - To indicate the end of the parameter list, a semicolon ";" is used. It must be escaped with a backslash "\" otherwise the shell will interpret it. You can also use the + instead of the ; to indicate the end of the parameter list. There should be a space between the + and the curly braces "{}". You can execute multiple commands using -exec in find. For example, this looks up word counts in text files and their disk usage in one invocation: $ find . -name "*.txt" -exec wc {} \; -exec du -sh {} \;

Linux is still the best operating system for developers . Right?