nipeng wrote:The eee specific kernel and tools... are those opensource or are they closed source?
Just wondering what will happen when Asus stops supporting the eee.
Well, the kernel from array.org is open, it includes a few questionable patches (like madwifi) and while 100% open source it does include outside code (like microcode for the wireless drivers). When Asus stops supporting the EeePC the drivers will still be around, after all the EeePC is simple stock hardware with a few ACPI keys and a semi-supported wireless chipset 
The main drivers required for the EeePC are slowly getting into the stock kernel. the asus-laptop module supports all of the EeePC's oddities, and the ath5k driver is simple, but provides working support for the 701 series. Not sure about the 901 and 1000, but I think they have better driver support anyway.
I really do wonder whats happening with Ubuntu and the EeePCs, It seems they're not really arsed about core support for the EeePC. Debian have got a strong drive to get all the drivers included in the core kernel package. Before #! I used a pure debian install with only a couple of minor packages (eeepc-scripts) to get everything working, but it seems for #!/Ubuntu I need to jump through some hoops. I know this isn't a issue of #! but still a point to look on.