K. J.

INSTITUTE OF ENGINEERING AND TECHNOLOGY

SAVLI

DEPARTMENT OF COMPUTER ENGINEERING

CERTIFICATE
This is to certify that Mr.Joshi Darshan v And Rathod Jayraj G of BE
Computer, Roll No. 120640107043 and 120640107014, has successfully
completed seminar on Chrome operating system to my satisfaction and
submitted the same during the academic year 2013-2014 towards the partial
fulfillment of degree of Bachelor of Engineering under Gujarat Technological
University, under the Department of Computer Engineering , K. J. Institute of
Engineering and Technology, Savli.

Mr. Makwana Mahesh

Seminar Guide

Mr. Sohil Shah

HOD (Computer Department)

OPEN SOURCE SOFTWARE : GOOGLE CHROME

GROUP MEMBERS:
Darshan V. Joshi (120640107043)
Jayrajsinh G. Rathod (120640107014)

ACKNOWLEDGEMENT

I take this opportunity to express my profound gratitude and deep

regards to my guide (Professor/Mentor Faculty Name) for his
exemplary guidance, monitoring and constant encouragement
throughout the course of this thesis. The blessing, help and guidance
given by him time to time shall carry me a long way in the journey of
life on which I am about to embark.

I also take this opportunity to express a deep sense of gratitude to

Company Mentor Name, Designation, Company Name, for his/her
cordial support, valuable information and guidance, which helped me
in completing this task through various stages.

ABSTRACT

Google Chrome OS is an open source, lightweight operating

system that will initially be targeted at net books. It is designed by Google to work with
web applications and announced on July 7, 2009. Later this year we will open-source its
code, and net books running Google Chrome OS will be available for consumers in the
second half of 2010. It provides a fast, simple, and more secure computing experience for
people who spend most of their time on the web. Speed, simplicity and security are the
key aspects of Google Chrome OS. Google Chrome OS will run on both x86 as well as
ARM chips and we are working with multiple OEMs to bring a number of net books to
market next year.
The disadvantage of this method is that Chromium OS wont be
as fast as the operating system is designed to be, because its running in a virtual machine
in other words, you wont get to see Chrome OSs amazing boot time or snappy
responsiveness. The advantage of this method, however, is that your internet connection,
keyboard, and mouse will work whether or not theyre on Googles list of approved
hardware.

INDEX

branding, and most noticeably has a blue-colored logo in place of the multicolored
Google logo.

Table of contents

1. INTRODUCTION

2. HISTORY
2.1
2.2
3.

2.3.2
2.3.3
2.4
2.4.1
2.4.2

INTRODUCTION

Chrome OS is an operating system based on the Linux kernel and designed

by Google to work with web applications and installed applications. Initially, Chrome
OS was almost a pure web thin client operating system,with only a handful of
"native" applications, but Google gradually began encouraging developers to create
"packaged applications", some of which can work offline. In 2014, Google upgraded
its Play Store standards for packaged apps, requiring that these applications work
offline. Around the same time, Google also announced that Chrome OS would gain
the ability to run Android apps natively, by late 2014. In September 2014, App
Runtime for Chrome (beta) was launched together with four Android apps being able
to run on Chrome OS.
Chrome OS is built upon the open source project called Chromium OS which,
unlike Chrome OS, can be compiled from the downloaded source code. Chrome OS
is the commercial version installed on specific hardware from Google's
manufacturing partners. The launch date for retail hardware featuring Chrome OS
was delayed from late 2010 to June 15, 2011, when "Chromebooks" from Samsung,
and then Acer shipped in July

PURPOSE OF GOOGLE CHROME

Google Chrome is a web browser developed by Google that uses the WebKit layout
engine. It was first released as a beta version for Microsoft Windows on September
2, 2008, and the public stable release was on December 11, 2008. The name is
derived from the graphical user interface frame, or "chrome", of web browsers. As of
July 2011, Chrome was the third most widely used browser with 22.14%
worldwide usage share of web browsers, according to StatCounter.
In September 2008, Google released a large portion of Chrome's source code,
including its V8 JavaScript engine, as an open source project entitled Chromium.This
move enabled third-party developers to study the underlying source code and to help
port the browser to the Mac OS X and Linux operating systems. Google also
expressed hope that other browsers would adopt V8 to improve web application
performance.The Google-authored portion of Chromium is released under the
permissive BSD license, which allows portions to be incorporated into both open
source and closed source software programs.Other portions of the source code are
subject to a variety of open source licenses.Chromium implements a similar feature
set as Chrome, but lacks built-in automatic updates, built-in PDF reader and Google

History
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. 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 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 was under contract to contribute
engineering resources to the project with the intent to build on existing open source
components and tools where feasible.
By February 2010, Google switched its development Linux distribution for Chrome
from Ubuntu to Gentoo Linux in order to use that distribution's Portage package
management system, which, according to sources at Google, is used with "Google's
own take on the vanilla Linux kernel".

Hardware
Main articles:
Chromebook and Chromebox

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. A year later, in May 2012, a desktop design marketed as a "chromebox"
was released by Samsung.

Feature updates
In April 2012, Google made the first update to Chrome OS's user interface since the
operating system had launched, introducing a hardware-accelerated window
manager called "Aura" along with a conventional taskbar. The additions marked a
departure from the operating system's original concept of a single browser with tabs
and gave Chrome OS the look and feel of a more conventional desktop operating
system. "In a way, this almost feels as if Google is admitting defeat here", wrote
Frederic Lardinois on TechCrunch. He argued that Google had traded its original
version of simplicity for greater functionality. "Thats not necessarily a bad thing,
though, and may just help Chrome OS gain more mainstream acceptance as new
users will surely find it to be a more familiar experience."

Applications
Google has encouraged developers to build not just conventional Web
applications for Chrome OS, but packaged applications using the company's
Package App Platform. Packaged apps are modified Web applications written
in HTML5, JavaScript, and CSS. They have the look and feel of traditional
"native" applications and lack the address bar, tab strip and other elements
typically associated with an application that runs on a browser. Packaged apps
load locally and are thus less dependent on the network and more apt to remain
functional without an Internet connection.
Support for running native Android applications on Chrome OS was announced
at Google I/O 2014.

Remote application access and virtual desktop access

In June 2010, Google software engineer Gary Kamark 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.

Integrated media player, file manager

Google integrates a media player into both Chrome OS and the Chrome browser,
enabling users to play back MP3s, view JPEGs, and handle other multimedia
files while offline. It supports DRM videos.
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.

Support for Android applications

At Google I/O 2014, a proof of concept showing Android apps,

including Flipboard, running on Chrome OS was presented. In September 2014,
Google introduced a beta version of the App Runtime for Chrome (ARC), which
allows Android applications to be used on Chrome OS, using a Native Clientbased environment that provides the platforms necessary to run Android
software. Android apps do not require any modifications to run on Chrome OS,
but may be modified to better support a mouse and keyboard environment. As
with other Chrome OS software, these apps are distributed through Chrome Web
Store, and appear as native programs within application menus. As of its
introduction, Chrome OS support is only available for selected Android apps,
including Duolingo, Evernote, Sight Words, and Vine. Google stated that it was
working with selected Android developers to add more supported apps to ARC
over the coming months.

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 applicationsthe 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 lowend 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 successful introduction of the popular Android and Chrome OS strategy
has resulted in some critics of the dual open source, client-based operating
systems.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 OSes 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.
The July 2013 press introduction of the Chromecast HDMI stick, which was
hosted by Pichai, demonstrated how the two operating systems could work in
tandem. The Chromecast device has a cut-down embedded version of Android,
which users control using a smartphone or tablet running Android (or
Apple's iOS or a PC running the Chrome browser). Gigaom reporter Kevin C.
Tofel described the relationship as "a merger of experiences and services", a
strategy that "fits with Google's overall theme of increasing user engagement in
its ecosystem with Chrome as the underlying platform.
The relationship between Android and Chrome OS became more substantial at
Google I/O 2014, where Google developers presented a demo depicting native
Android software running on Chrome OS through Native Client.

Design
Early in the project, Google put online many details of Chrome OS's design goals
and direction. However, the company has not followed up with a technical
description of the completed operating system.

User interface
Design goals for 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. 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".

Architecture
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 byUpstart, 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.

Hardware support
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 ARMbased 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
Chrome OS claimed that the Chrome OS consumes one-sixtieth as much drive
space as Windows 7.

Printing
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.

Security
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

Use of sandbox

sandbox is a security mechanism for separating running programs. It is often used to

execute untested code, or untrusted programs from unverified third parties,
suppliers, untrusted users and untrusted websites.
The sandbox typically provides a tightly controlled set of resources for guest
programs to run in, such as scratch space on disk and memory. Network access, the
ability to inspect the host system or read from input devices are usually disallowed or
heavily restricted. In this sense, sandboxes are a specific example of virtualization.
Sandboxing technology is frequently used to test unverified programs which may
contain a virus or other malignant code, without allowing the software to harm the
host device
A sandbox is implemented by executing the software in a restricted operating
system environment, thus controlling the resources
.

Shell access
Chrome OS includes the Chrome Shell, or "crosh", which documents minimal
functionality such as ping and SSH at crosh start-up. In the older Chrome OS
versions originally in Acer C710 no Bash-like shell abilities were provided. In the
newer Chromebooks such as Acer C720 bash is available from crosh, where the
entire Linux filesystem can be found and explored.
In developer mode, a full-featured Bash shell can be opened via VT-2, and is also
accessible via the crosh command shell . To access full privileges in shell

(e.g. sudo) theroot password is required; it is "chronos" in Chrome OS and

"facepunch" in Chrome OS Vanilla.

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 is updated with features and fixes that have been
thoroughly tested in the Beta channel, and the Beta channel is updated
approximately once a month with stable and complete features from the
Developer channel. New ideas get tested in the Developer channel, which can be
very unstable at times.
A fourth canary channel was confirmed to exist by Google Developer
Francois Beaufort and hacker Kenny Strawn, by entering the chrome os shell in
developer mode, typing the command shell to access the bash shell, and finally
entering the command update_engine_client -channel canary-channel -update. It
is possible to return to verified boot mode after entering the canary channel, but
the channel updater disappears and the only way to return to another channel is
via a powerwash.

Chrome OS on Windows 8
On Windows 8, exceptions allow the default desktop web browser to offer a
variant that can run inside its full-screen "Metro" shell and access features such
as the Share charm, without necessarily needing to be written with Windows
Runtime. Chrome's "Windows 8 mode" was previously a tablet-optimized version
of the standard Chrome interface. However, in October 2013, the mode was
changed on Dev channel to offer a variant of the Chrome OS desktop.

Google Chrome (BETA) for Window:

Google Chrome is a browser that combines a minimal design with sophisticated
technology to make the web faster, safer, and easier.

- One box for everything:

Type in the address bar and get suggestions
for both search and web pages.
- Thumbnails of your top sites:
Access your favorite pages instantly with
lightning speed from any new tab.
- Shortcuts for your apps:
Get desktop shortcuts to launch
your favorite web applications.

New Tab Page:

Every time you open a new tab, you'll see a visual sampling of your most
visited sites, most used search engines, and recently bookmarked pages and closed
tabs.

Application Shortcuts:
Use web apps without opening your browser. Application shortcuts can
directly load your favorite online apps.

Dynamic Tabs:
You can drag tabs out of the browser to create new windows, gather multiple
tabs into one window or arrange your tabs however you wish -- quickly and easily.

Cash Control:
Every tab you're using is run independently in the browser, so if one app
crashes it won't take anything else down.

Incognito Mode:
Don't want pages you visit to show up in your web history? Choose incognito
mode for private browsing.

Intelligent start page:

Although
not
completely
original (Opera has got a similar
approach to quick bookmarking),

Chromes start page is a pleasant surprise. Besides the ubiquitous search bar, it gives
you a list of most commonly visited Web pages to fire up quickly.

Safe Browsing:
Google Chrome warns you if you're about to visit a suspected phishing,
malware or otherwise unsafe website.

Dragging tabs out and back in again:

You can drag a tab out of Chrome
into a separate window, and you can drag a
separate window back into tab bar, where
itll be happily received by Chrome. Stuff like
this turns geeks into converts, and Googles
dev team knows that.

Instant Bookmarking:
Want to bookmark a web page? Just click the star icon at the left edge of the
address bar and you're done.

Importing Setting:
When you switch to Google Chrome, you can pick up where you left off with
all the bookmarks and passwords from your existing browser.

Simpler download:
No intrusive download manager; you see your download's status at the
bottom of your current window.

CONCLUSION

So, the chrome OS emerged as a Revolutionary open source system

Software with lot of user-friendly features

REFERENCES

http://www.google.com/googlebooks/chrome/med_00.html

http://googleblog.blogspot.in/2009/07/introducing-google-chrome-os.html

http://en.wikipedia.org/wiki/Google_chrome

https://www.google.com/intl/en/chrome/browser