Increasingly, the most critical networks, those run by telecom carriers, are turning to Linux, and MontaVista’s latest release of its “carrier grade” platform is intended to accelerate that trend.

Version 5.0 of MontaVista Linux, Carrier Grade Edition, is aimed at the network equipment vendors whose gear forms the heart of carrier nets. The Santa Clara, Calif., software vendor says seven of the top eight equipment suppliers now use its Linux platform, replacing any array of proprietary real-time operating systems.

The new release is based on the Linux 2.6.21 kernel, but includes a number of patches and features from the 2.6.22 release. Also included are the Glibc 2.5.90 Linux libraries and the GC 4.2.0 compilers. Many of the changes are aimed at making the operating system still more reliable and resilient, and at simplifying an array of application development tasks.

The previous release, Version 4.0, achieved what the vendor says is 99.999% uptime, a key milestone for carrier-quality operating systems. That percentage translates into less than 31.5 seconds of downtime yearly, according to Dan Cauchy, director of marketing for MontaVista’s carrier and mobile group.

The company offers an array of Linux platforms, including one aimed at smartphones and another at real-time embedded systems. 

A battery of real-time enhancements that had been in the past applied as a separate patch are now integrated with the kernel, making it possible for other parts of the software system to make use of them. Likewise, the high-resolution timers, used by protocol developers, are also integrated with the kernel.

For the first time, it’s possible to apply a binary software patch to the system while it’s running on a switch or router or other device, without having to reboot. “You can fix the [software] bug, recompile just that module as a binary patch, and apply the patch with our tool,” Cauchy says. “And when [the module] is next called, it’s called with the bug fix.”

A new debugging feature can be used on a live network, without worrying that system tasks will freeze up during the debugging process. “The developer can log into the system, set [debugging] trace points without stopping the system, and then log in later to see the results,” Cauchy says.