Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I was thinking about how fun it would be to add this my Python CLI [0] I made for launching Fedora CoreOS locally with QEMU for testing ignition, but with a flag that is turned off by default. Using the burn effect in TTE when launching a VM with my CLI would be so cool.

This instantly reminded me about Ansible and how it annoyed me that ANSIBLE_NOCOWS had to be enabled to disable the default output of Ansible with cowsay [1].

[0]: https://github.com/quickvm/bupy

[1]: https://github.com/ansible/ansible/issues/10530



Hot damn, I have to respect the author for shutting down any attempt to make him give in to the pressure.

All these serious enterprise people worried about their cows, but then they do install ‘cowsay’ on their systems xD


The people complaining probably don't have the authority to remove it from the base image they're forced to use, unfortunately.


How serious can your enterprise be if they install cowsay on their base image?


How serious it is, and how seriously the people who make decisions take it, are if not strictly orthogonal then certainly not guaranteed to closely correlate.


it's not a matter of seriousness, if you install all the packages, cowsay gets picked up in the mix


On a further tangent, that reminds me of two of my favorite things to install on a Linux system, ponysay and ascii-pony/systempony. I set each of my systems to a different character to show on bash logins with systempony (WSL instances included)

https://github.com/erkin/ponysay

https://blog.yjl.im/2016/01/ascii-pony-systempony-screenshot...


A while back I install ponysay on one of my servers, and put fortune | ponysay in the .bashrc, so I get a quip from a random mlp pony whenever I log in. Brightens my day a little




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: