LWN: Comments on "Quotes of the week" https://lwn.net/Articles/640266/ This is a special feed containing comments posted to the individual LWN article titled "Quotes of the week". en-us Mon, 15 Sep 2025 09:32:01 +0000 Mon, 15 Sep 2025 09:32:01 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Quotes of the week https://lwn.net/Articles/642056/ https://lwn.net/Articles/642056/ jch <div class="FormattedComment"> Yeah, the usual "userspace programmers are stupid, I won't even check the source" attitude from the kernel people.<br> <p> Folks, we understand that kernel development is a complex task, that's why we work around kernel lossage without complaints. Can we have just a little bit of respect?<br> </div> Mon, 27 Apr 2015 19:32:07 +0000 Quotes of the week https://lwn.net/Articles/641015/ https://lwn.net/Articles/641015/ niner <div class="FormattedComment"> Funny that I hit this exact error just a day before this lwn edition was published. It occured on a really crappy mobile connection with ping times of a full minute and large package loss (as you can imagine). I guess such a barely existent network connection can lead to surprising error cases.<br> </div> Mon, 20 Apr 2015 12:35:02 +0000 Quotes of the week https://lwn.net/Articles/640766/ https://lwn.net/Articles/640766/ Anssi <div class="FormattedComment"> According to the discussion on the Debian bugreport ( <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709052">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709052</a> ) it was a case of uninitialized variable which triggered the message.<br> </div> Fri, 17 Apr 2015 13:31:20 +0000 Quotes of the week https://lwn.net/Articles/640645/ https://lwn.net/Articles/640645/ pr1268 <p>Darn... I was hoping we might have stumbled upon another Easter Egg of the &quot;your printer is on fire&quot; variety. :-)</p> Thu, 16 Apr 2015 18:23:18 +0000 Quotes of the week https://lwn.net/Articles/640638/ https://lwn.net/Articles/640638/ klossner <div class="FormattedComment"> Ping doesn't actually check the kernel version. It prints the "not very fresh" message when it sees an IP_RECVERR breakage that was supposedly fixed in 2.4.9. There are scattered bug reports that say this still happens sporadically, so apparently the breakage wasn't completely healed.<br> <p> </div> Thu, 16 Apr 2015 17:55:34 +0000