1 files changed, 12 insertions, 92 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 016a0f104f..eeb792b370 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -158,56 +158,15 @@
                    Building an Image</ulink> section of the Yocto Project Quick Start.    
                    You might want to reference this information.</para></listitem>
                <listitem><para><emphasis>Build the image</emphasis>:  The Yocto Project uses the BitBake 
-                    tool to build images based on the type of image 
+                    tool to build images based on the type of image you want to create.  
-                    you want to create.  
                    You can find more information on BitBake 
                    <ulink url='http://bitbake.berlios.de/manual/'>here</ulink>.</para>
                    <para>The build process supports several types of images to satisfy different needs.  
-                    When you issue the BitBake command you provide a “top-level” recipe that essentially 
+                    See 
-                    starts the process off of building the type of image you want.</para>
+                    <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>
-                    <para>[WRITER'S NOTE: Consider moving this to the Poky Reference Manual.]</para>
+                    Reference: Images</ulink> in the 
-                    <para>You can find these recipes in the <filename>meta/recipes-core/images</filename> and 
+                    <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'>
-                    <filename>meta/recipes-sato/images</filename> directories of your local Yocto Project 
+                    Yocto Project Reference Manual</ulink>for information on supported images.</para></listitem>
-                    file structure (Git repository or extracted release tarball).  
-                    Although the recipe names are somewhat explanatory, here is a list that describes them:
-                    <itemizedlist>
-                        <listitem><para><emphasis>Base</emphasis> – A foundational basic image without support 
-                            for X that can be reasonably used for customization.</para></listitem>
-                        <listitem><para><emphasis>Core</emphasis> – A foundational basic image with support for 
-                            X that can be reasonably used for customization.</para></listitem>
-                        <listitem><para><emphasis>Direct Disk</emphasis> – An image that you can copy directory to 
-                            the disk of the target device.</para></listitem>
-                        <listitem><para><emphasis>Live</emphasis> – An image you can run from a USB device or from 
-                            a CD without having to first install something.</para></listitem>
-                        <listitem><para><emphasis>Minimal</emphasis> – A small image without a GUI.  
-                            This image is not much more than a kernel with a shell.</para></listitem>
-                        <listitem><para><emphasis>Minimal Development</emphasis> – A Minimal image suitable for 
-                            development work.</para></listitem>
-                        <listitem><para><emphasis>Minimal Direct Disk</emphasis> – A Minimal Direct 
-                            Disk image.</para></listitem>
-                        <listitem><para><emphasis>Minimal RAM-based Initial Root Filesystem</emphasis> – 
-                            A minimal image 
-                           that has the <filename>initramfs</filename> as part of the kernel, which allows the 
-                            system to find the first “init” program more efficiently.</para></listitem>
-                        <listitem><para><emphasis>Minimal Live</emphasis> – A Minimal Live image.</para></listitem>
-                       <listitem><para><emphasis>Minimal MTD Utilities</emphasis> – A minimal image that has support 
-                            for the MTD utilities, which let the user interact with the MTD subsystem in 
-                            the kernel to perform operations on flash devices.</para></listitem>
-                        <listitem><para><emphasis>Sato</emphasis> – An image with Sato support, a mobile environment 
-                            and visual style that works well with mobile devices.</para></listitem>
-                        <listitem><para><emphasis>Sato Development</emphasis> – A Sato image suitable for 
-                            development work.</para></listitem>
-                        <listitem><para><emphasis>Sato Direct Disk</emphasis> – A Sato Direct 
-                            Disk image.</para></listitem>
-                        <listitem><para><emphasis>Sato Live</emphasis> – A Sato Live image.</para></listitem>
-                        <listitem><para><emphasis>Sato SDK</emphasis> – A Sato image that includes the Yocto Project 
-                            toolchain and development libraries.</para></listitem>
-                        <listitem><para><emphasis>Sato SDK Direct Disk</emphasis> – A Sato SDK Direct 
-                            Disk image.</para></listitem>
-                        <listitem><para><emphasis>Sato SDK Live</emphasis> – A Sato SDK Live 
-                           image.</para></listitem>
-                    </itemizedlist>
-                </para></listitem>
            </orderedlist>
        </para>
@@ -387,51 +346,12 @@
                        You can find more information on BitBake 
                        <ulink url='http://bitbake.berlios.de/manual/'>here</ulink>.</para>
                        <para>The build process supports several types of images to satisfy different needs.  
-                        When you issue the BitBake command you provide a “top-level” recipe that essentially 
+                        See 
-                        starts the process off of building the type of image you want.</para>
+                        <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>
-                        <para>[WRITER'S NOTE: Consider moving this to the Poky Reference Manual.]</para>
+                        Reference: Images</ulink> in the 
-                        <para>You can find these recipes in the <filename>meta/recipes-core/images</filename> and 
+                        <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'>
-                        <filename>meta/recipes-sato/images</filename> directories of your local Yocto Project 
+                        Yocto Project Reference Manual</ulink> for information on supported 
-                        file structure (Git repository or extracted release tarball).  
+                        images.</para></listitem>
-                        Although the recipe names are somewhat explanatory, here is a list that describes them:
-                        <itemizedlist>
-                            <listitem><para><emphasis>Base</emphasis> – A foundational basic image without support 
-                                for X that can be reasonably used for customization.</para></listitem>
-                            <listitem><para><emphasis>Core</emphasis> – A foundational basic image with support for 
-                                X that can be reasonably used for customization.</para></listitem>
-                            <listitem><para><emphasis>Direct Disk</emphasis> – An image that you can copy directory to 
-                                the disk of the target device.</para></listitem>
-                            <listitem><para><emphasis>Live</emphasis> – An image you can run from a USB device or from 
-                                a CD without having to first install something.</para></listitem>
-                            <listitem><para><emphasis>Minimal</emphasis> – A small image without a GUI.  
-                                This image is not much more than a kernel with a shell.</para></listitem>
-                            <listitem><para><emphasis>Minimal Development</emphasis> – A Minimal image suitable for 
-                                development work.</para></listitem>
-                            <listitem><para><emphasis>Minimal Direct Disk</emphasis> – A Minimal Direct 
-                                Disk image.</para></listitem>
-                            <listitem><para><emphasis>Minimal RAM-based Initial Root Filesystem</emphasis> – 
-                                A minimal image 
-                                that has the <filename>initramfs</filename> as part of the kernel, which allows the 
-                                system to find the first “init” program more efficiently.</para></listitem>
-                            <listitem><para><emphasis>Minimal Live</emphasis> – A Minimal Live image.</para></listitem>
-                            <listitem><para><emphasis>Minimal MTD Utilities</emphasis> – A minimal image that has support 
-                                for the MTD utilities, which let the user interact with the MTD subsystem in 
-                                the kernel to perform operations on flash devices.</para></listitem>
-                            <listitem><para><emphasis>Sato</emphasis> – An image with Sato support, a mobile environment 
-                                and visual style that works well with mobile devices.</para></listitem>
-                            <listitem><para><emphasis>Sato Development</emphasis> – A Sato image suitable for 
-                                development work.</para></listitem>
-                            <listitem><para><emphasis>Sato Direct Disk</emphasis> – A Sato Direct 
-                                Disk image.</para></listitem>
-                            <listitem><para><emphasis>Sato Live</emphasis> – A Sato Live image.</para></listitem>
-                            <listitem><para><emphasis>Sato SDK</emphasis> – A Sato image that includes the Yocto Project 
-                                toolchain and development libraries.</para></listitem>
-                            <listitem><para><emphasis>Sato SDK Direct Disk</emphasis> – A Sato SDK Direct 
-                                Disk image.</para></listitem>
-                            <listitem><para><emphasis>Sato SDK Live</emphasis> – A Sato SDK Live 
-                               image.</para></listitem>
-                        </itemizedlist>
-                    </para></listitem>
                    <listitem><para><emphasis>Make your configuration changes available
                        in the kernel layer</emphasis>:  Up to this point all the configuration changes to the 
                        kernel have been done and tested iteratively.

diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 016a0f104f..eeb792b370 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml
@@ -158,56 +158,15 @@
158	Building an Image</ulink> section of the Yocto Project Quick Start.	158	Building an Image</ulink> section of the Yocto Project Quick Start.
159	You might want to reference this information.</para></listitem>	159	You might want to reference this information.</para></listitem>
160	<listitem><para><emphasis>Build the image</emphasis>: The Yocto Project uses the BitBake	160	<listitem><para><emphasis>Build the image</emphasis>: The Yocto Project uses the BitBake
161	tool to build images based on the type of image	161	tool to build images based on the type of image you want to create.
162	you want to create.
163	You can find more information on BitBake	162	You can find more information on BitBake
164	<ulink url='http://bitbake.berlios.de/manual/'>here</ulink>.</para>	163	<ulink url='http://bitbake.berlios.de/manual/'>here</ulink>.</para>
165	<para>The build process supports several types of images to satisfy different needs.	164	<para>The build process supports several types of images to satisfy different needs.
166	When you issue the BitBake command you provide a “top-level” recipe that essentially	165	See
167	starts the process off of building the type of image you want.</para>	166	<ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>
168	<para>[WRITER'S NOTE: Consider moving this to the Poky Reference Manual.]</para>	167	Reference: Images</ulink> in the
169	<para>You can find these recipes in the <filename>meta/recipes-core/images</filename> and	168	<ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'>
170	<filename>meta/recipes-sato/images</filename> directories of your local Yocto Project	169	Yocto Project Reference Manual</ulink>for information on supported images.</para></listitem>
171	file structure (Git repository or extracted release tarball).
172	Although the recipe names are somewhat explanatory, here is a list that describes them:
173	<itemizedlist>
174	<listitem><para><emphasis>Base</emphasis> – A foundational basic image without support
175	for X that can be reasonably used for customization.</para></listitem>
176	<listitem><para><emphasis>Core</emphasis> – A foundational basic image with support for
177	X that can be reasonably used for customization.</para></listitem>
178	<listitem><para><emphasis>Direct Disk</emphasis> – An image that you can copy directory to
179	the disk of the target device.</para></listitem>
180	<listitem><para><emphasis>Live</emphasis> – An image you can run from a USB device or from
181	a CD without having to first install something.</para></listitem>
182	<listitem><para><emphasis>Minimal</emphasis> – A small image without a GUI.
183	This image is not much more than a kernel with a shell.</para></listitem>
184	<listitem><para><emphasis>Minimal Development</emphasis> – A Minimal image suitable for
185	development work.</para></listitem>
186	<listitem><para><emphasis>Minimal Direct Disk</emphasis> – A Minimal Direct
187	Disk image.</para></listitem>
188	<listitem><para><emphasis>Minimal RAM-based Initial Root Filesystem</emphasis> –
189	A minimal image
190	that has the <filename>initramfs</filename> as part of the kernel, which allows the
191	system to find the first “init” program more efficiently.</para></listitem>
192	<listitem><para><emphasis>Minimal Live</emphasis> – A Minimal Live image.</para></listitem>
193	<listitem><para><emphasis>Minimal MTD Utilities</emphasis> – A minimal image that has support
194	for the MTD utilities, which let the user interact with the MTD subsystem in
195	the kernel to perform operations on flash devices.</para></listitem>
196	<listitem><para><emphasis>Sato</emphasis> – An image with Sato support, a mobile environment
197	and visual style that works well with mobile devices.</para></listitem>
198	<listitem><para><emphasis>Sato Development</emphasis> – A Sato image suitable for
199	development work.</para></listitem>
200	<listitem><para><emphasis>Sato Direct Disk</emphasis> – A Sato Direct
201	Disk image.</para></listitem>
202	<listitem><para><emphasis>Sato Live</emphasis> – A Sato Live image.</para></listitem>
203	<listitem><para><emphasis>Sato SDK</emphasis> – A Sato image that includes the Yocto Project
204	toolchain and development libraries.</para></listitem>
205	<listitem><para><emphasis>Sato SDK Direct Disk</emphasis> – A Sato SDK Direct
206	Disk image.</para></listitem>
207	<listitem><para><emphasis>Sato SDK Live</emphasis> – A Sato SDK Live
208	image.</para></listitem>
209	</itemizedlist>
210	</para></listitem>
211	</orderedlist>	170	</orderedlist>
212	</para>	171	</para>
213		172
@@ -387,51 +346,12 @@
387	You can find more information on BitBake	346	You can find more information on BitBake
388	<ulink url='http://bitbake.berlios.de/manual/'>here</ulink>.</para>	347	<ulink url='http://bitbake.berlios.de/manual/'>here</ulink>.</para>
389	<para>The build process supports several types of images to satisfy different needs.	348	<para>The build process supports several types of images to satisfy different needs.
390	When you issue the BitBake command you provide a “top-level” recipe that essentially	349	See
391	starts the process off of building the type of image you want.</para>	350	<ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>
392	<para>[WRITER'S NOTE: Consider moving this to the Poky Reference Manual.]</para>	351	Reference: Images</ulink> in the
393	<para>You can find these recipes in the <filename>meta/recipes-core/images</filename> and	352	<ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'>
394	<filename>meta/recipes-sato/images</filename> directories of your local Yocto Project	353	Yocto Project Reference Manual</ulink> for information on supported
395	file structure (Git repository or extracted release tarball).	354	images.</para></listitem>
396	Although the recipe names are somewhat explanatory, here is a list that describes them:
397	<itemizedlist>
398	<listitem><para><emphasis>Base</emphasis> – A foundational basic image without support
399	for X that can be reasonably used for customization.</para></listitem>
400	<listitem><para><emphasis>Core</emphasis> – A foundational basic image with support for
401	X that can be reasonably used for customization.</para></listitem>
402	<listitem><para><emphasis>Direct Disk</emphasis> – An image that you can copy directory to
403	the disk of the target device.</para></listitem>
404	<listitem><para><emphasis>Live</emphasis> – An image you can run from a USB device or from
405	a CD without having to first install something.</para></listitem>
406	<listitem><para><emphasis>Minimal</emphasis> – A small image without a GUI.
407	This image is not much more than a kernel with a shell.</para></listitem>
408	<listitem><para><emphasis>Minimal Development</emphasis> – A Minimal image suitable for
409	development work.</para></listitem>
410	<listitem><para><emphasis>Minimal Direct Disk</emphasis> – A Minimal Direct
411	Disk image.</para></listitem>
412	<listitem><para><emphasis>Minimal RAM-based Initial Root Filesystem</emphasis> –
413	A minimal image
414	that has the <filename>initramfs</filename> as part of the kernel, which allows the
415	system to find the first “init” program more efficiently.</para></listitem>
416	<listitem><para><emphasis>Minimal Live</emphasis> – A Minimal Live image.</para></listitem>
417	<listitem><para><emphasis>Minimal MTD Utilities</emphasis> – A minimal image that has support
418	for the MTD utilities, which let the user interact with the MTD subsystem in
419	the kernel to perform operations on flash devices.</para></listitem>
420	<listitem><para><emphasis>Sato</emphasis> – An image with Sato support, a mobile environment
421	and visual style that works well with mobile devices.</para></listitem>
422	<listitem><para><emphasis>Sato Development</emphasis> – A Sato image suitable for
423	development work.</para></listitem>
424	<listitem><para><emphasis>Sato Direct Disk</emphasis> – A Sato Direct
425	Disk image.</para></listitem>
426	<listitem><para><emphasis>Sato Live</emphasis> – A Sato Live image.</para></listitem>
427	<listitem><para><emphasis>Sato SDK</emphasis> – A Sato image that includes the Yocto Project
428	toolchain and development libraries.</para></listitem>
429	<listitem><para><emphasis>Sato SDK Direct Disk</emphasis> – A Sato SDK Direct
430	Disk image.</para></listitem>
431	<listitem><para><emphasis>Sato SDK Live</emphasis> – A Sato SDK Live
432	image.</para></listitem>
433	</itemizedlist>
434	</para></listitem>
435	<listitem><para><emphasis>Make your configuration changes available	355	<listitem><para><emphasis>Make your configuration changes available
436	in the kernel layer</emphasis>: Up to this point all the configuration changes to the	356	in the kernel layer</emphasis>: Up to this point all the configuration changes to the
437	kernel have been done and tested iteratively.	357	kernel have been done and tested iteratively.