System Overlord

A blog about security engineering, research, and general hacking.

3 Things in Linux you should NOT Install

While I'm all for promoting the use of Linux and software on Linux, unless you absolutely know what you're doing, there are certain things you should not install. Entirely too often, I see people on asking how to configure one of these or why they will not work. So, in no particular order, 3 Things you should NOT Install:

'Embedded Linux Primer': A Review

A review originally published on

"Embedded Linux Primer" by Christopher Hallinan is an excellent resource for anyone looking to use Linux in an embedded system.  It does not cover basics, so is more targeted to experienced Linux or embedded systems developers looking to move to Linux embedded systems.

The book covers a variety of topics including the Linux kernel's interaction with hardware, system initialization, design considerations when working with an embedded system, and porting Linux.  The book provides a detailed description of most of these topics, including many step-by-step directions on reference implementations.

The book does not provide command-by-command howtos for many of the steps involved, but the details should be obvious to anyone familiar with basic kernel building and software development.

The book also briefly discusses the new hard real-time support for the Linux kernel, including hardware-specific implementation issues.  It also provides all code samples in the book under the GPL license, though it does not provide a CD.

All in all, I would strongly recommend this book for anyone looking to develop an Embedded Linux System or for anyone curious about the inner workings of the Linux kernel on embedded systems.

Community Colocation Project

Several cities have a "community colocation project", such as the San Francisco Community Colocation Project. I feel that Atlanta is in a perfect place to join this movement.

Community colocation projects (CCPs) are a non-profit datacenter for non-profity entities and individuals. This would be a great opportunity for an advancement of Open source projects and for the community in Atlanta and the metro area. Atlanta is the center of high-tech development for the Southeastern United States, and as such, should become a leader in the Open Source arena.

Thoughts and comments are appreciated.

Microsoft is 'not litigating'

Microsoft's VP for Intellectual Property has announced that Microsoft has no intent of litigating against Linux users.  So why the recent announcement of the number of patents they feel Linux and Linux distributions infringe on?  They want to spread the usual round of FUD -- fear, uncertainty, and doubt -- to encourage business who might be afraid of litigation to choose Windows over Linux.  Nice marketing strategy, don't you think?

I just noticed that declanmcgrath has a similar theory over on his blog.  Guess it's seeming pretty obvious to the Free world.

Linux and Software Patents

Several news outlets are reporting that Microsoft has put a specific number on the patents they claim Linux infringes upon. To some, this may seem like a move by Microsoft towards some form of legal action, or even a risk to the longevity of Linux. I do not believe this to be the case for a number of reasons, but I must first make the usual disclaimers: I am not a lawyer, I do not play one on TV, and any Linux user concerned about their rights should consult a lawyer.

  1. Microsoft has previously had patents invalidated where prior art existed. Some of the Microsoft patents probably fall into this category, particularly if they were filed after the supposed infringement occurred. In order to protect intellectual property, you would have to have your patent application file before anyone else duplicates your work.
  2. Software patents in themselves are basically ridiculous because the idea of patenting software is like patenting a language or a screwdriver. Software (and, by extension, computers) should not be seen as an end. They are a tool to get things done. Furthermore, software MUST be able to inter-operate and that requires the ability for multiple developers to implement the same protocols and formats. At present, the European Union does not even allow software patents. The US supreme court has (fortunately) never upheld that software patents are specifically permitted under US law.
  3. The whole idea that patents are needed to protect the market is ridiculous. Copyright can protect a particular implementation, preventing anyone from being able to copy
  4. Linux is too important to be completely destroyed in a patent war. Too many large companies use it and don't want to see it disappear. Google runs all its data centers on Linux, which is good because it needs high reliability and uptime, something Microsoft software doesn't seem to offer. LucasArts and Pixar run their 3-D rendering farms on Linux. Dozens of other fortune 500 companies run Linux. IBM, Red Hat, Novell and others have stood up to SCO over claims of copyright infringement, so the battle with Microsoft will be nothing new to them. I imagine Canonical will also enter the ring at some point.
  5. By extension of #4, Linux is too important to Microsoft. That's not because of some patent royalties, either. The importance of Linux comes from its position as Microsoft's whipping boy. Microsoft can blame a number of problems on "open source hackers." Linux is also a more legitimate server operating system than Apple's OS X, helping Microsoft deftly avoid some of the laws regarding monopolies. Let's not forget that they were sued in the late 90s by several states and the US Department of Justice for violating anti-trust law. Let's also keep in mind that they are currently negotiating a settlement of fines with the European Union for similar business practices.
  6. If Microsoft files a lawsuit against Linux users, they may open themselves to many forms of retaliation, including businesses completely dumping Microsoft software, counter-suits from other Linux users wishing to clearly establish their legal right to use Linux, and a public relations nightmare. In all likelihood, they would end up losing more than they could hope to gain.

Why should software be all about business, anyway? Why should hobbyists and small developers be restricted from making something that works with other software? Microsoft is simply another case of corporate America looking for more money. Most notably, Steve Ballmer comes across as an unethical, arrogant, and self-serving "suit".

Software patents restrict choice to give rich executives a few more dollars. If Microsoft had it their way, we'd have to pay for each reboot of our computers: and with their software, Bill Gates himself could not afford that.

Edit: Growler knows what he's talking about when he says Microsoft takes on the free world.