Cowsay
en.wikipedia.org
en.wikipedia.org
> fortune | cowsay
in to my .bashrc. Every time I open a new terminal I get a cow telling me a fortune. I have done this for about 10 years now and it just feels right.
I don't think I've ever seen a cookie repeat in over 10 years, but it might just be my poor memory
[1] - The Oracle system pw was intentionally as offensive as it could be and people would forget it on purpose so it could be shouted across the room. I have good memories of that place. It was laid back and the people were fun. It was acquired and parted out by a bank.
It caused questions sometimes when I had to open a new terminal in a demo with the team.
-----------------------------------------
< pg says 'What problem does this solve?' >
-----------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||I.e. watch out for survivorship bias.
True, but just wait until we unleash the first CaaS (Cowsay as a Service) on the world in a few weeks...
We're going to make a gazillion dollars! I can feel it.
I'm not sure why anyone would want to, but you can disable this behavior by setting ANSIBLE_NOCOWS=1
Someone who doesn't appreciate a little fun, probably won't have cowsay installed on their controller
And yet... I've been toting around a role that's basically a list of packages to ensure are absent from the controller/managed hosts. Cowsay has been a long time resident
For such a little piece of fun, I 'have' to maintain a lot unnecessarily (if I want useful output)
I think this not being a "whoa neat" thing I encounter every now and then... but something I regularly endure, is part of it. We aren't all solo administrators
The Unix way is to do one thing and do it well:
fortune | cowsay | lolcat neofetch --ascii "$(fortune | cowsay -W 25)"
__________________________ ...@fedora
/ Q. Why is this so \ -----------------
| clumsy? A. The trick is | OS: Fedora Linux 39 (KDE Plasma) x86_64
| to use Perl's strengths | Host: Laptop 13 (AMD Ryzen 7040Series) A5
| rather than its | Kernel: 6.7.6-200.fc39.x86_64
| weaknesses. | Uptime: 3 hours, 48 mins
| | Packages: 3936 (rpm), 50 (flatpak)
| -- Larry Wall in | Shell: bash 5.2.26
| <8225@jpl-devvax.JPL.NAS | Resolution: 2256x1504
\ A.GOV> / DE: Plasma 5.27.10
-------------------------- WM: kwin
\ ^__^ Theme: [Plasma], Breeze [GTK2/3]
\ (oo)\_______ Icons: [Plasma], breeze [GTK2/3]
(__)\ )\/\ Terminal: konsole
||----w | CPU: AMD Ryzen 5 7640U w/ Radeon 760M Graphics (12) @ 4.971GHz
|| || GPU: AMD ATI c1:00.0 Phoenix1
Memory: 4702MiB / 27742MiBThat's one of my top uses for espeak. I have a script setup as /home/bin/work that looks like this:
#!/bin/bash
sleepTime="20m" # default is 20 minutes
if [ -z "$1" ]; then
echo "using sleepTime = $sleepTime"
else
echo "using sleepTime = $1"
sleepTime=$1
fi
reset ; date ; echo "You should be working ($sleepTime)" ; sleep $sleepTime ; reset ; echo "Time to take a break!" ; while true ;
do
espeak-ng "Time to take a break"; sleep 3s ;
done
This was inspired by another HN poster from a post a few years ago. I'd credit them, but I don't remember exactly who it was now.That said, I'm sure this script could be improved considerably, but for my purposes it suffices.
Definitely be careful about using fortune in a corporate environment or public space if you don't know what dat files you are using or you might just get an extremely unwelcome surprise.
I was practicing a presentation and used to use fortune all the time. I forget exactly what it output but I remember being absolutely mortified about what could have happened if that had popped up during an internal company tech talk.
Kudos to brew for keeping unsuspecting people safe
https://github.com/Homebrew/homebrew-core/commit/3fb3c4c3e55...
I still use it when I want to impress someone.
I've been using this a lot. Check this out:
$ fortune | figlet | cowsay -n -f tux
or
$ fortune | cowsay -n -f dragon
even this!
$ fortune | cowsay -n -f dragon | cowsay -n | cowsay -n -tux