> For the complete documentation index, see [llms.txt](https://nks.gitbook.io/rna-seq/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nks.gitbook.io/rna-seq/2.-getting-started/optional-my-click-moment-about-why-linux.md).

# (optional) My click moment about "Why Linux"

Except for the very obvious reason that most, if not all, of the essential R package has to be run on a Linux/Unix system, "Why Linux" is a very interesting question to address.  The one word answer would be "power". 

That was when my control freakiness got the best of me.  Consider the code `sudo ufw allow from any to any port 3389 proto tcp`, I was not really fond with the idea to open a port to allow *any* ip to connect to my computer via the specific port.  And then it spread to "Get me your manager I want to check the log".  So long story short I got to know there is a `syslog` among others, and as expected it was long and impossible to read in the Terminal.  Anyway I spotted something like \[UFW BLOCKED] and I started to (super unnecessarily) panic.  It was time to extract all the lines with \[UFW BLOCKED] and examine the source ip/MAC closely.

Immediately came to my mind, was `grep`.  What about I ran `grep 'UFW BLOCKED' syslog > log.txt`?  And BOOM the next second I got a file named log.txt with all the lines from syslog which contained the phrase UFW BLOCKED.

How awesome was that?  Imagine if you were working in a graphic user interface.  In case you can wait for a 3.5MB files to slowly open in Microsoft word and/or notepad if it opens at all, then tiresomely search for UFW BLOCKED and copy and paste it onto another files.  In the case of knowing grep, I did this maybe half an hour work in seconds.

I literally fell in a mysterious love that no one could ever understand.  And FYI no one bothered to crash into my network.  It was all me.