summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/ref-classes.xml
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2016-04-15 07:57:37 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-04-18 16:28:24 +0100
commit4d5ff5e0757b72112c902fb067fa91907759ff18 (patch)
tree946c4030b6c5bc290ac709f927a8f18fa1b2f3d1 /documentation/ref-manual/ref-classes.xml
parentcd2aaaa31008b7aae4b9ef7b2b7aacb6ffce174f (diff)
downloadpoky-4d5ff5e0757b72112c902fb067fa91907759ff18.tar.gz
ref-manual, dev-manual: Scrubbed boot-directdisk and bootimg classes
These classes have been removed. The bootimg class was sucked into the image-live class. I removed the reference sections to both classes and fixed the references throughout the manual set as needed. (From yocto-docs rev: 649d56b54987580039cbd52f54642112f810ffad) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/ref-classes.xml')
-rw-r--r--documentation/ref-manual/ref-classes.xml58
1 files changed, 0 insertions, 58 deletions
diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
index 1351991985..ccab5e68ab 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -319,64 +319,6 @@
319 </para> 319 </para>
320</section> 320</section>
321 321
322<section id='ref-classes-boot-directdisk'>
323 <title><filename>boot-directdisk.bbclass</filename></title>
324
325 <para>
326 The <filename>boot-directdisk</filename> class
327 creates an image that can be placed directly onto a hard disk using
328 <filename>dd</filename> and then booted.
329 The image uses SYSLINUX.
330 </para>
331
332 <para>
333 The end result is a 512 boot sector populated with a
334 Master Boot Record (MBR) and partition table followed by an MSDOS
335 FAT16 partition containing SYSLINUX and a Linux kernel completed by
336 the <filename>ext2</filename> and <filename>ext3</filename>
337 root filesystems.
338 </para>
339</section>
340
341<section id='ref-classes-bootimg'>
342 <title><filename>bootimg.bbclass</filename></title>
343
344 <para>
345 The <filename>bootimg</filename> class creates a bootable
346 image using SYSLINUX, your kernel, and an optional initial RAM disk
347 (<filename>initrd</filename>).
348 </para>
349
350 <para>
351 When you use this class, two things happen:
352 <itemizedlist>
353 <listitem><para>
354 A <filename>.hddimg</filename> file is created.
355 This file is an MSDOS filesystem that contains SYSLINUX,
356 a kernel, an <filename>initrd</filename>, and a root filesystem
357 image.
358 All three of these can be written to hard drives directly and
359 also booted on a USB flash disks using <filename>dd</filename>.
360 </para></listitem>
361 <listitem><para>
362 A CD <filename>.iso</filename> image is created.
363 When this file is booted, the <filename>initrd</filename>
364 boots and processes the label selected in SYSLINUX.
365 Actions based on the label are then performed (e.g. installing
366 to a hard drive).</para></listitem>
367 </itemizedlist>
368 </para>
369
370 <para>
371 The <filename>bootimg</filename> class supports the
372 <link linkend='var-INITRD'><filename>INITRD</filename></link>,
373 <link linkend='var-NOISO'><filename>NOISO</filename></link>,
374 <link linkend='var-NOHDD'><filename>NOHDD</filename></link>, and
375 <link linkend='var-ROOTFS'><filename>ROOTFS</filename></link>
376 variables.
377 </para>
378</section>
379
380<section id='ref-classes-bugzilla'> 322<section id='ref-classes-bugzilla'>
381 <title><filename>bugzilla.bbclass</filename></title> 323 <title><filename>bugzilla.bbclass</filename></title>
382 324