Being Clear About The Work I Want To Do (Part 2)

A month ago, I wrote a post saying I want to be clear about the work I want to do and that I'd follow up every month or so.  It's about that time.

I'm doing something interesting.  I'm learning.  It's open source.  There's, so far, no bureaucracy.
I'm not yet teaching and I'm still a long way off from making any money.

I've started working on the CLFS (Cross Linux From Scratch) project.  I've opened two tickets for changes that should be made to the embedded book and submitted patches.  They're minor things, no one seems to have noticed yet, but I feel very proud of myself.

I'm making progress and it feels really good.

Read More

America. $&#* Yeah!

I've been having conversations with various different people over the past few months about the state of America: our education system, economy, corporations, tax law, and politics.  One trend I'm seeing from the people I have conversations with (and both on TV and online articles) is that people are very pessimistic.

I'm not pessimistic.  I'm very optimistic.

Maybe we don't have the highest ranking education system.  Maybe we're outsourcing a lot of jobs to India and China.  Maybe our political system is fractured and uncooperative.  Maybe all this is true.

But you know what?  Everyone outside North America, even if only slightly, is envious of us.  Maybe they're not envious of all our things, but we have something that's better, worth being envious of.

We have the best sports leagues (NHL, NFL, MLB, NBA, and PGA).  We have THE financial market (Wall St.).  We have the best higher education system (everyone knows Harvard, Princeton, MIT, Yale, heck even my alma mater RPI).  We have the biggest, most high tech companies (Google, Facebook, IBM, Apple, and Intel).

Almost all of these things that we have, that are the best, are spreading world wide.  It's a global economy and in order to grow, it's required.  But they all started here and for the most part are based here, in the USA.

This is the reason so many people still flock to the US.  We're still the land of opportunity, of the free, and where dreams can come true.  It's why we have an illegal immigrant "problem."  So many people want so badly to come here that they're willing to break the law, hide, and do jobs for very little pay with horrid work conditions.

Stop being pessimistic.  It'll only hold you back from greatness, especially in America.

Read More

Gawker Got Hacked... I Dislike Online Accounts

Gawker got hacked over the weekend and had all their users' data stolen, including encrypted passwords.  Awesome.

Gawker at least emailed all the people who had accounts letting them know that this happened, which is nice of them.  I didn't even realize I had a Gawker account, but I do.  I've changed my password there as well as my Google and Amazon passwords.  I don't have any idea what password I used for Gawker but figure I should be cautious since I did use my real Gmail address for the Gawker account.  All my banking stuff uses usernames and passwords I don't use anywhere else so I'm not concerned about those.

I'm thoroughly annoyed by this.  Generally I don't like getting accounts at tons of websites, mostly because I don't want to remember all the logins.  On my work laptop I use Password Safe so I don't have to remember any passwords or usernames, but I shouldn't have to.

OpenID isn't the answer.  I don't have the ability to easily generate throw away email addresses (right now).  Using Gmail's "+" option doesn't work on 90% of the sites I've tried.  So far, just not having accounts is the only answer.  But not having accounts is actually fairly difficult these days.

I'm thoroughly annoyed and I don't know how to fix this.

Read More

My Inspiration

I like playing with computers.  Professionally, that's all I really want to do.

I've been playing with computers since 5th grade.  My family bought an Apple Mac Performa 577 and I couldn't get enough of it.  I bought huge books all about how the software worked, I downloaded all sorts of things from AOL and then the Internet.  I just had to play and learn.

In high school I attended a vocational program for computing.  Most people thought it was odd I'd that I'd attend vocational school as I had good grades and took honors courses and that just wasn't something that people thought went together.  I loved it.  I'm so glad I went to vocational school.  Everybody should go.  Learning the basics of a trade is invaluable further on in life.  And yes, basic IT tasks are basically a trade these days, that's what we learned (A+ certification, installing Windows, putting together computers, basic networking, etc).

I used to be a die-hard Apple fan.  I bought the first G4 Yikes! tower from our local Apple reseller in high school.  I had read about the announcement of this model and just had to have one.  I spent my entire savings from working that summer to get it.  I got the 400 MHz one, before they downgraded the lowest model to 350 MHz.  I felt special.  66 MHz PCI graphics!  Yeah! :)
Apple gave me a free copy of OS9 because I answered a lot of questions on their online support forums.  This was huge for me.  I didn't have much money but I really wanted OS9.  Getting a free copy built a ton of loyalty for me.
I then bought the OSX beta.  It was slow as balls, but that was OK because I was on the cutting edge.

In college I played with a lot of Linux but still had my G4.  I went to opening day at the Crossgates Mall Apple Store in Albany, NY.  I got a free t-shirt and that built even more Apple loyalty.  I couldn't afford buying updates to OSX, so I installed Yellow Dog Linux on the G4 and it became my NFS server for my music collection.

I then went on to built computers and install Linux on them.  One winter when I came home for the holidays I literally had 8 computers packed in mom's minivan.  It was awesome.  I built Gentoo Linux from stage 1 on a 200 MHz Pentium system.  It took days.  It was so much fun.  I ran Return to Castle Wolfenstein demo servers off my laptop and built my first ever computer from scratch just so I could play the demo on Linux.    It was an amazing learning experience.  I learned that the motherboard I got had a newer chip set that didn't have support built into the Red Hat 7.2 provided kernel for the IDE controller, so it got stuck having the processor clock everything in and out in PIO mode.  The hard disk performance was atrocious.  So I learned to build kernels.

Fast forward about a decade.  Now I work at a big Fortune 500 company writing .NET software, playing with RFIDs and smart cards, and soon I'll be diving into some Verilog.  I'm basically an engineer who does DRM for physical things, but I can't really go into the details.  It's interesting, but I want to get back to playing with computers and especially Linux.  Up to the beginning of 2010, I was designing and building an embedded XML-RPC server in C++ for a PowerPC board and the desktop Java app to control automated board testing.  That was a cool job for the technical things, but the business side of things seemed to be turning for the worse and I jumped to the division I'm in now.

These days, I want to play with embedded Linux.  It's cool.  It runs a whole ton of stuff.  It's inexpensive and there seems to be a real dearth of quality people out there who know what they're doing with it and are willing to share that knowledge for a reasonable price.  I want to become one of the people who knows what they're doing and then teach other people those same skills.  Along with my continued interest in many things related to computing and Linux, this is my inspiration for writing a book about embedded Linux and for wanting to help with the Cross Linux From Scratch project.

Read More

Absolute FreeBSD and Building A Server With FreeBSD 7

Two books on my bookshelf, that I read over a year ago, are Absolute FreeBSD: The Complete Guide to FreeBSD, 2nd Edition by Michael Lucas and Building a Server with FreeBSD 7 by Bryan Hong.  I bought them at about the same time and read them together.  I was wanting to use FreeBSD on my desktop machine and I was setting up a virtual private server (VPS) on RootBSD to serve web pages, mail, and be an network time protocol server.  These two books, although both published by No Starch Press and about the same operating system, are very different in both content and style.

Absolute FreeBSD is a thick tome covering everything about FreeBSD that an aspiring computer savvy person would want to know.  Basically, you could read Absolute FreeBSD, never read the official FreeBSD Handbook, and learn very similar information all while building a computer system that can serve web pages, DNS, mail, and many users.  Michael Lucas is a great technical writer.  He keeps things light when describing situations but then provides just enough technical details about how things are supposed to work, interspersed with step by step instruction, to assist you with setting up your own server.  It's one of the best written books about computing that I've ever read.  I thoroughly enjoyed reading it and putting the information to practical use.  It's an awesome book and I learned not only how to set up a FreeBSD server, but also, why certain things work the way they do (especially DNS which is rather difficult to explain).  This book will be a lasting reference book on my bookshelf that I will refer to in the future, even when doing non-FreeBSD things (like DNS), to help refresh my memory.

Contrast this with Building a Server with FreeBSD 7, which is purely a step by step (literally) manual on installing and configuring often used software packages on a FreeBSD 7 system.  There's very little, if any, explanation on: why you should set up configuration files in the specified ways, why certain commands are issued the way they are, and how to do anything beyond the basics of installing and getting said software running.  I'm sad that I spent money buying this book, I could have gotten just as much out of it by borrowing it from a friend or library.  I only used it once and now some of it is already outdated because the software packages described are either out of date or because FreeBSD has moved on (already being at version 8.1).

The way these two books contrast each other is astounding.  Usually, the No Starch Press books I've read are mostly written similarly to Lucas's style.

One thing I definitely got out of these two books is that I want to be a writer like Michael Lucas.

Read More

QEMU Booting CLFS PPC Issues

I'm building version 1.1.0 of the Cross Linux From Scratch (CLFS) PowerPC system.  I don't actually have any PowerPC hardware so I'm using QEMU.  I have built QEMU 0.13.0 from source because Debian Lenny only comes with version 0.9.1 and it's a bit old.

When booting my CLFS system in QEMU, this is my command line:

andrew@bigbox:~$ qemu-system-ppc -nographic \
-hda cross-lfs-ppc/disk.img -kernel \
cross-lfs-ppc/clfs-fs/boot/clfskernel-2.6.24.7 -M g3beige

The switches used are:
-nographic -> QEMU should output to my terminal rather than VNC
-hda -> This is the file to use as disk /dev/hda
-kernel -> The kernel to use
-M g3beige -> QEMU should emulate a beige G3 PowerMac

When I was building my CLFS system, I didn't follow the directions for Yaboot because I was under the impression that I could simply hand QEMU the kernel and root file system and it would be happy.  When creating my disk image, I didn't create any partitions, everything's simply in hda.  One of these two spots are probably the root of my problem.  I'm going to try building Yaboot first and if that doesn't fix it, I'll work on creating the partitions correctly within my disk image file.

When booting, QEMU goes through its normal bios output but after finding a display and building the device tree, it hangs with:

Calling quiesce ...
returning from prom_init

After a few minutes, it will reboot and end up at the same place.  The verbosity is not much help for debugging and Google doesn't seem to be my friend with this issue.

I'll be sure to either comment on this post as to my resolution or I'll write another post detailing the fix.

Read More

Being Clear About The Work I Want To Do

A Better Way of Work blog has a posting saying people should make it clear what the work you want to do is.  I'm going to do that and I'd like to be able to write additional posts under the "work" tag to update my status on this.

I want to do work that:

• Is interesting
• Allows me to learn and to teach
• Involves open source software or hardware
• Pays well enough that I feel secure
• Doesn't bog me down with corporate bureaucracy

I'm willing to give up playing hockey.  I've played for the past 22 years but I'd rather focus on the work I want to do.  That will net me extra time in the evenings to spend with my family or to do my work.

I'm willing to give up sleeping in.  I'm trying to create the habit of waking up before 6am so I can work before going to my job.  So far I've been successful at doing this 2 or 3 times per week.  I'd like do this more often.  Yes, I get tired earlier, but I'm much more focused and productive early in the morning.

My biggest fear is that I won't be able to do the work I want to do and still make enough money to be secure.  I don't need to be rich but I do need to be able to provide for my family.

Read More

LED Lighting to Replace Fluorescents, The Future!

I broke a fluorescent U shaped bulb yesterday evening in my kitchen.  I was attempting to set it on the counter so I could remove the bulb that was in the fixture and it tapped the counter ever-so-slightly, shattering into a million pieces.  I attempted to follow the EPA guidelines for cleaning up the mess, mercury and all, but it's not easy.  We have hardwood-like floors in the kitchen, so after opening a bunch of windows and going in another room for a bit, I was able to scoop up most of the glass and powders that were near where the break occurred.  But then there's glass everywhere, and I mean everywhere!  Little tiny shards of it.  It was a pain to clean up.  After cleaning up, I proceeded to freak out about mercury.  How much is in the air?  What's too much?  Am I breathing it?  What's the impact on me, my wife, and our cats?  I proceeded to cleaning of the entire kitchen: floor, counters, and stove top, multiple times.  Windows and doors were open with fans running full blast for about 3 hours.  That should get it all out, right?

Come today, I'm still paranoid.  Who can I call about this on a Saturday?  Well, the National Poison Center is open 24/7, so I called them.  A very professional woman answered all my questions, told me the way I cleaned up was fine, and reassured me that even cleaning up just one bulb completely the wrong way on wood flooring is nothing to get concerned over if I've had windows and doors open.  It made me feel a whole lot better.
I still cleaned the kitchen again after hanging up.  Just to be safe :)

Why am I so concerned over this?
It's because there's no sure way to know what the heck is going on with mercury.  I'm no expert but I do know about RoHS, and mercury is definitely one of the restricted substances (ironically with an exemption for fluorescent bulbs).  It can't be good for you.  But you can't see it (when it's vapor), smell it, taste it, or easily test what concentration it exists in with a DIY kit.  Thus, I was paranoid about it.

I don't want this to happen ever again.  But how can I ensure that this doesn't happen again?
Getting rid of all my fluorescent bulbs seems like a decent answer.  But incandescents use quite a lot more electricity and don't really come in tube sizes so they're not really an option.  What about LED lights?

LED lights aren't really easy to buy right now.  Home Depot lists quite a few different types of bulbs (84 in the LED lighting section) but many are only available online and some of those listed are holiday lights.  None of those listed are tube type that can replace fluorescent bulbs.  All are expensive (think 10x the price of incandescents or CFLs) and generally have lower light output compared to fluorescent or incandescent bulbs.  I searched around online and found some places selling tube type LED lights but every single one I found requires you to rewire the fixture to bypass the ballast and starter.  Some even require an external power unit (I assume to convert the AC to DC) that has to be wired in. 

I can rewire my fixtures to support different types of bulbs (I'm an EE and I know my way around a wire nut) but I don't want to do this.  I'm pretty sure no body wants to do this, they just want to buy a light bulb and put it in.  That's how light bulbs are expected to work.

I think this is a market ripe for innovation.  With upcoming US regulations requiring higher light output per watt combined with people's dislike for CFLs (and fluorescent bulbs in general [warm up time, flickering, buzz, cold weather performance, lack of dimming, etc]), the LED market place is going to experience rapid growth.  Right now the growth seems to be in normal screw in type bulbs with some less elegant systems for tube bulbs.

I'd expect the LED tube bulb market to be the largest market, yet there doesn't seem to be a (literally) drop in tube LED bulb out there at any price.  Schools, corporate facilities, and hospitals use tons of tube lights and are often concerned about mercury releases, energy consumption, and "green-ness."  These same institutions also don't want to have to pay an electrician to rewire every single light fixture.  Tube LED lights that are a drop in replacement for tube fluorescent bulbs would sell like hotcakes!  Even if there was a price premium, early adopters would pay extra to get their benefits.  This would drive volume and technology development, ultimately bringing prices down.

Maybe I should design a tube LED lighting system...

Read More

Computer Configuration User Interfaces Suck

When buying a computer, especially desktop or workstation class computers, why is it so annoying to configure a computer that you want?

For example, go to Dell.com's "Large Enterprise" store and find the lowest cost configuration that gets you a workstation computer with at least the following specs:

• 2 or more processor cores with VT extensions (of any speed)
• 4GB of RAM (with or without ECC and of any speed)
• Either a 160GB 10k RPM or 128GB SSD hard disk drive
• DVD+/-RW burner
• Windows7 32bit Professional w/ XP mode

It's so impossible it's not even funny.  I attempted to wade through this exact situation at my Fortune 500 the other day and I was not a happy camper.
What's the difference between an Optiplex 980, 960, and 780?  How do those compare to the Precision T1500 and T3500?  Which one will let you get at least the above specs for the least money?  Why the #%@$ can't I get a 256GB solid state drive in any computer I want?

I have no friggin idea.

A great idea would be a web 2.0 style drag and drop interface for configuration of a PC.  Along one side it would list all the different categories of things you can choose, like processors, RAM, disk drives, graphics, etc.  You'd have a work area in the middle and you can drag any of the categories onto the work area.  Once you drag a category onto the work area you can narrow your selection of available choices by putting constraints on the category, like I only want >2 cores.  As you refine your search by adding constraints, options that aren't compatible with your constraints would simply not be available (like if you choose a constraint of ECC memory being required, you wouldn't be able to choose a Core2Duo processor anymore).  As you refine your search by putting constraints on categories and adding additional categories to your work area, another column would list the number of configurations that fit your requirement along with highest and lowest prices.  Most people would simply pick the lowest price computer that met their requirements.

This would be great for pretty much anyone who has specific requirements for their PC.  It wouldn't be that hard to develop (at least compared to other configuration interfaces) and would probably get a lot of use by customers.  I'd think someone like Dell would really reduce the headache of customers by offering a system like this.  It'd even help their internal sales people, probably especially when quoting larger orders for corporate clients.

If no one has something like this next year, maybe I'll teach myself Ruby on Rails and some JavaScript and do it myself.

Read More

Open Source (at my Fortune 500)

At my Fortune 500 company the other day, there was a presentation performed by some of the lawyers about open source software and how it can be used within the company for internal uses and for use in products.  It was interesting and I'm glad I went, but it was held right before lunch and I was very hungry, so I only stayed for the first half.

In the first half of the meeting the lawyers reviewed the requirements of open source licensing, such as the fact that with most licenses you must provide the same freedoms you received and that open source licenses are just like closed source licenses, they use similar laws to be effective.  This is interesting because one word that got a lot of attention is "distribution".  Another topic that came up frequently is "viral" licenses that can "infect" other software (those are words from the presentation, not my words).

What counts as distribution?  Does passing a copy of a software from one employee to another count as distribution?  With pay-for software, often it does, as you're expected to purchase a license for each person or machine that the software executes on.  But sometimes with open source software it can be assumed that distribution means passing the software to another entity, be it another corporate entity or a customer.  Like when I download a copy of Debian GNU/Linux from debian.org, that's clearly distribution because I'm not a part of Debian, I'm just a user of Debian.  If I install Debian on my computer and my wife's computer, does that count as distribution?  Do I then have to comply with all of Debian's licensing terms regarding distribution?  It gets tricky, did I just "distribute" a copy to my wife?

The "viral" part is also interesting.  My company doesn't want to have to release large amounts of our currently closed source software to the public (or even just our customers) because we currently make a bunch of money selling said software.  Should a "viral" license "infect" our current closed source software in such a way that we release some software that used something with a "viral" license, we'd then be obligated to give away the source to our closed source (or at least part of it).  It's a legitimate issue for closed source software shops that make money the Microsoft way, by charging for each copy sold.  It also makes sense because some of our software does really neat stuff that not many competitors can do.  It's what sets us apart and we don't want to give our competitors any advantage if we can help it.

I understand that distribution is a strange term that may be defined differently by different people and that makes it tricky.  And I understand that "viral" licenses could force us to disclose source code that's currently secret.  But what saddens me is that we're not changing our business model or internal practices (very much) to take advantage of open source.  Not even in just a few of our products.

Jeff Atwood blogged recently about how routers are becoming a commodity hardware platform because of things like DD-WRT.  My company makes hardware and provides services for both our software and hardware (along with various other things that we do).  It would be interesting to see my company (and / or competing companies) release source code to the public and focus on other avenues of making money, mainly service, support, and hardware.  We'd have to keep ownership of the software in the sense that the Mozilla Foundation retains ownership of Firefox but allows the public to contribute.

Read More

What's Going On in CLFS Chapter 5? [/tools and /cross-tools]

In building the CLFS PowerPC cross compiler the instructions say to create both the /tools and /cross-tools directories (these are actually symlinks to directories of your choosing but it's the easiest way to reference what I'm talking about).  I didn't fully understand why this is the case so I did some Googling and re-read parts of the CLFS book.

Turns out it's briefly described across various sections, including: 4.2 (Creating the /tools Directory), 4.3 (Creating the /cross-tools Directory), 5.4 (Linux-Headers), and 6.1 (Introduction to chapter 6).

The /cross-tools directory is where the actual cross compiler and its assorted "friends" will live.  The /tools directory is where we're building a temporary system that can actually build a real system.  The entire goal of chapter 5 is to build a GCC cross compiler that executes on your desktop PC and builds executables for some other computer system (in my case, my desktop's an x86_64 box running Debian Lenny and I'm wanting to create executables for PowerPC Linux).

A fun problem is that in order to build a cross compiler, we need a compiler (and a bunch of other stuff).  There may be a shorter method to achieving this, but I outline the CLFS way of doing things:

• Starting off with section 5.4 (Linux Headers), just the header files for a Linux kernel are installed into /tools/include.  The headers will be needed later to build Glibc.   
• In section 5.5 (File), we build and install File into /cross-tools (File lets us figure out what type any given file is).  This version of File we build is a native application on our desktop PC and is used by other steps.
• Section 5.6 (Cross Binutils) has us build a set of binutils, again these are native to our desktop PC.  No cross compiling yet.  Binutils assists in compiling and linking programs.  We'll use this set of binutils to build our cross compiler, GCC.  Binutils gets installed into /cross-tools.
• Now we get to some compiler compiling, section 5.7 (Cross GCC - Static).  Here we build a very simple, statically linked version (it includes all libraries it needs internally to itself rather than reference them being installed in another location) of GCC that can only compile C programs.  GCC is actually built without any C library (Glibc) as we don't yet have it.  GCC goes into /cross-tools.
• Section 5.8 (Glibc) finally gets us to the C library.  When configuring Glibc, we must tell the configuration script how to find all the different items we've already installed, as they're in non-standard locations.  Glibc gets built using our statically linked GCC and our kernel headers, it has just enough ability to do so, and installed into the /tools directory.  The kernel headers are needed as some of the implementation of the C library involves making system calls, thus the C library needs to know how to make those system calls.
• Now we can finally create an actual cross compiler.  Section 5.9 (Cross GCC - Final) finally has us build a real C and C++ cross compiler.  This step uses the previously built statically linked GCC and Glibc to create a real, dynamically linked, version of GCC.  Now we have a cross compiler!

I'm curious to see how much of what was used to build our cross compiler is still needed in order to complete the CLFS book.  Maybe this is a job for git (another thing I'd like to learn).

Read More

Cross-Compiled Linux From Scratch

I'm following the Cross-Compiled Linux From Scratch (CLFS) version 1.1.0 book for PowerPC.  I'm using this to make sure I understand what's going on with cross compilation and setting up a basic Linux system for a different architecture.

I've previously followed the CLFS book for creating x86 and x86_64 based cross compilers for PowerPC Linux at my day job, but I never really understood why I did each step in the process.  I also do not have good experience with a lot of the tools used, such as ar, as, sed, and qemu (as I don't actually own any PowerPC hardware).

My goal is to first understand the entire CLFS process and be able to either commit helpful changes back to the project or to be able to write additional documentation about how and why the CLFS project book has each step in it.  I consider myself to be a decent Linux user but there are so many widely different things that can be done with Linux that it's difficult to be excellent at all of them.

About 8 years ago I was a Gentoo zealot and through my adventures in installing and maintaining Gentoo boxes I learned a lot about Linux systems, but I wouldn't consider myself an expert [I've since reformed and I'm no longer a zealot, or a Gentoo user ;)].  I'm hoping to move closer to expert status by diving into the CLFS project and I want to be able to explain the entire process.  I think it's very important to have an understanding of how things go together to create a Linux "distribution" (in quotes because CLFS isn't really a distribution as much as a receipe).

Read More

Short and Sweet, But Not Always

Jason @ 37signals posted a blog entry about how he'd like to teach a class where the goal is to learn how to edit complex ideas into various sized chunks that are still meaningful.

I think that's awesome!  I would love to improve my ability in this area.  I tend to ramble on about things when writing and often I can get off of my original train of thought.  I end up with long "papers" written about things I was excited to write about when I began writing.  Other people do this too and I get turned off by long essays - even on things I'm interested in - if my mood isn't ready to read something long and detailed.

Having the choice to get different sized versions of the same material is a sweet idea for marketing a product that conveys an idea.  Offer different price points that coincide with different sized versions of the idea and the customer decides which version / price / size they want based on their own factors.  This could even be applied such that the customer can "buy" the lower priced but shorter version as a trial (maybe for free?) and then opt to get a discount on a longer version that has more detail.

Or this could revolutionize the "news" industry.  Currently the fad is Twitter or articles, often they overlap.  What's missing is the sizes between 140 characters and full blown articles.  Maybe another part that's missing is the true long form version where detailed analysis and further investigation takes place.

If I ran a newspaper and I wanted to survive in today's world, I'd make an iPad / iPhone / Android app that delivers news in this way.  Then have it automatically pick articles you'd be interested in (a la Google News) based on browsing habits and present a 2-3 sentence or Twitter'ized version aggregated on a home screen but also pick the size you'd be interested in when you go to view the article with the option to see or "buy" other sizes of the same article.  Google News meets Twitter meets traditional news reporting meets LexisNexis.

It's MY SIZED news.  That's a good idea.

Read More

Revolution OS

I just finished watching Revolution OS on Netflix.  It was actually pretty good.  I'd be curious to see an updated version made today.  Things have changed but they're still going in the same direction they were when the movie was made.

Even though I've been using Linux and BSDs for about 11 years, I didn't really know the faces or voices of the people who've made it all happen.  It was cool to see and hear Richard Stallman and Linus.  I've known who Bill Gates is, he was often on TV back when he ran Microsoft, and Steve Ballmer throws chairs, so I know who he is (plus he's really intense looking).  It's funny that I don't care for Microsoft that much, yet I know the guys who made it happen.  With GNU/Linux (to please Richard who makes the point over and over in the movie [probably in real life too]) I had no real idea who the people behind it were other than the names.

I'm glad I watched Revolution OS.  If you've got an hour and 20 minutes to kill, it's worth a viewing if you're interested in free / open source software and Linux.

Read More

Rework, Drive, and Linchpin

I have just finished (in this order) reading Rework by Hansson and Fried, Drive by Dan Pink, and Linchpin by Seth Godin.

I really enjoyed Rework.  It is part of the reason I started this blog and want to get back into Linux.  I'm not yet sure how I can make decent money off Linux with the skills I have, but I'm excited to try.  And Rework, combined with reading a lot of things written by VCs, has given me a good feel for the tech new business starting landscape.  Mostly that there's no one right way to start up a business, but without trying, it won't work.

Drive was also very good, but a little more wordy than Rework.  Also, before I read Drive, I watched some of Dan Pink's presentations on YouTube.  Basically what he says in the book is what he says in the videos online.  That was somewhat a letdown for me, but still worth reading the book as he is able to go into more detail of examples.

Linchpin kind of let me down.  It's very wordy for the message.  I liked the message, but it just takes too long for Godin to get it across.  A book with half the amount of pages would have gotten the message across just as well, if not better.

I'd recommend both Rework and Drive.  Especially if you're at a job where you feel something is missing but you're not sure what.  You're talented and capable but you're not reaching your full potential at work, these two books will talk to you.  Linchpin will talk to you too, but it's annoying and less inspirational.

Read More

I'm Writing a Book

I'm writing a book about embedded Linux but I'm not going to compete with traditional technical books.  O'Reilly isn't my competition.  (I personally really like many O'Reilly books and how they're often they're written by open source contributors.)

My competition is often outdated and unfriendly, hard to use technical resources such as the web, mailing lists, wikis, forums, and yes, books.

I want to teach people how to develop embedded Linux systems.  I don't want to provide a step by step here's how you put together an embedded Linux system, although I'm going to do that.  I want to provide the how, but right behind that I'm going to provide the why.

Why does the manual tell me to do this step and then that step?  What's going on under the covers?  What if I (the reader) want to do something similar to this but changing things X, Y, and Z?

I'm going to answer those questions.  You (the reader) are going to help me.

The book's going to be inexpensive (not free).  There's going to be online collaboration (think Google Groups or a forum).  The book's going to take on the mantra of release early, release often.  Trees are going to die, but the book will be available in electronic formats too.

I think it's going to be amazing!  I hope you will, too.

Read More