Re: corrections to the Installation manual
On Fri, Feb 26, 1999 at 02:26:21PM +0100, Stephane Bortzmeyer wrote:
> > install.sgml, line 1784:
> > for a list of other software that may do the trick. Note that if you
> > have Windows 95, you must run <prgn>defrag</prgn> from there, since
> > DOS doesn't understand the FAT32 type disk allocation tables sometimes
> > used in Windows 95 and higher.
> > What DOS doesn't understand is VFAT (support for long names), always
> > used in Windows 95 and higher.
>
> Are you sure? The Fips documentation says nothing at all about this issue?
<digging through old junk> A magazine from 1995 says:
``It is important that for defragmenting, which can speed up the
computer several times, only the distributed [with Windows 95]
Defragmenter is used, since older programs of this type, like Norton
Speedisk, do not recognize the VFAT structure and will corrupt data
on the disk.''
More corrections:
install.sgml, line 3108:
> You can do two things at the <tt>boot:</tt> prompt. You can press the
> function keys <em>F1</em> through <em>F10</em> to view a few pages of
> helpful information, or you can boot the system.
The function keys aren't available on sparc nor vme (probably other
platforms too).
install.sgml, line 3332:
> If your monitor is only capable of displaying black-and-white, press
> <em>Enter</em> to continue with the installation. <![ %m68k [ If you
> have a A2024 monitor, you might need to choose the black-and-white
> option. ]]> Otherwise, use the arrow keys to move the cursor to the
> <em>Color</em> menu item and then press <em>Enter</em>. The display
> should change from black-and-white to color. Then press
The Color option, not Monochrome, is the default one
(utilities/dinstall/color_or_monochrome.c:41).
install.sgml, line 4289:
> The &RESCUE-FLOPPY; has an MS-DOS filesystem, and you should be
The sparc, vme and some alphas use an ext2 filesystem. This whole
chapter seems a bit i386-centric.
Some spelling fixes:
--- install.sgml.orig Sun Mar 7 13:00:23 1999
+++ install.sgml Sun Mar 7 19:18:53 1999
@@ -994,7 +994,7 @@
and the <url id="&url-alpha-marc;" name="Debian ALPHA Installation HOWTO">.
<p>
Yes, there are several installation guides and you have to browse them all. We
-apologize for the inconvenience but this reflect the recent work done on the
+apologize for the inconvenience but this reflects the recent work done on the
Alpha.
]]>
@@ -1541,7 +1541,7 @@
<![ %m68k [
<item>
-The first ASCI devices is named ``/dev/ada'', the second is named
+The first ACSI device is named ``/dev/ada'', the second is named
``/dev/adb''. ]]>
</list>
@@ -1777,7 +1777,7 @@
The following recipe is for partition with Apple's <prgn>HD SC Setup</prgn>.
<p>
Whatever tool you use, the partition type has to be set to
-``Apple_Unix_SVR2''. The partition names names need to be ``A/UX
+``Apple_Unix_SVR2''. The partition names need to be ``A/UX
Root'', ``A/UX Root&Usr'' or ``A/UX Usr'' for data partitions; and
``A/UX swap'' for swap partitions. <prgn>HD SC Setup</prgn> will use
the right names and type when creating A/UX partitions in a ``Custom''
@@ -2420,7 +2420,7 @@
10MB free. We recommend you unpack it into the main directory.
<item>
After unpacking, you should have a <file>debian</file> directory.
-Move &base-disk-tarball; into that same <file>debian</file>
+Move <file>&base-disk-tarball;</file> into that same <file>debian</file>
directory. Do not rename any files in this directory.
<item>
Write down the Linux partition name for the location where your new
@@ -2510,7 +2510,7 @@
directory. Do not rename any files in this directory.
<item>
Write down the Linux partition name for the location where your new
-<file>debian</file> directory is. See <ref id="disk-naming"> Linux'
+<file>debian</file> directory is. See <ref id="disk-naming">
for more information on Linux partition naming.
<item>
Prepare your partitions for Linux, if you haven't already done so. See
@@ -2665,7 +2665,7 @@
look for is
<file><var>client-ip-in-hex</var>.<var>client-architecture</var></file>.
To compute <var>client-ip-in-hex</var>, take each byte of the client
-IP address and translate it into hexadecimal notation. You have you
+IP address and translate it into hexadecimal notation. If you
have a machine handy with the <prgn>bc</prgn> program, you can use the
program. First issue the <tt>obase=16</tt> command to set the output
to hex, then enter the individual components of the client IP one at a
@@ -2674,7 +2674,7 @@
names, such as ``SUN4M'' or ``SUN4C''; in some cases, the architecture
is left blank, so the file the client looks for is just
<file>client-ip-in-hex</file>.]]> Once you've determined the name,
-make the link like so: <tt>ln /boot/tftpboot.img
+make the link like this: <tt>ln /boot/tftpboot.img
/boot/<var>file-name</var></tt>.
<p>
Now you should be ready to actually boot your system. <![ %sparc [ On
@@ -3256,7 +3256,7 @@
Depending on the nature of the bug, it also might be useful to report
the disk model, disk capacity, and the model of video card.
<p>
-In the bug report, describes what the problem is, including the last
+In the bug report, describe what the problem is, including the last
visible kernel messages in the event of a kernel hang. Describe the
steps that you did which brought the system into the problem state.
@@ -3659,7 +3659,7 @@
&MSG-CONFIGURE-MODULES;. You will be asked which PCMCIA controller
your system contains. In most cases, this will be <tt>i82365</tt>.
In some cases, it will be <tt>tcic</tt>; your laptop's vendor-supplied
-specifications should provide the information if in doubt. The You
+specifications should provide the information if in doubt. You
can generally leave the next few sets of options blank. Again,
certain hardware has special needs; the <url id="&url-pcmcia-howto;"
name="Linux PCMCIA HOWTO"> contains plenty of information in case the
@@ -3672,7 +3672,7 @@
modules using <prgn>insmod</prgn> and <prgn>rmmod</prgn>.
<p>
Once PCMCIA is properly configured and installed, you should jump back
-up and configure your device drivers as described in the previous
+up and configure your device drivers as described in the next
section.
]]>
@@ -3707,7 +3707,7 @@
<p>
You'll have to configure the network even if you don't have a network,
but you'll only have to answer the first two questions --
-&MSG-CHOOSE-HOST;, and ``is your system connected to a network?''.
+&MSG-CHOOSE-HOST;, and ``Is your system connected to a network?''.
<p>
If you are connected to a network, you'll need the information you
collected from <ref id="needed-info">. However, if your primary
@@ -3744,7 +3744,7 @@
If you choose to install from a filesystem on the harddisk or from
CD-ROM, you will be prompted to specify the path to the
<file>&base-disk-tarball;</file>. As with the &MSG-INSTALL-OS; step,
-you can either let ``dbootstrap'' find the file on itself or type in
+you can either let <prgn>dbootstrap</prgn> find the file on itself or type in
the path at the prompt.
<p>
If you choose to install from floppy disk, feed in the base floppies
@@ -3874,7 +3874,7 @@
&RESCUE-FLOPPY;), or insert the Custom Boot floppy if you created one,
and reset your system. If you are <em>not</em> using the Custom Boot
floppy, you will probably need to add some boot arguments. If booting
-with the &RESCUE-FLOPPY or similar technique, you need to specific
+with the &RESCUE-FLOPPY or similar technique, you need to specify
<tt>rescue root=<var>root</var></tt>, where <var>root</var> is your
root partition, such as ``/dev/sda1''.
<p>
@@ -4098,7 +4098,7 @@
versions), then look in <file>/usr/doc/HOWTO</file>. International
versions of the LDP HOWTOs are also available as Debian packages.
<p>
-information specific to Debian can be foud below.
+Information specific to Debian can be found below.
<sect id="debian-orientation">Orienting Yourself to Debian
@@ -4151,7 +4151,7 @@
<sect id="kernel-baking">Compiling a New Kernel
<p>
-Why would someone wants to compile a new kernel? It is often not
+Why would someone want to compile a new kernel? It is often not
necessary since the default kernel shipped with Debian handles most
configurations. However, it is useful to compile a new kernel in order
to:
--- release-notes.sgml.orig Thu Mar 4 13:00:24 1999
+++ release-notes.sgml Sun Mar 7 19:04:53 1999
@@ -228,7 +228,7 @@
steps of <prgn>dselect</prgn> initially. As soon as you enter
``Select'' you should press <em>Enter</em> immediately. A
conflict/depend resolution screen will probably be presented. After
-resolving the conflicts (usually you can just press <em>Enter</em>,
+resolving the conflicts (usually you can just press <em>Enter</em>),
run ``Install'', and then ``Configure'' to simply upgrade all
installed packages. After that you may use the ``Select'' and
``Install'' modules to install additional packages, if desired.
@@ -349,7 +349,7 @@
The <package>xbase</package> should be removed. Leaving it in place will
make it necessary to supply the <tt>--force-depends</tt> option to dpkg to
remove any package that xbase depends on (such as <package>xdm</package> or
-<package>xfs</package>.
+<package>xfs</package>).
<example>
dpkg --remove xbase
</example>
Reply to: