Networking change causes distribution headaches
Posted Oct 29, 2008 12:59 UTC (Wed) by
epa (subscriber, #39769)
In reply to:
Networking change causes distribution headaches by PaulWay
Parent article:
Networking change causes distribution headaches
the intention is to alert the user that they have non-compliant hardware on their network and they should upgrade.
Yes, that's exactly what the intention is. Clearly, what the users want most of all is not to get their work done, but to receive useful and informative messages about hardware purchases they need to make in order to remain fully standards-compliant. Imagine a new user's heartfelt shame on first installing Linux and finding out they had been running a router that didn't strictly follow the RFCs, soon turning to joy and gratitude that Linux had revealed their sins and given them an opportunity to buy a replacement, helping to financially support honest manufacturers who test their products with all the world's wide diversity of operating systems.
Compared to these noble goals, it would be baseness and narrow-mindedness indeed for anyone to complain that Linux "doesn't work" or does not let them access networks that seemingly worked with Microsoft Windows. Indeed, we should surely add more of these features to the kernel, righteously refusing to work with any hardware or program that doesn't correctly implement standards, to lead us further towards the goal of a world where all computers work harmoniously together. Let Linux lead the way!
(Excuse the excess of sarcasm, I'm really missing the Linux Hater's Blog since he stopped posting.)
(
Log in to post comments)