path: root/handbook
diff options
authorRichard Purdie <>2010-09-01 14:08:09 (GMT)
committerRichard Purdie <>2010-09-01 14:08:45 (GMT)
commitcaab7fc509bf27706ff3248689f6afd04225cfda (patch)
treef832f656c91502303968fcee1aae382b9f713626 /handbook
parent232ef8430e2cfbf6eee54f602dc74b9986e3997f (diff)
Drop chroot usage as its not well used, tested and is broken
Signed-off-by: Richard Purdie <>
Diffstat (limited to 'handbook')
1 files changed, 0 insertions, 42 deletions
diff --git a/handbook/development.xml b/handbook/development.xml
index 4f36c7a..3bcf405 100644
--- a/handbook/development.xml
+++ b/handbook/development.xml
@@ -241,48 +241,6 @@
241 </para> 241 </para>
242 </section> 242 </section>
243 243
244 <section id="platdev-appdev-chroot">
245 <title>Developing externally in a chroot</title>
246 <para>
247 If you have a system that matches the architecture of the Poky machine you're using,
248 such as qemux86, you can run binaries directly from the image on the host system
249 using a chroot combined with tools like <ulink url=''>Xephyr</ulink>.
250 </para>
251 <para>
252 Poky has some scripts to make using its qemux86 images within a chroot easier. To use
253 these you need to install the poky-scripts package or otherwise obtain the
254 <filename>poky-chroot-setup</filename> and <filename>poky-chroot-run</filename> scripts.
255 You also need Xephyr and chrootuid binaries available. To initialize a system use the setup script:
256 </para>
257 <para>
258 <literallayout class='monospaced'>
259# poky-chroot-setup &lt;qemux86-rootfs.tgz&gt; &lt;target-directory&gt;
261 </para>
262 <para>
263 which will unpack the specified qemux86 rootfs tarball into the target-directory.
264 You can then start the system with:
265 </para>
266 <para>
267 <literallayout class='monospaced'>
268# poky-chroot-run &lt;target-directory&gt; &lt;command&gt;
270 </para>
271 <para>
272 where the target-directory is the place the rootfs was unpacked to and command is
273 an optional command to run. If no command is specified, the system will drop you
274 within a bash shell. A Xephyr window will be displayed containing the emulated
275 system and you may be asked for a password since some of the commands used for
276 bind mounting directories need to be run using sudo.
277 </para>
278 <para>
279 There are limits as to how far the the realism of the chroot environment extends.
280 It is useful for simple development work or quick tests but full system emulation
281 with QEMU offers a much more realistic environment for more complex development
282 tasks. Note that chroot support within Poky is still experimental.
283 </para>
284 </section>
286 <section id="platdev-appdev-insitu"> 244 <section id="platdev-appdev-insitu">
287 <title>Developing in Poky directly</title> 245 <title>Developing in Poky directly</title>
288 <para> 246 <para>