diff --git a/doc/html/index.html b/doc/html/index.html index 9cbbd8d..066330f 100644 --- a/doc/html/index.html +++ b/doc/html/index.html @@ -3,7 +3,7 @@
-
@@ -49,15 +49,18 @@ their sources.list:
deb http://prdownloads.sourceforge.net/avd ./
Older versions found at this -site
and
-How to Use gBootRoot
+How to Use gBootRoot's UIThe most important button to familiarize yourself with is the Submit button which starts the whole process; dialogs are presented as the process continues asking you if you want to @@ -356,41 +359,38 @@ $HOME/.gbootroot/yard/.
FAQ
-- - -What's the advantage of using this program? [back] - -How can I test gBootRoot? - -What are all these CVS directories doing in my replacements? - -Can I use a program linked to uClibc in the template? - -What do you mean by macro distribution? - -How am I able to create root filesystems as a normal user? - -How can a normal user create a root filesystem larger than 8192k? - -How can I create boot disks as a normal user? - -What is make_debian, and how do I use it? - -My root filesystem doesn't start in single mode when started like this: "bootdisk 1?" - -What does the 2 disk compression method do? - -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? - -gBootRoot doesn't start because it can't locate Gtk.pm? - -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. - -+ +1. What's the advantage of using this program? +
What's the advantage of using this program?
+What's the advantage of using this program? [back]
BootRoot was the original program, but I decided that a GUI approach @@ -407,19 +407,14 @@ 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 booting method. Observation, reveals that all these +filesystem and boot method. Observation, reveals that all these approaches share many commonalities. gBootRoot has been designed to embrace these similiarities, and to allow developers to create drop-in methods via modules or easy to understand templates. gBootroot is the GIMP of distribution creation!
-How can I test gBootRoot?
- -- -(Note: You may run most of these tests as a normal user. -See the exceptions which apply in the FAQ.)
+How do I use gBootRoot? [back]
- -What are all these CVS directories doing in my replacements?
+What are all these CVS directories doing in my replacements? [back]
CVS directories are deliberately put in the Replacement directories to @@ -610,7 +603,7 @@ not to delete the CVS directories because /usr/share is meant to be used for data which shouldn't be modified (see FHS).
-Can I use a program linked to uClibc in the template? +Can I use a program linked to uClibc in the template? [back]@@ -621,7 +614,7 @@ is used to discover shared library dependencies, otherwise ldd is called without any path.
-What do you mean by macro distribution? +What do you mean by macro distribution? [back]@@ -638,7 +631,7 @@ used to run experiments safely without fear of corrupting the host system via user-mode-linux.
-How am I able to create root filesystems as a normal user? +How am I able to create root filesystems as a normal user? [back]@@ -654,7 +647,7 @@ can be changed when the filesystem is run from a kernel.
-How can a normal user create a root filesystem larger than 8192k?
+How can a normal user create a root filesystem larger than 8192k? [back]@@ -724,7 +717,7 @@ don't exist. For this example, /mnt1 and
-7. Mount the host filsystem on /mnt2: +7. Mount the host filesystem on /mnt2:
mount -t hostfs none -o /tmp/gboot_non_root_1000/loopback /mnt2@@ -750,16 +743,18 @@ don't exist. For this example, /mnt1 and
-How can I create boot disks as a normal user?
+How can I create boot disks as a normal user? [back]-Make the boot disk as you normally would. Not all boot loaders -can be set-up as a non-root user, however, you may still continue to +Make the boot disk as you normally would. As long as you have +write permissions to the boot device you shouldn't run +into a problem. However, not all boot loaders +can be set-up as a non-root user, but, you may still continue to the end of the process and set-up the boot loader later from a machine you have root access on. In order to use lilo while running gbootroot there -are two pre-requisites your administrator will have to establish for you. +are two prerequisites your administrator will have to establish for you. First, he will have to edit the fstab to allow you to mount a certain block device. For instance, to allow you to mount /dev/fd0, you have to mount the /tmp/gboot_non_root_mnt_`id -u` directory. If @@ -772,9 +767,9 @@ your UID is 1000, then a line like this is added to the fstab: Next, the administrator needs to give you access to the lilo command. Sudo is a good solution, and in gbootroot the -$sudo variable is assigned "sudo", this can be changed by the administrator -to some other sudo-like program. The administrator then uses -visudo to edit the sudoers file with a line like this: +$main::sudo variable is assigned "sudo", this can be changed by the +administrator to some other sudo-like program. The administrator +then uses visudo to edit the sudoers file with a line like this:
user hostname = NOPASSWD: /sbin/lilo @@ -782,14 +777,16 @@ user hostname = NOPASSWD: /sbin/lilo-Note, that NOPASSWD is used. Gbootroot won't prompt for a password, +Note that NOPASSWD is used. Gbootroot won't prompt for a password, and just assumes no password in necessary. I could change this -behavior if people request it. Now a bootdisk with lilo can be -made. +behavior if people request it. If modules are required for +the boot method to work properly, you need to have read +permissions to them so they can be copied. Now a bootdisk with +lilo can be made.
-What is make_debian, and how do I use it?
+What is make_debian, and how do I use it? [back]@@ -840,8 +837,8 @@ in the template was modified to reflect these replacements.
-My root filesystem doesn't start in single mode when started like -this:  "bootdisk 1?" +My root filesystem doesn't start in single mode when started like +this:  "bootdisk 1?" [back]@@ -864,16 +861,16 @@ down all the bugs.
-What does the 2 disk compression method do?
+What does the 2 disk compression method do? [back]
This Boot Method creates a boot disk with lilo, a kernel and an initrd image. The initrd script mounts another root disk with a compressed (gzip or bzip2) filesystem.
-There isn't enough room left on my 1440 floppy to make a Boot or Root +
+the size of the kernel? [back]Move the device size to 1722. This is a trick that tomsrtbt uses on his famous rescue disk.
@@ -907,11 +904,12 @@ to add your comments to the Feature Request. Thanks.-gBootRoot doesn't start because it can't locate Gtk.pm?
+gBootRoot doesn't start because it can't locate Gtk.pm? [back] +This program requires Gtk-Perl available from CPAN, Freshmeat or most GNU/Linux distributions.
-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.
+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. [back]
This is because of the way Gtk works. There are two adjustments,