diff --git a/doc/html/index.html b/doc/html/index.html index 8132bf2..618825d 100644 --- a/doc/html/index.html +++ b/doc/html/index.html @@ -3,7 +3,7 @@ -
$Id: index.html,v 1.47 2001/12/22 05:13:43 freesource Exp $
+
$Id: index.html,v 1.48 2001/12/22 05:39:58 freesource Exp $

@@ -625,7 +625,7 @@ system.  And that is just the beginning of the things you can do.

Oops, I can't get something to work, what should I do?  [back]

-If something isn't working for you, I want to know because you have probably +If something isn't working for you, I want to know because you probably have found a bug.  Don't fall into the trap that makes you believe that developers don't want to be deluged with bugs, quite to the contrary. developers love to receive bugs, @@ -634,7 +634,7 @@ problems.   I have experience working in Quality Assurance, and I know that a program with the complexity of gbootroot is a perfect recipe for the existence of all types of bugs.  As a developer focusing on the -deployment of code it is easy for bugs to slip by unoticed.   +deployment of code it is easy for bugs to slip by unnoticed.   Free Source software depends on users sending in bugs if the software is to ever experience rapid development; users shouldn't leave this process to the developers, because this guarantees that they will need to spend lots @@ -648,8 +648,8 @@ new features.  

Just because a project doesn't have a name like "Linux" doesn't -mean it doesn't need your love, so please send in those -bugs.   +mean that the project should live by itself without community support, +so please send in those bugs.   I consider a bug anything which effects the user negatively, whether it is a user interface (UI) which is hard to understand or use, documentation which seems misleading, or if the program doesn't @@ -761,8 +761,9 @@ User-mode-linux is used to boot up a root_fs helper, the program then communicates with the user linux system via expect to automatically create a UID/GID 0 filesystem from the files copied over from the /tmp/gboot_non_root_`id -u1/loopback directory.  The steps will -vary slightly depending on which filsystem command is chosen, however, the same -concept is used.  You may appy this to filesystems smaller than +vary slightly depending on which filesystem command is chosen, however, the +same +concept is used.  You may apply this to filesystems smaller than 8192 by adjusting the settings in the Filesystem Box.   If you want to learn how to do this manually, look at the ten steps below.