aboutsummaryrefslogtreecommitdiffstats
path: root/handbook/development.xml
diff options
context:
space:
mode:
authorRichard Purdie <rpurdie@linux.intel.com>2010-09-01 15:08:09 +0100
committerRichard Purdie <rpurdie@linux.intel.com>2010-09-01 15:08:45 +0100
commitcaab7fc509bf27706ff3248689f6afd04225cfda (patch)
treef832f656c91502303968fcee1aae382b9f713626 /handbook/development.xml
parent232ef8430e2cfbf6eee54f602dc74b9986e3997f (diff)
downloadopenembedded-core-contrib-caab7fc509bf27706ff3248689f6afd04225cfda.tar.gz
openembedded-core-contrib-caab7fc509bf27706ff3248689f6afd04225cfda.tar.bz2
openembedded-core-contrib-caab7fc509bf27706ff3248689f6afd04225cfda.zip
Drop chroot usage as its not well used, tested and is broken
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Diffstat (limited to 'handbook/development.xml')
-rw-r--r--handbook/development.xml42
1 files changed, 0 insertions, 42 deletions
diff --git a/handbook/development.xml b/handbook/development.xml
index 4f36c7aa82..3bcf40506c 100644
--- a/handbook/development.xml
+++ b/handbook/development.xml
@@ -241,48 +241,6 @@
</para>
</section>
- <section id="platdev-appdev-chroot">
- <title>Developing externally in a chroot</title>
- <para>
- If you have a system that matches the architecture of the Poky machine you're using,
- such as qemux86, you can run binaries directly from the image on the host system
- using a chroot combined with tools like <ulink url='http://projects.o-hand.com/xephyr'>Xephyr</ulink>.
- </para>
- <para>
- Poky has some scripts to make using its qemux86 images within a chroot easier. To use
- these you need to install the poky-scripts package or otherwise obtain the
- <filename>poky-chroot-setup</filename> and <filename>poky-chroot-run</filename> scripts.
- You also need Xephyr and chrootuid binaries available. To initialize a system use the setup script:
- </para>
- <para>
- <literallayout class='monospaced'>
-# poky-chroot-setup &lt;qemux86-rootfs.tgz&gt; &lt;target-directory&gt;
-</literallayout>
- </para>
- <para>
- which will unpack the specified qemux86 rootfs tarball into the target-directory.
- You can then start the system with:
- </para>
- <para>
- <literallayout class='monospaced'>
-# poky-chroot-run &lt;target-directory&gt; &lt;command&gt;
-</literallayout>
- </para>
- <para>
- where the target-directory is the place the rootfs was unpacked to and command is
- an optional command to run. If no command is specified, the system will drop you
- within a bash shell. A Xephyr window will be displayed containing the emulated
- system and you may be asked for a password since some of the commands used for
- bind mounting directories need to be run using sudo.
- </para>
- <para>
- There are limits as to how far the the realism of the chroot environment extends.
- It is useful for simple development work or quick tests but full system emulation
- with QEMU offers a much more realistic environment for more complex development
- tasks. Note that chroot support within Poky is still experimental.
- </para>
- </section>
-
<section id="platdev-appdev-insitu">
<title>Developing in Poky directly</title>
<para>