SF.net SVN: morphix: [2412] trunk/how_tos/morphix_docbook.xml
[email protected] Mon, 04 Sep 2006 15:38:23 -0700
| Newsgroups | gmane.linux.morphix.cvs |
|---|---|
| Message-ID | <[email protected]> |
Revision: 2412
http://svn.sourceforge.net/morphix/?rev=2412&view=rev
Author: bmsleight
Date: 2006-09-04 15:38:12 -0700 (Mon, 04 Sep 2006)
Log Message:
-----------
Updating manaul to reflect MM_0.3
Modified Paths:
--------------
trunk/how_tos/morphix_docbook.xml
Modified: trunk/how_tos/morphix_docbook.xml
===================================================================
--- trunk/how_tos/morphix_docbook.xml 2006-09-04 22:37:50 UTC (rev 2411)
+++ trunk/how_tos/morphix_docbook.xml 2006-09-04 22:38:12 UTC (rev 2412)
@@ -368,7 +368,8 @@
<title>HowTo: Building a new LiveCD in two commands</title>
<simpara><indexterm>
<primary>HowToLiveCD</primary>
-</indexterm></simpara>
+</indexterm>
+<anchor id="BuildingLiveCDtwocommands" xreflabel="[BuildingLiveCDtwocommands]"/></simpara>
<itemizedlist>
<listitem>
@@ -606,177 +607,174 @@
Some <emphasis>updated</emphasis> How Tos to help you get started with Morphing. These HowTos are available on interacive <emphasis>How To</emphasis> LiveCD called <emphasis>Morphing-Morphix</emphasis>, much better than a boring document.</simpara>
<section>
-<title>A look at Morphing-Morphix</title>
-<simpara>The purpose of <emphasis>Morphing-Morphix</emphasis> is to provide the quick way to start <emphasis>Morphing</emphasis> and making your own LiveCD. Just boot the CD and start Morphing, no need to install tools, compile applications or switch operating systems. All is required is some space on a connected hard drive. The aim is to be able make new Morphix LiveCDs using this LiveCD, as an introduction to Morphix. In fact this LiveCD was made using Morphing-Morphix.</simpara>
+<title>A look at MorphingMorphix 0.3</title>
+<simpara>The purpose of MorphingMorphix is to provide a quick way
+to start Morphing and to showcase all the Morphix tools
+- a LiveCD contruction kit. Just boot the CD and start
+Morphing, no need to install tools, compile applications or
+switch operating systems. All that is required is some space
+on a connected hard drive.</simpara>
-<simpara>You do not have to use Morphing-morphix you just need a debian based system and <link linkend="SettingUptheBuildEnvironment">Set Up the Build Environment</link></simpara>
+<simpara>You do not have to use MorphingMorphix you just need a debian based system and <link linkend="SettingUptheBuildEnvironment">Set Up the Build Environment</link></simpara>
-<simpara><emphasis role="strong">The following applies to Morphing-Morphix Version 0.3</emphasis></simpara>
+<simpara>On MorphingMorphix there are a number of interactive
+HowTo/examples. The examples work best if you work though
+them in order. First configure MorphingMorphix so that some
+extra disk space is available. Then work through the
+examples in order.</simpara>
-<simpara><emphasis role="strong">Version 0.3 is not yet complete</emphasis></simpara>
+<simpara>Some of the examples, such as using mmaker and isomaker
+require access to the internet, so that software can be
+downloaded from repositories to build new parts of a
+MorphixCD. The examples are very machine intensive,
+using lots of disk space, memory, and bandwidth.</simpara>
-<simpara><emphasis role="strong">We like to write documentation first then code</emphasis></simpara>
-
<simpara>The following Morphs can be completed from the LiveCD.</simpara>
<itemizedlist>
<listitem>
<simpara>
-<link linkend="FirstMorph">My First Morph - change the background</link>
+<link linkend="Introduction">Introduction to isomorph</link>
</simpara>
</listitem>
<listitem>
<simpara>
-<link linkend="Rebranding">Rebranding</link>
+<link linkend="Remove">Remove Modules</link>
</simpara>
</listitem>
<listitem>
<simpara>
-<link linkend="AutoLaunch">morphmini example - Auto-Launching Firefox</link>
+<link linkend="MiniMorphExample">MiniMorph Example</link>
</simpara>
</listitem>
<listitem>
<simpara>
-<link linkend="HomeDir">Morphing the Home Directory</link>
+<link linkend="HomeDir">Saving files in /home/morph</link>
</simpara>
</listitem>
<listitem>
<simpara>
-<link linkend="AutoBuilding">Auto-Building using mmaker</link>
+<link linkend="AutoBuilding">Mmaker Example</link>
</simpara>
</listitem>
<listitem>
<simpara>
-<link linkend="MainModule">Morphing a MainModule</link>
+<link linkend="MainModule">Chrooting a Main Module</link>
</simpara>
</listitem>
<listitem>
<simpara>
+<link linkend="Rebrand">Rebrand an ISO</link>
+</simpara>
+</listitem>
+<listitem>
+<simpara>
+<link linkend="BuildingwholeISO">Building a whole ISO from Scratch</link>
+</simpara>
+</listitem>
+<listitem>
+<simpara>
<link linkend="TestQemu">Testing an iso using Qemu</link>
</simpara>
</listitem>
</itemizedlist>
-<simpara>Boot the Morphing-Morphix CD, then from the IceWM button select Morphing-Mophix. All off the following morphs are available from the nice graphic menu.
-After you have used this interative <emphasis>How To</emphasis> a script is available as /tmp/mmscript.sh This script contain all the commands used in your morphing session. In fact you can use this mmscript to reproduce exactly the same results. The best thing is, you can read thought the commands listed in the script. This will give you an introduction to use some of the morphix tools.</simpara>
-
-<simpara>With each of the Morphs beow included is an example output of /tmp/mmscript.sh</simpara>
-
</section>
-<section id="FirstMorph">
-<title>My First Morph - change the background</title>
-<simpara>Now we know how a Morphix live CD can be structured, lets make us a new Live CD to illustrate. Even if you only skimmed over the last section, <emphasis>morphing</emphasis> isn't hard to start with. Lets say you want to do something simple, like change the default background of your live CD.</simpara>
+<section id="Introduction">
+<title>Introduction</title>
+<simpara>LiveCD are stored as .iso files. Which can then be written
+to a CD. One of the morphing-tools is isomorph. This can be
+used to manipulate morphix iso files.</simpara>
-<simpara>Now, where was that background located? Checking the XFCE4 settings, you discover it is located at /morphix/background.png. Not wanting to figure out in which module it is located, you use the /copy-directory instead to copy your new background (located at ./background.png) over the other one at boot time:</simpara>
+<simpara>Isomorph can list, add, del and get files on the Morphix
+LiveCDs.</simpara>
-<literallayout class="monospaced">isomorph --add ./background.png /morphix/ ./MyMorph.iso ./tmp.iso
-mv ./tmp.iso ./MyMorph.iso</literallayout>
-<simpara>Well, that was it! The beauty of isomorph - it takes all the hardwork of mounting etc away.</simpara>
+<simpara>Isomorph is used in all of the other examples.</simpara>
-<simpara>You can burn your iso using your favorite CD-R burning tool, and you're done. One freshly baked live CD with your own background, coming right up:</simpara>
+<simpara>For example we will now run the command
+ isomorph —list MyMorph.iso</simpara>
-<literallayout class="monospaced">cdrecord -scanbus
-cdrecord speed=8 dev=0,0,0 /tmp/mylivecd.iso</literallayout>
-<simpara>Of course, this was a pretty simple morph. You can do quite amazing stuff using Morphix without needing to remaster modules directly</simpara>
-
</section>
-<section id="Rebranding">
-<title>Rebranding a Morphix ISO</title>
-<simpara>The next Morph is to rebrand the iso using a single graphics file.</simpara>
+<section id="Remove">
+<title>Remove Modules</title>
+<simpara>We have now got our CD Image file, by copying this running
+CD. As you have seen in the last example, this image
+contains the MainModule and lots of MiniModules. The easy
+way to make a new LiveCD is to build new MiniModules and a
+new MainModule.</simpara>
-<simpara>The following will be changed</simpara>
+<simpara>Hence the first task is to delete the MainModule and
+MiniModules from the LiveCD image.
+Remove Modules</simpara>
-<itemizedlist>
-<listitem>
-<simpara>
-Grub background
-</simpara>
-</listitem>
-<listitem>
-<simpara>
-Grub titles.
-</simpara>
-</listitem>
-<listitem>
-<simpara>
-Bootsplash
-</simpara>
-</listitem>
-<listitem>
-<simpara>
-Bootsplash background
-</simpara>
-</listitem>
-<listitem>
-<simpara>
-Bootsplash messages
-</simpara>
-</listitem>
-<listitem>
-<simpara>
-Hostname
-</simpara>
-</listitem>
-<listitem>
-<simpara>
-Username
-</simpara>
-</listitem>
-<listitem>
-<simpara>
-X Background
-</simpara>
-<literallayout class="monospaced">morphix-rebrand ./MyMorph.iso ./tmp.iso ./MyMorph.png
+<simpara>We will again use isomorph</simpara>
+
+<literallayout class="monospaced">isomorph --del-all main ./MyMorph.iso ./tmp.iso
+mv ./tmp.iso ./MyMorph.iso
+isomorph --del-all mini ./MyMorph.iso ./tmp.iso
mv ./tmp.iso ./MyMorph.iso</literallayout>
-</listitem>
-</itemizedlist>
</section>
-<section id="AutoLaunch">
-<title>morphmini example - Auto-Launching Firefox</title>
-<simpara>The next Morph is make a minimodule to autorun an application once the window manager has loaded.</simpara>
+<section id="MiniMorphExample">
+<title>MiniMorph Example</title>
+<simpara>The next Morph is making the MiniModule to auto run an
+application once the window manager has loaded.</simpara>
-<simpara>This Morph is to demostrate the use of one of the morphix tools - morphmini. This is mmkaer little brother. As in other exmaples this makes use of XML template files.</simpara>
+<simpara>This Morph is to demonstrate the use of one of the morphix
+tools - morphmini. This is mmaker's little brother. As in
+other examples this makes use of XML template files.</simpara>
-<note>
-<title>Contents of MiniModuleLaunchFirefox.xml</title>
<screen><comps>
<group>
<minimod>
- <description>MorphMini launch firefox</description>
- <minitag>MorphixMini-Firefox</minitag>
+ <version>0.0.1</version>
+ <description>MorphMini launch Morphing-Morphix-GUI</description>
+ <minitag>MorphixMini-Launch-MM-GUI</minitag>
<maintag>ALL</maintag>
- <commandlist>
- <X>
- <command>firefox http://www.morphix.org &amp; </command> <!-- &amp; is xml format for & -->
+ <bootoption>ALL</bootoption>
+ <root> <!-- Files or Packages to be overlaid on the rootfile system - good for saving ramspace -->
+ <files>
+ <local>
+ <from>/home/morph/morphix/trunk/morph-scripts/mmorphix/morphing-morphix-gui.sh</from>
+ <to>/usr/sbin/morphing-morphix-gui</to>
+ </local>
+ <local>
+ <from>/home/morph/morphix/trunk/morph-scripts/mmorphix/MorphingMorphix.xpm</from>
+ <to>/usr/share/morphing-morphix/</to>
+ </local>
+ </files>
+ </root>
+ <commandlist> <!-- Commands to be started from minimodule -->
+ <X> <!-- Commands to run in X windows -->
+ <command>/usr/sbin/morphing-morphix-gui &amp; </command><!-- &amp; is xml format for & -->
</X>
</commandlist>
</minimod>
</group>
-</comps>
-</screen>
-</note>
-<literallayout class="monospaced">morphmini ./MiniModuleLaunchFirefox.xml ./MiniModuleLaunchFirefox.mod
-isomorph --add mini ./MiniModuleLaunchFirefox.mod ./MyMorph.iso ./tmp.iso
+</comps></screen>
+<simpara>We will now build the MiniModule then add the MiniModule to
+the the LiveCD.</simpara>
+
+<literallayout class="monospaced">morphmini ./MorphixMini-Launch-MM-GUI.xml ./MorphixMini-Launch-MM-GUI.mod
+isomorph --add mini ./MorphixMini-Launch-MM-GUI.mod ./MyMorph.iso ./tmp.iso
mv ./tmp.iso ./MyMorph.iso</literallayout>
<simpara><ulink url="http://svn.sourceforge.net/viewcvs.cgi/morphix/trunk/scripts-mini/">Other templates for morphmini are available</ulink></simpara>
-<simpara>By using the <root> tag it is possible to overlay files on top of the base and mainmodule without using an excessive amount of memory.See <ulink url="http://svn.sourceforge.net/viewcvs.cgi/morphix/trunk/morph-scripts/morphmini/example.xml?view=markup">example.xml</ulink> for all tags.</simpara>
-
</section>
<section id="HomeDir">
<title>Morphing the Home Directory</title>
-<simpara>The next Morph is to save the files in the users home directory when you are running the LiveCD. This is great for doing the final tweaks to a LiveCD. Boot the CD, make the minor changes that can only really be done when the LiveCD is running then save these tweaks as a minimodule.</simpara>
+<simpara>The next Morph is to save the files in the users home
+directory.</simpara>
<simpara>The following will be saved</simpara>
<itemizedlist>
<listitem>
<simpara>
-Any files and directories in the users home.
+Any files and directories in /home/morph
</simpara>
</listitem>
<listitem>
<simpara>
-Hidden sitting files. (The are the files beginning with a . e.g. .icewm)
+Hidden system files. (These are the files beginning with a . e.g. .icewm)
</simpara>
</listitem>
</itemizedlist>
@@ -787,24 +785,53 @@
<simpara>
The X server setting - these are generated on boot up.
</simpara>
-<literallayout class="monospaced">make-mini --homedir --hidden ./Morphix-Mini-Saved-Home.mod</literallayout>
</listitem>
</itemizedlist>
-<simpara>This miniodule needs to be saved to permanent storage so that we can add to the iso using</simpara>
+<simpara>Basically all the files and directories in /home/morph will
+be zipped into placed in to a self-extracting MiniModule.</simpara>
-<literallayout class="monospaced">isomorph --add mini ./Morphix-Mini-Saved-Home.mod ./MyMorph.iso ./tmp.iso
+<simpara>So feel free to save some files, settings, etc within the
+home directory before continuing.This is really useful for
+setting default homepages, menus etc.</simpara>
+
+<simpara>The power of a MiniModule is that they are very simple to
+build, but really useful to change the whole impression of
+the cd.</simpara>
+
+<simpara>We make the mini-module using one of the morphix-tools
+make-mini, along with isomorph to add the MiniModule to the
+image file.</simpara>
+
+<literallayout class="monospaced">make-mini --homedir --hidden MorphixMini-MM-Saved-Home.mod
+isomorph --add mini MorphixMini-MM-Saved-Home.mod ./MyMorph.iso ./tmp.iso
mv ./tmp.iso ./MyMorph.iso</literallayout>
</section>
<section id="AutoBuilding">
-<title>Auto-Building Morphix Modules</title>
-<simpara>We will take a look at Module Maker, or MMaker, a tool for autobuilding Morphix modules. Remastering modules is all fine and well, and you can do this just as you can with a compressed KNOPPIX image. However, laziness is seen as a virtue in Morphix-land: one command is all it should take to (re)build a module.
-A look at a module generator</simpara>
+<title>Mmaker Example</title>
+<simpara>MMaker is a tool that is quite simple in nature. Using a
+so-called template, an xml file with all the information
+about the module you want to build, you can auto-build a
+Morphix MainModule.</simpara>
-<simpara>MMaker is a tool under development at the moment, but is quite simple in nature. Using a so-called template, an xml file with all the information about the module you want to build, you can auto-build a Morphix module:</simpara>
+<simpara>That's it kids, we will just have a look at
+morphing-morphix.xml used to build this MainModule
+currently running.</simpara>
-<literallayout class="monospaced">mmaker mytemplate.xml mymodule.mod</literallayout>
-<simpara>What MMaker does when you execute this command is debootstrap a new debian filesystem using the details in the template, set up the necessary mainmodule directories and installs all packages specified in the template, while using apt to handle any dependancies. Afterwards it compresses the whole bunch into a fresh new module, ready to be added to a Morphix Live CD in the usual manner.</simpara>
+<simpara>We will then use mmaker to build a new version of the
+MainModule. Unless you one of the lucky people who has a
+local repository, you will be using the main Debian repository.</simpara>
+<simpara>You need a fast connection to Debian repository and a lot
+of space to build the MainModule before it is compressed.</simpara>
+
+<simpara>This step could take up to 45 minutes, but hey it is
+automated!</simpara>
+
+<simpara>We will use these commands</simpara>
+
+<literallayout class="monospaced">mmaker /usr/share/morphing-morphix/morphing-morphix.xml /tmp/morphing-morphix.mod
+isomorph --add main /tmp/morphing-morphix.mod ./MyMorph.iso ./tmp.iso
+mv ./tmp.iso ./MyMorph.iso</literallayout>
<simpara>As you might have guessed, the template is the key to all of this. A look at one for Morphix LightGUI: [note to editor: the template uses an xml notation, so might not appear when viewing in html]</simpara>
<literallayout class="monospaced"><comps>
@@ -830,7 +857,7 @@
</comps></literallayout>
<simpara>NB This is a partial template see <ulink url="http://svn.sourceforge.net/viewcvs.cgi/morphix/trunk/mmaker/templates/">http://svn.sourceforge.net/viewcvs.cgi/morphix/trunk/mmaker/templates/</ulink> for template examples.</simpara>
-<simpara>Seems simple, doesn't it? The actual template for LightGUI is quite a bit longer (and contains a package to start xfce4 at boot time), but it's very simple to specify which repositories you want to use, what Debian suite you want, what type of Morphix module you want to autobuild and naturally the packages you want. Currently, MMaker can only build base and main modules . A few tags might need some extra explaining:</simpara>
+<simpara>Seems simple, doesn't it? The actual template for MorphingMorphix is quite a bit longer (and contains a package to start xfce4 at boot time), but it's very simple to specify which repositories you want to use, what Debian suite you want, what type of Morphix module you want to autobuild and naturally the packages you want. Currently, MMaker can only build base and main modules . A few tags might need some extra explaining:</simpara>
<simpara><repository> - With this tag you define the Debian repository/repositories from which to build your module. Use the type="plain" attribute when you have a repository without separate suites (You can verify this by checking the repository, if it has a Packages file in the root directory of the repository we call it <emphasis>plain</emphasis>). Normal, Debian-style repositories is default</simpara>
@@ -848,167 +875,103 @@
<simpara>Below is a quick overview on the layout of a template.</simpara>
-<screen>Quick overview on the layout of a template. For examples, see the
-template/ directory.
-
----
-
-The syntax is derived from Progeny's CL scheme, which was derived from
-Redhat's. This one has a list of available options in your template, with
-comments to help you out.
-
-<comps>
- <group>
- <version>version number of module</version>
-
- <id>lowercase identifier</id>
-
- <name>natural-language name of module</name>
-
- <description>possibly multiline description of module</description>
-
- <type>[mainmod|basemod|minimod]</type> (
- <!-- currently only main/basemod are useful -->
-
- <suite>[sid|sarge|woody|unstable|testing|stable]</suite>
- <!-- debian flavour to use -->
-
- <arch>[i386|powerpc|sparc|hppa|amd64|whatnot]</arch>
- <!-- for attempting to build on a different architecture, use with care -->
-
- <retrieve>
- <from>/file/on/my/harddisk</from>
- <to>/place/in/module</to>
- </retrieve>
-
- <retrieve>
- <from>http://localhost/myfile</from>
- <to>/place/in/module</to>
- </retrieve>
-
- <retrieve type="[tar.gz|tar.bz2]"> <!-- only implemented for local from-to -->
- ...
- </retrieve>
-
- <repositorylist>
-
- <repository type="[debian|plain]" [nonfree="true"] [suite="woody|sarge|sid|stable|testing|unstable]>URL</repository>
- <!-- either a normal repository or a debian one.
- Need one debian repository for main/base modules
- use nonfree if you want to add contrib/non-free to your apt line
- adding the suite tag here overrides the default suite
- -->
- ...
- </repositorylist>
- <packagelist>
-
- <packagereq [target="sid|sarge|woody|unstable|testing|stable"]>packagename</packagereq>
- <!-- package to apt-get install, optionally set target to
- define the -t/--target-release of the package -->
- ...
-
- <packagedel>packagename</packagereq>
- <!-- package to apt-get purge -->
- ...
- </packagelist>
-
- <patchlist>
-
- <patch>path/to/shellscript.sh</patch> (
- <!-- shell script on HOST system, gets the build directory as $1 -->
- </patchlist>
-
- <commandlist>
-
- <command>echo "Real Morphers idle on #morphix"</command> (
- <!-- shell command run in the build chroot, just before compressing -->
- </commandlist>
-
- </group>
-</comps></screen>
+<screen></screen>
</section>
<section id="MainModule">
-<title>Morphing a MainModule</title>
-<simpara>The next Morph is make changes to a MainModule, rather than autobuild the module jumo inside the MainModuel and make changes by hand.</simpara>
+<title>Chrooting a Main Module</title>
+<simpara>One of the easiest ways to modify a MainModule is to
+extract the compressed filesystem then change the root
+directory to the extracted file system - chroot.</simpara>
-<simpara>One of the easiest way to modify a MainModule is to extract
-the compressed filesystem then change the root directory
-to the extracted file system - chroot.</simpara>
-
<simpara>Once you have issued the chroot command it is just like you
are running the compressed file system, rather than the
current filesystem.</simpara>
-<simpara>You can for example</simpara>
+<simpara>You can for example
+<emphasis role="strong"> apt-get install new-applications
+</emphasis> Edit configuration files
+* Have fun ….</simpara>
+<simpara>We will now extract the MainModule. This can take a while
+as ~800M is extracted. We started then dropped in to the
+MainModule root. Once we exit we re-compress the MainModule.</simpara>
+
+<simpara>We will use the commands</simpara>
+
+<literallayout class="monospaced">isomorph --get main ./MyMorph.iso /tmp/
+morphix-chroot /tmp/morphing-morphix.mod
+isomorph --add main /tmp/morphing-morphix.mod ./MyMorph.iso ./tmp.iso
+mv ./tmp.iso ./MyMorph.iso</literallayout>
+</section>
+<section id="Rebrand">
+<title>Rebrand an ISO</title>
+<simpara>This script Re-brands a Morphix CD image using a graphic
+file.</simpara>
+
+<simpara>The following will be changed</simpara>
+
<itemizedlist>
<listitem>
<simpara>
-apt-get install new-application
+Grub Titles
</simpara>
</listitem>
<listitem>
<simpara>
-Edit configuration files
+Grub Background
</simpara>
</listitem>
<listitem>
<simpara>
-Have fun ….
+Username, Hostname
</simpara>
-<literallayout class="monospaced">#!/bin/bash
-#Setting-up mmorphing
-sudo mount /mnt/hda3 -o dev
-sudo mkdir /mnt/hda3/mmorphix 2>/dev/null
-sudo chown mmorph.users /mnt/hda3/mmorphix 2>/dev/null
-mkdir /mnt/hda3/mmorphix/tmp 2>/dev/null
-mkdir /mnt/hda3/mmorphix/iso 2>/dev/null
-mkdir /mnt/hda3/mmorphix/morphing 2>/dev/null
-mkdir /mnt/hda3/mmorphix/morphed 2>/dev/null
-mkdir /mnt/hda3/mmorphix/mnt 2>/dev/null
-#Setting-up complete
-#Start of My First Morph Commands
-mount Morphing-Morphix_0-0-1.iso /mnt/hda3/mmorphix/mnt -o loop
-# sudo rm -R /mnt/hda3/mmorphix/morphed
-sudo cp -av /mnt/hda3/mmorphix/mnt/* /mnt/hda3/mmorphix/morphed
-#Start Morphing the main-module
-sudo -R /mnt/hda3/mmorphix/morphing/*
-sudo module-extractor /mnt/hda3/mmorphix/morphed/mainmod/morphing-morphix.mod /mnt/hda3/mmorphix/morphing/
-# resolv.conf required for network
-sudo cp /etc/resolv.conf /mnt/hda3/mmorphix/morphing/etc/resolv.conf
-sudo chroot /mnt/hda3/mmorphix/morphing/ mount -t proc /proc proc
-xterm -e sudo chroot /mnt/hda3/mmorphix/morphing/
-sudo chroot /mnt/hda3/mmorphix/morphing/ umount -lf /proc
-sudo rm /mnt/hda3/mmorphix/morphed/mainmod/morphing-morphix.mod
-#sudo rm /mnt/hda3/mmorphix/morphed/mainmod/*
-sudo module-builder /mnt/hda3/mmorphix/morphing/ /mnt/hda3/mmorphix/morphed/mainmod/morphing-morphix.mod
-sudo /usr/bin/make-iso /mnt/hda3/mmorphix/morphed /mnt/hda3/mmorphix/iso/My_Morph.iso</literallayout>
</listitem>
+<listitem>
+<simpara>
+Boot-up message
+</simpara>
+</listitem>
+<listitem>
+<simpara>
+Boot-up background
+</simpara>
+</listitem>
+<listitem>
+<simpara>
+Window Manager Wallpaper
+</simpara>
+</listitem>
</itemizedlist>
+<simpara>Any Graphic file will do. Rebrand.png, Rebrand.jpg or
+Rebrand.gif The name of the graphics file is important as
+the script takes Rebrand as the new title for the LiveCD.</simpara>
+
+<simpara>We will use these commands</simpara>
+
+<literallayout class="monospaced">morphix-rebrand ./MyMorph.iso ./tmp.iso Rebrand.jpg
+mv ./tmp.iso ./MyMorph.iso</literallayout>
</section>
+<section id="BuildingwholeISO">
+<title>Building a whole ISO from Scratch</title>
+<simpara>See <link linkend="BuildingLiveCDtwocommands">Building a LiveCD using two commands</link></simpara>
+
+</section>
<section id="TestQemu">
<title>Testing an iso using Qemu</title>
<simpara>The next Morph is not really a Morph. It is used to test
-other morphs.</simpara>
+other morphs. It is a common tool for Morphers to use.</simpara>
<simpara>Qemu is a generic and open source processor emulator which
achieves a good emulation speed by using dynamic
translation.</simpara>
-<simpara>In short: Boot you LiveCD inside this LiveCD, but a little
-slow. Faster than burning a cd and rebooting. Good for
-testing</simpara>
+<simpara>In short: Boot your LiveCD inside your current operating
+system. A little slower but faster than burning a cd and
+rebooting. Good for testing.</simpara>
-<literallayout class="monospaced">sudo qemu -cdrom ./My_Morph.iso</literallayout>
+<literallayout class="monospaced">qemu -boot d -cdrom ./MyMorph.iso</literallayout>
</section>
-<section>
-<title>Using iBuild</title>
-<simpara>To be added. In the meantime, see:
-<ulink url="http://ibuild.livecd.net/">http://ibuild.livecd.net/</ulink>
-<ulink url="http://wiki.livecd.net/livecd/IbuildHowto">http://wiki.livecd.net/livecd/IbuildHowto</ulink></simpara>
-
</section>
-</section>
<section>
<title>Appendix FAQ: Frequently Asked Questions FAQ</title>
<simpara><indexterm>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642