The first row presently has only one Boot Method choice: -"2 disk compression." -Clicking on the menu on the right selects the Boot Method.
+"2 disk compression." Clicking on the menu on the right selects +the Boot Method. -The second row allows you to select the kernel for the Boot/Root set. You +
The second row allows you to select the kernel for the Boot/Root set. You may either use the file selector button on the right hand side, or you may type in the location on the left hand side.
The third row allows you to select the compressed filesystem you are -providing, using either of the two ways mentioned before. You may use a +providing, using either of the two ways mentioned before. You may use a pre-made root filesystem or you may create one using one of the Methods provided in the Advanced Root Section.
-The fourth row allows you to select the device you want to use. The default +
The fourth row allows you to select the device you want to use. The default device is the first floppy disk - /dev/fd0.
-The fifth row allows you to choose the size of the device being used. -The default size of 1440 assumes you are using a floppy drive (Note: You may +The fifth row allows you to choose the size of the device being used. The default size of 1440 assumes you are using a floppy drive +(Note: You may want to experiment with 1722 which works fine with many floppy drives.), but -can be used with other sized devices like tape drives. Click on the +can be used with other sized devices like tape drives. Click on the appropriate radio button to choose either gzip or bzip2 compression if the program doesn't automatically detect it.
@@ -71,8 +71,8 @@ program doesn't automatically detect it. The slider bar on the right allows the output of the verbosity box to be changed from the highest (2) to the lowest setting (1) or to be turned off (0) -or on again. -At times it may be advantageous to turn off the verbosity box +or on again. At times it may be advantageous to turn off the +verbosity box since large quantities of output to this box may cause gbootroot to use too much cpu power; however, output may still be found in the text file "verbose" in /tmp/gbootroot_tmp'time-date'. @@ -84,108 +84,120 @@ Using the Advanced Boot Section
-"Stripping" On by default for libraries and binaries. The stripping
+Libraries & Binaries & Modules check boxes: Turn off and on the
+stripping of symbols. The stripping
behavior for libraries may be changed by clicking on the right mouse button
-to change from --strip-debug to --strip-all.
-"Devel Device" If the device used for development is different than the -actual boot device, use this field to indicate that device. You will have to +"Devel Device" If the device used for development is different than the +actual boot device, use this field to indicate that device. You will have to run lilo -v -C brlilo.conf -r "device mount point" manually at a later time on the actual boot device.
-"Opt. Device" Add devices to the boot disk which are necessary for the -kernel to function properly. -Put a space between each device. -For instance, /dev/fb0 for frame buffer devices.
+"Opt. Device" Add devices to the boot disk which are necessary for the +kernel to function properly. Put a space between each +device. For instance, /dev/fb0 for frame buffer devices.-"Kernel Module" Add the modules found in +"append =" Add append options to brlilo.conf. If you are using a frame +buffer device you could add something like video=matrox:vesa:402,depth:16.
+ ++ +"Kernel Module" Add the modules found in /lib/modules/kernel-version which are necessary for the Boot Method to work -properly. -If these modules aren't found in the modules directory it is assumed -that they either are in the kernel or they do not exist. -In the case of 2 disk compression, floppy needs to be included in the -kernel or included as a module. -Kmod inserts the modules, and kmod needs to be built into the kernel along -with initrd and ramdisk.",
+properly. If these modules aren't found in the modules directory +it is assumed +that they either are in the kernel or they do not exist. In the +case of 2 disk compression, floppy needs to be included in the +kernel or included as a module. Kmod inserts the modules, and +kmod needs to be built into the kernel along +with initrd and ramdisk."-"append =" Add append options to brlilo.conf. If you are using a frame -buffer device you could add something like video=matrox:vesa:402,depth:16.
+"Kernel Version" Override the kernel version number found in the +kernel header. This will change the /lib/modules/kernel-version +directory. + +
+
+System.map: When a non-running kernel is chosen it is important
+to include a copy of that kernel's System.map file so that depmod can use
+the correct set of kernel symbols to resolve kernel references in each
+module. This can be found in the kernel's source code after
+compilation.
-
+
Using the Advanced Root Section
-"Root Device"
-This is the device used for the root filesystem when
-constructing the Boot/Root set.
-You may choose a device which is different
+"Root Device" This is the device used for the root filesystem when
+constructing the Boot/Root set. You may choose a device which is
+different
than the Boot device, but presently only floppy devices are supported.
-"Root Device Size" The size of the actual media used for the Root Device.
+"Root Device Size" The size of the actual media used for the Root Device.-"Root Filename" - The name give to the root filesystem when initially made -in the temporary creation location. -The save button allows the creation to +"Root Filename" The name give to the root filesystem when +initially made in the temporary creation location. The save +button allows the creation to be saved in the permanent default location when the Accept button is pressed.
-"Filesystem Size" - Root Methods make the filesystem the size which is -specified here.
+"Filesystem Size" Root Methods make the filesystem the size +which is specified here.-"Compression" -Off by default to allow user-mode-linux testing. Turn on +"Compression" Off by default to allow user-mode-linux +testing. Turn on compression when you are ready to use a Boot Method which requires compression.
-"Method" The root filesystem creation method.
+"Method" The root filesystem creation method.-"Template" The template associated with a Root Method. - Not all Root Methods +"Template" The template associated with a Root +Method. Not all Root Methods have templates.
-"Generate" This puts the chosen Root Method in action.
+"Generate" This puts the chosen Root Method in action.-"UML" Abbreviation for user-mode-linux. - This is a linux kernel which runs on +"UML" Abbreviation for user-mode-linux. This is a +linux kernel which runs on top of the host system's linux kernel and allows a you run a live root filesystem.
-"Accept" -This accepts the created root filesystem if it is found in the -temporary creation directory. -The UML box and the main section will now -reflect the path to this root filesystem. - You can now test with the UML +"Accept" This accepts the created root filesystem if it is +found in the +temporary creation directory. The UML box and the main section +will now +reflect the path to this root filesystem. You can now test with +the UML button or a put together a complete Boot/Root set with the Submit button.
-"Xterm" Choose an xterm with its executable options switch.
@@ -203,12 +215,12 @@ devfs=nomount.
-"Root_Fs" Choose an uncompressed root filesystem. -Append with ubd?=.
+"Root_Fs" Choose an uncompressed root +filesystem. Append with ubd?=.-"Abort" Abort user-mode-linux kernel processes.
+"Abort" Abort user-mode-linux kernel processes.@@ -217,31 +229,31 @@ About the Yard Box
The check boxes at the bottom represent the different stages involved in -creating a root filesystem. - The behavior of these stages may be altered in +creating a root filesystem. The behavior of these stages +may be altered in three ways: Edit->Stages->one-by-one (default) will perform each stage sequentially, stopping between each stage, the user may continue the process -by pressing the Continue button. -Edit->Stages->continuous proceeds non-stop -through all the stages. -Edit->Stages->'user defined' allows the user to +by pressing the Continue +button. Edit->Stages->continuous proceeds non-stop +through all the +stages. Edit->Stages->'user defined' allows the user to choose any stages the user wants, and will then proceed through all the -chosen stages. -Choosing only 'Check', 'Links & Deps', 'Create" is a good +chosen +stages. Choosing only 'Check', 'Links & Deps', 'Create" is a good example.
-The behavior of some of the stages may be altered. -For instance Alt-T allows +The behavior of some of the stages may be +altered. For instance Alt-T allows you to choose which tests to run on the newly created root filesystem.
@@ -250,21 +262,19 @@ root filesystem.Press Alt-S to enable template text searching in either -direction. -Find exact matches or ignore case with the case sensitive check -box.
+direction. Find exact matches or ignore case with +the case sensitive check box.
Use Ctl-S to save the changes to an open template, and Alt-A to save the -template with a new name. -bOOTrOOT will not allow read-only templates or template links to be saved -with their own name. -A few of these example files are included. -You may make changes to them or clear their buffers. -Then you may save the template with a +template with a new name. bOOTrOOT will not allow read-only +templates or template links to be saved +with their own name. A few of these example files a +re included. You may make changes to them or +clear their buffers. Then you may save the template with a different name.
Edit->Settings->Stripping allows you to turn off/on stripping for -Libraries, Binaries, and Modules. ---strip-all is the default for binaries and libraries, +Libraries, Binaries, and Modules. --strip-all is the +default for binaries and libraries, and --strip-debug is the default for modules; however libraries may be changed to --strip-debug in the settings.
@@ -291,8 +301,8 @@ environments $PATH variable.Edit->'File System" may alter the type of filesystem used to make the root -filesystem. -Because the filesystem is created on a loop device, some +filesystem. Because the filesystem is +created on a loop device, some filesystem types may complain or not be created at all.
-Create->Replacements creates special replacement files. -Presently it creates +Create->Replacements creates special replacement +files. Presently it creates an fstab configuration file as Replacements/etc/fstab.new in $HOME/.gbootroot/yard/.
Little things you may want to know:
-* gBootRoot requires ash for initrd. Ash is a feather weight version of Bash.
+* gBootRoot requires ash for initrd. Ash is a feather weight version of Bash.
FAQ
What does the 2 disk compression method do?
This Boot Method creates a boot disk with lilo, a kernel and an initrd -image. The +image. The initrd script mounts another root disk with a compressed (gzip or bzip2) filesystem.
@@ -331,22 +341,22 @@ filesystem. (Explanation from the first gbootroot.)BootRoot 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, + Since the first gBootRoot, bOOTrOOT has become a full blown distribution creation program.
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. :)
How can I test gBootRoot?
-1. Download +
1. Download root_fs_tomrtbt_1.7.205.bz2 from @@ -356,50 +366,53 @@ $HOME/.gbootroot/root_filesystems.
-2. bzip2 -dc root_fs_tomrtbt_1.7.205.bz2 > root_fs_tomrtbt_1.7.205. +2. bzip2 -dc root_fs_tomrtbt_1.7.205.bz2 > root_fs_tomrtbt_1.7.205.
-3. Run gbootroot. -Click on the Advanced Root Section, click on -the UML button. Select root_fs_tomrtbt_1.7.205, and click on the Submit +3. Run +gbootroot. Click on the Advanced Root Section, click on +the UML button. Select root_fs_tomrtbt_1.7.205, and click on the Submit button.
-4. Click on the Advanced Boot Section. -Root_fs_tomrtbt is about 16M, so add ramdisk_size=16384 to -the 'append=' entry. -From the main box choose '2 disk compression', and +4. Click on the Advanced Boot +Section. 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.
-5. Click the Submit button on the main box. -Have two floppy disks ready. +5. Click the Submit button on the main +box. Have two floppy disks ready.-6. When you see Lilo you may access the menu using [Ctrl] and +6. When you see Lilo you may access the menu using [Ctrl] and [Tab] to see the available images. +
+ +7. +
My root filesystem doesn't start in single mode when started like -this: "bootdisk 1?"
+this: "bootdisk 1?"When you start a kernel image with 1, you are telling it to start in runlevel -1, not in single mode. Use "single" instead.
+1, not in single mode. Use "single" instead.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. Often +most challenging areas of creating a bootable root_fs. Often your creation will only work with "single" until all the conflicts -are resolved. Things are complicated even futher by the fact that +are resolved. Things are complicated even futher by the fact that devices can now be set up in two majors ways: tty? or ttys/? (devfs). - Fortunately, user-mode-linux comes in very handy for hunting + Fortunately, user-mode-linux comes in very handy for hunting down all the bugs. @@ -420,7 +433,7 @@ Move the device size to 1722. This is a trick that 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). -It should be noted that fdformat is an unacceptable solution because it tends +mini-distributions so I have issued Feature Request (#) at +(here). 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. -Feel free to add your comments to the Feature Request. Thanks.
+worked +everywhere. Feel free +to add your comments to the Feature Request. Thanks.@@ -446,13 +461,14 @@ Feel free to add your comments to the Feature Request. Thanks.
up towards 1440 and 1722, you get very funny figures.-This is because of the way Gtk works. There are two adjustments, +This is because of the way Gtk works. There are two adjustments, step and page increments. When you press your first mouse button the step has been set to 282 so that a person can easily switch between 1440 and 1722. When you use your second mouse button the page is set at 360. You can go -down to zero by pressing your third mouse button on the down arrow. Now +down to zero by pressing your third mouse button on the +down arrow. Now page up with the second button to 1440 and step with the first button to -1722. Pretty cool, eh?
+1722. Pretty cool, eh?Why we are on this subject please check out these keyboard shortcuts for Gtk.
@@ -493,13 +509,13 @@ page up with the second button to 1440 and step with the first button to