Browse Source

The FAQ was updated, the images have to be updated again, and message() in

gbootroot.
master
freesource 23 years ago
parent
commit
dec7e6a3dc
  1. 113
      doc/html/index.html

113
doc/html/index.html

@ -326,45 +326,86 @@ filesystem.</P>
<P><b>What's the advantage of using this program?</b></P>
<P>You can use a bzip2 compressed filesystem, this program is easy to use, and it provides a framework showing a simple initrd method which you can freely
modify.&nbsp;&nbsp; I wrote this program as an extension to BootRoot which was written
<p>
(Explanation from the first gbootroot.)<br>
"You can use a bzip2 compressed filesystem, this program is easy to use, and
it provides a framework showing a simple initrd method which you can freely
modify.&nbsp;&nbsp;
I wrote this program as an extension to BootRoot which was written
as a solution to help oster at EE (www.experts-exchange.com) create separate
boot and root floppies for an emergency system for his customers.</P>
boot and root floppies for an emergency system for his customers."</P>
<P><A href="./bootroot.html">BootRoot</A>
was the original program, but it was decided that a GUI approach
was the original program, but I decided that a GUI approach
provided the user much more versatility and power in creating distributions.
</P>
&nbsp;&nbsp; Since the first gBootRoot,
bOOTrOOT has become a full blown distribution creation program.</P>
<P>If you make a cool change to this program, or if this program helps you I'd love to know, that's better than receiving pizza. :)</P>
<P><b>How can I test gBootRoot?</b></P>
<P>1. Download
<P>1.&nbsp;&nbsp; Download
<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 user-mode-linux at Sourceforge.</p>
root_fs_tomrtbt_1.7.205.bz2</a> from
<a href="http://www.sourceforge.net/projects/user-mode-linux">
user-mode-linux</a> at Sourceforge to your
$HOME/.gbootroot/root_filesystems. </p>
<p>
2.
[Ctrl] ([Tab] to see available images)
<br> boot: bootdisk single [Enter]
<br> ( now filesystem is single user mode)
<br> exit [Enter]
<br> (now you are in multi user mode)
2.&nbsp;&nbsp; bzip2 -dc root_fs_tomrtbt_1.7.205.bz2 > root_fs_tomrtbt_1.7.205.
</p>
<p>
Better yet, do [Ctrl]
<br> boot: bootdisk 2 [Enter]
3.&nbsp;&nbsp; Run gbootroot.&nbsp;&nbsp;
Click on the Advanced Root Section, click on
the UML button. &nbsp;&nbsp; Select root_fs_tomrtbt_1.7.205, and click on the Submit
button.</p>
<P><b>Why doesn't looplinux work as &quot;bootdisk 1?&quot;</b></P>
<P>There is a difference between &quot;1&quot; and &quot;single.&quot; Looplinux was written in a
way that runlevel 1 doesn't work properly in relation to gBootRoot unless
single is used.&nbsp;&nbsp; And you thought they were the same thing?&nbsp;&nbsp; gBootRoot
proves otherwise. </P>
<p>
4.&nbsp;&nbsp; Click on the Advanced Boot Section.&nbsp;&nbsp;
Root_fs_tomrtbt is about 16M, so add ramdisk_size=16384 to
the 'append=' entry. &nbsp;&nbsp;
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.&nbsp;&nbsp; Click the Submit button on the main box.&nbsp;&nbsp;
Have two floppy disks ready.
<p>
6.&nbsp;&nbsp; When you see Lilo you may access the menu using [Ctrl] and
[Tab] to see the available images.
<P><b>My root filesystem doesn't start in single mode when started like
this:&nbsp;&nbsp &quot;bootdisk 1?&quot;</b></P>
<P>
When you start a kernel image with 1, you are telling it to start in runlevel
1, not in single mode.&nbsp;&nbsp Use "single" instead.</p>
<p>
Why on the subject, it should be pointed at the setting up init and its
runlevels is one of the
most challenging areas of creating a bootable root_fs.&nbsp;&nbsp Often
your creation will only work with "single" until all the conflicts
are resolved.&nbsp;&nbsp Things are complicated even futher by the fact that
devices can now be set up in two majors ways: tty? or ttys/? (devfs).
&nbsp;&nbsp Fortunately, user-mode-linux comes in very handy for hunting
down all the bugs.
</P>
<P><b>gBootRoot doesn't start because it can't locate Gtk.pm?</b></P>
<p>This program requires Gtk-Perl available from <a href="http://www.perl.com/CPAN">CPAN</a>, <a href="http://freshmeat.net/projects/gtk-perl">Freshmeat</a> or most GNU/Linux distributions.</p>
<p><b>There isn't enough room left on my 1440 floppy to make a Boot or Root
disk.&nbsp;&nbsp;Is there any way to free up more space apart from reducing
@ -373,6 +414,34 @@ the size of the kernel?</b></p>
<p>
Move the device size to 1722. This is a trick that <a href="http://www.toms.net/rb/">tomsrtbt</a> uses on his famous rescue disk.</p>
<p>
(Update 10/05/2001) <br>
Up until mke2fs version 1.19 you were able to do
`mke2fs -F /dev/fd0 1722` on a 1440 device without any problem, but since
then mke2fs has become much more particular about enforcing actual device
size. .&nbsp;&nbsp; Mke2fs will complain:</p>
<p>
"mke2fs: Attempt to write block from filesystem resulted in short write
zeroing block 1600 at end of filesystem."</p>
<p>
I understand Theodore Ts'o reasoning for doing this, but I strongly believe
that the old behavior was very useful for people creating
mini-distributions so I have issued Feature Request (#) at (here).&nbsp;&nbsp;
It should be noted that fdformat is an unacceptable solution because it tends
to be machine specific, and the original mke2fs behavior made floppies that
worked everywhere.&nbsp;&nbsp;
Feel free to add your comments to the Feature Request.&nbsp;&nbsp; Thanks.</p>
<p>
<b>gBootRoot doesn't start because it can't locate Gtk.pm?</b></P>
<p>This program requires Gtk-Perl available from <a href="http://www.perl.com/CPAN">CPAN</a>, <a href="http://freshmeat.net/projects/gtk-perl">Freshmeat</a> or most GNU/Linux distributions.</p>
<p><b>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.</b></p>

Loading…
Cancel
Save