Language Selection

English French German Italian Portuguese Spanish

ChromeOS first impressions

Filed under
OS
Google

As with anything new coming from Google, there has been a lot of expectation regarding the new Google “operating system” for PCs based on the Chrome browser.

Truth is that, as the mobile-devices-oriented Android, ChromeOS can be hardly called an Operating system but rather a Linux distribution.

ChromeOS’s concept is simple; remove absolutely everything from GNU/Linux that is not essential for browsing the internet. That lets ChromeOS boot quickly, in about 10 seconds, a bit more time than of Moblin or the tuned-up version of Fedora by Intel. Google Chrome has still a lot of glitches, but I’m sure they will fix’em all in time for production.

As soon as we boot ChromeOS we are prompted not for a user on the computer but for our Google account and password. On log-on you are presented with your gmail and calendar in the Chrome browser/interface.

Rest Here




Also:

It's the morning after the big Chrome OS event where Google executives and engineers revealed a myriad of details about the company's first attempt at creating their own operating system. The highly anticipated news conference was tracked all over the web, liveblogged by technology sites, and Twittered so much that it's still listed as a "trending topic" as of this morning.

But now that the news is out, has Chrome OS lost its shine? People had high expectations for Google's new operating system but the end result doesn't look like the revolutionary, "change the world" product many had hoped for.

Rest of that here

And:

Google has prepared its Chromium OS, alias Chromium, for download. Anyone hesitant to intall if from source code will find a functioning VMware image from Linux Magazine Online.

And: Life with Chromium OS, good or tasteless!!

More in Tux Machines

A free culture event in Pakistan

digital materials freely online. With regards to the open source community in Pakistan, the situation is analogous to that on Wikipedia. Outside of a core group of members of Mozilla Pakistan and Linux Pakistan, the majority of internet users are not familiar with the free culture and open movements. This, in all likelihood, is due to a lack of widespread awareness of the movements. Even as Pakistan is experiencing a widespread internet penetration amongst the public, unfortunately the country has not yet adapted well to the ideas of free culture and open. Copyright protection in Pakistan is a critical issue and copyright infringement and online piracy has always been a concern. With Wikimedia Pakistan, we can help to raise awareness of the advantages and benefits of having open and free platforms, and the major role this could play in developing our market and economy. We all need to play our part in ensuring a bright future for the open and free internet. I think the success of the movement globally depends on participation of people from not only the developed countries but also from the Global South. Read more

Mesa 10.3 release candidate 2

Mesa 10.3 release candidate 2 is now available for testing. The current plan of record is to have an additional release candidate each Friday until the 10.3 release on Friday, September 12th. The tag in the GIT repository for Mesa 10.3-rc2 is 'mesa-10.3-rc2'. I have verified that the tag is in the correct place in the tree. Mesa 10.3 release candidate 2 is available for download at ftp://freedesktop.org/pub/mesa/10.3/ Read more

Linux 3.17-rc3

I'm back to the usual Sunday release schedule, and -rc3 is out there now. As expected, it is larger than rc2, since people are clearly getting back from their Kernel Summit travels etc. But happily, it's not *much* larger than rc2 was, and there's nothing particularly odd going on, so I'm going to just ignore the whole "it's summer" argument, and hope that things are just going that well. Please don't prove me wrong, Linus Read more

Revisiting How We Put Together Linux Systems

Traditional Linux distributions are built around packaging systems like RPM or dpkg, and an organization model where upstream developers and downstream packagers are relatively clearly separated: an upstream developer writes code, and puts it somewhere online, in a tarball. A packager than grabs it and turns it into RPMs/DEBs. The user then grabs these RPMs/DEBs and installs them locally on the system. For a variety of uses this is a fantastic scheme: users have a large selection of readily packaged software available, in mostly uniform packaging, from a single source they can trust. In this scheme the distribution vets all software it packages, and as long as the user trusts the distribution all should be good. The distribution takes the responsibility of ensuring the software is not malicious, of timely fixing security problems and helping the user if something is wrong. Read more