![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
237216938 logging off.
237216938 logging off.
Nah, that can’t be right, I’m pretty sure it was them sweet sweet scritches. I asked, former wolf agrees.
As proven by the fact that dogs exist. I bet wolves were constantly itchy as well, but receiving those excellent scritches over millennia, they turned into the gentle doggos that we know today. And now I can have one of these 30kg predators in my house, trusting me with their life and sleeping on me occasionally and not mauling me with their sharp teeth, just because of the power of scritches.
This. I’ve had nothing but great experiences with zram on resource constrained VMs in an enterprise grade cluster.
Ken Shirrif’s Blog is incredibly great!
Urectum.
Astronomers renamed Uranus in 2620 to end that stupid joke once and for all.
That’s some proper fur, I love it!
Upvote for doggo!
Metube might be right for you.
Clearly left.
I’m not sure. It just might be if you count all the things that you can do with Jinja2, but I really hope it’s not.
Neither does mine, but, I keep it to test a new tool from time to time.
Ansiblings for Ansible (yes, I know this isn’t a programming language)
Rest of the list:
DNS tools:
Good stuff for pentesters and security researchers:
### .bashrc
### CUSTOM FUNCTIONS
# https://www.linuxjournal.com/content/boost-productivity-bash-tips-and-tricks
ftext () {
grep -iIHrn --color=always "$1" . | less -R -r
}
duplicatefind (){
find -not -empty -type f -printf "%s\n" | sort -rn | uniq -d | \
xargs -I{} -n1 find -type f -size {}c -print0 | \
xargs -0 md5sum | sort | uniq -w32 --all-repeated=separate
}
generateqr (){
# printf "$@" | curl -F-=\<- qrenco.de
printf "$@" | qrencode -t UTF8 -o -
}
deleted by creator
bash
, because I never had the time to learn anything else.
shebang.bash
is just fine for me, though I’ve customized it using Starship and created some aliases to have colored/pretty output where possible.shellcheck
before running your scripts in production, err on the side of caution, set -o pipefail
. There are best practices guides for Bash, use those and you’ll probably be fine.set -x
inside your Bash script or bash -x scriptname
on the CLI for debugging. Remember that you can always fallback to interactive CLI to test/prepare commands before you put them into your script. Think before you type. Test. Optimize only what needs optimization. Use long options for readability. And remember: Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows your address.I switched to fish because it has tab completion Yeah, so does Bash, just install it.
Oh, I also “curate” a list of Linux tools that I like, that are more modern alternatives to “traditional” Linux tools or that provide information I would otherwise not easily get. I’ll post i
Debian-Packages available
no Deb pkg avail
___
Yeah, but how would they wear their pants?
I’m surprised nobody said wank yet.