1. <ahref="#1">What's the advantage of using this program?</a>
<br>
2. <ahref="#2">How do I use gBootRoot?</a>
<br>
3. <ahref="#3">Oops, I can't get something to work, what should I do?</a>
<br>
4. <ahref="#4">What are all these CVS directories doing in my replacements?</a>
<br>
5. <ahref="#5">Can I use a program linked to uClibc in the template?</a>
<br>
6. <ahref="#6">What do you mean by macro distribution?</a>
<br>
7. <ahref="#7">How am I able to create root filesystems as a normal user?</a>
<br>
8. <ahref="#8">How does this program allow a normal user to create a root filesystem larger than 8192k?</a>
<br>
9. <ahref="#9">How can I create boot disks as a normal user?</a>
<br>
10. <ahref="#10">What is make_debian, and how do I use it?</a>
<br>
11. <ahref="#11">My root filesystem doesn't start in single mode when started like this: "bootdisk 1?"</a>
<br>
12. <ahref="#12">What does the 2 disk compression method do?</a>
<br>
13. <ahref="#13">I've created a root fs. Then I've tried to create the boot disk using the 2 disk compression method. The device selection is /dev/fd0, size is 1440k, but the initrd_image.gz is 715k. I don't know much about boot disks but shouldn't the boot disks contain mainly the kernel?</a>
<br>
14. <ahref="#14">If libc is included in the boot disk, why is it needed in the root disk as well?</a>
<br>
15. <ahref="#15">So if I understand correctly, it is not possible to copy libc from dev/ram0 to /dev/ram1 before mounting /dev/ram1 as / ?</a>
<br>
16. <ahref="#16">There isn't enough room left on my 1440 floppy to make a Boot or Root disk. Is there any way to free up more space apart from reducing the size of the kernel?</a>
<br>
17. <ahref="#17">Last, but not least...the boot disk boots, waits for the root disk, and now fails. "Can't open console"??? or sth like this (I'm pretty tired right now, recheck later), which appears after "VFS:ext2fs was found..."</a>
<br>
18. <ahref="#18">What are the kernel's drivers/fs that must be directly compiled, not as modules, except ext2, floppy? Could you attach your kernel's .config?</a>
<br>
19. <ahref="#19">What is the root_fs_helper 2Mb file in the grootboot package?</a>
<br>
20. <ahref="#20">
Now the creation works, but actually the whole image is less than 1440k... Still, unclear to me is the purpose of the device/size in the main widget - is it only for the boot or also for the root disk? After all, the root fs image size has been already entered in the ARS.</a>
<br>
21. <ahref="#21">gBootRoot doesn't start because it can't locate Gtk.pm?</a>
<br>
22. <ahref="#22">If you roll the floppy density counter down to 0 and then try go back up towards 1440 and 1722, you get very funny figures.</a>
<tt>
<ahref="#1">1.</a> What's the advantage of using this program?
<p>
<ahref="#2">2.</a> How do I use gBootRoot?
<p>
<ahref="#3">3.</a> Oops, I can't get something to work, what should I do?
<p>
<ahref="#4">4.</a> What are all these CVS directories doing in my replacements?
<p>
<ahref="#5">5.</a> Can I use a program linked to uClibc in the template?
<p>
<ahref="#6">6.</a> What do you mean by macro distribution?
<p>
<ahref="#7">7.</a> How am I able to create root filesystems as a normal user?
<p>
<ahref="#8">8.</a> How does this program allow a normal user to create a root filesystem larger than 8192k?
<p>
<ahref="#9">9.</a> How can I create boot disks as a normal user?
<p>
<ahref="#10">10.</a> What is make_debian, and how do I use it?
<p>
<ahref="#11">11.</a> My root filesystem doesn't start in single mode when started like this: "bootdisk 1?"
<p>
<ahref="#12">12.</a> What does the 2 disk compression method do?
<p>
<ahref="#13">13.</a> I've created a root fs. Then I've tried to create the boot disk using the 2 disk compression method. The device selection is /dev/fd0, size is 1440k, but the initrd_image.gz is 715k. I don't know much about boot disks but shouldn't the boot disks contain mainly the kernel?
<p>
<ahref="#14">14.</a> If libc is included in the boot disk, why is it needed in the root disk as well?
<p>
<ahref="#15">15.</a> So if I understand correctly, it is not possible to copy libc from dev/ram0 to /dev/ram1 before mounting /dev/ram1 as / ?
<p>
<ahref="#16">16.</a> There isn't enough room left on my 1440 floppy to make a Boot or Root disk. Is there any way to free up more space apart from reducing the size of the kernel?
<p>
<ahref="#17">17.</a> Last, but not least...the boot disk boots, waits for the root disk, and now fails. "Can't open console"??? or sth like this (I'm pretty tired right now, recheck later), which appears after "VFS:ext2fs was found..."
<p>
<ahref="#18">18.</a> What are the kernel's drivers/fs that must be directly compiled, not as modules, except ext2, floppy? Could you attach your kernel's .config?
<p>
<ahref="#19">19.</a> What is the root_fs_helper 2Mb file in the grootboot package?
<p>
<ahref="#20">20.</a>
Now the creation works, but actually the whole image is less than 1440k... Still, unclear to me is the purpose of the device/size in the main widget - is it only for the boot or also for the root disk? After all, the root fs image size has been already entered in the ARS.
<p>
<ahref="#21">21.</a> gBootRoot doesn't start because it can't locate Gtk.pm?
<p>
<ahref="#22">22.</a> If you roll the floppy density counter down to 0 and then try go back up towards 1440 and 1722, you get very funny figures.
</a>
<br>
23. <ahref="#23">Changing from gz to bz2 compression for the boot image in the main section has no effect and gzip is still executed.</a>
<br>
<p>
<ahref="#23">23.</a> Changing from gz to bz2 compression for the boot image in the main section has no effect and gzip is still executed.
<p>
</tt>
<P><aname="1"><b>What's the advantage of using this program?</b></a> <ahref="#FAQ">[back]</a></P>
<P><Ahref="./bootroot.html">BootRoot</A>
was the original program, but I decided that a GUI approach
provided the user much more versatility and power in creating
distributions. Since the first gBootRoot,
bOOTrOOT has become a full blown distribution creation program which may
be used by a normal user.
It may be used for the creation of root filesystems in every
imaginable application from Embedded Systems to Mini Distributions to
Macro distributions to Full sized Distributions.  The root
and boot filesystems may
be tested long before implementation by using user-mode-linux.
Boot Methods are provided to allow root filesystems to run from different types
of media.
Historically, developers have written scripts
which have focused on providing a particular type of root
filesystem and boot method. Observation reveals that all these
approaches share many commonalities. gBootRoot has been
designed to embrace
these similarities, and to allow developers to create drop-in methods
via modules or easy to understand templates.
gBootroot is the GIMP of distribution creation!</P>
<P><Ahref="./bootroot.html">BootRoot</A> was the original program,
but I decided that a GUI approach provided the user much more
versatility and power in creating distributions. Since the
first gBootRoot, bOOTrOOT has become a full blown distribution
creation program which may be used by a normal user. It may be used
for the creation of root filesystems in every imaginable application
from Embedded Systems to Mini Distributions to Macro distributions to
Full sized Distributions.  The root and boot filesystems may
be tested long before implementation by using
user-mode-linux. Boot Methods are provided to allow root
filesystems to run from different types of media.
Historically, developers have written scripts which have focused on
providing a particular type of root filesystem and boot
method. Observation reveals that all these approaches share
many commonalities. gBootRoot has been designed to embrace
these similarities, and to allow developers to create drop-in methods
via modules or easy to understand templates. gBootroot is
the GIMP of distribution creation!</P>
<P><aname="2"><b>How do I use gBootRoot?</b></a> <ahref="#FAQ">[back]</a></P>
<center><u>Test an existing mini distribution.</u></center>
Learn how from this tutorial that focuses primarily on the Yard
Method:
<p>
3. Run
gbootroot. Click on the Advanced Root Section (ARS), click on
the UML button. Select root_fs_tomrtbt_1.7.205, add devfs=nomount
to the options, and click on the Submit
button.</p>
<center><u>Create a boot and root floppy for an existing mini distribution.</u></center>
<p>
4. Click on the Advanced Boot
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
press on the Root Filesystem button and select root_fs_tomrtbt_1.7.205.bz2.
</p>
5. Click the Submit button on the main
box. Have two floppy disks ready.
<u>Test an existing mini distribution.</u>
<p>
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
prompt to insert the root disk.</p>
Run gbootroot. Click on the Advanced Root Section (ARS),
click on the UML button. Select
/usr/lib/bootroot/root_filesystem/root_fs_helper, and click on the
Submit button.</p>
<center><u>Test a macro distribution created by make_debian-X11.</u></center>
<u>Test a macro distribution created by make_debian-X11.</u>
freesource
22 years ago