ChromeOS source code released (and binaries)

Timbauns · 2009-11-20 22:09:32

It is perfect for 98 % of contemporary people, be glad this makes archuser elitist

Anikom15 · 2009-11-20 23:15:04

It's the exact opposite of UNIX.

skottish · 2009-11-21 01:54:19

*** Was there some misunderstanding when I said to not turn this into a Google vs. privacy thread? Back on topic please. ***

flamelab · 2009-11-21 01:59:36

Ιn order to maintain what skottish says (and should be done): has anyone else tried any ChromeOS image yet ? I managed to create my own with the official guides and downloaded the one on thepiratebay (it's not illegal, it's free software, so you can download it freely) (I saw no difference since I built it without doing something different from what the guide told).

I saw that it's unusable for now. You see the chromium browser with clock, network options etc, but in the VM it was awfully slow, the VT1/7 didn't work (I hope that they didn't work because of a VM malfunction, not because they don't exist), the network barelly worked.

Ranguvar · 2009-11-21 03:08:31

flamelab wrote:

the VT1/7 didn't work (I hope that they didn't work because of a VM malfunction, not because they don't exist)

I heard on IRC that they were disabled

EDIT: http://cocaman.ch/wp/2009/11/virtual-te … chrome-os/

Last edited by Ranguvar (2009-11-21 03:09:04)

markc · 2009-11-21 03:40:51

Okay, so I'm dumb, what is the difference between...

http://build.chromium.org/buildbot/snap … -linux.zip
http://build.chromium.org/buildbot/snap … -linux.zip

they are both 21Mb zipfiles?

@flamelab: has anyone else tried any ChromeOS image yet ? I've got the torrented version running in virtualbox and it seems okay except the x86_64 vbox becomes disabled when it loses focus, but that's a vbox issue. I managed to create my own with the official guides... did you manage to script any of the procedure at all, like enough to start on a PKGBUILD?

Jimi · 2009-11-21 04:38:07

I was looking forward to maybe seeing a project like iron (chromium stripped of google tracking) out of ChromeOS, but I guess it's impossible since they wanted to make it cloud...

markc · 2009-11-21 04:47:39

@Jimi: give it time, it's only been released for 2 days. I suspect there will be a dozen entire alternate distros based on ChromeOS by the time it's officially released in 12 months.

Ranguvar · 2009-11-21 06:53:28

Jimi wrote:

I was looking forward to maybe seeing a project like iron (chromium stripped of google tracking) out of ChromeOS, but I guess it's impossible since they wanted to make it cloud...

Err?
Chrome doesn't run on the cloud, that's still a native app... Chrome is how you get to the Internet in ChromeOS in the first place.

And as much as I like Iron, let's please heed skottish's warning and really focus in on ChromeOS itself

flamelab · 2009-11-21 13:49:54

markc wrote:

Okay, so I'm dumb, what is the difference between...
http://build.chromium.org/buildbot/snap … -linux.zip
http://build.chromium.org/buildbot/snap … -linux.zip
they are both 21Mb zipfiles?
@flamelab: has anyone else tried any ChromeOS image yet ? I've got the torrented version running in virtualbox and it seems okay except the x86_64 vbox becomes disabled when it loses focus, but that's a vbox issue. I managed to create my own with the official guides... did you manage to script any of the procedure at all, like enough to start on a PKGBUILD?

Unfortunately, I can create only a script for which I can create a PKGBUILD, not a PKGBUILD for the creation of the image itself. I have started already. When I release this verbose script, I'd like some of your help fellow archers :p

Sakurina · 2009-11-21 16:24:38

Obi-Lan wrote:

I wonder if usb mass storage could be still used..

According to the product announcement from the other day, any USB mass storage device can be accessed from Chrome OS. (That said, files will open in the Web app capable of using such files; Excel files opened in Office Live for example.)

lman · 2009-11-21 19:21:51

markc wrote:

<opinion> Folks who don't like the idea of google keeping your private data can just use Chrome on their normal OS and lose no sweat. However, using Chrome OS and keeping a significant snapshot of the current state of the OS on the google cloud has a very practical benefit that "normal" OS users do not have access to and can't yet appreciate, and that is when you go to another machine, or buy a new one, almost the entire previous state of whatever you were doing gets downloaded to the new device. I don't know about some of you guys but I am absolutely sick of re-setting up my entire online life every time I move to a new system or re-install yet another OS. I'm happy to let google catalog my online settings if they are prepared to offer me the facility of automatically updating any extra other COS enabled computer I may use in the future. What I don't want them to know about won't be on a netbook that I could easily lose or get stolen anyway.

On that thought. I agree, I just wanted to add, that probably good part of your "private" data is in the "cloud" anyways if you use emial/facebook/twitter/forums etc. I think the security will be the main issue here for google. but still I think It's perfect for "normal" users... I'm still not sure what happens if you have no internet access, let's say you want to read a pdf on a train (to study for example), but with no hdd? Just for that carry a usb mass storage with you, hm....
Also if chrome OS is going to be a success, google is going to be reeaaally scary. More scary than microsoft... all that data in the hands of a single corporation

Randy Penguin · 2009-11-21 20:20:41

I'm still trying to answer a bunch of questions but this is what I have so far. Any comments?

pkgname=chromium-os-git
_pkgver=$(wget -qO - http://build.chromium.org/buildbot/continuous/linux/LATEST/REVISION)
pkgver=$_pkgver
pkgrel=1
pkgdesc="An open source operating system developed by Google."
arch=('i686')
url="http://www.chromium.org/chromium-os"
license=('GPL')
depends=('nss>=3.12' 'gconf' 'ffmpeg' 'freetype2' 'alsa-lib' 'cairo')
makedepends=('debootstrap' 'reprepro>=4.0.2' 'depot_tools-svn' 'python>=2.4' 'perl>=5' 'bison>=2.3' 'flex>=2.5.34' 'gperf>=3.0.3' 'pkgconfig>=0.20' 'alsa-lib' 'nspr>=4.7.1')
provides=('chromium-os')
md5sums=('')

  build() {
    diskspace=`df -m "${srcdir}" | awk 'END {print $4}'`
    if [ "$diskspace" -lt 10000 ]; then
      echo
      msg "The Chromium compilation can take up to 5GB of disk space--"
      msg "you only have ${diskspace}M free. Building anyway."
      echo
      sleep 1
    fi

    mkdir "${srcdir}/chromiumos" || return 1
    cd "${srcdir}/chromiumos"

    if [ ! -f .gclient ]; then
      msg "Configuring gclient..."
      gclient config http://src.chromium.org/git/chromiumos.git
    fi

    msg "Starting GIT pull..."

    gclient sync --force

    msg "GIT pull done or server timeout"
        
    mkdir -p "${srcdir}/chromiumos/chromiumos.git/src/build/x86/local_assets || return 1
    
    cd "${srcdir}/chromiumos/chromiumos.git/src/build/x86/local_assets

    msg "Downloading chromium snapshot..."    

    wget --no-cache -c http://build.chromium.org/buildbot/continuous/linux/LATEST/chrome-linux.zip || return 1

    mv chrome-linux.zip chrome-chromeos.zip || return 1

    cd "${srcdir}/chromiumos/chromiumos.git/src/scripts"

    msg "Creating package repo and setting up build environment..."

    ./make_chroot.sh --mirror=http://build.chromium.org/buildbot/packages --suite=chromeos_dev

    ./enter_chroot.sh ## This can be done in a fakeroot, right?
        
    msg "Set shared user password" ## Will makepkg pause for this? not tested
    
    ./set_shared_user_password.sh
    
     msg "Building platform packages..."  
        
    ./build_platform_packages.sh
    
    msg "Building kernel..."

    ./build_kernel.sh
    
    msg "Building image..."
    
    ./build_image.sh --mirror=http://build.chromium.org/buildbot/packages --suite=chromeos_dev

## Now what? Since this is not an installable program, would a PKGBUILD even be appropriate?
    
}

* Post install msg for .install file if appropriate *

pkgname=chromium-os-git

# arg 1:  the new package version
post_install() {
  echo "For instruction on using your newly built image, please refer to"
  echo "http://sites.google.com/a/chromium.org/dev/chromium-os/building-chromium-os/build-instructions#TOC-Using-your-image"
  echo ""
}

post_upgrade() {
  post_install $1
}

op=$1
shift
$op $*

Last edited by Randy Penguin (2009-11-22 06:15:19)

flamelab · 2009-11-21 20:30:47

It can't be a PKGBUILD. You can't install an OS with a package, like you wouldn't install Debian in a package. Move the commands into a standalone script like "make-chromeos-script" and create a PKGBUILD for it.

Randy Penguin · 2009-11-21 20:42:52

flamelab wrote:

It can't be a PKGBUILD. You can't install an OS with a package, like you wouldn't install Debian in a package. Move the commands into a standalone script like "make-chromeos-script" and create a PKGBUILD for it.

I was wondering if it could be done like the WebOS package that makes a virtualbox setup for you. You could use the image for a traditional install of course but that would not be the primary purpose of the PKGBUILD. Hence the reason for the message in the .install file. What do you think?

flamelab · 2009-11-21 20:53:34

Randy Penguin wrote:

flamelab wrote:
It can't be a PKGBUILD. You can't install an OS with a package, like you wouldn't install Debian in a package. Move the commands into a standalone script like "make-chromeos-script" and create a PKGBUILD for it.
I was wondering if it could be done like the WebOS package that makes a virtualbox setup for you. You could use the image for a traditional install of course but that would not be the primary purpose of the PKGBUILD. Hence the reason for the message in the .install file. What do you think?

Well, it's a different situation here, even though the result is a minimal system for use, since there are almost no programs preinstalled (all are web apps). I think that it shouldn't be an arch package, but a standalone script (or more scripts) that would allow customisation (ie kernel config customisation, do you remember the numerous scripts in the chromium-os untarred script directory ?). This way, it could be used in another distros as well, in order to create custom spins that could be usable in the future, with enabled VTs, better hardware support etc

Last edited by flamelab (2009-11-21 20:54:56)

Randy Penguin · 2009-11-21 21:01:04

flamelab wrote:

Randy Penguin wrote:
flamelab wrote:
It can't be a PKGBUILD. You can't install an OS with a package, like you wouldn't install Debian in a package. Move the commands into a standalone script like "make-chromeos-script" and create a PKGBUILD for it.
I was wondering if it could be done like the WebOS package that makes a virtualbox setup for you. You could use the image for a traditional install of course but that would not be the primary purpose of the PKGBUILD. Hence the reason for the message in the .install file. What do you think?
Well, it's a different situation here, even though the result is a minimal system for use, since there are almost no programs preinstalled (all are web apps). I think that it shouldn't be an arch package, but a standalone script (or more scripts) that would allow customisation (ie kernel config customisation, do you remember the numerous scripts in the chromium-os untarred script directory ?). This way, it could be used in another distros as well, in order to create custom spins that could be usable in the future, with enabled VTs, better hardware support etc

True. I see, though it would be great if you could simply run makepkg and get a new grub entry allowing you to boot into your new loop-backed Chromium OS. Or another version that does the virtualbox thing for testing purposes. Gosh I feel like a kid in a candy store! Lol, thanks for the input flame.

^_^

markc · 2009-11-24 23:50:40

Just have the pkg post install set it up in /home/chromeos and have a /usr/bin/chromeos startup script that fires up Xephyr first then does a chroot into /home/chromeos and starts up the browser (and whatever else) on DISPLAY=:1, then it'll run at native speed. If /home/chromeos happens to be a mounted partition then the user has the option of booting up into it as well. Install pacman -r /home/chromeos and other light apps like mrxvt, sylpheed. leafpad etc and run them from the terminal, until someone figures out how to link up Chromium to run native apps from it's gui (perhaps use a light webserver and php/perl/python to exec apps from an AJAX link, dunno as I haven't had a chance to try any of this yet).

wonder · 2009-11-28 04:41:43

this package is really needed? you guys are using it?

markc · 2009-11-28 05:54:10

Yes and yes. I have every intention of providing a single large chromeos tarball to start with and then eventually replace the individual deb packages with Archlinux equivs. I'll also provide x86_64 and ARM versions when that becomes possible. My build server is dead atm otherwise I'd probably have some kind of initial tarball available right now and would update it at least once a week, perhaps even on a daily basis once I get a feel for what involved.

cmlr · 2010-05-09 19:24:10

Here's a NY Times article
http://www.nytimes.com/2010/05/09/busin … ng.html?hp

A 17-year old from Manchester, UK, has put ChromeOS into a usable form. You can run it from a USB stick.
http://chromeos.hexxeh.net/

Misfit138 · 2010-05-09 23:28:30

cmlr wrote:

Here's a NY Times article
http://www.nytimes.com/2010/05/09/busin … ng.html?hp
A 17-year old from Manchester, UK, has put ChromeOS into a usable form. You can run it from a USB stick.
http://chromeos.hexxeh.net/

I'm glad someone is doing something with it; I have heard nothing about it for 8 months. Was starting to think of it as vaporware.

Arch Linux

#26 2009-11-20 22:09:32

Re: ChromeOS source code released (and binaries)

#27 2009-11-20 23:15:04

Re: ChromeOS source code released (and binaries)

#28 2009-11-21 01:54:19

Re: ChromeOS source code released (and binaries)

#29 2009-11-21 01:59:36

Re: ChromeOS source code released (and binaries)

#30 2009-11-21 03:08:31

Re: ChromeOS source code released (and binaries)

#31 2009-11-21 03:40:51

Re: ChromeOS source code released (and binaries)

#32 2009-11-21 04:38:07

Re: ChromeOS source code released (and binaries)

#33 2009-11-21 04:47:39

Re: ChromeOS source code released (and binaries)

#34 2009-11-21 06:53:28

Re: ChromeOS source code released (and binaries)

#35 2009-11-21 13:49:54

Re: ChromeOS source code released (and binaries)

#36 2009-11-21 16:24:38

Re: ChromeOS source code released (and binaries)

#37 2009-11-21 19:21:51

Re: ChromeOS source code released (and binaries)

#38 2009-11-21 20:20:41

Re: ChromeOS source code released (and binaries)

#39 2009-11-21 20:30:47

Re: ChromeOS source code released (and binaries)

#40 2009-11-21 20:42:52

Re: ChromeOS source code released (and binaries)

#41 2009-11-21 20:53:34

Re: ChromeOS source code released (and binaries)

#42 2009-11-21 21:01:04

Re: ChromeOS source code released (and binaries)

#43 2009-11-24 23:50:40

Re: ChromeOS source code released (and binaries)

#44 2009-11-28 04:41:43

Re: ChromeOS source code released (and binaries)

#45 2009-11-28 05:54:10

Re: ChromeOS source code released (and binaries)

#46 2010-05-09 19:24:10

Re: ChromeOS source code released (and binaries)

#47 2010-05-09 23:28:30

Re: ChromeOS source code released (and binaries)

Board footer