== Begin Opening ==

I ventured onto the gnu.org website wanting to read what their licenses actually were. In the process I decided that I should figure out what GNU actually is. Aside from discovering that the FSF seems to be just a source of income for GNU, I was quite disturbed.

I want to make very clear that I went into this with no bias in one way or the other. It is only after all my research that I developed a very strong opinion. I also want to say that a majority of my research was done by reading pro-GNU information. I also asked about this in the #gnu channel on Freenode. Below I'm giving my opinion on two specific documents that bothered me in particular. Their text is cited verbatim as well as links to the original.

# Documents are below the conclusion.

== Begin Conclusion ==

Instead of placing my conclusion at the very bottom it's going here.

If you don't want to read the whole thing, it boils down to GNU feeling they thought of it first so their the originators of the Linux project and all work belongs to them. However, I encourage you to actually read it for yourself. Just follow the links, you don't need my opinions for this.

After everything below I have no doubt that what we call "Linux" should be "Linux" and NOT "GNU/Linux." I'm actually very certain that GNU doesn't belong in the name of any operating system at this point. If they can ever finish their own OS, then perhaps they can call that system "GNU." Until then, they should realize their failures as developers and as free software idealists. They should realize that they can make a "GNU Linux" system that is stripped of anything they don't like and realize that this is what theire "GNU system" is.

They claim we can't exist without them but that's wrong. Linux distributions exist without any GNU software in them. They really need to remove themselves from their communist beliefs and take a jump into the real world.

00:00 GNU: No! I use "Linux" and I will never use "GNU/Linux." FOSS belongs to everyone. Stop trying to claim the work of so many others as your own.

Many of us know of and have met MootBot. The authors describe MootBot as:

Mootbot is an eggdrop script that is used by the Ubuntu Scribes team to log meetings. It logs messages that begin with certain keywords in an attempt to make it easier to summarise the meeting and introduce a defined structure.

If you've been in #ubuntu-meeting then you've definitely seen it work. It's a very efficient tool for managing Meetings.

By now we've all heard about the Bazaar (bzr) version control system. If you're a coder then you're well aware of what a version control system is and why it's helpful. If you code on Launchpad you're equally aware how incredibly awesome this system is.

Rather than discuss how incredible bazaar is, I'd like to explain how to set up a production level deployment for a bzr server. If you're curious what makes bazaar great, just try it out. You can use https://staging.launchpad.net/ to create branches for playing around.

I was hosting my own email server for about a year. I enjoyed the fact that I had full and complete control over the entire mail server. I enjoyed being able to fine tune everything to fit my needs exactly. I was doing this for about 1.5 years.

Unfortunately, there were a few things I couldn't control that really killed the fun of running my own email server. First of all, dealing with the people complaining that it's not how they want it weighed on me. Aside from that there were also power outages, hardware failures, software hangs (from power dips), firewall/router deaths, modem spasms (now very frequent), etc. Not only that, but I only had 1mbit upload available and 1.5mib max available at about $100/mo more.

What it came down to is that running a mail server just isn't for me given my limitations. I needed an alternative and I found one. There is this thing called Google Apps (google.com/a) that is capable of hosting your domain email for you.

I decided to give it a shot. It's not a quick or idiot proof process, but it was worth the effort.

I hear a lot of people drooling over how super fast their system boots on Jaunty. I saw one mention on the Planet already about 20.03 seconds being fast. Just after reading this, I decided I need to post mine.

It's less than 15 seconds. Readahead is using up 14seconds of that and I have a feeling I can reduce the readahead time to about 2.5 seconds by just tuning it a little better. Perhaps there's some large files that it's loading which are being counter productive to this process.

I've attached the bootchart image to show how fast it currently boots.