Letters to the Editor
I always look forward to reading my issue of LJ each month. Great magazine; thanks.
The reason I am writing is to share a concern regarding Linux API stability. I enjoy system work too, but the fact is my company sells applications, not operating systems. If I am to produce shrink-wrapped applications, user and kernel APIs must remain stable. I just worked my way through our several drivers to get them from 2.0.* to 2.2.* series kernels, and now I see the driver API is changing again in 2.3.*. It is a terrible temptation to keep improving, but if it works, let's leave it for a while. And maintaining old APIs is not a long-term answer either—that's what makes UNIX systems so fat, all the baggage they carry around.
Thanks for listening.
—Elwood Downey ECDowney@ClearSkyInstitute.com
|Using tshark to Watch and Inspect Network Traffic||Aug 31, 2015|
|Where's That Pesky Hidden Word?||Aug 28, 2015|
|A Project to Guarantee Better Security for Open-Source Projects||Aug 27, 2015|
|Concerning Containers' Connections: on Docker Networking||Aug 26, 2015|
|My Network Go-Bag||Aug 24, 2015|
|Doing Astronomy with Python||Aug 19, 2015|
- Using tshark to Watch and Inspect Network Traffic
- Problems with Ubuntu's Software Center and How Canonical Plans to Fix Them
- Concerning Containers' Connections: on Docker Networking
- A Project to Guarantee Better Security for Open-Source Projects
- Where's That Pesky Hidden Word?
- Firefox Security Exploit Targets Linux Users and Web Developers
- My Network Go-Bag
- Doing Astronomy with Python
- Build a “Virtual SuperComputer” with Process Virtualization
- diff -u: What's New in Kernel Development