Patch for 2.1 Installation manual
Hello, I read "Installing Debian GNU/Linux 2.1 For Intel X86", dated
13th February (the .txt file). Here is output of
diff -u install.sgml.1999-02-13 install.sgml
where install.sgml is the new version. I mainly fixed typos, but there
are some proposals for corrections and clarifications.
The diff -output is at the end, here are some more general issues:
- looks like long URLs are split to two lines, and unfortunately using
hyphenation rules. This makes them split in the middle of a
word. For an example see the last line of chapter 2.
- I read the document as a preparation to translating it to Finnish. I
have not seen the other translations, they probably have my
questions already solved, but here goes: Should also cfdisk.txt,
fdisk.txt and dselect-beginner be translated?
- Where is the change log?
- There is on line in example in chapter 6.6, the cd-rom: -line does
not fit in the .txt file.
- is the rdate command available in chapter 7.12., Configure the
Network?
--- install.sgml.1999-02-14 Sun Feb 14 20:31:58 1999
+++ install.sgml Sun Feb 14 21:11:45 1999
@@ -46,7 +46,7 @@
<version>version &docversion;, &docdate;</version>
<abstract>
This document contains installation instructions for the Debian
-GNU/Linux &release; system, for the the &arch-title;
+GNU/Linux &release; system, for the &arch-title;
(``&architecture;''); architecture. It also contains pointers to more
information and information on how to make the most of your new Debian
system. The procedures in this document are <em>not</em> to be used
@@ -573,7 +573,7 @@
<p>
<![ %i386 [ Both SCSI and IDE/ATAPI CD-ROMs are supported. In
-addition, all non-standards CD interfaces supported by Linux are
+addition, all non-standard CD interfaces supported by Linux are
supported by the boot disks (such as Mitsumi and Matsushita drives).
However, these models might require special boot parameters or other
massaging to get them to work, and booting off these non-standard
@@ -702,7 +702,7 @@
etc. However, none of these devices are required while installing the
system. This section contains information about peripherals
specifically <em>not</em> supported by the installation system, even
-though may be supported by Linux.
+though they may be supported by Linux.
<![ %i386 [
@@ -784,7 +784,7 @@
<sect1>Avoid Proprietary or Closed Hardware
<p>
Some hardware manufacturers simply won't tell us how to write drivers
-for their hardware. Others they won't allow us access to the
+for their hardware. Others won't allow us access to the
documentation without a non-disclosure agreement that would prevent us
from releasing the Linux source code. One example is the IBM laptop
DSP sound system used in recent ThinkPad systems -- some of these
@@ -877,7 +877,7 @@
after backing up be careful and think about your answers and
actions. Two minutes of thinking can save hours of unnecessary work.
<p>
-Even if you are installing a multi-operating system, make sure that
+Even if you are installing a multi-boot system, make sure that
you have on hand the distribution media of any other present operating
systems. Especially if you repartition your boot drive, you might
find that you have to reinstall your operating system's boot loader,
@@ -1034,7 +1034,7 @@
<![ %i386 [
<sect1>Invoking the BIOS Set-Up Menu
<p>
-BIOS provides the basic functions needed to boot your machine allow
+BIOS provides the basic functions needed to boot your machine to allow
your operating system to access your hardware. Your system probably
provides a BIOS set-up menu, which is used to configure the BIOS.
Before installing, you <em>must</em> ensure that your BIOS is setup
@@ -1411,7 +1411,7 @@
<item>
The first XT disk is named ``/dev/xda''.
<item>
-The first XT disk is named ``/dev/xdb''.
+The second XT disk is named ``/dev/xdb''.
]]>
<!--
@@ -1617,7 +1617,7 @@
<p>
If you are manipulating existing FAT or NTFS partitions, it is
recommended that you either use the scheme below or native Windows or
-DOS tools. Otherwise, it is not really necessary to parition from DOS
+DOS tools. Otherwise, it is not really necessary to partition from DOS
or Windows; the Linux partitioning tools will generally do a better
job.
@@ -1626,7 +1626,7 @@
Win-32 or OS/2</heading>
<p>
One of the most common installations is onto a system that already
-contains DOS (including Windows 3.1), Win-32 (such as Windows 95 et),
+contains DOS (including Windows 3.1), Win-32 (such as Windows 95 and 98 (or NT??)),
or OS/2 and it is desired to put Debian onto the same disk without
destroying the previous system. As explained in the <ref
id="partition-intro">, decreasing the size of an existing partition
@@ -1743,7 +1743,7 @@
&MSG-BASE-SYSTEM;. Below you will find a description of the different
installation methods, and a description of files which might be
required for installation. Which files you use, and what steps you
-have to take to prepare you installation media, will vary with the
+have to take to prepare your installation media, will vary with the
method that you select to install Debian.
@@ -1799,7 +1799,7 @@
<p>
This section contains an annotated list of files you will find in the
<file>disks-&architecture;</file> directory. You may not need to
-download these at all; it all depends on the the booting and base
+download these at all; it all depends on the booting and base
system installation media you have chosen.
<p>
Most files are floppy disk images; that is, a single file which can be
@@ -1881,8 +1881,8 @@
<![ %i386 [ If you have a 5.25 inch floppy drive, use the image with
`1200' in the name; otherwise, use the image with `1440' in the
name. <![ %supports-tecra [ The `tecra' images are an alternate kernel
-forpeople who have
-problems with the standard disks, ]]> ]]>
+for people who have
+problems with the standard disks. ]]> ]]>
<![ %m68k [ If you have a low-density drive on an Atari, you can use
<url id="atari/resc720.bin">. ]]>
@@ -2003,7 +2003,7 @@
<item>
<p>
-This file contains an image of temporary filesystem that gets loaded
+This file contains an image of a temporary filesystem that gets loaded
into memory when you boot. This is used for installations from hard
disk and from CD-ROM.
<p>
@@ -2360,7 +2360,7 @@
<sect id="boot-from-floppies">Booting from Floppies
<p>
-Booting from floppies is a simple process. Simply download the the
+Booting from floppies is a simple process. Simply download the
&RESCUE-FLOPPY; image and the &DRIVER-FLOPPY; image. Copy these to
floppies as described in <ref id="create-floppy">. You can also
modify the &RESCUE-FLOPPY;; see <ref id="rescue-replace-kernel">.
@@ -2385,7 +2385,7 @@
<item>
a &DRIVER-FLOPPY; image
<item>
-that base system disk images, i.e., <url id="base14-1.bin">, <url
+the base system disk images, i.e., <url id="base14-1.bin">, <url
id="base14-2.bin">, etc.
</list>
@@ -2468,7 +2468,7 @@
<prgn>rawrite2</prgn>.
<p>
To write the floppy disk image files to the floppy disks, first make
-sure that you are booted into DOS. Maybe problems have been reported
+sure that you are booted into DOS. Many problems have been reported
when trying to use <prgn>rawrite2</prgn> from within a DOS box from
within Windows. Double-clicking on <prgn>rawrite2</prgn> from within
the Windows Explorer is also reported to not work. If you don't know
@@ -2700,7 +2700,7 @@
peripherals you don't own. You may also see the system pause for a
while. This happens when it is waiting for a device to respond, and
that device is not present on your system. If you find the time it
-takes to boot the system unacceptably long, later you can create a
+takes to boot the system unacceptably long, you can create a
custom kernel later (see <ref id="kernel-baking">).
@@ -2708,7 +2708,7 @@
<sect id="boot-troubleshooting">Troubleshooting the Boot Process
<p>
If you have problems and the kernel hangs during the boot process,
-doesn't recognized peripherals you actually have, or drives are not
+doesn't recogniz peripherals you actually have, or drives are not
recognized properly, the first thing to check is the boot parameters,
as discussed in <ref id="boot-parms">.
<p>
@@ -2774,7 +2774,7 @@
initial system configuration and the installation of the ``base
system''.
<p>
-This main job of <prgn>dbootstrap</prgn>, and the main purpose of your
+The main job of <prgn>dbootstrap</prgn>, and the main purpose of your
initial system configuration, is to configure certain core elements of
your system. For instance, this includes your network IP, host name,
and other aspects of your networking setup, if any. This also
@@ -2813,7 +2813,7 @@
virtual consoles, although the &RESCUE-FLOPPY; only uses a few of
them.
<p>
-Error messages are usually redirected the the third virtual terminal
+Error messages are usually redirected the third virtual terminal
(known as <tt>tty3</tt>). You can access this terminal by pressing
<em>Alt-F3</em> (hold the <em>Alt</em> key while pressing the
<em>F3</em> function key); get back to <prgn>dbootstrap</prgn> with
@@ -2989,7 +2989,7 @@
instructions">.
<p>
Thus, if you are using old disk partitions that are not empty, i.e.,
-if you want to just throw away what is one them, you should initialize
+if you want to just throw away what is on them, you should initialize
them (which erases all files). Moreover, you must initialize any
partitions that you created in the disk partitioning step. About the
only reason to mount a partition without initializing it at this point
@@ -3090,7 +3090,7 @@
If you want to install the base system via NFS you must load and
configure the driver module for your network card, and the NFS module
itself, available under ``filesystems''. If you are installing from a
-local disk, make sure you that look for the filesystem type in the
+local disk, make sure that you look for the filesystem type in the
modules list; support for that filesystem type <em>may</em> already be
compiled in the kernel, but it's best to check.
@@ -3148,7 +3148,7 @@
faster ones.
<p>
If you are installing the base system from NFS, then choose NFS and
-continue. You'll be prompeted to specify the server, the share on the
+continue. You'll be prompted to specify the server, the share on the
server, and the subdirectory within that share where the
<file>&base-disk-tarball;</file> file can be found. If you have
problems mounting NFS, make sure that the system time on the NFS
@@ -3203,7 +3203,7 @@
<![ %i386 [
If you answer &MSG-NO; to this question, you can set the bootable
-partition later using with the Linux commands <prgn>fdisk</prgn> or
+partition later with the Linux commands <prgn>fdisk</prgn> or
<prgn>activate</prgn> programs. From DOS, you can use <tt>fdisk
/mbr</tt> to reinstall the DOS boot block (but then you'll need to use
some other way to get into Debian).
@@ -3283,7 +3283,7 @@
is the right to use the machine, and it has a name and a password).
As explained above, you should <em>not</em> use the root account for
daily use. Mistakes or errors done while you're root can be
-disastrous, and require to total reinstallation of your system.
+disastrous, and require a total reinstallation of your system.
Remember that, unlike toy systems, you're never supposed to have to
reinstall a GNU/Linux system.
<P>
@@ -3294,18 +3294,18 @@
<sect>Shadow Password Support
<p>
Next, the system will ask whether you want to enable shadow passwords.
-This is a system in which your system is made to be a bit secure. In
+This is a system in which your Linux system is made to be a bit more secure. In
a system without shadow passwords, passwords are stored (encrypted) in
a world-readable file, <file>/etc/password</file>. This file has to
-be readable anyone who can log in because it contains vital user
+be readable to anyone who can log in because it contains vital user
information, for instance, how to map between numeric user identifiers
and login names. Therefore, someone could conceivably grab your
<file>/etc/password</file> file and run a brute force attack against
it to try to determine passwords.
<p>
-If you have shadow passwords enables, passwords are stored instead in
-<file>/etc/shadow</file>, which is <em>not</em> readable by anyone
-logged in. Therefore, we recommend that you enable shadow passwords.
+If you have shadow passwords enabled, passwords are instead stored in
+<file>/etc/shadow</file>, which is <em>not</em> readable only to
+root. Therefore, we recommend that you enable shadow passwords.
<p>
Reconfiguration of the shadow password system can be done at any time
with the <prgn>shadowconfig</prgn> program. See
@@ -3443,7 +3443,8 @@
<p>
Information about the installation of the rest of your Debian system
is examined in separate document, the <url id="dselect-beginner.html"
-name="dselect Tutorial">. <![ %FIXME [ <em>FIXME: to be written</em>
+name="dselect Tutorial">. <![ %FIXME [ <em>FIXME: to be written
+(it seems quite ready alredy (1999-02-14))</em>
]]>
@@ -3453,12 +3454,12 @@
<sect id="unix-intro">If You Are New to Unix
<p>
If you are new to Unix, you probably should go out and buy some books
-and do some reading. The <url id="url-unix-faq" name="Unix FAQ">
+and do some reading. The <url id="&url-unix-faq;" name="Unix FAQ">
contains a number of references to books and Usenet news groups which
should help you out a lot. You can also take a look at the <url
-id="url-unix-user-friendly" name="User-Friendly Unix FAQ">.
+id="&url-unix-user-friendly;" name="User-Friendly Unix FAQ">.
<p>
-Linux is an implementation of Unix. The <url id="url-ldp" name="Linux
+Linux is an implementation of Unix. The <url id="&url-ldp;" name="Linux
Documentation Project (LDP)"> collects a number of HOWTOs and online books
relating to Linux. Most of these documents can be installed locally;
just install the <package>doc-linux-html</package> package (HTML
@@ -3556,7 +3557,10 @@
<p>
Hereafter, we'll assume your kernel source is located in
<file>/usr/local/src</file> and that your kernel version is
-&kernelversion;. As your normal non-root account, change your
+&kernelversion;. As root, create a directory under
+<file>/usr/local/src</file> and change the owner of that file
+to your normal non-root account.
+As your normal non-root account, change your
directory to where you want to unpack the kernel sources (<tt>cd
/usr/local/src</tt>), extract the kernel sources (<tt>tar xzf
/usr/src/kernel-source-&kernelversion;.tar.gz</tt>), change your
@@ -3698,7 +3702,7 @@
Delaunay (SPARC information), and Stéphane Bortzmeyer for numerous
edits and text.
<p>
-Extremely helpful text and infomration was found in Jim Mintha's <url
+Extremely helpful text and information was found in Jim Mintha's <url
id="http://www.geog.ubc.ca/s_linux/howto/netboot.html"; name="HOWTO for
network booting">, the <url id="&url-debian-faq;" name="Debian FAQ">,
the <url id="&url-m68k-faq;" name="Linux/m68k FAQ">, the <url
--
Tapio Lehtonen
Tapio.Lehtonen@IKI.FI
--- install.sgml.1999-02-14 Sun Feb 14 20:31:58 1999
+++ install.sgml Sun Feb 14 21:11:45 1999
@@ -46,7 +46,7 @@
<version>version &docversion;, &docdate;</version>
<abstract>
This document contains installation instructions for the Debian
-GNU/Linux &release; system, for the the &arch-title;
+GNU/Linux &release; system, for the &arch-title;
(``&architecture;''); architecture. It also contains pointers to more
information and information on how to make the most of your new Debian
system. The procedures in this document are <em>not</em> to be used
@@ -573,7 +573,7 @@
<p>
<![ %i386 [ Both SCSI and IDE/ATAPI CD-ROMs are supported. In
-addition, all non-standards CD interfaces supported by Linux are
+addition, all non-standard CD interfaces supported by Linux are
supported by the boot disks (such as Mitsumi and Matsushita drives).
However, these models might require special boot parameters or other
massaging to get them to work, and booting off these non-standard
@@ -702,7 +702,7 @@
etc. However, none of these devices are required while installing the
system. This section contains information about peripherals
specifically <em>not</em> supported by the installation system, even
-though may be supported by Linux.
+though they may be supported by Linux.
<![ %i386 [
@@ -784,7 +784,7 @@
<sect1>Avoid Proprietary or Closed Hardware
<p>
Some hardware manufacturers simply won't tell us how to write drivers
-for their hardware. Others they won't allow us access to the
+for their hardware. Others won't allow us access to the
documentation without a non-disclosure agreement that would prevent us
from releasing the Linux source code. One example is the IBM laptop
DSP sound system used in recent ThinkPad systems -- some of these
@@ -877,7 +877,7 @@
after backing up be careful and think about your answers and
actions. Two minutes of thinking can save hours of unnecessary work.
<p>
-Even if you are installing a multi-operating system, make sure that
+Even if you are installing a multi-boot system, make sure that
you have on hand the distribution media of any other present operating
systems. Especially if you repartition your boot drive, you might
find that you have to reinstall your operating system's boot loader,
@@ -1034,7 +1034,7 @@
<![ %i386 [
<sect1>Invoking the BIOS Set-Up Menu
<p>
-BIOS provides the basic functions needed to boot your machine allow
+BIOS provides the basic functions needed to boot your machine to allow
your operating system to access your hardware. Your system probably
provides a BIOS set-up menu, which is used to configure the BIOS.
Before installing, you <em>must</em> ensure that your BIOS is setup
@@ -1411,7 +1411,7 @@
<item>
The first XT disk is named ``/dev/xda''.
<item>
-The first XT disk is named ``/dev/xdb''.
+The second XT disk is named ``/dev/xdb''.
]]>
<!--
@@ -1617,7 +1617,7 @@
<p>
If you are manipulating existing FAT or NTFS partitions, it is
recommended that you either use the scheme below or native Windows or
-DOS tools. Otherwise, it is not really necessary to parition from DOS
+DOS tools. Otherwise, it is not really necessary to partition from DOS
or Windows; the Linux partitioning tools will generally do a better
job.
@@ -1626,7 +1626,7 @@
Win-32 or OS/2</heading>
<p>
One of the most common installations is onto a system that already
-contains DOS (including Windows 3.1), Win-32 (such as Windows 95 et),
+contains DOS (including Windows 3.1), Win-32 (such as Windows 95 and 98 (or NT??)),
or OS/2 and it is desired to put Debian onto the same disk without
destroying the previous system. As explained in the <ref
id="partition-intro">, decreasing the size of an existing partition
@@ -1743,7 +1743,7 @@
&MSG-BASE-SYSTEM;. Below you will find a description of the different
installation methods, and a description of files which might be
required for installation. Which files you use, and what steps you
-have to take to prepare you installation media, will vary with the
+have to take to prepare your installation media, will vary with the
method that you select to install Debian.
@@ -1799,7 +1799,7 @@
<p>
This section contains an annotated list of files you will find in the
<file>disks-&architecture;</file> directory. You may not need to
-download these at all; it all depends on the the booting and base
+download these at all; it all depends on the booting and base
system installation media you have chosen.
<p>
Most files are floppy disk images; that is, a single file which can be
@@ -1881,8 +1881,8 @@
<![ %i386 [ If you have a 5.25 inch floppy drive, use the image with
`1200' in the name; otherwise, use the image with `1440' in the
name. <![ %supports-tecra [ The `tecra' images are an alternate kernel
-forpeople who have
-problems with the standard disks, ]]> ]]>
+for people who have
+problems with the standard disks. ]]> ]]>
<![ %m68k [ If you have a low-density drive on an Atari, you can use
<url id="atari/resc720.bin">. ]]>
@@ -2003,7 +2003,7 @@
<item>
<p>
-This file contains an image of temporary filesystem that gets loaded
+This file contains an image of a temporary filesystem that gets loaded
into memory when you boot. This is used for installations from hard
disk and from CD-ROM.
<p>
@@ -2360,7 +2360,7 @@
<sect id="boot-from-floppies">Booting from Floppies
<p>
-Booting from floppies is a simple process. Simply download the the
+Booting from floppies is a simple process. Simply download the
&RESCUE-FLOPPY; image and the &DRIVER-FLOPPY; image. Copy these to
floppies as described in <ref id="create-floppy">. You can also
modify the &RESCUE-FLOPPY;; see <ref id="rescue-replace-kernel">.
@@ -2385,7 +2385,7 @@
<item>
a &DRIVER-FLOPPY; image
<item>
-that base system disk images, i.e., <url id="base14-1.bin">, <url
+the base system disk images, i.e., <url id="base14-1.bin">, <url
id="base14-2.bin">, etc.
</list>
@@ -2468,7 +2468,7 @@
<prgn>rawrite2</prgn>.
<p>
To write the floppy disk image files to the floppy disks, first make
-sure that you are booted into DOS. Maybe problems have been reported
+sure that you are booted into DOS. Many problems have been reported
when trying to use <prgn>rawrite2</prgn> from within a DOS box from
within Windows. Double-clicking on <prgn>rawrite2</prgn> from within
the Windows Explorer is also reported to not work. If you don't know
@@ -2700,7 +2700,7 @@
peripherals you don't own. You may also see the system pause for a
while. This happens when it is waiting for a device to respond, and
that device is not present on your system. If you find the time it
-takes to boot the system unacceptably long, later you can create a
+takes to boot the system unacceptably long, you can create a
custom kernel later (see <ref id="kernel-baking">).
@@ -2708,7 +2708,7 @@
<sect id="boot-troubleshooting">Troubleshooting the Boot Process
<p>
If you have problems and the kernel hangs during the boot process,
-doesn't recognized peripherals you actually have, or drives are not
+doesn't recogniz peripherals you actually have, or drives are not
recognized properly, the first thing to check is the boot parameters,
as discussed in <ref id="boot-parms">.
<p>
@@ -2774,7 +2774,7 @@
initial system configuration and the installation of the ``base
system''.
<p>
-This main job of <prgn>dbootstrap</prgn>, and the main purpose of your
+The main job of <prgn>dbootstrap</prgn>, and the main purpose of your
initial system configuration, is to configure certain core elements of
your system. For instance, this includes your network IP, host name,
and other aspects of your networking setup, if any. This also
@@ -2813,7 +2813,7 @@
virtual consoles, although the &RESCUE-FLOPPY; only uses a few of
them.
<p>
-Error messages are usually redirected the the third virtual terminal
+Error messages are usually redirected the third virtual terminal
(known as <tt>tty3</tt>). You can access this terminal by pressing
<em>Alt-F3</em> (hold the <em>Alt</em> key while pressing the
<em>F3</em> function key); get back to <prgn>dbootstrap</prgn> with
@@ -2989,7 +2989,7 @@
instructions">.
<p>
Thus, if you are using old disk partitions that are not empty, i.e.,
-if you want to just throw away what is one them, you should initialize
+if you want to just throw away what is on them, you should initialize
them (which erases all files). Moreover, you must initialize any
partitions that you created in the disk partitioning step. About the
only reason to mount a partition without initializing it at this point
@@ -3090,7 +3090,7 @@
If you want to install the base system via NFS you must load and
configure the driver module for your network card, and the NFS module
itself, available under ``filesystems''. If you are installing from a
-local disk, make sure you that look for the filesystem type in the
+local disk, make sure that you look for the filesystem type in the
modules list; support for that filesystem type <em>may</em> already be
compiled in the kernel, but it's best to check.
@@ -3148,7 +3148,7 @@
faster ones.
<p>
If you are installing the base system from NFS, then choose NFS and
-continue. You'll be prompeted to specify the server, the share on the
+continue. You'll be prompted to specify the server, the share on the
server, and the subdirectory within that share where the
<file>&base-disk-tarball;</file> file can be found. If you have
problems mounting NFS, make sure that the system time on the NFS
@@ -3203,7 +3203,7 @@
<![ %i386 [
If you answer &MSG-NO; to this question, you can set the bootable
-partition later using with the Linux commands <prgn>fdisk</prgn> or
+partition later with the Linux commands <prgn>fdisk</prgn> or
<prgn>activate</prgn> programs. From DOS, you can use <tt>fdisk
/mbr</tt> to reinstall the DOS boot block (but then you'll need to use
some other way to get into Debian).
@@ -3283,7 +3283,7 @@
is the right to use the machine, and it has a name and a password).
As explained above, you should <em>not</em> use the root account for
daily use. Mistakes or errors done while you're root can be
-disastrous, and require to total reinstallation of your system.
+disastrous, and require a total reinstallation of your system.
Remember that, unlike toy systems, you're never supposed to have to
reinstall a GNU/Linux system.
<P>
@@ -3294,18 +3294,18 @@
<sect>Shadow Password Support
<p>
Next, the system will ask whether you want to enable shadow passwords.
-This is a system in which your system is made to be a bit secure. In
+This is a system in which your Linux system is made to be a bit more secure. In
a system without shadow passwords, passwords are stored (encrypted) in
a world-readable file, <file>/etc/password</file>. This file has to
-be readable anyone who can log in because it contains vital user
+be readable to anyone who can log in because it contains vital user
information, for instance, how to map between numeric user identifiers
and login names. Therefore, someone could conceivably grab your
<file>/etc/password</file> file and run a brute force attack against
it to try to determine passwords.
<p>
-If you have shadow passwords enables, passwords are stored instead in
-<file>/etc/shadow</file>, which is <em>not</em> readable by anyone
-logged in. Therefore, we recommend that you enable shadow passwords.
+If you have shadow passwords enabled, passwords are instead stored in
+<file>/etc/shadow</file>, which is <em>not</em> readable only to
+root. Therefore, we recommend that you enable shadow passwords.
<p>
Reconfiguration of the shadow password system can be done at any time
with the <prgn>shadowconfig</prgn> program. See
@@ -3443,7 +3443,8 @@
<p>
Information about the installation of the rest of your Debian system
is examined in separate document, the <url id="dselect-beginner.html"
-name="dselect Tutorial">. <![ %FIXME [ <em>FIXME: to be written</em>
+name="dselect Tutorial">. <![ %FIXME [ <em>FIXME: to be written
+(it seems quite ready alredy (1999-02-14))</em>
]]>
@@ -3453,12 +3454,12 @@
<sect id="unix-intro">If You Are New to Unix
<p>
If you are new to Unix, you probably should go out and buy some books
-and do some reading. The <url id="url-unix-faq" name="Unix FAQ">
+and do some reading. The <url id="&url-unix-faq;" name="Unix FAQ">
contains a number of references to books and Usenet news groups which
should help you out a lot. You can also take a look at the <url
-id="url-unix-user-friendly" name="User-Friendly Unix FAQ">.
+id="&url-unix-user-friendly;" name="User-Friendly Unix FAQ">.
<p>
-Linux is an implementation of Unix. The <url id="url-ldp" name="Linux
+Linux is an implementation of Unix. The <url id="&url-ldp;" name="Linux
Documentation Project (LDP)"> collects a number of HOWTOs and online books
relating to Linux. Most of these documents can be installed locally;
just install the <package>doc-linux-html</package> package (HTML
@@ -3556,7 +3557,10 @@
<p>
Hereafter, we'll assume your kernel source is located in
<file>/usr/local/src</file> and that your kernel version is
-&kernelversion;. As your normal non-root account, change your
+&kernelversion;. As root, create a directory under
+<file>/usr/local/src</file> and change the owner of that file
+to your normal non-root account.
+As your normal non-root account, change your
directory to where you want to unpack the kernel sources (<tt>cd
/usr/local/src</tt>), extract the kernel sources (<tt>tar xzf
/usr/src/kernel-source-&kernelversion;.tar.gz</tt>), change your
@@ -3698,7 +3702,7 @@
Delaunay (SPARC information), and Stéphane Bortzmeyer for numerous
edits and text.
<p>
-Extremely helpful text and infomration was found in Jim Mintha's <url
+Extremely helpful text and information was found in Jim Mintha's <url
id="http://www.geog.ubc.ca/s_linux/howto/netboot.html"; name="HOWTO for
network booting">, the <url id="&url-debian-faq;" name="Debian FAQ">,
the <url id="&url-m68k-faq;" name="Linux/m68k FAQ">, the <url
Reply to: