If you hold a Unix shell up to your ear you can hear the C.

If you hold up a UNIX shell to you ear, can you hear the C?

If you put a UNIX shell to your ear, you can hear the C.

If you put a Unix shell up to your ear, can you hear the C?

If you hold a UNIX shell to your ear, you can hear the C.

When I was in college, our email was on a Unix server. We would login via serial connection or telnet over the network, and get a korn shell. The server was poorly secured. Everyone's login device was world writable. So people would just see who was online, see the username of someone they wanted to mess with, take note of the pts(network) or tty(serial) device their connection used, and cat ASCII penises to it.

cat animated_dong.txt > /dev/pts/4

It was a simpler time.

A t-shirt I found online😂

I previously worked as a Linux/unix sysadmin. There was one app team owning like 4 servers accessible in a very speciffic way.
* logon to main jumpbox
* ssh to elevated-privileges jumpbox
* logon to regional jumpbox using custom-made ssh alternative [call it fkup]
* try to fkup to the app server to confirm that fkup daemon is dead
* logon to server's mgmt node [aix frame]
* ssh to server directly to find confirm sshd is dead too
* access server's console
* place root pswd request in passwords vault, chase 2 mangers via phone for approvals [to login to the vault, find my request and aprove it]
* use root pw to login to server's console, bounce sshd and fkupd
* logout from the console
* fkup into the server to get shell.

That's not the worst part... Aix'es are stable enough to run for years w/o needing any maintenance, do all this complexity could be bearable.

However, the app team used to log a change request asking to copy a new pdf file into that server every week and drop it to app directory, chown it to app user. Why can't they do that themselves you ask? Bcuz they 'only need this pdf to get there, that's all, and we're not wasting our time to raise access requests and chase for approvals just for a pdf...'

oh, and all these steps must be repeated each time a sysadmin tties to implement the change request as all the movements and decisions must be logged and justified.

Each server access takes roughly half an hour. 4 servers -> 2hrs.

So yeah.. Surely getting your accesses sorted out once is so much more time consuming and less efficient than logging a change request for sysadmins every week and wasting 2 frickin hours of my time to just copy a simple pdf for you.. Not to mention that threr's only a small team of sysadmins maintaining tens of thousands of servers and every minute we have we spend working. Lunch time takes 10-15 minutes or so.. Almost no time for coffee or restroom. And these guys are saying sparing a few hours to get their own accesses is 'a waste of their time'...

That was the time I discovered skrillex.

This sums it all up.

Unix lovers be like,
Where there is a shell.
There is a way.

Man, people have the weirdest fetishes for using the most unreadable acrobatic shell garbage you have ever seen.

Some StackOverflow answers are hilarious, like the question could be something like "how do I capture regex groups and put them in a variable array?".

The answer would be some multiline command using every goddamn character possible, no indentation, no spaces to make sense of the pieces.

Regex in unix is an unholy mess. You have sed (with its modes), awk, grep (and grep -P), egrep.
I'll take js regex anytime of the day.

And everytime you need to do one simple single goddamn thing, each time it's a different broken ass syntax.

The resulting command that you end up picking is something that you'll probably forget in the next hour.

I like a good challenge, but readability is important too.

Or maybe I have very rudimentary shell skills.

Dear God,
Not a single time in my life I was able to correctly spell "sudo" on the first shot: I always get "sudp" first. Am I praying the wrong prayers?

Don't you just love it when you come in late and the commit you made last night and were certain was going to work, doesn't work and everybody is pissed because of it? And all because your shell won't run since the line ending of your sh file was somehow Windows instead of UNIX.

Fucking love it ^_^

To all Linux-, Unix-, MacOS-Users here.
Stop whatever your doing,
Install Elvish-Shell,
Forget what what you wanted to do because you get distracted by this awesome piece of software,
Eventually continue what you were doing in a few hours.

How it started:

Need to replace in a lot of SQL files certain stuff...

find . -type f -iname '*.sql' -exec sed -i 's|new|old|g' {} \;

12 hours later that find executed a shell script containing roughly 120 lines of text pipelining.

The jolly of inconsistent workflows.

Different SQL format stylings... Makes fun when single line string replace needs to be extended to multiline RegEx handling. Or matching SQL comment configuration..

Different line endings. MacOS, Windows, Unix, Bukkake.

Different charsets / collations. Anyone wants latin1_swedish_ci... utf8... utf16... :/

Realizing some people even left sensitive data inside the SQL files (e.g. API Tokens..... Yayyyyyyy).

...

Ugh. It's never a one liner. It's never easy. -.-

I hate cleaning up messy shit.

Linux shell skills level:

apt-get moo

Tl;Dr Im the one of the few in my area that sees sftping as the prod service account shouldn't be a deployment process. And the ONLY ONE THAT CARES THAT THIS IS GONNA BREAK A BUNCH OF SHIT AT SOME POINT.

The non tl;dr:

For a whole year I've been trying to convince my area that sshing as the production service account is not the proper way to deploy and/or develop batch code. My area (my team and 3 sister teams) have no concept of using version control for our various Unix components (shell scripts and configuration files) that our CRITICAL for our teams ongoing success. Most develop in a "prodqa like" system and the remainder straight in production. Those that develop straight in prodqa have no "test" deployment so when they ssh files straight to actual production. Our area has no concept of continuous integration and automated build checking. There is no "test cases", no "systems testing" or "regression testing". No gate checks for changing production are enforced. There is a standing "approved" deployment process by the enterprise (my company is Whyyyyyyyyyy bigger than my area ) but no one uses it. In fact idk anyone in my area who knows HOW to deploy using the official deployment method. Yes, there is privileged access management on the service account. Yes the managers gets notified everytime someone accesses the privileged production account. The managers don't see fixing this as a priority. In fact I think I've only talk to ONE other person in my area who truly understands how terrible it is that we have full production change access on a daily basis. Ive brought this up so many times and so many times nothing has been done and I've tried to get it changed yet nothing has happened and I'm just SO FUCKING SICK that no one sees how big of a deal this. I mean, overall I live the area I work in, I love the people, yet this one glaring deficiency causes me so much fucking stress cause it's so fucking simple to fix.
We even have an newer enterprise deployment. Method leveraging a product called "urban code deploy" (ucd) to deploy a git repository. JUST FUCKING GIT WITH THE PROGRAM!!!!..... IT WAS RELEASED FUCKING 12 YEARS AGO......

Please..... Please..... I just want my otherwise normally awesome team to understand the importance and benefits of version control and approved/revertable deployments

Is it just me or Reverse Search (Ctrl+R) is so addictive?

From last few years I have been using shell too much that I will use Ctrl+R to just search for even `ls`.

BASH = "Bourne" Again SHell .if you know what I mean!

The unix shell syntax is weird looking.
Gonna learn it next. Using Arch without knowing how some scripts work isn't optimal.

I am lazy to pair my android device to another android device via blutooth for tethering(Pan Access Network) for internet access. Wifi sucks too much battery. Whenever pairing is done, device asks for prompt message stating "yes" or "no" for connection. I want that it automatically by default give permission to connect. Is there any possible solution (maybe through adb shell or something). I have tried every site related to this issue but most of them have unix system Bluetooth issues so no luck. Reply if you know a fix.

Passwordless Unix login leading to a console menu. You can then FTP in for free and remove ~/.login . Boom ! Shell access! And I already had a superuser access from another "dialog" asking to confirm a dangerous action with the superuser's password. Boom! Root access !!

I love linux but it doesn't run Windows applications natively, but Windows doesn't have the awesome UNIX shell so I'm kinda stuck

After missing Linux, OS X (bow macOS) and other Unix systems, I started installing WLS, anyone know if I can change shell to fish, install a package manager and point to repos?