Every Unix command eventually become an internet service .

Grep- > Google
rsync- > Dropbox
man- > stack overflow
cron- > ifttt

It's quite "sed" and "awk"ward. 😂

Ah, these classic LINUX commands:

$ unzip; strip; touch; finger; grep; mount; fsck; more; yes; fsck; fsck; umount; clean; sleep

A quote if Trump was a dev on linux

"grep them by the pussy"

Me: *kills process*
Linux: 3243 killed.
Me: "sudo netstat -ntlp | grep 3243"
Linux: 3243 running.
* hour later *
Me: *kills process with 3045974th method*
Linux: 3243 killed.
Me: "sudo netstat -ntlp | grep 3243"
Linux: 3243 running.
Me: "Are you absolutely FUCKING kidding me?! What is this fucking thing, the god damn grim reaper? I've done some SKETCHY fucking things at the terminal to kill this BASIC fucking server and it is still running!! WHAT THE FUCK ARE YOU?!"
Manager: *peeks in helpfully* "Did you try the 'kill' command?"

Why devs like Linux/Unix :
unzip, strip, touch, finger, grep, mount, fsck, more, yes, fsck, fsck, fsck, umount, sleep

You know you are cool when you grep the man page for grep 😎

So we found an interesting thing at work today...

Prod servers had 300GB+ in locked (deleted) files. Some containers marked them for deletion but we think the containers kept these deleted files around.

300 GB of ‘ghost’ space being used and `du` commands were not helping to find the issue.

This is probably a more common issue than I realize, as I’m on the newer side to Linux. But we got it figured out with:

`lsof / | grep deleted`

How a linux sysadmin has sex :
who | grep -i hot && grep -i female | date; cd ~; unzip; touch; strip; finger; mount; gasp; yes; uptime; umount; sleep;

Hi, I am an Linux/Unix noobie.

Is there any other command line tools like GREP?

I want to take a look at it and think whetehr it will be great for a small school project or not.

How do you define a seniority in a corporate is beyond me.
This guy is supposed to be Tier3, literally "advanced technical support". Taking care of network boxes, which are more or less linux servers. The most knowledgable person on the topic, when Tier1 screws something and it's not BAU/Tier2 can't fix it.
In the past hour he:
- attempted to 'cd' to a file and wondered why he got an error
- has no idea how to spell 'md5sum'
- syntax for 'cp' command had to be spelled out to him letter by letter
- has only vague idea how SSH key setup works (can do it only if sombody prepares him the commands)
- was confused how to 'grep' a string from a logfile

This is not something new and fancy he had no time to learn yet. These things are the same past 20-30 years. I used to feel sorry for US guys getting fired due to their work being outsourced to us but that is no longer the case. Our average IT college drop-out could handle maintenance better than some of these people.

Im in the process of developing a tool for small comunity of gamers.

That tool will help people in mod making.

Currently you have to use notepad++ in order to modify .json files that contain unit properties.

I downloaded grep for win to check for patterns in those .json files to understand how they work

I ran a simple search and...

Avast decided to frezze my pc for 20min to check 300 files because winGrep accesed them...
WHY THE FUCK DID YOU DECIDE TO SATURATE MY HDD IO YOU FUCKING PIECE OF SHIT? I HAVENT GOT ANY WIRUSES FOR 6 YEARS YOU ARE USELESS. I WILL UNINSTALL YOU BECAUSE YOU ARE JUST WASTING MY RESORUCES AND MY TIME.

I cant even reboot my laptop because i would lose my code!

Fuck AV's
Fuck slow hdd's
Fuck inefficient programs
Fuck people who thought that instaling a bunch of crap on win 10 is a good idea
Fuck people who will try to convince me to swich to linux
Fuck apple
Fuck M$
I love my C hashtag

I might swich to win10 ltsb

Spent last 2 days trying to get an upstream data file loaded. I've now concluded it's just corrupted during transfer beyond repair... But I got to practice lots of Linux commands trying to figure out what the issue was and fix it (xml parser was throwing some error about nulls originally)

vi, grep, head, tail, sed, tr, wc, nohup, gzip, gunzip, input output redirection

linux rant number 23094823094

Linux is a marvel of modern engineering. Well, at least in a sense that it somehow manages to work despite its design.

Basic commands like ls, grep, rm, cp (think busybox) do work predictably. Given that some of them are older than you and me combined (grep is 51 years old), it would've been weird if they didn't.

Yet, when comes the time to configure linux itself, there is no right way to do it — there are 5 or 6 wrong ones.
The wrong way number 1 to configure linux is to use predictable commands and their combinations. You know, cat + grep some config files, then awk to change them… If you do it, you will instantly break your system to the point that you'll have to back up your data, reinstall everything and put your data back.

All the other wrong ways are wrong because each of them will break your system in their own unique way. All of them kinda-sorta do what you want, at the expense of messing up some other things that have nothing to do with what you were trying to fix. The worst way to use them is combining one wrong way with some other one, like configuring xorg directly and then using ubuntu-specific userland config tools. This will instantly break your system too.

You'll have to google/chatgpt your way through historic quirks that are somehow still there in 2025. Remember: the worse the shell command looks, the more likely it is that it's the right way (or at least the least wrong way) to do things in linux.

Some minimal distros like alpine is a notable exception, in a way that they're more predictable, but they will become useless the moment you try to get some actual work done. I've used alpine as my desktop os for quite a while. I know what I'm talking about.

If you want so much as to install a browser, you'll have to use flatpak. But flatpak will only bail you out so many times. Your colleagues, and people that write tools that your colleagues use, are using macos, windows or ubuntu. You'll have to use whatever they're using, and if it uses glibc/is not in flatpak, well, tough cookies.

sudo apt install fuse breaks ubuntu instantly — it won't boot into graphical desktop anymore until you reinstall everything, including systemd, and do initramfs. Why does it do that in 2025? who knows.

After coming back to my desk I cannot unlock my screen. So again I have to go to my Mac or even Windows to google my shitty Linux problem. Nothing particular turns up. So I switch to another tty and rummage through the process list. Kill some java that took 11GB of RAM and Firefox that always keeps some zombies. Nothing.
Grep the processes: oh let's nuke "light-locker". Bingo.
The only downside of this brutal unlock: I cannot lock the screen again. So in any case another reboot? Wasn't this the standard repair method of that other OS that should not be named?

Fuck you Linux! I thought user password validation would be a piece of cake, like bash one liner. How wrong could I be!

Yeah, it's already ugly to grep hash and salt from /etc/shadow, but I could accept that. But then give me a friggin' tool to generate the hash. And of course the distro I chose has the wrong makepswd, OpenSSL is too old to have the new SHA-512 built in, as it should be a minimal installation I don't want to use perl or python...
And the stupid crypto function that would do me the job is even included in glibc. So it's only one line of C-code to give me all I want, but there is no package that would provide me this dull binary? Instead I will have to compile it myself and then again remove the compiler to keep image small?