@ -380,6 +380,13 @@ bOOTrOOT has become a full blown distribution creation program.</P>
< P > < b > How can I test gBootRoot?< / b > < / P >
< P > < b > How can I test gBootRoot?< / b > < / P >
< p >
(Note: You may run all these tests as a normal user.
See the exceptions which apply to creating boot disks.)< / p >
< center > < u > Test an existing mini distribution.< / u > < / center >
< P > 1. Download
< P > 1. Download
< a href = "http://prdownloads.sourceforge.net/user-mode-linux/root_fs_tomrtbt_1.7.205.bz2" >
< a href = "http://prdownloads.sourceforge.net/user-mode-linux/root_fs_tomrtbt_1.7.205.bz2" >
root_fs_tomrtbt_1.7.205.bz2< / a > from
root_fs_tomrtbt_1.7.205.bz2< / a > from
@ -396,15 +403,17 @@ $HOME/.gbootroot/root_filesystems. </p>
< p >
< p >
3. Run
3. Run
gbootroot. Click on the Advanced Root Section, click on
gbootroot. Click on the Advanced Root Section (ARS) , click on
the UML button. Select root_fs_tomrtbt_1.7.205, add devfs=nomount
the UML button. Select root_fs_tomrtbt_1.7.205, add devfs=nomount
to the options, and click on the Submit
to the options, and click on the Submit
button.< / p >
button.< / p >
< center > < u > Create a boot and root floppy for an existing mini distribution.< / u > < / center >
< p >
< p >
4. Click on the Advanced Boot
4. Click on the Advanced Boot
Section. Root_fs_tomrtbt is about 16M, so add ramdisk_size=16384 to
Section (ABS) . Root_fs_tomrtbt is about 16M, so add ramdisk_size=16384 to
the 'append=' entry. From the main box choose '2 disk compression', and
the 'append=' entry. From the main box choose '2 disk compression', and
press on the Root Filesystem button and select root_fs_tomrtbt_1.7.205.bz2.
press on the Root Filesystem button and select root_fs_tomrtbt_1.7.205.bz2.
< / p >
< / p >
@ -414,10 +423,15 @@ box. Have two floppy disks ready.
< p >
< p >
6. When you see Lilo you may access the menu using [Ctrl] and
6. When you boot the boot disk you will see Lilo, you may access the menu using [Ctrl] and [Tab] to see the available images, or wait for the
[Tab] to see the available images.
prompt to insert the root disk.< / p >
< center > < u > Test a macro distribution created by make_debian-X11.< / u > < / center >
< p >
< p >
7. Download
7. Download
< a href = "http://sourceforge.net/project/showfiles.php?group_id=9513" >
< a href = "http://sourceforge.net/project/showfiles.php?group_id=9513" >
@ -427,10 +441,136 @@ first three steps, but don't add devfs=nomount. This root
filesystem was created with
filesystem was created with
the make_debian-X11 script from the make-debian-x11 add-on found at
the make_debian-X11 script from the make-debian-x11 add-on found at
< a href = "http://sourceforge.net/project/showfiles.php?group_id=9513" >
< a href = "http://sourceforge.net/project/showfiles.php?group_id=9513" >
gbootroot's< / a > Sourceforge home.
gbootroot's< / a > Sourceforge home.< / p >
< center > < u > Make your own micro distribution from an existing template.< / u > < / center >
< p >
8. Click on the ARS if its not already opened.
Choose Yard from the Method pull-down menu. Chosse Example-Mini.yard
from the pull-down Template menu. Click on the Generate button.
The Yard Box will pop up. Click on the Continue button
until you reach the Create check box. You could continue to the
tests, but they really wouldn't apply to this minimalistic example because
there are no links or login type files in the template.< / p >
< p >
9. Experiment with Edit->Stages from the Yard Box menu.
Try different types of staging behavior, and notice the
differences.< / p >
< p >
10. Test your creation with the UML box as explained in step 3.
You will want to add init=/bin/bash to the Options entry.< / p >
< p >
11. At this point you will probably want to play around a little
bit. Familiarize yourself with the Format Rules found
near the top of the template. You may want to save the template
with a different name and experiment with changes, or create a new template
using File->New (Shortcut: Alt-N).< / p >
< center > < u > Make your own mini distribution from an existing template.< / u > < / center >
< p >
12. Choose Example.yard from the Template menu in the ARS.
Save it with a new name.< / p >
< p >
13. There are two types of inittabs provided for each major
distribution type. The inittab with nodevfs appended doesn't use
the
device fs, i.e. the devfs=nomount kernel option. Uncomment the
inittab, getty, and gettydefs (if required) for
your distribution type. If you aren't using Debian and make sure to
comment (#) out the corresponding stuff for Debian.< / p >
< p >
14. The Example.yard template introduces you to Replacements like
the inittabs described above.
Replacements can be anywhere as long as they are either in an absolute path
or found in $PATH
(Edit->Settings->Path); the default location for users is
$HOME/.gbootroot/yard/Replacements. For more information see the
FAQ question
"What are all these CVS directories doing in my replacements?"
Also, this template introduces you to links, $VERSION,
how library dependencies are automatically figured for binaries
and the automated
approach for finding service modules and dependencies for PAM and NSS.
Once you learn the format rules and how they are interpreted
by the program you will find that making your own templates is
quite simple.< / p >
< p >
15 Click on the Continue button until you finish the Space Left
stage. Adjust the Filesystem Size in the ARS to a size larger than
the Total space shown in the verbosity box. Create your
root_fs,
and make sure there was enough room left. You may have to adjust the
size and run Create again.< / p >
< p >
16 Now that you have a root filesystem you may continue to
the Test stage and observe what is missing. Next run the root_fs
from the UML box.
If things don't work correctly you will have to hunt down the cause,
make the appropriate changes and proceed through the stages again. & nbsp
If you only make a change to a Replacement, you only have to run
the Create stage again. If you make a change to the template you
have to run at least the Check, Links & Deps, and Create stages again.< / p >
< center > < u > Make your own root filesystems from your own templates.< / u > < / center >
< p >
17. Now that you have done your homework, I set you free to create
your own root filesystems from your own templates with replacements
of your own choice. Create a root_fs which can fit on a block
device, and then create an emergency disk customized for your own system,
or create your own customized macro distribution and run it from the
UML box to try things you never would have dreamed of doing on your host
system. And that is just the beginning of the things you can do.
< P >
< b > What are all these CVS directories doing in my replacements?< / b > < / p >
< P >
< P >
< b > Can I use a program linked to uClibc in the template?< / b > < / p >
< p >
< b > What is make_debian, and how do I use it?< / b > < / p >
< p >
< b > How am I able to create root filesystems as a normal user?< / b > < / p >
< p >
< b > How can I create boot disks as a normal user?< / b > < / p >
< p >
< b > My root filesystem doesn't start in single mode when started like
< b > My root filesystem doesn't start in single mode when started like
this:  " bootdisk 1?" < / b > < / P >
this:  " bootdisk 1?" < / b > < / P >