Apt-Get in Chorme OS

[Firerouge]

The copy of Chrome OS that comes on the CR-48 has no Apt-Get
installed. Is it at all possible to install this program into the OS
in developer mode without having to install a completely new copy of
the OS?

[Firerouge]

I have tried installing yum from source but make isn't installed. I
then tried installing make but I don't have build-essentials so I cant
make make (lol). I don't know how to install the build essentials
without a package manager or make installed. This is where I am
currently stuck.

[Jeff Rasmussen]

Chrome OS is intended to be a new thin client web operating system.  Neither the user or the system has the permissions necessary to install applications as we normally see it.  The only way to install applications is through the http://chrome.google.com/webstore although I believe that anyone can create their own webstore like creating your own marketplace on Android.

If you are missing applications on the CR-48 you have two choices.  Either create a new web application or you can download chromium OS and compile a specific application or driver.  Remember that if you compile apt-get into the system you still won't have permission to install from the repository unless you make significant changes.  You would be better off making Ubuntu duel boot.

Jeff Rasmussen

On Dec 12, 2010 2:55 AM, "Firerouge" <alexan...@gmail.com> wrote:

[Firerouge]

Thank you for the help, I feared that a simple solution of integrating
it might be impossible and that appears to be the case. As a side note
has this (http://www.chromium.org/chromium-os/how-tos-and-
troubleshooting/portage-build-faq) been removed from the build that is
on the CR-48 as it doesn't appear to work.

On Dec 12, 7:07 am, Jeff Rasmussen <jeff.rasmus...@gmail.com> wrote:
> Chrome OS is intended to be a new thin client web operating system.  Neither
> the user or the system has the permissions necessary to install applications

> as we normally see it.  The only way to install applications is through thehttp://chrome.google.com/webstorealthough I believe that anyone can create

> their own webstore like creating your own marketplace on Android.
>
> If you are missing applications on the CR-48 you have two choices.  Either
> create a new web application or you can download chromium OS and compile a
> specific application or driver.  Remember that if you compile apt-get into
> the system you still won't have permission to install from the repository
> unless you make significant changes.  You would be better off making Ubuntu
> duel boot.
>
> Jeff Rasmussen

> On Dec 12, 2010 2:55 AM, "Firerouge" <alexandera...@gmail.com> wrote:

[Rich]

Yes,

Chrome OS does not have any of the available developer tools
associated with Chromium OS, as the user shouldn't ever need access to
those anyway.

Really makes me wonder how difficult it would be to get Chromium OS
running on CR-48.

On Dec 13, 12:05 am, Firerouge <alexandera...@gmail.com> wrote:
> Thank you for the help, I feared that a simple solution of integrating
> it might be impossible and that appears to be the case. As a side note
> has this (http://www.chromium.org/chromium-os/how-tos-and-
> troubleshooting/portage-build-faq) been removed from the build that is
> on the CR-48 as it doesn't appear to work.
>
> On Dec 12, 7:07 am, Jeff Rasmussen <jeff.rasmus...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Chrome OS is intended to be a new thin client web operating system.  Neither
> > the user or the system has the permissions necessary to install applications

> > as we normally see it.  The only way to install applications is through thehttp://chrome.google.com/webstorealthoughI believe that anyone can create

[Rich]

Jeff,

Has anyone internally been able to get a Ubuntu dual boot to work?

I also wonder about getting busybox onto Chrome OS in the mean time.
I notice it is compiled in the Chromium OS source, however it is not
provided on Chrome OS. Is there a chance that a compatible busybox
for CR-48 can be provided for those that would like to use some of the
more basic linux commands like zip, more, and less?

Thanks

On Dec 12, 10:07 am, Jeff Rasmussen <jeff.rasmus...@gmail.com> wrote:
> Chrome OS is intended to be a new thin client web operating system.  Neither
> the user or the system has the permissions necessary to install applications

> as we normally see it.  The only way to install applications is through thehttp://chrome.google.com/webstorealthough I believe that anyone can create

> their own webstore like creating your own marketplace on Android.
>
> If you are missing applications on the CR-48 you have two choices.  Either
> create a new web application or you can download chromium OS and compile a
> specific application or driver.  Remember that if you compile apt-get into
> the system you still won't have permission to install from the repository
> unless you make significant changes.  You would be better off making Ubuntu
> duel boot.
>
> Jeff Rasmussen

> On Dec 12, 2010 2:55 AM, "Firerouge" <alexandera...@gmail.com> wrote:

[Gaurav Shah]

On Mon, Dec 13, 2010 at 7:53 AM, Rich <sci...@gmail.com> wrote:
> Jeff,
>
> Has anyone internally been able to get a Ubuntu dual boot to work?

Instructions for this just got posted today:

https://sites.google.com/a/chromium.org/dev/chromium-os/developer-information-for-chrome-os-devices/cr-48-chrome-notebook-developer-information/how-to-boot-ubuntu-on-a-cr-48

For getting Chromium OS on the Cr-48:

http://dev.chromium.org/chromium-os/developer-guide#TOC-Getting-your-image-running-on-a-Chr

> --
> Chromium OS discuss mailing list: chromium-...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en
>

--
-g

[Firerouge]

It seems odd that they include a developer mode switch but in the end
it really doesn't unlock that many dev features.... Maybe they can fix
this in later builds so we can have a bit more freedom when the switch
has been used without having to install an entirely different OS
first.

On Dec 13, 7:50 am, Rich <sci...@gmail.com> wrote:
> Yes,
>
> Chrome OS does not have any of the available developer tools
> associated with Chromium OS, as the user shouldn't ever need access to
> those anyway.
>
> Really makes me wonder how difficult it would be to get Chromium OS
> running on CR-48.
>
> On Dec 13, 12:05 am, Firerouge <alexandera...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Thank you for the help, I feared that a simple solution of integrating
> > it might be impossible and that appears to be the case. As a side note
> > has this (http://www.chromium.org/chromium-os/how-tos-and-
> > troubleshooting/portage-build-faq) been removed from the build that is
> > on the CR-48 as it doesn't appear to work.
>
> > On Dec 12, 7:07 am, Jeff Rasmussen <jeff.rasmus...@gmail.com> wrote:
>
> > > Chrome OS is intended to be a new thin client web operating system.  Neither
> > > the user or the system has the permissions necessary to install applications

> > > as we normally see it.  The only way to install applications is through thehttp://chrome.google.com/webstorealthoughIbelieve that anyone can create

[Chris Masone]

On Mon, Dec 13, 2010 at 9:26 PM, Firerouge <alexan...@gmail.com> wrote:

It seems odd that they include a developer mode switch but in the end
it really doesn't unlock that many dev features....

It unlocks a root shell, the ability to install arbitrary software, and the ability to wipe the machine and install the operating system of your choice.

 

Maybe they can fix
this in later builds so we can have a bit more freedom when the switch
has been used without having to install an entirely different OS
first.

You don't have to install a different OS first.  You just can't use debian or fedora tools to install software.  

 

[Firerouge]

Neither dpkg nor yum is installed so I am not sure what you mean by

debian or fedora tools to install software.

On Dec 14, 2:22 am, Chris Masone <cmas...@chromium.org> wrote

[Chris Masone]

On Tue, Dec 14, 2010 at 4:02 PM, Firerouge <alexan...@gmail.com> wrote:

Neither dpkg nor yum is installed so I am not sure what you mean by

debian or fedora tools to install software.

Or ubuntu, then.  Other people have been asking about installing yum, and I was conflating apt-get with debian tools, as they both use the .deb package format.  The point still stands that you can absolutely compile and install your own software.

 

On Dec 14, 2:22 am, Chris Masone <cmas...@chromium.org> wrote

> You don't have to install a different OS first.  You just can't use debian
> or fedora tools to install software.

[kindofabuzz]

apt-get is a Debian based tool. GoogleOS is not a Debian/Ubuntu based
"distro".

[Wei Hu]

On Dec 12, 10:07 am, Jeff Rasmussen <jeff.rasmus...@gmail.com> wrote:
> If you are missing applications on the CR-48 you have two choices.  Either
> create a new web application or you can download chromium OS and compile a
> specific application or driver.  Remember that if you compile apt-get into
> the system you still won't have permission to install from the repository
> unless you make significant changes.  You would be better off making Ubuntu
> duel boot.

If I understood correctly, it's because the current root fs is mounted
read-only, and the writable stateful partition is mounted non-
executable. Can we remove the restriction, or is it enforced by the
firmware that we cannot change?

[Randall Spangler]

It's just a kernel / mount table setting.

Once you've flipped the dev switch, you can just

sudo mount -o remount,rw /

sudo mount -o remount,exec /mnt/stateful_partition

Note that unless you've turned off rootfs verification, dm-verity will get upset with the now-changed rootfs partition.  To do that,

sudo /usr/share/vboot/bin/make_dev_ssd --remove_rootfs_verification

- Randall

[Wei Hu]

I got the following error when trying to remount / as rw:
mount: cannot remount block device /dev/ROOT read-write, is write-
protected.

The error persists after I removed the verification using the command
you gave.

On Dec 18, 1:12 pm, Randall Spangler <rspang...@chromium.org> wrote:

> > Chromium OS discuss mailing list: chromium-os-disc...@chromium.org

[Richard Barnette]

On Dec 18, 2010, at 11:57 AM, Wei Hu wrote:

> I got the following error when trying to remount / as rw:
> mount: cannot remount block device /dev/ROOT read-write, is write-
> protected.
>
> The error persists after I removed the verification using the command
> you gave.
>

That's expected. :-( One final required step Randall forgot to mention
is that you'll have to reboot before you can finally perform the
'remount' commands he cited.

Note that while the 'make_dev_ssd' command to remove verification is
a one-time step, you'll need to re-run the remount commands on
every reboot, if you want a read-write root file system.

Good Luck!

> Chromium OS discuss mailing list: chromium-...@chromium.org

> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?
> hl=en

-- jrb

[Wei Hu]

On Dec 18, 6:29 pm, Richard Barnette <jrbarne...@chromium.org> wrote:
> On Dec 18, 2010, at 11:57 AM, Wei Hu wrote:
>
> > I got the following error when trying to remount / as rw:
> > mount: cannot remount block device /dev/ROOT read-write, is write-
> > protected.
>
> > The error persists after I removed the verification using the command
> > you gave.
>
> That's expected.  :-(  One final required step Randall forgot to mention
> is that you'll have to reboot before you can finally perform the
> 'remount' commands he cited.
>
> Note that while the 'make_dev_ssd' command to remove verification is
> a one-time step, you'll need to re-run the remount commands on
> every reboot, if you want a read-write root file system.

Thanks! It worked like a charm!

In theory though, once I had read-write root fs, I could change the
configuration so that it's always mounted read-write, no?

I looked at the usual suspect /etc/fstab which doesn't seem like the
right file to edit.

[Richard Barnette]

On Dec 18, 2010, at 6:57 PM, Wei Hu wrote:
[ ... ]

>> That's expected. :-( One final required step Randall forgot to
>> mention
>> is that you'll have to reboot before you can finally perform the
>> 'remount' commands he cited.
>>
>> Note that while the 'make_dev_ssd' command to remove verification is
>> a one-time step, you'll need to re-run the remount commands on
>> every reboot, if you want a read-write root file system.
>
> Thanks! It worked like a charm!
>
> In theory though, once I had read-write root fs, I could change the
> configuration so that it's always mounted read-write, no?
>
> I looked at the usual suspect /etc/fstab which doesn't seem like the
> right file to edit.
>

Right, /etc/fstab is unused (and bogus) on Chrome OS. The root file
system options are specified on the kernel command line; I believe to
get a writable root by default you delete the "ro" option. I believe
you can edit the command line, but the exact procedure depends on the
kind of firmware you've got, and I don't know how to do this for a Cr48.

Hopefully, someone who knows more can pipe up with an answer.

[Wei Hu]

Interesting, my root fs seems to remain writable after reboot.

On Dec 19, 1:24 am, Richard Barnette <jrbarne...@chromium.org> wrote:
> On Dec 18, 2010, at 6:57 PM, Wei Hu wrote:
> [ ... ]
>
>
>
>
>
>
>
> >> That's expected.  :-(  One final required step Randall forgot to  
> >> mention
> >> is that you'll have to reboot before you can finally perform the
> >> 'remount' commands he cited.
>
> >> Note that while the 'make_dev_ssd' command to remove verification is
> >> a one-time step, you'll need to re-run the remount commands on
> >> every reboot, if you want a read-write root file system.
>
> > Thanks! It worked like a charm!
>
> > In theory though, once I had read-write root fs, I could change the
> > configuration so that it's always mounted read-write, no?
>
> > I looked at the usual suspect /etc/fstab which doesn't seem like the
> > right file to edit.
>
> Right, /etc/fstab is unused (and bogus) on Chrome OS.  The root file
> system options are specified on the kernel command line; I believe to
> get a writable root by default you delete the "ro" option.  I believe
> you can edit the command line, but the exact procedure depends on the
> kind of firmware you've got, and I don't know how to do this for a Cr48.
>
> Hopefully, someone who knows more can pipe up with an answer.
>
> > --

> > Chromium OS discuss mailing list: chromium-os-disc...@chromium.org

[Randall Spangler]

On Sat, Dec 18, 2010 at 10:24 PM, Richard Barnette <jrbar...@chromium.org> wrote:

On Dec 18, 2010, at 6:57 PM, Wei Hu wrote:
[ ... ]

That's expected.  :-(  One final required step Randall forgot to mention
is that you'll have to reboot before you can finally perform the
'remount' commands he cited.

Note that while the 'make_dev_ssd' command to remove verification is
a one-time step, you'll need to re-run the remount commands on
every reboot, if you want a read-write root file system.

Thanks! It worked like a charm!

In theory though, once I had read-write root fs, I could change the
configuration so that it's always mounted read-write, no?

I looked at the usual suspect /etc/fstab which doesn't seem like the
right file to edit.

Right, /etc/fstab is unused (and bogus) on Chrome OS.  The root file
system options are specified on the kernel command line; I believe to
get a writable root by default you delete the "ro" option.  I believe
you can edit the command line, but the exact procedure depends on the
kind of firmware you've got, and I don't know how to do this for a Cr48.

Hopefully, someone who knows more can pipe up with an answer.

The version of make_dev_ssd.sh in the repo has --save_config and --set_config options which allow editing the kernel command line.  Not sure if we've pushed it in an autoupdate yet.  If not, grab it from here:

http://git.chromium.org/gitweb/?p=vboot_reference.git;a=blob_plain;f=scripts/image_signing/make_dev_ssd.sh;hb=HEAD

(you may also need the current version of common.sh from that directory)

- Randall

[Ron Nnn]

You get make with chromebrew or you can use curl

Install Chromebrew: 

curl -Ls git.io/vddgY | bash