Permission Denied when entering chroot for ChromiumOS SDK on Chrome OS

684 views
Skip to first unread message

James Costello

unread,
Jul 30, 2012, 11:50:43 AM7/30/12
to chromium-...@chromium.org
I'm attempting to install the ChromiumOS SDK on as a standalone SDK on Chrome OS  on a CR-48.The CR-48 is in developer mode, I removed rootfs verification, and downloaded and unzipped the SDK using the instructions from http://www.chromium.org/chromium-os/developer-guide/using-sdk-standalone

However, when I attempt to enter chroot, I get a permission denied error:
localhost sdk # sudo chroot . /bin/bashchroot: failed to run command `/bin/bash': Permission denied

Mike Frysinger

unread,
Jul 30, 2012, 11:55:58 AM7/30/12
to jamesc...@gmail.com, chromium-...@chromium.org
a few things ...
- the cros_sdk is designed to not be run as root ... we never test it
being executed as root (and i think we'll probably add a check to make
sure it isn't run as root)
- the CR-48 is a pretty slow machine ... are you sure you really want
to build packages on the device itself ?
- the CR-48 doesn't have a very big disk, and the sdk will take up
quite a lot of gigs for the source/build/etc...
- i'm not sure if the ChromiumOS kernel (build & runtime env) are
configured in such a way to even allow what you're trying to do

i really think you should do this on a better machine, and one with a
more developer friendly kernel running. otherwise, i think you might
be on your own here.
-mike

James Costello

unread,
Jul 30, 2012, 12:10:00 PM7/30/12
to chromium-...@chromium.org, jamesc...@gmail.com
Thanks Mike.

From the standalone instructions, it sounded as if executing the SDK as root was OK:
2. Unzipping, entering SDK
...
Enter by using chroot:
  sudo chroot . /bin/bash

Good points about the CR-48 though. I was willing to wait for the slow builds, but saw that the SDK was going to eat up too much disk once I started downloading it.

Thanks,
James
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages