For those too lazy to convert, that's 0xDEADBEEF and 0xB16B00B5, respectively. E... | Hacker News

HN2new | past | comments | ask | show | jobs | submit

		tspike on Oct 12, 2012 \| parent \| context \| favorite \| on: Why does pinging 192.168.072 return a response fro... For those too lazy to convert, that's 0xDEADBEEF and 0xB16B00B5, respectively. EDIT: Fun fact: Chrome's address bar will convert hex IPs for you on the fly. Try typing in http://0xDEADBEEF and look in the suggest box.

scoot on Oct 12, 2012 | [–]

Apparently 0xB16B00B5 made into some Microsoft HyperV code: http://www.bbc.co.uk/news/technology-18922629

Blame? http://www.spinics.net/lists/linux-driver-devel/msg15311.htm...

rplnt on Oct 13, 2012 | [–]

I tried the first one and since I have Google's Feeling Lucky as the default search engine I ended up here http://en.wikipedia.org/wiki/Hexspeak :)

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