Re: Dr Horrible DNS geekery

2015-09-26 Thread Victor Odhner
I’m sure I’d used it before, maybe it was left behind by a library upgrade. I can’t install it now because of an obsolete repo. It’s time to wipe and replace my linux system. My Macbook has traceroute, bad.horse worked fine, and we just viewed Dr. Horrible again. _ On Sep 26, 2015,

Re: Dr Horrible DNS geekery

2015-09-26 Thread Phil Waclawski
Well, if it's a desktop distro it's not always installed (like kubuntu) just do sudo apt-get install traceroute or yum install traceroute (or whatever package system your distro uses :) Phil W On Sat, Sep 26, 2015 at 7:45 PM, Victor D Odhner wrote: > Wow, I really need to upgrade my March 201

Re: Dr Horrible DNS geekery

2015-09-26 Thread Victor D Odhner
Wow, I really need to upgrade my March 2013 version of Linux!!! Turns out I don't have traceroute . . . ___ On 09/26/2015 04:16 PM, Fabian Santiago wrote: I just tried it. It's very much alive and well. Quite humorous. Perhaps your isp is proxying / caching you in some capacity

Re: Dr Horrible DNS geekery

2015-09-26 Thread Fabian Santiago
I just tried it. It's very much alive and well. Quite humorous. Perhaps your isp is proxying / caching you in some capacity ?? -- Fabe > On Sep 26, 2015, at 2:45 PM, Michael Butash wrote: > > Looks like someone took it down, but dead.horse resolves to a service > provider (CariNet, Inc) hos

Re: Dr Horrible DNS geekery

2015-09-26 Thread Mike Bushroe
Mine was pretty boring until I added traceroute bad.horse --resolve-hostnames I am betting that everyone who was not impressed also did not have default set to DNS names. If you didn't see the fun try it again with the switch. Mike >traceroute bad.horse >no really... -- "Creativity is inte

Re: Dr Horrible DNS geekery

2015-09-26 Thread Michael Butash
For the replay out cox's network: # traceroute bad.horse traceroute to bad.horse (162.252.205.157), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 100.127.69.152 (100.127.69.152) 20.267 ms 22.860 ms 22.863 ms 4 70.169.75.248 (70.169.75.248) 22.861 ms 23.292 ms 23.294 ms 5 langbprj01-ae7.0.rd.la.c

Re: Dr Horrible DNS geekery

2015-09-26 Thread Michael Butash
Looks like someone took it down, but dead.horse resolves to a service provider (CariNet, Inc) hosted on cox's network now. They're just not allowing it. Interesting, yesterday it was egressing to hurricane electric, to atlantic metro's DC in NY. Something tells me someone didn't like the att

Re: Dr Horrible DNS geekery

2015-09-26 Thread Matt Graham
On Fri, Sep 25, 2015 at 1:47 PM, Stephen Partington wrote: traceroute bad.horse no really... On 2015-09-25 14:28, Anthony Radzykewycz wrote: Lol. That's awesome. This didn't work for me at all from my home box--something in Cox's network is eating all the packets after hop 11. And from my

rsync works again

2015-09-26 Thread Michael Havens
I finally got rsync working. It seems that it didn't like --progress and --compress-level=5. Or maybe something else... the quotes? worked: rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/USB\ DISK/ not work: rsync -aWq --progress --delete-before --compress-level=5 /home/bmike1/D