Linux 2.6.37 Kernel Promises to Unlock OS
Official Nagios Training Schedule January 2011
Why Linux is Alpha and Omega
Detecting net neutrality violations?there's an app for that!
Ubuntu?s Cloud-Init Promotes Customization in the Cloud
Motorola Takes Wraps Off Xoom Android Tablet
What the WWF has to learn about FOSS
Introduction to RAID
Virtualization With KVM On An OpenSUSE 11.3 Server
CA Court Rules Smartphones Can Be Searched Without A Warrant
Switching to Linux (For the Right Reasons)
Virtualization With KVM On An OpenSUSE 11.3 Server
Official Nagios Training Schedule January 2011
Why Linux is Alpha and Omega
Detecting net neutrality violations?there's an app for that!
Ubuntu?s Cloud-Init Promotes Customization in the Cloud
Motorola Takes Wraps Off Xoom Android Tablet
What the WWF has to learn about FOSS
Introduction to RAID
Virtualization With KVM On An OpenSUSE 11.3 Server
CA Court Rules Smartphones Can Be Searched Without A Warrant
Switching to Linux (For the Right Reasons)
Switching to Linux (For the Right Reasons)
Switching to Linux (For the Right Reasons)
Jan 6, 2011, 14 :12 UTC (4 Talkback[s]) (2055 reads)
(Other stories by Matt Hartley)
[ Thanks to James Maguire for this link. ]
"So what is my concern about making the switch to Linux in order to save money? These are trying economic times -- wouldn't using a platform without licensing costs make a lot of sense?
"Yes, I am a fan of the cost savings of using open source solutions, but only when coupled with other Linux advantages. Switching merely based on cost savings is almost always going to lead to a massive switch back to the previous platform. Why? Because any hurdles along the way will be seen as a big deal, thus sending those migrating running back to the familiar.
"Instead I think there needs to be more focus on 'control' over how things are running. This means no surprise updates despite disabling this feature, and no concern over lost software copies since the software is readily available from the software online repositories. It also means the benefit of a generally consistent experience regardless of the system the software is installed on."
Complete Story
Related Stories:
How You Know When It?s Time to Switch to Linux(Dec 29, 2010)
What If All the World Ran Linux?(Dec 27, 2010)
20 reasons you should switch to Linux(Dec 06, 2010)
Detecting net neutrality violations�there's an app for that!
Official Nagios Training Schedule January 2011
Why Linux is Alpha and Omega
Detecting net neutrality violations?there's an app for that!
Ubuntu?s Cloud-Init Promotes Customization in the Cloud
Motorola Takes Wraps Off Xoom Android Tablet
What the WWF has to learn about FOSS
Introduction to RAID
Virtualization With KVM On An OpenSUSE 11.3 Server
CA Court Rules Smartphones Can Be Searched Without A Warrant
Switching to Linux (For the Right Reasons)
DACA could mean fewer bugs in Debian
Each piece has written software bugs. The insignificant, the showstopper are bugs despite the Herculean efforts of the developers. But thanks to a new Debian project, many previously unidentified error can get squashed.
Raphael Geissert, multi-talented Debian developer, has new automated code analysis from recent Debian project. Geissert describes DACA as that.
Automated code analysis helps identify and resolve bugs and other problems in the source code. The project aims to draw users easily distributed access to a variety of tools for improving software quality to give Debian, while the tool developer, a test bed, more visibility and more feedback. This is achieved by running this tool on the entire Debian archive.
It seems to wait for the often delayed publications that is Debian's main goal, stability and error correction, and this impression many outsiders not inaccurate. Debian has worked hard to its reputation as to earn one of the most stable Linux distributions. Get through but even many bugs; many more as some developers can accept. DACA will be from a batch of tool to run tests on the source code Debian packages then reports offer to developers.
The project is just started when the there are only two tools in the box, but many more are planned. The tool is Cppcheck. Cppcheck audits C/C++ code for the actual functionality bugs instead of syntax errors. These are the kind of errors that typically go through compiling process without errors, leading developers to believe everything is fine. Although it is far from complete and new and more comprehensive measures are planned in the coming months and years, it does quite a few controls. Some are out of bounds checking, automatic variables, and memory leaks.
The other available tool is Checkbashisms. As the name implies, it looks for Bashisms, the bash extensions that are not only POSIX compatible. The first round of the reports is available online.
Although the list is now short, grow the number of tools at over twenty. Geissert says the major limitation is, "most are tools CPU-bound, to limit the number of tools, and it takes time to review by the entire Debian archive." He called for bug check reporting false positives, tool evaluation and hardware donations. See his full post for more information.
