@ -480,7 +480,7 @@ 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">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>
15. <ahref="#15">gBootRoot doesn't start because it can't locate Gtk.pm?</a>
15. <ahref="#15">gBootRoot doesn't start because it can't locate Gtk.pm?</a>
<br>
<br>
@ -1125,7 +1125,7 @@ the kernel.
So you are probably wondering what all this has to do with the large initrd
So you are probably wondering what all this has to do with the large initrd
size when using the 2 disk compression method.
size when using the 2 disk compression method.
Linuxrc can be anything, from a statically-linked executable to a script
Linuxrc can be anything from a statically-linked executable to a script
which requires the dynamically-linked ash executable.
which requires the dynamically-linked ash executable.
In the case of the 2
In the case of the 2
disk compression method, the later method is employed, and this uses
disk compression method, the later method is employed, and this uses