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
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Three More Lessons
- Django Models and Migrations
- August 2015 Issue of Linux Journal: Programming
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- The Controversy Behind Canonical's Intellectual Property Policy
- Shashlik - a Tasty New Android Simulator
- Huge Package Overhaul for Debian and Ubuntu
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile