Attachment 21881 Details for Bug 38188 – chapter.sgml.diff

[patch] chapter.sgml.diff

chapter.sgml.diff (text/plain), 21.33 KB, created by Marc Fonvieille on 2002-05-17 17:20:02 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Marc Fonvieille

Created: 2002-05-17 17:20:02 UTC

Size: 21.33 KB

patch

obsolete

>--- chapter.sgml.org	Fri May 17 16:17:41 2002
>+++ chapter.sgml	Fri May 17 17:59:34 2002
>@@ -228,7 +228,7 @@
> 	extended partition.</para>
> 
>       <para>Each partition has a <firstterm>partition ID</firstterm>, which is
>-	a number used to identify the type of data on the partition. FreeBSD
>+	a number used to identify the type of data on the partition.  FreeBSD
> 	partitions have the partition ID <literal>165</literal>.</para>
> 
>       <para>In general, each operating system that you use will identify
>@@ -240,7 +240,7 @@
>       <para>FreeBSD must be installed into a primary partition.  FreeBSD can
> 	keep all its data, including any files that you create, on this one
> 	partition.  However, if you have multiple disks, then you can create a
>-	FreeBSD partition on all, or some, of them. When you install FreeBSD,
>+	FreeBSD partition on all, or some, of them.  When you install FreeBSD,
> 	you must have one partition available.  This might be a blank
> 	partition that you have prepared, or it might be an existing partition
> 	that contains data that you no longer care about.</para>
>@@ -325,14 +325,14 @@
> 	<indexterm><primary>Alpha</primary></indexterm>
> 
> 	<para>You will need a dedicated disk for FreeBSD on the
>-	  Alpha. It is not possible to share a disk with another
>+	  Alpha.  It is not possible to share a disk with another
> 	  operating system at this time.  Depending on the specific
> 	  Alpha machine you have, this disk can either be a SCSI disk
> 	  or an IDE disk, as long as your machine is capable of
> 	  booting from it.</para>
> 
> 	<para>Following the conventions of the Digital / Compaq
>-	  manuals all SRM input is shown in uppercase. SRM is case
>+	  manuals all SRM input is shown in uppercase.  SRM is case
> 	  insensitive.</para>
> 
> 	<para>To find the names and types of disks in your machine, use
>@@ -350,18 +350,18 @@
> pqb0.0.1.4.0               PQB0                       PCI EIDE</screen>
> 
> 	<para>This example is from a Digital Personal Workstation
>-	  433au and shows three disks attached to the machine. The
>+	  433au and shows three disks attached to the machine.  The
> 	  first is a CDROM drive called <devicename>DKA0</devicename> and
> 	  the other two are disks and are called
> 	  <devicename>DKC0</devicename> and
> 	  <devicename>DKC100</devicename> respectively.</para>
> 
> 	<para>Disks with names of the form <devicename>DKx</devicename>
>-	  are SCSI disks. For example <devicename>DKA100</devicename>
>+	  are SCSI disks.  For example <devicename>DKA100</devicename>
> 	  refers to a SCSI with SCSI target ID 1 on the first SCSI bus (A), 
> 	  whereas <devicename>DKC300</devicename> refers to a SCSI disk
>-	  with SCSI ID 3 on the third SCSI bus (C). Devicename <devicename>
>-	  PKx</devicename> refers to the SCSI host bus adapter. As
>+	  with SCSI ID 3 on the third SCSI bus (C).  Devicename <devicename>
>+	  PKx</devicename> refers to the SCSI host bus adapter.  As
> 	  seen in the <literal>SHOW DEVICE</literal> output SCSI
> 	  CDROM drives are treated as any other SCSI hard disk drive.</para>
> 
>@@ -468,7 +468,7 @@
> 	<para>If you have FreeBSD on CDROM or DVD, and your computer allows
> 	  you to boot from the CDROM or DVD (typically a BIOS option called
> 	  <quote>Boot Order</quote> or similar) then you can skip this
>-	  section. The FreeBSD CDROM and DVD images are bootable and can be
>+	  section.  The FreeBSD CDROM and DVD images are bootable and can be
> 	  used to install FreeBSD without any other special
> 	  preparation.</para>
>       </tip>
>@@ -908,7 +908,7 @@
> 	</listitem>
> 
> 	<listitem>
>-	  <para>Drivers that have been marked inactive. They remain in the
>+	  <para>Drivers that have been marked inactive.  They remain in the
> 	    kernel, but they will not probe for their device when the kernel
> 	    starts.  These are subdivided into groups in the same way as the
> 	    active driver list.</para>
>@@ -1073,8 +1073,8 @@
>       <para>The last few hundred lines that have been displayed on screen are
> 	stored and can be reviewed.</para>
> 
>-      <para>To review the buffer, press <keycap>Scroll Lock</keycap>. This
>-	turns on scrolling in the display. You can then use the arrow keys, or
>+      <para>To review the buffer, press <keycap>Scroll Lock</keycap>.  This
>+	turns on scrolling in the display.  You can then use the arrow keys, or
> 	<keycap>PageUp</keycap> and <keycap>PageDown</keycap> to view the
> 	results.  Press <keycap>Scroll Lock</keycap> again to stop
> 	scrolling.</para>
>@@ -1276,7 +1276,7 @@
> 
>       <para>A different keyboard mapping may be chosen by selecting the
> 	menu item using up/down arrow keys and pressing <keycap>Space</keycap>.
>-	Pressing <keycap>Space</keycap> again will unselect the item. When
>+	Pressing <keycap>Space</keycap> again will unselect the item.  When
> 	finished, choose the &gui.ok; using the
> 	arrow keys and press
> 	<keycap>Enter</keycap>.</para>
>@@ -1327,7 +1327,7 @@
> 	not need to be changed.</para>
> 
>       <para>The description of the selected item will appear at the
>-	bottom of the screen highlighted in blue. Notice that one of the
>+	bottom of the screen highlighted in blue.  Notice that one of the
> 	options is <guimenuitem>Use Defaults</guimenuitem> to reset all
> 	values to startup defaults.</para>
> 
>@@ -1388,7 +1388,7 @@
> 	.  Then, if the
> 	first drive fails, or is attacked by a virus, or is scribbled upon by an
> 	operating system defect, he can easily recover by instructing the BIOS
>-	to logically swap the drives. It is like switching the cables on the
>+	to logically swap the drives.  It is like switching the cables on the
> 	drives, but without having to open the case.</para>
> 
>       <indexterm><primary>SCSI</primary></indexterm>
>@@ -1414,7 +1414,7 @@
> 	  Adventures:</title>
>       
> 	<para>Bill breaks-down an older Wintel box to make another FreeBSD box
>-	  for Fred. Bill installs a single SCSI drive as SCSI unit zero and
>+	  for Fred.  Bill installs a single SCSI drive as SCSI unit zero and
> 	  installs FreeBSD on it.</para>
> 
> 	<para>Fred begins using the system, but after several days notices that
>@@ -1453,7 +1453,7 @@
> 	  SCSI unit four, unit four became the <quote>new clone</quote>.
> 	  When Bill
> 	  re-ordered the SCSI BIOS so that he could boot from SCSI unit four, he
>-	  was only fooling himself. FreeBSD was still running on SCSI unit zero.
>+	  was only fooling himself.  FreeBSD was still running on SCSI unit zero.
> 	  Making this kind of BIOS change will cause some or all of the Boot and
> 	  Loader code to be fetched from the selected BIOS drive, but when the
> 	  FreeBSD kernel drivers take-over, the BIOS drive numbering will be
>@@ -1684,7 +1684,7 @@
> 	partition they are contained in.</para>
> 
>       <para>FreeBSD also uses disk space for <firstterm>swap
>-	  space</firstterm>. Swap space provides FreeBSD with
>+	  space</firstterm>.  Swap space provides FreeBSD with
> 	<firstterm>virtual memory</firstterm>.  This allows your computer to
> 	behave as though it has much more memory than it actually does.  When
> 	FreeBSD runs out of memory it moves some of the data that is not
>@@ -1753,13 +1753,13 @@
> 
>       <para>Slice numbers follow
> 	the device name, prefixed with an <literal>s</literal>,
>-	starting at 1. So <quote>da0<emphasis>s1</emphasis></quote>
>-	is the first slice on the first SCSI drive. There can only be
>+	starting at 1.  So <quote>da0<emphasis>s1</emphasis></quote>
>+	is the first slice on the first SCSI drive.  There can only be
> 	four physical slices on a disk, but you can have logical
>-	slices inside physical slices of the appropriate type. These
>+	slices inside physical slices of the appropriate type.  These
> 	extended slices are numbered starting at 5, so
> 	<quote>ad0<emphasis>s5</emphasis></quote> is the first
>-	extended slice on a disk. These devices are used by file
>+	extended slice on a disk.  These devices are used by file
> 	systems that expect to occupy a slice.</para> 
> 
>       <para>Slices, <quote>dangerously dedicated</quote> physical
>@@ -1775,7 +1775,7 @@
>       <para>Finally, each disk on the system is identified.  A disk name
> 	starts with a code that indicates the type of disk, and then a number,
> 	indicating which disk it is.  Unlike slices, disk numbering starts at
>-	0. Common codes that you will see are listed in 
>+	0.  Common codes that you will see are listed in 
> 	<xref linkend="install-dev-codes">.</para>
> 
>       <para>When referring to a partition FreeBSD requires that you also name
>@@ -2159,7 +2159,7 @@
> 
>       <para>Certain applications can benefit from particular partition
> 	schemes, especially if you are laying out partitions across more than
>-	one disk. However, for this, your first FreeBSD installation, you do
>+	one disk.  However, for this, your first FreeBSD installation, you do
> 	not need to give too much thought to how you partition the disk.  It
> 	is more important that you install FreeBSD and start learning how to
> 	use it.  You can always re-install FreeBSD to change your partition
>@@ -2789,7 +2789,7 @@
>     <title>Post-installation</title>
> 
>     <para>Configuration of various options follows the successful 
>-      installation.    An option can be configured by re-entering the
>+      installation.  An option can be configured by re-entering the
>       configuration options before booting the new FreeBSD
>       system or after installation using
>       <command>/stand/sysinstall</command> and selecting
>@@ -2898,8 +2898,8 @@
> 
> 	  <listitem>
> 	    <para>IP address of host forwarding packets to non-local
>-	      destinations. Fill this in only if the machine is a node
>-	      on the network. <emphasis>Leave this field blank</emphasis>
>+	      destinations.  Fill this in only if the machine is a node
>+	      on the network.  <emphasis>Leave this field blank</emphasis>
> 	      if the machine is the gateway to the Internet for the
> 	      network.</para>
> 	  </listitem>
>@@ -2909,7 +2909,7 @@
> 	  <term>Name server</term>
> 
> 	  <listitem>
>-	    <para>IP address of your local DNS server. There is no local
>+	    <para>IP address of your local DNS server.  There is no local
> 	      DNS server on this private local area network so the IP
> 	      address of the provider's DNS server (208.163.10.2) was
> 	      used.</para>
>@@ -2941,7 +2941,7 @@
> 
> 	  <listitem>
> 	    <para>Any interface-specific options to <command>ifconfig</command>
>-	      you would like to add. There were none in this case.</para>
>+	      you would like to add.  There were none in this case.</para>
> 	  </listitem>
> 	</varlistentry>
> 
>@@ -3018,7 +3018,7 @@
> which of its Internet services will be available.  The default FreeBSD
> inetd.conf(5) leaves all services disabled by default, so they must be
> specifically enabled in the configuration file before they will
>-function, even once inetd(8) is enabled.  Note that services for
>+function, even once inetd(8) is enabled. Note that services for
> IPv6 must be seperately enabled from IPv4 services.
> 
> Select [Yes] now to invoke an editor on /etc/inetd.conf, or [No] to
>@@ -3565,7 +3565,7 @@
>       <title>Mouse Settings</title>
> 
>       <para>This option will allow you to cut and paste text in the
>-	console and user programs with a 3-button mouse. If using a 2-button
>+	console and user programs with a 3-button mouse.  If using a 2-button
> 	mouse, refer to manual page, &man.moused.8;, after installation for
> 	details on emulating the 3-button style.  This example depicts a
> 	non-USB mouse.</para>
>@@ -3711,7 +3711,7 @@
>       </figure>
> 
>       <para>There are several ways to configure the X
>-	server. <application>XF86Setup</application> is fully graphical and
>+	server.  <application>XF86Setup</application> is fully graphical and
> 	probably the easiest.  Use the arrow keys to select the
> 	<guimenuitem>XF86Setup</guimenuitem> and press
> 	<keycap>Enter</keycap>.</para>
>@@ -3735,10 +3735,10 @@
>                                  [ OK ]</screen>
> 
>       <para>Press <keycap>Enter</keycap> to switch to the graphics mode and
>-	continue. It will <emphasis>not</emphasis> try to switch to the
>+	continue.  It will <emphasis>not</emphasis> try to switch to the
> 	graphics mode until <keycap>Enter</keycap> is pressed.  The screen
> 	will go black and then shortly a screen with a large X in the
>-	center will appear. Be patient and wait.</para>
>+	center will appear.  Be patient and wait.</para>
> 
>       <para>After a few more moments, the <application>XF86Setup</application>
> 	introduction will display.  Read all instructions
>@@ -3804,7 +3804,7 @@
> 	    additional help in configuring your video card.</para>
> 
> 	  <para>Select the appropriate video card from the list using the
>-	    scrollbar. Clicking on your card will show as
>+	    scrollbar.  Clicking on your card will show as
> 	    <quote>Card selected:</quote> above the list box.</para>
> 
> 	  <para>Next, the <guimenuitem>Detailed Setup</guimenuitem> was
>@@ -3817,19 +3817,19 @@
> 	<step>
> 	  <title><guimenuitem>Monitor</guimenuitem></title>
> 
>-	  <para>There are two ways to proceed. One method requires that you
>+	  <para>There are two ways to proceed.  One method requires that you
> 	    enter the horizontal and vertical sweep capabilities of your
> 	    monitor in the text boxes.</para>
> 
> 	  <para>Choosing one of the monitor options listed that the monitor
> 	    is the other method.  After selecting a listed option, the
> 	    horizontal and vertical sweep rates that will be used will
>-	    display. Compare those to your monitor specifications.  The
>+	    display.  Compare those to your monitor specifications.  The
> 	    monitor must be capable of using those ranges.</para>
> 
> 	  <para>Do not exceed the ratings of your monitor. Damage could
>-	    occur. If you have doubts select <guimenuitem>ABORT</guimenuitem>
>-	    and get the information. The remainder of the installation process
>+	    occur.  If you have doubts select <guimenuitem>ABORT</guimenuitem>
>+	    and get the information.  The remainder of the installation process
> 	    will be unaffected and configuring the X-Server can be done
> 	    later using <command>/stand/sysinstall</command>.</para>
> 
>@@ -3916,9 +3916,9 @@
> 	    by using <application>xvidtune</application>.</para>
> 
> 	  <para>There are warnings that improper settings can
>-	    damage your equipment.  Heed them. If in doubt, do not do
>+	    damage your equipment.  Heed them.  If in doubt, do not do
> 	    it. Instead, use the monitor controls to adjust the display for
>-	    x-windows. There may be some display differences when switching
>+	    x-windows.  There may be some display differences when switching
> 	    back to text mode, but it is better than damaging equipment.
> 	    <application>xvidtune</application> can be ran later using 
> 	    <command>/stand/sysinstall</command>.</para>
>@@ -4236,7 +4236,7 @@
>       </figure>
> 
>       <para>Groups could also be added at this time if specific needs
>-	are known. Otherwise, this may be accessed through using
>+	are known.  Otherwise, this may be accessed through using
> 	<filename>/stand/sysinstall</filename> after installation is
> 	completed.</para>
> 
>@@ -4260,7 +4260,7 @@
> 	password.</para>
> 
>       <para>The password will need to be typed in twice
>-	correctly. Needless to say, make sure you have a way of finding
>+	correctly.  Needless to say, make sure you have a way of finding
> 	the password if you forget.</para>
> 
>       <screen>Changing local password for root. 
>@@ -4309,8 +4309,8 @@
>                             [ Yes ]   No</screen>
> 
>       <para>Select <guibutton>[ Yes ]</guibutton> and remove floppy if
>-	booting from floppy. The CDROM drive is locked until the machine
>-	starts to reboot. The CDROM drive is then unlocked and can
>+	booting from floppy.  The CDROM drive is locked until the machine
>+	starts to reboot.  The CDROM drive is then unlocked and can
> 	be removed from drive (quickly).</para>
> 
>       <para>The system will reboot so watch for any error messages that
>@@ -4519,7 +4519,7 @@
> 
>       <para>It is safe to turn off the power after the shutdown command
> 	has been issued and the message <quote>Please press any key to reboot</quote>
>-	appears. If any key is pressed instead of turning off the power
>+	appears.  If any key is pressed instead of turning off the power
> 	switch, the system will reboot.</para>
> 
>       <para>You could also use the <keycap>CTRL+ALT+DEL</keycap> key
>@@ -4676,7 +4676,7 @@
> 	      <application>DEFRAG</application> utility (go into Explorer,
> 	      right-click on the
> 	      hard drive, and choose to defrag your
>-	      hard drive), or Norton Disk Tools. You then must run 
>+	      hard drive), or Norton Disk Tools.  You then must run 
> 	      <application>FIPS</application>.  It
> 	      will prompt you for the rest of the information it needs.
> 	      Afterwards, you can reboot and install FreeBSD on the new
>@@ -4690,11 +4690,11 @@
> 	    <para>There is also a <emphasis>very</emphasis> useful
> 	      product from <ulink
> 	      url="http://www.powerquest.com/">PowerQuest</ulink>
>-	      called <application>Partition Magic</application>. This
>+	      called <application>Partition Magic</application>.  This
> 	      application has far more functionality than 
> 	      <application>FIPS</application>, and is
> 	      highly recommended if you plan to often add/remove
>-	      operating systems (like me). However, it does cost
>+	      operating systems (like me).  However, it does cost
> 	      money, and if you plan to install FreeBSD once and then
> 	      leave it there, <application>FIPS</application> will probably 
> 	      be fine for you.</para>
>@@ -4829,17 +4829,17 @@
>       <para>This type of installation is called a <quote>headless install</quote>,
>         because the machine that you are trying to install FreeBSD on
>         either does not have a monitor attached to it, or does not even
>-        have a VGA output. How is this possible you ask? Using a
>-        serial console. A serial console is basically using another
>+        have a VGA output.  How is this possible you ask? Using a
>+        serial console.  A serial console is basically using another
>         machine to act as the main display and keyboard for a
>-        system. To do this, just follow these steps:</para>
>+        system.  To do this, just follow these steps:</para>
> 
>       <procedure>
>         <step>
>           <title>Fetch the Right Boot Floppy Images</title>
> 
>           <para>First you will need to get the right disk images so
>-            that you can boot into the install program. The secret
>+            that you can boot into the install program.  The secret
>             with using a serial console is that you tell the boot
>             loader to send I/O through a serial port instead of
>             displaying console output to the VGA device and trying to
>@@ -4918,9 +4918,9 @@
>           <primary><command>mount</command></primary>
>         </indexterm>
> 	    <para>If you were to boot into the floppies that you just
>-	      made, FreeBSD would boot into its normal install mode. We
>+	      made, FreeBSD would boot into its normal install mode.  We
> 	      want FreeBSD to boot into a serial console for our
>-	      install. To do this, you have to mount the
>+	      install.  To do this, you have to mount the
> 	      <filename>kern.flp</filename> floppy onto your FreeBSD
> 	      system using the &man.mount.8; command.</para>
> 
>@@ -4932,7 +4932,7 @@
> 	    <screen>&prompt.root; <userinput>cd /mnt</userinput></screen>
> 
> 	    <para>Here is where you must set the floppy to boot into a
>-	      serial console. You have to make a file called
>+	      serial console.  You have to make a file called
> 	      <filename>boot.config</filename> containing 
> 	      <literal>/boot/loader -h</literal>.  All this does is pass a flag to the bootloader to
> 	      boot into a serial console.</para>
>@@ -4955,8 +4955,8 @@
> 
>   	    <indexterm><primary>null-modem cable</primary></indexterm>
> 	    <para>You now need to connect a null modem cable between
>-	      the two machines. Just connect the cable to the serial
>-	      ports of the 2 machines. <emphasis>A normal serial cable
>+	      the two machines.  Just connect the cable to the serial
>+	      ports of the 2 machines.  <emphasis>A normal serial cable
> 	      will not work here</emphasis>, you need a null modem
> 	      cable because it has some of the wires inside crossed
> 	      over.</para>
>@@ -4965,7 +4965,7 @@
> 	  <step>
> 	    <title>Booting Up for the Install</title>
> 
>-	    <para>It is now time to go ahead and start the install. Put
>+	    <para>It is now time to go ahead and start the install.  Put
> 	      the <filename>kern.flp</filename> floppy in the floppy
> 	      drive of the machine you are doing the headless install
> 	      on, and power on the machine.</para>
>@@ -4987,7 +4987,7 @@
>         machine through your <command>cu</command> session now.  It will ask 
> 	you to put
>         in the <filename>mfsroot.flp</filename>, and then it will come
>-        up with a selection of what kind of terminal to use. Just
>+        up with a selection of what kind of terminal to use.  Just
>         select the FreeBSD color console and proceed with your
>         install!</para>
> 
>@@ -5264,11 +5264,11 @@
> 	  words, if you can connect to the ISP in Windows without
> 	  using a script), then all you will need to do is type in
> 	  <command>dial</command> at the
>-	  <application>ppp</application> prompt. Otherwise,
>+	  <application>ppp</application> prompt.  Otherwise,
> 	  you will need to know
> 	  how to dial your ISP using the <quote>AT commands</quote>
> 	  specific to your modem, as the PPP dialer provides only a very
>-	  simple terminal emulator. Please refer
>+	  simple terminal emulator.  Please refer
> 	  to the user-ppp <link linkend="userppp">handbook</link> and <ulink
> 	  url="../faq/ppp.html">FAQ</ulink> entries for further
> 	  information.  If you have problems, logging can be directed to

Actions: View | Diff

Attachments on bug 38188: 21881