All of these are pretty good, but my favorite is life savers.

We’re a Linux shop at my work. We do have a windows PC due to corporate policies…but everything we do on our windows PCs we could do from Linux.

Outlook? Website. Excel? Website. Jira? Website. Teams? Website. Nearly everything we do front end wise is all web based. Which, I know electron sucks, but from a “Linux as a main desktop environment”…I’m pretty damn happy with everything being web based nowadays. It’s all OS agnostic.

There are a lot of great commands in here, so here are my favorites that I haven’t seen yet:

• crontab -e
• && and || operators
• “>” and >> chevrons and input/output redirection
• for loops, while/if/then/else
• Basic scripts
• Stdin vs stdout vs /dev/null

Need to push a file out to a couple dozen workstations and then install it?

for i in $(cat /tmp/wks.txt); do echo $i; rsync -azvP /tmp/file $i:/opt/dir/; ssh -qo Connect timeout=5 $i “touch /dev/pee/pee”; done

Or script it using if else statements where you pull info from remote machines to see if an update is needed and then push the update if it’s out of date. And if it’s in a script file then you don’t have search through days of old history commands to find that one function.

Or just throw that script into crontab and automate it entirely.

You can do “ss -aepni” and that will dump literally everything ss can get its hands on.

Also, ss can’t find everything, it does have some limitations. I believe ss can only see what the kernel can see(host connections), but tcpdump can see the actual network flow on the network layer side. So incoming, outgoing, hex(?) data in transit, etc.

I usually try to use ss first for everything since I don’t think it requires sudo access for the majority of its functionality, and if it can’t find something then I bring out sudo tcpdump.

And I believe shift+r will let you go forward in history if you’re spamming ctrl+r too fast and miss whatever you’re looking for