4 ms·
Most likely it was doing something naughty in it's network stack.
by kgabis 10y ago
Most likely it was doing something naughty in it's network stack.
- teaearlgraycold 10y agoYeah but that could have been any number of things.
- deleted 10y ago[deleted]
- laumars 10y agoI had worked that much out for myself. What with it being explicitly stated in the quote that the network stack wasn't working correctly and had to be fixed. :P The bit I was interested in was what was Linux doing wrong and how was the fault detected? Did it take anything else down with it? Was the fix something straightforward (ie it was a silly oversight that caused the problem) or something complicated? It can be interesting to read stories about tech going wrong. Sometimes because the results can be amusing in retrospect (less so at the time of the problem) and sometimes because it's just nice to read that problems and mistakes can happen to other people too.