SF.net SVN: morphix: [2354] trunk/how_tos
[email protected] Wed, 12 Jul 2006 13:13:43 -0700
| Newsgroups | gmane.linux.morphix.cvs |
|---|---|
| Message-ID | <[email protected]> |
Revision: 2354
Author: bmsleight
Date: 2006-07-12 13:13:37 -0700 (Wed, 12 Jul 2006)
ViewCVS: http://svn.sourceforge.net/morphix/?rev=2354&view=rev
Log Message:
-----------
manual source files
Modified Paths:
--------------
trunk/how_tos/morphix_docbook.txt
trunk/how_tos/morphix_docbook.xml
Modified: trunk/how_tos/morphix_docbook.txt
===================================================================
--- trunk/how_tos/morphix_docbook.txt 2006-07-12 00:09:49 UTC (rev 2353)
+++ trunk/how_tos/morphix_docbook.txt 2006-07-12 20:13:37 UTC (rev 2354)
@@ -1,15 +1,12 @@
-////////////////////////////////////////////////////////////
-This file is used to generate the docbook.xml
-Edit this file then use:-
-asciidoc -b docbook thisfile.txt
-To create the html Use either:-
-xmlto html ../docbook.xml
-asciidoc -b xhtml11 -a theme=pretty_css
- (where pretty_css.css have install - see man asciidoc)
+////////////////////////////////////////////////////////////////////////////////////
+This file is used to generate the morphix_docbook.xml
+Edit this file!
+ docbook_html/prepare_html.sh
+ Is used to make the xml and html
Try not to use :-
Yes :- acsciidoc -> xmlto does no work with ':-'
-////////////////////////////////////////////////////////////
+////////////////////////////////////////////////////////////////////////////////////
Morphix Manual
==============
@@ -421,6 +418,8 @@
The purpose of 'Morphing-Morphix' is to provide the quick way to start 'Morphing' 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.
+You do not have to use Morphing-morphix you just need a debian based system and <<SettingUptheBuildEnvironment, Set Up the Build Environment>>
+
*The following applies to Morphing-Morphix Version 0.3*
*Version 0.3 is not yet complete*
@@ -432,10 +431,10 @@
* <<FirstMorph, My First Morph - change the background>>
* <<Rebranding, Rebranding>>
+* <<AutoLaunch, morphmini example - Auto-Launching Firefox>>
* <<HomeDir, Morphing the Home Directory>>
-* <<AutoLaunch, Auto-Launching Firefox>>
-* <<MainModule, Morphing a MainModule>>
* <<AutoBuilding, Auto-Building using mmaker>>
+* <<MainModule, Morphing a MainModule>>
* <<TestQemu, Testing an iso using Qemu>>
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.
@@ -446,33 +445,16 @@
[[FirstMorph]]
-Your First Morph
-~~~~~~~~~~~~~~~~
+My First Morph - change the background
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-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, 'morphing' isn't hard to start with. Lets say you want to do something simple, like change the default background of your live CD. There are plenty of scripts available to automate most or all of the process, but we won't use them here. Please note that you will need to be root for some of these commands. In this example we are using a version 0.5 Morphix CD.
+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, 'morphing' isn't hard to start with. Lets say you want to do something simple, like change the default background of your live CD.
-We need to change the contents of our CD-ROM iso. First things first, lets make sure we can access the files on it. Lets make a directory and mount the iso:
+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:
- #!/bin/bash
- #Setting-up mmorphing
- mount /mnt/hda3 -o dev
- mkdir /mnt/hda3/mmorphix 2>/dev/null
- 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/modules 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
+ isomorph --add ./background.png /morphix/ ./MyMorph.iso ./tmp.iso
+ mv ./tmp.iso ./MyMorph.iso
-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 /mnt/hda3/background.png) over the other one at boot time:
-
- isomorph --add /mnt/hda3/background.png /morphix/ /mnt/hda3/mmorphix/iso/MyMorph.iso /mnt/hda3/mmorphix/iso/tmp.iso
- mv /mnt/hda3/mmorphix/iso/tmp.iso /mnt/hda3/mmorphix/iso/MyMorph.iso
-
Well, that was it! The beauty of isomorph - it takes all the hardwork of mounting etc away.
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:
@@ -489,7 +471,7 @@
The next Morph is to rebrand the iso using a single graphics file.
-The following will be changes
+The following will be changed
* Grub background
* Grub titles.
@@ -500,16 +482,54 @@
* Username
* X Background
- morphix-rebrand /mnt/hda3/mmorphix/iso/MyMorph.iso /mnt/hda3/mmorphix/iso/tmp.iso /mnt/hda3/MyMorph.png
- mv /mnt/hda3/mmorphix/iso/tmp.iso /mnt/hda3/mmorphix/iso/MyMorph.iso
+ morphix-rebrand ./MyMorph.iso ./tmp.iso ./MyMorph.png
+ mv ./tmp.iso ./MyMorph.iso
+[[AutoLaunch]]
+morphmini example - Auto-Launching Firefox
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The next Morph is make a minimodule to autorun an application once the window manager has loaded.
+
+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.
+
+[NOTE]
+.Contents of MiniModuleLaunchFirefox.xml
+======================================
+--------------------------------------
+<comps>
+ <group>
+ <minimod>
+ <description>MorphMini launch firefox</description>
+ <minitag>MorphixMini-Firefox</minitag>
+ <maintag>ALL</maintag>
+ <commandlist>
+ <X>
+ <command>firefox http://www.morphix.org & </command> <!-- & is xml format for & -->
+ </X>
+ </commandlist>
+ </minimod>
+ </group>
+</comps>
+
+--------------------------------------
+======================================
+
+ morphmini ./MiniModuleLaunchFirefox.xml ./MiniModuleLaunchFirefox.mod
+ isomorph --add mini ./MiniModuleLaunchFirefox.mod ./MyMorph.iso ./tmp.iso
+ mv ./tmp.iso ./MyMorph.iso
+
+http://svn.sourceforge.net/viewcvs.cgi/morphix/trunk/scripts-mini/[Other templates for morphmini are available]
+
+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 http://svn.sourceforge.net/viewcvs.cgi/morphix/trunk/morph-scripts/morphmini/example.xml?view=markup[example.xml] for all tags.
+
[[HomeDir]]
Morphing the Home Directory
~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The next Morph is to save the files in the users home directory.
+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.
The following will be saved
@@ -520,78 +540,13 @@
* The X server setting - these are generated on boot up.
- make-mini --homedir --hidden /mnt/hda3/mmorphix/morphed/minimod/Morphix-Mini-Saved-Home.mod
- isomorph --add mini /mnt/hda3/mmorphix/morphed/minimod/Morphix-Mini-Saved-Home.mod /mnt/hda3/mmorphix/iso/MyMorph.iso /mnt/hda3/mmorphix/iso/tmp.iso
- mv /mnt/hda3/mmorphix/iso/tmp.iso /mnt/hda3/mmorphix/iso/MyMorph.iso
+ make-mini --homedir --hidden ./Morphix-Mini-Saved-Home.mod
+
+This miniodule needs to be saved to permanent storage so that we can add to the iso using
+ isomorph --add mini ./Morphix-Mini-Saved-Home.mod ./MyMorph.iso ./tmp.iso
+ mv ./tmp.iso ./MyMorph.iso
-[[AutoLaunch]]
-
-Auto-Launching Firefox
-~~~~~~~~~~~~~~~~~~~~~~
-
-The next Morph is make a minimodule to autorun an application once the window manager has loaded.
-
-This Morph is to demostrate the use of one of the morphix tools - morphmini
-*TO be Complete*
-
-
-[[MainModule]]
-
-Morphing a MainModule
-~~~~~~~~~~~~~~~~~~~~~
-
-The next Morph is make changes to a MainModule.
-
-In short: mainmodules contain your filesystem, except for
-your kernel, loadable kernel modules and hardware detection
-scripts. This filesystem is stored as a compressed cloop
-image.
-
-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.
-
-Once you have issued the chroot command it is just like you
-are running the compressed file system, rather than the
-current filesystem.
-
-You can for example
-
-* apt-get install new-application
-* Edit configuration files
-* Have fun ....
-
- #!/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/modules 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
-
-
[[AutoBuilding]]
Auto-Building Morphix Modules
@@ -651,74 +606,61 @@
Below is a quick overview on the layout of a template.
--------------------------------------
-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.
+include::../mmaker/README.template[]
+--------------------------------------
-<comps>
- <group>
- <version>version number of module</version>
- <id>lowercase identifier</id>
+[[MainModule]]
- <name>natural-language name of module</name>
+Morphing a MainModule
+~~~~~~~~~~~~~~~~~~~~~
- <description>possibly multiline description of module</description>
+The next Morph is make changes to a MainModule, rather than autobuild the module jumo inside the MainModuel and make changes by hand.
- <type>[mainmod|basemod|minimod]</type> (
- <!-- currently only main/basemod are useful -->
+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.
- <suite>[sid|sarge|woody|unstable|testing|stable]</suite>
- <!-- debian flavour to use -->
+Once you have issued the chroot command it is just like you
+are running the compressed file system, rather than the
+current filesystem.
- <arch>[i386|powerpc|sparc|hppa|amd64|whatnot]</arch>
- <!-- for attempting to build on a different architecture, use with care -->
+You can for example
- <retrieve>
- <from>/file/on/my/harddisk</from>
- <to>/place/in/module</to>
- </retrieve>
+* apt-get install new-application
+* Edit configuration files
+* Have fun ....
- <retrieve>
- <from>http://localhost/myfile</from>
- <to>/place/in/module</to>
- </retrieve>
+ #!/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
- <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>
- </group>
-</comps>
-
---------------------------------------
-
[[TestQemu]]
Testing an iso using Qemu
@@ -735,8 +677,9 @@
slow. Faster than burning a cd and rebooting. Good for
testing
- sudo qemu -boot d -cdrom /mnt/hda3/mmorphix/iso/My_Morph.iso
+ sudo qemu -cdrom ./My_Morph.iso
+
Using iBuild
~~~~~~~~~~~~
@@ -836,7 +779,7 @@
Once you read this boot options section of the FAQ have a look at the list of all possible Boot Options, http://www.morphix.org/wiki/index.php/MorphixBootOptions[]
-A dasebase for boot options that other people have used to get hardware working is in the wiki, http://www.morphix.org/wiki/index.php/MorphixHardwareVsBootOptionsRequired
+A dasebase for boot options that other people have used to get hardware working is in the wiki, http://www.morphix.org/wiki/index.php/MorphixHardwareVsBootOptionsRequired[]
The new grub menu (0.4-1d or later) allows you to select most of the boot options using the menu system and the cursor keys. To add extra boot options to the menu you can edit the command line, just type in the extra boot option. If you do not want to add any further boots option grub menu automatic times out after 5 seconds and starts the boot process.
@@ -1140,4 +1083,3 @@
The index is normally left completely empty, it's contents being
generated automatically by the DocBook toolchain.
////////////////////////////////////////////////////////////////
-
Modified: trunk/how_tos/morphix_docbook.xml
===================================================================
--- trunk/how_tos/morphix_docbook.xml 2006-07-12 00:09:49 UTC (rev 2353)
+++ trunk/how_tos/morphix_docbook.xml 2006-07-12 20:13:37 UTC (rev 2354)
@@ -433,7 +433,7 @@
</itemizedlist>
<note>
<title>Note on Templates</title>
-<simpara>These template may point to a local mirror of the debian repository. Uncomment the remote repository and command out the local repository</simpara>
+<simpara>These templates may point to a local mirror of the debian repository. Un-comment the remote repository and comment out the local repository.</simpara>
<simpara>For example replace the lines</simpara>
@@ -474,7 +474,7 @@
</listitem>
<listitem>
<simpara>
-morphix-rebrand ./morphix-livekiosk.iso ./Morphix-LiveKiosk.iso ./Morphix-LiveKiosk.png
+morphix-rebrand ./morphix-livekiosk.iso ./MorphixLiveKiosk.iso ./MorphixLiveKiosk.png
</simpara>
</listitem>
</itemizedlist>
@@ -609,6 +609,8 @@
<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>
+<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><emphasis role="strong">The following applies to Morphing-Morphix Version 0.3</emphasis></simpara>
<simpara><emphasis role="strong">Version 0.3 is not yet complete</emphasis></simpara>
@@ -630,22 +632,22 @@
</listitem>
<listitem>
<simpara>
-<link linkend="HomeDir">Morphing the Home Directory</link>
+<link linkend="AutoLaunch">morphmini example - Auto-Launching Firefox</link>
</simpara>
</listitem>
<listitem>
<simpara>
-<link linkend="AutoLaunch">Auto-Launching Firefox</link>
+<link linkend="HomeDir">Morphing the Home Directory</link>
</simpara>
</listitem>
<listitem>
<simpara>
-<link linkend="MainModule">Morphing a MainModule</link>
+<link linkend="AutoBuilding">Auto-Building using mmaker</link>
</simpara>
</listitem>
<listitem>
<simpara>
-<link linkend="AutoBuilding">Auto-Building using mmaker</link>
+<link linkend="MainModule">Morphing a MainModule</link>
</simpara>
</listitem>
<listitem>
@@ -661,29 +663,13 @@
</section>
<section id="FirstMorph">
-<title>Your First Morph</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. There are plenty of scripts available to automate most or all of the process, but we won't use them here. Please note that you will need to be root for some of these commands. In this example we are using a version 0.5 Morphix CD.</simpara>
+<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>
-<simpara>We need to change the contents of our CD-ROM iso. First things first, lets make sure we can access the files on it. Lets make a directory and mount the iso:</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>
-<literallayout class="monospaced">#!/bin/bash
-#Setting-up mmorphing
-mount /mnt/hda3 -o dev
-mkdir /mnt/hda3/mmorphix 2>/dev/null
-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/modules 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</literallayout>
-<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 /mnt/hda3/background.png) over the other one at boot time:</simpara>
-
-<literallayout class="monospaced">isomorph --add /mnt/hda3/background.png /morphix/ /mnt/hda3/mmorphix/iso/MyMorph.iso /mnt/hda3/mmorphix/iso/tmp.iso
-mv /mnt/hda3/mmorphix/iso/tmp.iso /mnt/hda3/mmorphix/iso/MyMorph.iso</literallayout>
+<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>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>
@@ -697,7 +683,7 @@
<title>Rebranding a Morphix ISO</title>
<simpara>The next Morph is to rebrand the iso using a single graphics file.</simpara>
-<simpara>The following will be changes</simpara>
+<simpara>The following will be changed</simpara>
<itemizedlist>
<listitem>
@@ -739,14 +725,46 @@
<simpara>
X Background
</simpara>
-<literallayout class="monospaced">morphix-rebrand /mnt/hda3/mmorphix/iso/MyMorph.iso /mnt/hda3/mmorphix/iso/tmp.iso /mnt/hda3/MyMorph.png
-mv /mnt/hda3/mmorphix/iso/tmp.iso /mnt/hda3/mmorphix/iso/MyMorph.iso</literallayout>
+<literallayout class="monospaced">morphix-rebrand ./MyMorph.iso ./tmp.iso ./MyMorph.png
+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>
+
+<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>
+
+<note>
+<title>Contents of MiniModuleLaunchFirefox.xml</title>
+<screen><comps>
+ <group>
+ <minimod>
+ <description>MorphMini launch firefox</description>
+ <minitag>MorphixMini-Firefox</minitag>
+ <maintag>ALL</maintag>
+ <commandlist>
+ <X>
+ <command>firefox http://www.morphix.org &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
+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.</simpara>
+<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 following will be saved</simpara>
@@ -769,85 +787,14 @@
<simpara>
The X server setting - these are generated on boot up.
</simpara>
-<literallayout class="monospaced">make-mini --homedir --hidden /mnt/hda3/mmorphix/morphed/minimod/Morphix-Mini-Saved-Home.mod
-isomorph --add mini /mnt/hda3/mmorphix/morphed/minimod/Morphix-Mini-Saved-Home.mod /mnt/hda3/mmorphix/iso/MyMorph.iso /mnt/hda3/mmorphix/iso/tmp.iso
-mv /mnt/hda3/mmorphix/iso/tmp.iso /mnt/hda3/mmorphix/iso/MyMorph.iso</literallayout>
+<literallayout class="monospaced">make-mini --homedir --hidden ./Morphix-Mini-Saved-Home.mod</literallayout>
</listitem>
</itemizedlist>
-</section>
-<section id="AutoLaunch">
-<title>Auto-Launching Firefox</title>
-<simpara>The next Morph is make a minimodule to autorun an application once the window manager has loaded.</simpara>
+<simpara>This miniodule needs to be saved to permanent storage so that we can add to the iso using</simpara>
-<simpara>This Morph is to demostrate the use of one of the morphix tools - morphmini
-<emphasis role="strong">TO be Complete</emphasis></simpara>
-
+<literallayout class="monospaced">isomorph --add mini ./Morphix-Mini-Saved-Home.mod ./MyMorph.iso ./tmp.iso
+mv ./tmp.iso ./MyMorph.iso</literallayout>
</section>
-<section id="MainModule">
-<title>Morphing a MainModule</title>
-<simpara>The next Morph is make changes to a MainModule.</simpara>
-
-<simpara>In short: mainmodules contain your filesystem, except for
-your kernel, loadable kernel modules and hardware detection
-scripts. This filesystem is stored as a compressed cloop
-image.</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>
-
-<itemizedlist>
-<listitem>
-<simpara>
-apt-get install new-application
-</simpara>
-</listitem>
-<listitem>
-<simpara>
-Edit configuration files
-</simpara>
-</listitem>
-<listitem>
-<simpara>
-Have fun ….
-</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/modules 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>
-</itemizedlist>
-</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.
@@ -901,7 +848,12 @@
<simpara>Below is a quick overview on the layout of a template.</simpara>
-<screen>The syntax is derived from Progeny's CL scheme, which was derived from
+<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.
@@ -959,15 +911,81 @@
<!-- package to apt-get purge -->
...
</packagelist>
+
<patchlist>
- <patch>path/to/shellscript.sh</patch>
+ <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>
+</comps></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>
+
+<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>
+
+<itemizedlist>
+<listitem>
+<simpara>
+apt-get install new-application
+</simpara>
+</listitem>
+<listitem>
+<simpara>
+Edit configuration files
+</simpara>
+</listitem>
+<listitem>
+<simpara>
+Have fun ….
+</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>
+</itemizedlist>
+</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
@@ -981,7 +999,7 @@
slow. Faster than burning a cd and rebooting. Good for
testing</simpara>
-<literallayout class="monospaced">sudo qemu -boot d -cdrom /mnt/hda3/mmorphix/iso/My_Morph.iso</literallayout>
+<literallayout class="monospaced">sudo qemu -cdrom ./My_Morph.iso</literallayout>
</section>
<section>
<title>Using iBuild</title>
@@ -1196,7 +1214,7 @@
<simpara>Once you read this boot options section of the FAQ have a look at the list of all possible Boot Options, <ulink url="http://www.morphix.org/wiki/index.php/MorphixBootOptions">http://www.morphix.org/wiki/index.php/MorphixBootOptions</ulink></simpara>
-<simpara>A dasebase for boot options that other people have used to get hardware working is in the wiki, http://www.morphix.org/wiki/index.php/MorphixHardwareVsBootOptionsRequired</simpara>
+<simpara>A dasebase for boot options that other people have used to get hardware working is in the wiki, <ulink url="http://www.morphix.org/wiki/index.php/MorphixHardwareVsBootOptionsRequired">http://www.morphix.org/wiki/index.php/MorphixHardwareVsBootOptionsRequired</ulink></simpara>
<simpara>The new grub menu (0.4-1d or later) allows you to select most of the boot options using the menu system and the cursor keys. To add extra boot options to the menu you can edit the command line, just type in the extra boot option. If you do not want to add any further boots option grub menu automatic times out after 5 seconds and starts the boot process.</simpara>
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