Diff & Named pipes in OSX?

previously I wrote about using named pipes to avoid temporary files when working from the CLI. The odd thing is that the following command seems to work on bash/linux but responds with an error message (curl: (23) Failed writing body) on bash/OSX

diff <(curl http://www.google.com) <(curl http://www.google.com?q=a)

I don’t really understand why this doesn’t work, but it seems that to the process the pipes differ from the default stdout where they shouldn’t. To bad, it would be useful!

update

While googling arround I found a page breaking down the problem. Greg Miller discovered that the actual problem is HFS+ (the filesystem) returning the same inode number for two different files; which since it isn’t inode base could be somehow correct.

Hopefully Apple will fix this in the near future, but I guess I’d better grab myself the sources and build my own version of diff.


0 Responses to “Diff & Named pipes in OSX?”

  1. No Comments

Leave a Reply





About

Welcome to the weblog of Peter Maas. Here you'll find various posts related to stuff I like (like my kids and espresso) and stuff I do (like developing software).

JavaOne 2008 Pictures


Hotel room javaone 2008 goodybag Cable Car line Joshua Bloch at JavaOne2008 Tim Bray introducing the (J)Ruby panel Charles Nutter & Guillaume Laforge golden_gate_warning_sign pub Stage being build in the nearby park Moscone Center - JavaOne sea_lion Java + You on a cab Rudie smashmouth Community One Keynote Okke en Rudie Stretched Limo Greenland Golden Gate nearby hotel
View more photos >

Categories



Meld u aan voor PayPal en begin direct met het accepteren van creditcardbetalingen.