Reliability and availability: What’s the difference?

How do you design a computing system to provide continuous service and to ensure that any failures interrupting service do not result in customer safety issues or loss of customers due to dissatisfaction? Historically, system architects have taken two approaches to answer this question: building highly reliable, fail-safe systems with low probability of failure, or building mostly reliable systems with quick automated recovery.

Editorial: OSS Software, Deaf Developers & Unsatisfied Users

To make it clear: I am not against Open Source Software, in fact, I am for it. But I am increasingly frustrated with Open Source software written by hobbyists; hobbyists who write a specific application or library because they need a specific function out of their applications, for their own needs and only their own needs. Here's what happened: UPDATE: Some explanation here. Make sure you read it first.

Interview: Jim Curtin, CEO of Win4Lin

Orange Crate has an interview with Jim Curtin, CEO of Win4Lin, a company that makes software that allows users to run Windows from within Linux. The company recently restructured, and they have big plans to "play a lead role in un-coupling applications from operating systems and hardware dependencies" and "make end user computing as cost-efficient, stable and secure as possible."

Puppy: A Linux Live-CD that Saves Back to CD

As far as I am aware, this is a world first, a live-CD that saves back to the CD at the end of the session. So how does it work? "Boot the PC with the multi-session CD inserted in the CD-burner drive -- thus, Puppy automatically knows which drive is the CD-burner, in case you have more than one CD/DVD drive. Then you use Puppy in the normal way. At shutdown, all the changed files in your home directory are saved back to CD. That's it. Next time you boot, all the personal files are restored."