Google Chrome OS
Google Chrome OS displaying the app drawer and Chrome browser.
|Company / developer||Google Inc.|
|Programmed in||C, C++|
|Working state||Preinstalled on specific hardware (Chromebooks, Chromeboxes)|
|Latest stable release||26.0.1410.57 (Platform version: 3701.81.2) (April 11, 2013[±])|
|Latest unstable release||28.0.1500.11 (Platform versions: 4100.7.0) (May 14, 2013[±])|
|Update method||Rolling release|
|Supported platforms||x86, ARM|
|Kernel type||Monolithic: Linux kernel|
|Default user interface||Graphical interface based on the Google Chrome browser|
|License||Google Chrome OS Terms of Service|
Google Chrome OS is a Linux-based operating system designed by Google to work exclusively with web applications. Google announced the operating system on July 7, 2009 and made it an open source project, called Chromium OS, in November 2009.
Unlike Chromium OS, which can be compiled from the downloaded source code, Chrome OS only ships on specific hardware from Google's manufacturing partners. The user interface takes a minimalist approach, resembling that of the Google Chrome web browser. Because Google Chrome OS is aimed at users who spend most of their computer time on the Web, the only application on the device is a browser incorporating a media player and a file manager.
The launch date for retail hardware featuring Chrome OS slipped after Google first announced the operating system: from an initial forecast date in late 2010 to June 15, 2011, when "Chromebooks" from Samsung (and then Acer in July) actually shipped.
Chrome OS's origins are unclear. Jeff Nelson, a former Google engineer, claimed to have developed the original technology, code named "Google OS", described as "a webapp-centric chopped-down Linux with a Chrome browser front-end". As proof, Nelson cited a patent filed by Google in March 2009, listing Nelson as the inventor, entitled "Network-based Operating System Across Devices". In a discussion on Google+ in February 2013, Nelson wrote that by the end of 2007, after a series of meetings, he and a product manager had convinced "management to launch the Chrome OS project and assign head count". But other Google employees disputed his claim, including Antoine Labour, one of the three original engineers on the Chrome OS project. Labour wrote in the February 2013 Google+ discussion that he had never heard of Nelson, and that Nelson's work on a Linux distribution "based on the concept of running off of a ram disk" has "pretty much nothing to do with Chrome OS." A ZDNet article by Steven J. Vaughan-Nichols published in March 2013 also cast doubt on Nelson's claim, quoting an unnamed source at Google as saying that Nelson "was not involved with the Chrome OS project at any point of time nor was Chrome OS inspired by his work." According to Vaughan-Nichols, Chrome OS "seems to have started with Ubuntu Linux".
Google announced Chrome OS on July 7, 2009,describing it as an operating system in which both applications and user data reside in the cloud. The concept was new enough to confuse users and analysts, as well as Google co-founder Sergey Brin, who didn't at first realize his data did not reside on his personal computer, but could be accessed from any machine running the operating system. To ascertain marketing requirements, the company relied on informal metrics, including monitoring the usage patterns of some 200 Chrome OS machines used by Google employees. Developers also noted their own usage patterns. Matthew Papakipos, former engineering director for the Chrome OS project, put three machines in his house and found himself logging in for brief sessions: to make a single search query or send a short email.
On November 19, 2009, Google released Chrome OS's source code as the Chromium OS project. As with other open source projects, developers can modify the code from Chromium OS and build their own versions, whereas Google Chrome OS code is only supported by Google and its partners and only runs on hardware designed for the purpose. Unlike Chromium OS, Chrome OS is automatically updated to the latest version.
At a November 19, 2009 news conference, Sundar Pichai, the Google vice president overseeing Chrome, demonstrated an early version of the operating system. He previewed a desktop which looked very similar to the Chrome browser, and in addition to the regular browser tabs also had application tabs, which take less space and can be pinned for easier access. At the conference, the operating system booted up in seven seconds, a time Google said it would work to reduce.
Also on November 19, 2009, Chris Kenyon, vice president of OEM services at Canonical Ltd announced that Canonical "is contributing engineering to Google [Chrome OS] under contract. In our discussions, Sundar Pichai and Linus Upson made it clear that they want, wherever feasible, to build on existing components and tools from the open source community without unnecessary re-invention. This clear focus should benefit a wide variety of existing projects and we welcome it."
By February 2010, Google switched to Gentoo Linux in order to use that distribution's Portage package management system. But while Portage is still used, sources at Google stated that "today's Chrome OS is based on Google's own take on the vanilla Linux kernel".
Version History 
Laptops running Chrome OS are known collectively as "Chromebooks". The first was the Cr-48, a reference hardware design that Google gave to testers and reviewers beginning in December 2010. Retail machines followed in May 2011, including a desktop design known as a Chromebox.
Preliminary reception 
At its debut, Chrome OS was viewed as a competitor to Microsoft, both directly to Microsoft Windows and indirectly the company's word processing and spreadsheet applications—the latter through Chrome OS's reliance on cloud computing. But Chrome OS engineering director Matthew Papakipos argued that the two operating systems would not fully overlap in functionality because Chrome OS is intended for netbooks, which lack the computational power to run a resource-intensive program like Adobe Photoshop.
Some observers claimed that other operating systems already filled the niche that Chrome OS was aiming for, with the added advantage of supporting native applications in addition to a browser. Tony Bradley of PC World wrote in November 2009:
We can already do most, if not all, of what Chrome OS promises to deliver. Using a Windows 7 or Linux-based netbook, users can simply not install anything but a web browser and connect to the vast array of Google products and other web-based services and applications. Netbooks have been successful at capturing the low-end PC market, and they provide a web-centric computing experience today. I am not sure why we should get excited that a year from now we'll be able to do the same thing, but locked into doing it from the fourth-place web browser.
Relationship to Android 
Google's successive introductions of the popular Android and Google Chrome OS have put the company behind two open source, client-based operating systems. The dual-OS strategy drew some critics. Microsoft CEO Steve Ballmer accused Google of not being able to make up its mind. Steven Levy wrote that "the dissonance between the two systems was apparent" at the 2011 Google I/O developer conference. The event featured a daily press conference in which each team leader, Android's Andy Rubin and Chrome's Sundar Pichai, "unconvincingly tried to explain why the systems weren't competitive." Google co-founder Sergey Brin addressed the question by saying that owning two promising OS's was "a problem that most companies would love to face". Brin suggested that the two operating systems "will likely converge over time." The speculation over convergence increased in March 2013 when Chrome OS chief Pichai replaced Rubin as the senior vice president in charge of Android, thereby putting Pichai in charge of both.
Early in the project, Google put online many details of Chrome OS's design goals and direction. But the company has not followed up with a technical description of the completed operating system.
User interface 
Design goals for Google Chrome OS's user interface included using minimal screen space by combining applications and standard Web pages into a single tab strip, rather than separating the two. Designers considered a reduced window management scheme that would operate only in full-screen mode. Secondary tasks would be handled with "panels": floating windows that dock to the bottom of the screen for tasks like chat and music players. Split screens were also under consideration for viewing two pieces of content side-by-side. Google Chrome OS would follow the Chrome browser's practice of leveraging HTML5's offline modes, background processing, and notifications. Designers proposed using search and pinned tabs as a way to quickly locate and access applications.
New window manager and graphics engine 
On April 10, 2012, a new build of Chrome OS offered a choice between the original full-screen window interface and overlapping, re-sizable windows, such as found on Microsoft Windows and Apple's Mac OS X. The feature was implemented through the Ash window manager, which runs atop the Aura hardware-accelerated graphics engine. The April 2012 upgrade also included the ability to display smaller, overlapping browser windows, each with its own translucent tabs, browser tabs that can be "torn" and dragged to new positions or merged with another tab strip, and a mouse-enabled shortcut list across the bottom of the screen. One icon on the task bar shows a list of installed apps and bookmarks. Writing in CNET, Stephen Shankland argued that with overlapping windows, "Google is anchoring itself into the past" as both iOS and Microsoft's Metro interface are largely or entirely full-screen. Even so, "Chrome OS already is different enough that it's best to preserve any familiarity that can be preserved".
In preliminary design documents for the Chromium OS open source project, Google described a three-tier architecture: firmware, browser and window manager, and system-level software and userland services.
- The firmware contributes to fast boot time by not probing for hardware, such as floppy disk drives, that are no longer common on computers, especially netbooks. The firmware also contributes to security by verifying each step in the boot process and incorporating system recovery.
- System-level software includes the Linux kernel that has been patched to improve boot performance. Userland software has been trimmed to essentials, with management by Upstart, which can launch services in parallel, re-spawn crashed jobs, and defer services in the interest of faster booting.
- The window manager handles user interaction with multiple client windows much like other X window managers.
Remote application access and virtual desktop access 
In June 2010, Google software engineer Gary Kačmarčík wrote that Chrome OS will access remote applications through a technology unofficially called "Chromoting", which would resemble Microsoft's Remote Desktop Connection. The name has since been changed to "Chrome Remote Desktop", and is "probably closer to running an application via Remote Desktop Services or by first connecting to a host machine by using RDP or VNC". Initial roll-outs of Chrome-OS laptops (Chromebooks) indicate an interest in enabling users to access virtual desktops.
Hardware support 
Google Chrome OS is initially intended for secondary devices like netbooks, not as a user's primary PC, and will run on hardware incorporating an x86 or ARM-based processor. While Chrome OS will support hard disk drives, Google has requested that its hardware partners use solid-state drives "for performance and reliability reasons" as well as the lower capacity requirements inherent in an operating system that accesses applications and most user data on remote servers. In November 2009 Matthew Papakipos, engineering director for the Google Chrome OS claimed that the Chrome OS consumes one-sixtieth as much drive space as Windows 7.
Integrated media player, file manager 
Chrome OS also includes an integrated file manager resembling those found on other operating systems, with the ability to display folders and their associated files, as well as preview and manage file contents using a variety of Web applications, including Google Docs and Box.net.
Google Cloud Print is a Google service that helps any application on any device to print on any printer. While the cloud provides virtually any connected device with information access, the task of "developing and maintaining print subsystems for every combination of hardware and operating system – from desktops to netbooks to mobile devices – simply isn't feasible." However, the cloud service would entail installing a piece of software, called a proxy, as part of Chrome OS. The proxy would register the printer with the service, manage the print jobs, provide the printer driver functionality, and give status alerts for each job.
Link handling 
Chrome OS was designed with the intention of having user documents and files stored on online servers. However, both Chrome OS and the Chrome browser have unresolved decisions regarding handling specific file types offline. For example, if a JPEG is opened from a local storage device, should a specific Web application be automatically opened to view it, and if so, which one? Similarly, if a user clicks on a .doc file, which website should open: Microsoft Office Live, Gview, or a previewing utility? The project director at that time, Matthew Papakipos, noted that Windows developers have faced the same fundamental problem: "Quicktime is fighting with Windows Media Player, which is fighting with Chrome." As the number of Web applications increases, the same problem arises.
In March 2010, Google software security engineer Will Drewry discussed Chrome OS security. Drewry described Chrome OS as a "hardened" operating system featuring auto-updating and sandbox features that will reduce malware exposure. He said that Chrome OS netbooks will be shipped with Trusted Platform Module (TPM), and include both a "trusted bootpath" and a physical switch under the battery compartment that actuates a developer mode. That mode drops some specialized security functions but increases developer flexibility. Drewry also emphasized that the open source nature of the operating system will contribute greatly to its security by allowing constant developer feedback.
At a December 2010 press conference, Google claimed that Chrome OS would be the most secure consumer operating system due in part to a verified boot ability, in which the initial boot code, stored in read-only memory, checks for system compromises.
Shell access 
Chrome OS includes the Chrome Shell, or "crosh", which offers minimal functionality such as ping and SSH, but no Bash-like shell abilities. In developer mode, a full-featured Bash shell can be opened via VT-2, and is also accessible via the crosh command "shell".
Release channels and updates 
Chrome OS uses the same release system as Google Chrome: there are three distinct channels: Stable, Beta, and Developer preview (called the "Dev" channel). The stable channel will be updated with features and fixes once they have been thoroughly tested in the Beta channel, and the Beta channel will be updated roughly monthly with stable and complete features from the Developer channel. The Developer channel is where ideas get tested (and sometimes fail) and can be very unstable at times. In 2013 Google introduced an even less stable, fourth channel: the "Canary" release; the name refers to using canaries in coal mines, so if a change "kills" Chrome OS Canary, they will block it from the developer build (it existed in Chrome before).
See also 
- "Kernel Design: Background, Upgrades". Google. Retrieved September 7, 2011.
- Google. "Google Chrome OS Terms of Service". Retrieved September 5, 2012.
- Mediati, Nick (July 7, 2009). "Google Announces Chrome OS". PC World. Retrieved July 8, 2009.
- Sengupta, Caesar (November 19, 2009). "Releasing the Chromium OS open source project". Official Google Blog. Google, Inc. Retrieved November 19, 2009.
- Dylan F. Tweney (November 19, 2009). "Gadget Lab Hardware News and Reviews Google Chrome OS: Ditch Your Hard Drives, the Future Is the Web". Wired. Retrieved November 22, 2009.
- Stokes, Jon (January 19, 2010). "Google talks Chrome OS, HTML5, and the future of software". Ars Technica. Retrieved January 23, 2010.
- Womack, Brian (July 8, 2009). "Google to Challenge Microsoft With Operating System". Bloomberg. Retrieved July 8, 2009.
- Hansell, Saul (July 8, 2009). "Would you miss Windows with a Google operating system?". New York Times. Retrieved July 8, 2009.
- Pichai, Sundar (July 7, 2009). "Introducing the Google Chrome OS". Official Google Blog. Google, Inc. Retrieved July 11, 2012.
- "Google sets "late fall" release for Chrome". Reuters. June 2, 2010.
- Ahmed, Murad (July 8, 2009). "Google takes on Microsoft with Chrome operating system". The Times (UK). Retrieved July 8, 2009.
- Boulton, Clint (November 2010). "Google CEO Schmidt on Google TV, Chrome OS, NFC Chip". Google Watch. Retrieved November 19, 2010.
- Paul, Ryan (December 2010). "Google demos Chrome OS, launches pilot program". Ars Technica. Retrieved December 8, 2010.
- Sherr, Ian (May 11, 2011). "Google to launch Chrome Laptops in June". Wall Street Journal. Retrieved May 11, 2011.
- Nelson, Jeff (13 November 2012). "Inventing Chromebook". Retrieved 13 November 2012.
- US patent 8239662
- Kasting, Peter (13 February 2013). "Some people today are linking to Xoogler Jeff Nelson". Retrieved 13 February 2013.
- Vaughan-Nichols, Steven J. (March 6, 2013). "The secret origins of Google's Chrome OS". ZDNet. Retrieved 6 March 2013.
- Miller, Clair Cain (November 24, 2010). "For Google, the Browser Does It All". New York Times. Retrieved 14 February 2013.
- Brodkin, Jon (June 28, 2010). "Google Chrome OS creator takes job at Facebook, announces switch on Twitter". Business Week. Retrieved June 29, 2010.
- "Developer FAQ". Google. Retrieved December 12, 2009.
- "Linux commands". The New York Times.
- Yegulalp, Serdar (December 5, 2009). "Google Chrome OS Previewed". InformationWeek. Retrieved December 6, 2009.
- Rapoza, Jim (December 3, 2009). "REVIEW: Google Chrome OS Developer Edition Provides Intriguing Look at Web-Only Computing". eWeek.com. Retrieved December 4, 2009.
- Kenyon, Chris (November 2009). "Google Chrome OS and Canonical". Canonical Blog. Retrieved December 14, 2010.
- Keegan, Victor (July 10, 2009). "Can Chrome steal Microsoft's shine?". The Guardian (UK). Retrieved July 11, 2009.
- Bertolucci, Jeff (July 10, 2009). "Google, Microsoft Invade Enemy Territory: Who Wins?". PC World. Retrieved July 11, 2009.
- Bradley, Tony (April 2010). "Five Reasons the Google Chrome OS will Flop". Retrieved April 21, 2010.
- Dignan, Larry (November 23, 2009). "Admob: Droid and Android army make big browsing splash". ZDNet. Retrieved December 1, 2009.
- Patel, Nilay (July 14, 2009). "Steve Ballmer calls Chrome OS "highly interesting," says Google "can't make up their mind"". AOL (Engadget). Retrieved November 28, 2009.
- Levy, Steven (June 7, 2011). "Jobs to PC: 'You're Busted!' And Other Notes From The OS Wars". Wired. Retrieved June 7, 2011.
- Krazit, Tom (November 20, 2009). "Brin: Google's OSes likely to converge". CNET News. Retrieved November 28, 2009.
- Olivarez-Giles, Nathan (March 13, 2013). "Google Replaces Android Boss Andy Rubin With Chrome’s Sundar Pichai". Wired. Retrieved 13 March 2013.
- "The Chromium Projects: Chrome OS". Retrieved July 2, 2011.
- "The Chromium Projects: User Experience". Google. Retrieved November 21, 2009.
- Stephen Shankland (April 10, 2012). "Google gives Chrome OS a less alienating interface". CNET.
- Caleb Garling (April 10, 2012). "Google Chrome OS Busts Out Of Browser With New Interface". Wired.
- Paul, Ryan (April 16, 2012). "Hands-on: getting work done with Google's new Aura interface for Chrome OS". Ars Technica. Retrieved April 17, 2012.
- "Security Overview: Chromium OS design documents". Google. Retrieved November 25, 2009.
- Metz, Cade (June 9, 2010). "Google morphs Chrome OS into netbook thin client". The Register. Retrieved June 14, 2010.
- Mathews, Lee (August 13, 2010). "Google Chrome's Remoting feature shows up in Chromium with enterprise implications". Retrieved August 22, 2010.
- Claburn, Thomas. "Google Pleased With Chromebook Sales". InformationWeek.
- Thibodeau, Patrick. "Orlando tries out 600 Chromebooks, The Chrome OS-based laptops may fit into city's cloud strategy". Computerworld.
- Mearian, Lucas (November 19, 2009). "Google Chrome OS will not support hard-disk drives". Computerworld. Retrieved November 21, 2009.
- Rosenblatt, Seth (August 10, 1011). "Chrome OS goes offline, gets file manager". CNET download.com. Retrieved August 11, 2011.
- Jazayeri, Mike (April 15, 2010). "A New Approach to Printing". The Chromium Blog. Google Inc. Retrieved April 16, 2010.
- Heater, Brian (April 16, 2010). "Google Talks Cloud-Based Printing for Chrome OS". App Scout. Retrieved April 16, 2010.
- Whitney, Lance. "Google moving closer to Chrome OS printing". CNET News. Retrieved April 17, 2010.
- Messmer, Ellen (March 2010). "Google sheds light on Chrome OS Netbook security". Retrieved March 8, 2010.
- "Poking around your Chrome OS Notebook". The Chromium Projects. Retrieved February 6, 2011.
- Mark Larson (January 8, 2009). "Google Chrome Release Channels". Retrieved January 9, 2009.
- Mark Larson (January 8, 2009). "Dev update: New WebKit version, new features, and a new Dev channel". Retrieved January 9, 2009.
- Commit: Add extra appids to support changing from/to canary-channels.
- Chrome Story: Chrome OS is Getting Canary Channel for Experimental Features
|Wikimedia Commons has media related to: Chrome OS|
- Release blog
- Google Chrome official blog
- Chromium OS project page
- What is Google Chrome OS? on YouTube
- Official announcement
- Google Chrome OS Live Webcast; November 19, 2009