1
0
mirror of https://github.com/fspc/gbootroot.git synced 2025-02-23 09:03:23 -05:00

A few grammar fixes.

This commit is contained in:
freesource 2002-01-07 19:24:44 +00:00
parent 975d04da6d
commit 1daab59cf6

View File

@ -3,7 +3,7 @@
<body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#51188E"
alink="#FF0000">
<center>$Id: index.html,v 1.63 2002/01/07 19:05:25 freesource Exp $</center>
<center>$Id: index.html,v 1.64 2002/01/07 19:19:47 freesource Exp $</center>
<p>
@ -480,7 +480,7 @@ and things should become more clear.
<br>
13.&nbsp;&nbsp;<a href="#13">I've created a root fs.&nbsp;&nbsp;Then I've tried to create the boot disk using the 2 disk compression method.&nbsp;&nbsp;The device selection is /dev/fd0, size is 1440k, but the initrd_image.gz is 715k.&nbsp;&nbsp;I don't know much about boot disks but shouldn't the boot disks contain mainly the kernel?</a>
<br>
14.&nbsp;&nbsp;<a href="#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.&nbsp;&nbsp;<a href="#14">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 the size of the kernel?</a>
<br>
15.&nbsp;&nbsp;<a href="#15">gBootRoot doesn't start because it can't locate Gtk.pm?</a>
<br>
@ -1125,7 +1125,7 @@ the kernel.
So you are probably wondering what all this has to do with the large initrd
size when using the 2 disk compression method.&nbsp;&nbsp;
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.&nbsp;&nbsp;
In the case of the 2
disk compression method, the later method is employed, and this uses