A taste of what’s to come…

by Hexxeh on Dec.09, 2009, under ChromiumOS

I thought I’d best create a blog to keep you informed of what I’m getting up to, especially currently with Chromium OS. So here’s a quick overview of my current plans with that:

  • Fully automated build system
  • More wireless support
  • Pushing changes back into the main source tree
  • New website with automatic status showing on how a build is going, possibly even ETAs generated automatically
  • Faster releases, I aim to get the build process tuned down so we can get builds rolling off as fast as changes hit the main source tree
  • And here’s the big one I think many of your have been waiting for, automatic updates. This may not be in initial versions, but it is certainly now a long-term goal for my builds
  • Less soda-themed names

Those are just a few of the things I’m planning. Right now, I’m working on building the automated build system, and that’s coming along well (though the 512MB of RAM the server has is becoming rather restrictive). I’ll be posting more about each of these new features and plans soon.

The long term goal, is basically to become the de facto Chromium OS build for general users (as opposed to developers who are comfortable building themselves). I’ll also be publishing every single bit of my code as open-source.

I’d also like to take this opportunity to express my thanks to various people:

  • Google, and redpig in particular for helping me out when I needed it amongst other things.
  • Every single other developer working on the Chromium projects, because none of this could happen without each and every one of you.
  • Users on the Google Groups for ChromiumOS/Chromium, many problems I’ve encountered have been resolved from very useful posts by the users there, my thanks go out to you all!
  • Donators who helped to pay for the VPS and who are ensuring I can continue to run it to provide you with fresh builds regularly. Big thank you to you guys, and everyone else, you should thank them too! They’re playing a big part in making this happen.
  • All the users who have supported me and send their thanks via Twitter/email, really, thankyou! Please, keep spreading the word as you’ve been doing so well so that more people can try out this fantastic OS and hopefully use it on their netbooks.

If you love what I’m doing (thanks! I enjoy doing it and I’ve met some fantastic people whilst working on it), and would like to help out, here are a few of the things you could do:

  • Work on the wiki! Editing a wiki is something anybody can do, you don’t need to have edited one before, it’s very intuitive and you can pretty much learn as you go along. If you’re still unsure, stick to the existing format and just add to the compatibility lists, for example.
  • Spread the word! Give your friends copies of the builds and point them to the site, let them try it out! If their hardware is incompatible, add details to the wiki, and you never know, I may be able to ship a fix in a future version!
  • Donate! Donations have paid for the server on which builds happen and much of the site runs on, and this project simply could not function without their support! Any amount is very much appreciated. :)
  • Share your ideas/suggestions for the project! While not everything is feasible for implementing, most ideas are and you may have thought of something I or somebody else didn’t!
  • Use the builds! This is by far and away the most important thing you can do to show your support. :)

To those who have tried to reach me via Twitter and haven’t gotten a reply, please, tweet at me again. I sometimes may miss a tweet by accident when I open my client and see many hundreds of new tweets. Please do check the wiki and FAQ first to see if your question is answered there. Many of the questions I am asked, are, and I’ll simply point people to the relevant page. Save me a little time by checking there first, please.

Any future updates to my Chromium OS builds will be found here first, and hopefully you can enjoy my comments/stories about how the project is getting on.


6 Comments for this entry

  • 如一

    Hello, I have a question, why do I figure out the hash value and you are not given the same? Only ChromeOS-Flow.tar.gz not the same as!!!!!!!!!!!!!!!!

  • tweet adder review

    Twitter is the best mini blogging website that have the potential to drive incredible volume of traffic to your website or business. Twitter can make your business go one step forward, because you can search and get connected to people across the world and build long term relationship.

  • tweet adder discount

    The purpose of Twitter is to receive and send short bursts of content from other Twitter users. Many use it only to interact socially, but Twitter is also becoming a essential tool for online marketing. 

  • chesse20

    this will be very helpfull

  • has_te

    Got the USB image unloaded.

    -NICE to find the F8 and keyboard commands page.

    -Initially got flummoxed by trying to transfer the image from a USB key to the SD, so if you get these error messages, just put the zip or extracted .img onto the main machine whatever it is…and
    the load works.

    -Found that Mepis will not get me the Image Writer but
    kUbuntu will.

    But that the .img write out is just a data dump..so that would be possible even if you couldn’t get the very nice Image Writer
    which is accessed from the command line as outlined by hexxeh instrux.
    I.e..”dd if=/home/username/Downloads/ChromeOS-Flow.img of=/dev/sdc”

    -Here’s the error messages (on an MSI Wind Atom2.0 barebone)
    “error message:
    Traceback (most recent call last): *On the terminal screen
    “File “/usr/lib/imagewriter/imagewriter.py”, line 112, in do_write
    self.raw_write(source, target

    “File “/usr/lib/imagewriter/imagewriter.py”, line 150, in raw_write
    src_size = float(data.stdout.readline().split()[4])*1.0
    IndexError: list index out of range”

    *Image writer readout…
    Image: /media/disk-1/ChromeOS-Flow pkg/ChromeOS-Flow.img
    Target Device: Generic- Multi-Card (/dev/sdc)
    Unmounting all partitions of /dev/sdc:
    Trying to unmount /dev/sdc1…
    /dev/sdc1 successfully unmounted”

    And then it just quits.
    Or maybe just my bad.

    -On this machine using an Adesso USB keyboard trackball combo
    the cursor will arrest after an operation, I’ve found that simply clicking any adjacent ‘non-alive’ key will get it going again.

    -Volume on streaming audio is at the lowest limits of audiability…
    maybe it’s set for phones? Dunno. Basically unhearable

    -And from the web learned that a terminal command
    #sudo shutdown -h now
    and
    password = punchface
    works.
    THAT was a conundrum, too, until…

    So thank you hexxeh, was nice to have had an experience with this still very choppy..but promising..OS

Leave a Reply