@ -480,14 +480,25 @@ and things should become more clear.
<br>
<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>
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>
<br>
14. <ahref="#14">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>
14. <ahref="#14">If libc is included in the boot disk, why is it needed in the root disk as well?</a>
<br>
<br>
15. <ahref="#15">gBootRoot doesn't start because it can't locate Gtk.pm?</a>
15. <ahref="#15">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>
<br>
16. <ahref="#16">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>
16. <ahref="#16">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>
17. <ahref="#17">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>
18. <ahref="#18">What is the root_fs_helper 2Mb file in the grootboot package?</a>
<br>
19. <ahref="#19">
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>
20. <ahref="#20">gBootRoot doesn't start because it can't locate Gtk.pm?</a>
<br>
21. <ahref="#21">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>
</a>
</a>
<br>
<br>
17. <ahref="#17">Changing from gz to bz2 compression for the boot image in the main section has no effect and gzip is still exectuted.</a>
22. <ahref="#22">Changing from gz to bz2 compression for the boot image in the main section has no effect and gzip is still exectuted.</a>
<br>
<br>
<P><aname="1"><b>What's the advantage of using this program?</b></a> <ahref="#FAQ">[back]</a></P>
<P><aname="1"><b>What's the advantage of using this program?</b></a> <ahref="#FAQ">[back]</a></P>
@ -1165,7 +1176,28 @@ Unfortunately (or fortunately for root filesystem making, a process which
used to take days), I've been devoting a lot of time to the ARS, but
used to take days), I've been devoting a lot of time to the ARS, but
hopefully I'll be adding major changes to the ABS in the near future.
hopefully I'll be adding major changes to the ABS in the near future.
<p><aname="14"><b>There isn't enough room left on my 1440 floppy to make a Boot or Root
<p>
<aname="14"><b>If libc is included in the boot disk, why is it needed in the root disk as
I don't want to take all the fun away from you. There is a
config for the uml kernel in
/usr/lib/bootroot/yard/Replacements/lib/modules. If you get
it running with uml, and it doesn't run with your own kernel, take a look
here.
<p>
<aname="18"><b>What is the root_fs_helper 2Mb file in the grootboot package?</b></a> <ahref="#FAQ">[back]</a></P>
<p>
This is the ultimate in root filesystem engineering. The root
filesystem helper is actually a much bigger filesystem made with cramfs, and it
originated from a genext2fs filessytem made as a normal user.
It includes
utilities like filesystem creators. It is part of the automated
filesystem creation system, and after it is booted by uml, it is
intereacted with via expect based on user choices placed in the filesystem
box. Considering that mkreiserfs doesn't allow loop devices to
be used,
this is an easy way to get around this limitation, and most importantly it
allows non-root users to create UID/GID 0 root filesystems.
Try creating a root filesystem as a normal user with both "uml exclusively" and
"preserve ownership" turned on and discover if you can successfully create
a working root filesystem. Answer: No, you will not be able
to unless preserve ownership is off.
<p>
<aname="19"><b>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.</b></a> <ahref="#FAQ">[back]</a></P>
<p>
Gbootroot is designed with the idea that new Linux users don't need to
open up the ARS or ABS; basically, they just choose a boot method, provide
a pre-made compressed root_fs and kernel, and then press the submit button
to get a two disk floppy system. What this means is
that if the ARS is
never opened then the boot and root devices will both be /dev/fd0.
But, if the ARS is opened up, then the boot device is whatever is found in the
main section, and the root device is whatever is found in the ARS.
Likewise, if the ABS is opened up, and the user decides that they would like
to do
development work on a different device than the boot device, for instance,
/dev/fd1, then they can change the device in the ABS. In this
case, the
device should be left to /dev/fd0 in the main section, unless you have one
of those amazing Bioses which allow /dev/fd1 to be booted.
At a later
date the user can run "lilo -v -C brlilo.conf -r /mnt" where /mnt
represents the mounted device provided in the main section.
<p>
<p>
<aname="15"><b>gBootRoot doesn't start because it can't locate Gtk.pm?</b></a> <ahref="#FAQ">[back]</a></P>
<aname="20"><b>gBootRoot doesn't start because it can't locate Gtk.pm?</b></a> <ahref="#FAQ">[back]</a></P>
<p>This program requires Gtk-Perl available from <ahref="http://www.perl.com/CPAN">CPAN</a>, <ahref="http://freshmeat.net/projects/gtk-perl">Freshmeat</a> or most GNU/Linux distributions.</p>
<p>This program requires Gtk-Perl available from <ahref="http://www.perl.com/CPAN">CPAN</a>, <ahref="http://freshmeat.net/projects/gtk-perl">Freshmeat</a> or most GNU/Linux distributions.</p>
<p><aname="16"><b>If you roll the floppy density counter down to 0 and then try go back
<p><aname="21"><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></a> <ahref="#FAQ">[back]</a></p>
up towards 1440 and 1722, you get very funny figures.</b></a> <ahref="#FAQ">[back]</a></p>
<p>
<p>
@ -1252,7 +1372,7 @@ page up with the second button to 1440 and step with the first button to
<LI> Ctrl-V Paste from clipboard </LI>
<LI> Ctrl-V Paste from clipboard </LI>
</UL>
</UL>
<p><aname="17"><b>Changing from gz to bz2 compression for the boot image in the main section has no effect and gzip is still exectuted.</b></a> <ahref="#FAQ">[back]</a></p>
<p><aname="22"><b>Changing from gz to bz2 compression for the boot image in the main section has no effect and gzip is still exectuted.</b></a> <ahref="#FAQ">[back]</a></p>
freesource
23 years ago