Sadly the author of ping, Mike Muss, died in a car accident in 2000. [1]<p>[1]<a href="https://en.wikipedia.org/wiki/Mike_Muuss" rel="nofollow">https://en.wikipedia.org/wiki/Mike_Muuss</a>
Am I the only one that finds the MS Windows ping more useful for quick troubleshooting that the Linux/Unix variants? A few weeks ago I was dealing poor performance on my cable modem. When I pinged a valid IP, I was seeing the successful packets only. It didn't show time-out packets until the summary displayed on exit. This makes it useless for quick real-time monitoring. MS ping on the other hand will show time-outs along with the successful ones.<p>Why is Linux ping this way? Is this a fundamental design flaw?
I loved the bit about piping ping through sed through vocoder, playing it on the stereo at 11, and finding the network fault by seeing which wiggled connector caused silence.
For those who want to reproduce the ping example, get espeak and run:<p><pre><code> ping mit.edu | sed -u 's/.*/ping/' | espeak</code></pre>
I remember years ago the SunOS documentation used to have a ping joke: <a href="http://docs.oracle.com/cd/E19504-01/802-5753/6i9g71m4p/index.html" rel="nofollow">http://docs.oracle.com/cd/E19504-01/802-5753/6i9g71m4p/index...</a>
The following command will work on OS X and do the voice ping:<p><pre><code> ping google.com | sed -l -e 's/.*/ping/' | while read line; do say $line; done
</code></pre>
The `while read line ...` is required because the `say(1)` command will wait for an EOF when reading from a non-TTY... so it won't speak line by line.