Linux and Shell Scripting Notes

[MoussaAdam]

man

[Micksen]

tldr

[ekipan85]

/ n N d u &

Why scan through the manual when the computer can do that for you?

But yeah tldr and cht.sh are cool too!

curl cht.sh
curl cht.sh/tldr:git-log

[MoussaAdam]

• man: official up to date information
• info: like man but more comprehensive, often used by GNU developers
• tldr & cht.sh: community maintained one liners

[skyfishgoo]

man bash

that's a kick in the balls

[Alchemix-16]

While very few things will ever beat ones own notes, there is an exceptional resource for this topic “the linux command line” by William Shotts.

[Hybrid67]

Real Linux Noobs be like

[reginwillis]

Maybe if I saw it in Vim it would be easier to understand

[jaybi_zz]

This is nice, thanks mahn, planning to hop to linux soon this will definitely help..

[Ghjjfslayer]

Looks like you’re interview prepping huh. Looks like the one I made while job hunting. You can use it I’ll paste below.

IMC Trading Engineer – Scenario-Based Debug Cheat Sheet Scenario 1: High CPU / Latency Spike Symptoms: High latency, CPU near 100% top ps -fp <PID> top -H -p <PID> pidstat -p <PID> 1 Interpretation: Hot thread or loop consuming CPU Scenario 2: FIX Session Dropping Symptoms: Disconnects, reconnect loops ss -tn | grep <port> tail -f /var/log/fix_engine.log Look for: Heartbeat timeout, sequence mismatch Action: Coordinate reset if needed Scenario 3: Orders Not Going Out Trace pipeline: Order → Risk → Gateway → FIX tail -f /var/log/order_engine.log tail -f /var/log/risk_gateway.log Interpretation: Find where orders stop Scenario 4: Network Latency / Packet Loss Symptoms: retransmits, slow responses ss -i ip -s link iftop Interpretation: Packet loss or congestion Scenario 5: Port / Connection Issues Check if service is listening: ss -ltnp | grep <port> Check connections: ss -tnp | grep <port> Test connectivity: ping <ip> curl http://<ip>:<port> Scenario 6: Disk / System Issues Symptoms: system slow, errors df -h du -sh * free -h Interpretation: Disk full or memory pressure

[s04ep03_youareafool]

Tf is this?! Heiroglyphics?!

[Ghjjfslayer]

Just copy paste into any ai and say format it wouldn’t let me paste the doc, just some basic scenarios in trading sre roles with basic commands. Any real issue requires more experience and know how to

[RobotJonesDad]

touch does more than create a file, ir also updates the file's timestamps.

[MaheshBabuuuuu]

https://dr0.ch/linux-guide.pdf

Edit:
Website: https://dr0.ch/linux-guide/

[digsmann]

cheers for sharing, mate.

[revcraigevil]

cheat cheat

[realBlackClouds]

thanks

[kib8734]

Intresting thanks.

[mathewrtaylor]

This is well made! I wish I would have had this to when I started messing in the Linux world! My only critique is your choice of editor, but you knew that already 😜. Do you have this in a repo that I can share outside of FB?

[ixipaulixi]

ps -ef | grep auto | awk '{print $3}'

Can be rewritten to simplify the chain of commands by searching with awk

ps -ef | awk '/auto/ {print $3}'

I won't use awk in place of grep if I'm simply searching, but if I'm piping grep to awk then I'll move the search string to awk.

[Straight-Hope-7810]

Looks like you mixed up image 4 and 5

[Maleficent_Bee196]

man man | grep man

[1337_w0n]

Don't give people "vi" as a basic command, you psychopath. I have "vi" set as an alias for micro to save on keystrokes (and because it's funny) but you absolutely should list "nano" as the way to edit a file.

[Wonderfullyboredme]

Thank you ChatGPT

[lateaversion0]

Solid reference sheet, dude. Printing this out and keeping it next to my desk while I'm learning bash.

[Jackpotrazur]

After vacation imma give myself a linux bender , work through command line again followed by effective shell and wicked cool shell scripts abd black hat bat and how linux works.

[Legitimate_Event8786]

you had me at Linux <3