diff options
| author | Nik Clayton <nik@FreeBSD.org> | 1998-10-21 21:58:40 +0000 |
|---|---|---|
| committer | Nik Clayton <nik@FreeBSD.org> | 1998-10-21 21:58:40 +0000 |
| commit | cfb82ba9ca6e760d71f6a0c0f81cdf1dc9cdcfec (patch) | |
| tree | 013128fb90ebc09234bafe525b31b9af93fa32f8 /en_US.ISO_8859-1 | |
| parent | 2a882be047fbbeb1b9f0bcced0205b1e72773a54 (diff) | |
Notes
Diffstat (limited to 'en_US.ISO_8859-1')
| -rw-r--r-- | en_US.ISO_8859-1/books/handbook/book.sgml | 635 |
1 files changed, 322 insertions, 313 deletions
diff --git a/en_US.ISO_8859-1/books/handbook/book.sgml b/en_US.ISO_8859-1/books/handbook/book.sgml index bca291a6fd..cc090db9d5 100644 --- a/en_US.ISO_8859-1/books/handbook/book.sgml +++ b/en_US.ISO_8859-1/books/handbook/book.sgml @@ -17,9 +17,8 @@ <pubdate>March 1998</pubdate> <abstract><para>Welcome to FreeBSD! This handbook covers the - installation and day to day use of <emphasis remap=bf>FreeBSD - Release &rel.current;</emphasis>. This manual is a <emphasis - remap=bf>work in progress</emphasis> and is the work of many + installation and day to day use of <emphasis>FreeBSD + Release &rel.current;</emphasis>. This manual is a <emphasis>work in progress</emphasis> and is the work of many individuals. Many sections do not yet exist and some of those that do exist need to be updated. If you are interested in helping with this project, send email to the &a.doc; The latest version of this @@ -69,13 +68,13 @@ <itemizedlist> <listitem> - <para><emphasis remap=bf>Preemptive multitasking</emphasis> with + <para><emphasis>Preemptive multitasking</emphasis> with dynamic priority adjustment to ensure smooth and fair sharing of the computer between applications and users.</para> </listitem> <listitem> - <para><emphasis remap=bf>Multiuser</emphasis> access means that + <para><emphasis>Multiuser</emphasis> access means that many people can use a FreeBSD system simultaneously for a variety of things. System peripherals such as printers and tape drives are also properly SHARED BETWEEN ALL users on the @@ -83,7 +82,7 @@ </listitem> <listitem> - <para>Complete <emphasis remap=bf>TCP/IP networking</emphasis> + <para>Complete <emphasis>TCP/IP networking</emphasis> including SLIP, PPP, NFS and NIS support. This means that your FreeBSD machine can inter-operate easily with other systems as well act as an enterprise server, providing vital @@ -93,7 +92,7 @@ </listitem> <listitem> - <para><emphasis remap=bf>Memory protection</emphasis> ensures + <para><emphasis>Memory protection</emphasis> ensures that applications (or users) cannot interfere with each other. One application crashing will not affect others in any way.</para> @@ -106,57 +105,53 @@ </listitem> <listitem> - <para>The industry standard <emphasis remap=bf>X Window + <para>The industry standard <emphasis>X Window System</emphasis> (X11R6) provides a graphical user interface (GUI) for the cost of a common VGA card and monitor and comes with full sources.</para> </listitem> <listitem> - <para><emphasis remap=bf>Binary compatibility</emphasis> with + <para><emphasis>Binary compatibility</emphasis> with many programs built for SCO, BSDI, NetBSD, Linux and 386BSD.</para> </listitem> <listitem> - <para>Hundreds of <emphasis remap=bf>ready-to-run</emphasis> - applications are available from the FreeBSD <emphasis - remap=bf>ports</emphasis> and <emphasis - remap=bf>packages</emphasis> collection. Why search the net + <para>Hundreds of <emphasis>ready-to-run</emphasis> + applications are available from the FreeBSD <emphasis>ports</emphasis> and <emphasis>packages</emphasis> collection. Why search the net when you can find it all right here?</para> </listitem> <listitem> - <para>Thousands of additional and <emphasis - remap=bf>easy-to-port</emphasis> applications available on + <para>Thousands of additional and <emphasis>easy-to-port</emphasis> applications available on the Internet. FreeBSD is source code compatible with most popular commercial Unix systems and thus most applications require few, if any, changes to compile.</para> </listitem> <listitem> - <para>Demand paged <emphasis remap=bf>virtual memory</emphasis> + <para>Demand paged <emphasis>virtual memory</emphasis> and <quote>merged VM/buffer cache</quote> design efficiently satisfies applications with large appetites for memory while still maintaining interactive response to other users.</para> </listitem> <listitem> - <para><emphasis remap=bf>Shared libraries</emphasis> (the Unix + <para><emphasis>Shared libraries</emphasis> (the Unix equivalent of MS-Windows DLLs) provide for efficient use of disk space and memory.</para> </listitem> <listitem> - <para>A full compliment of <emphasis remap=bf>C</emphasis>, - <emphasis remap=bf>C++</emphasis> and <emphasis - remap=bf>Fortran</emphasis> development tools. Many + <para>A full compliment of <emphasis>C</emphasis>, + <emphasis>C++</emphasis> and <emphasis>Fortran</emphasis> development tools. Many additional languages for advanced research and development are also available in the ports and packages collection.</para> </listitem> <listitem> - <para><emphasis remap=bf>Source code</emphasis> for the entire + <para><emphasis>Source code</emphasis> for the entire system means you have the greatest degree of control over your environment. Why be locked into a proprietary solution and at the mercy of your vendor when you can have a truly Open @@ -164,12 +159,12 @@ </listitem> <listitem> - <para>Extensive <emphasis remap=bf>on-line + <para>Extensive <emphasis>on-line documentation</emphasis>.</para> </listitem> <listitem> - <para><emphasis remap=bf>And many more!</emphasis></para> + <para><emphasis>And many more!</emphasis></para> </listitem> </itemizedlist> @@ -183,7 +178,7 @@ the system for maximum performance and reliability in real-life load situations. As many of the commercial giants struggle to field PC operating systems with such features, performance and reliability, - FreeBSD can offer them <emphasis remap=bf>now</emphasis>!</para> + FreeBSD can offer them <emphasis>now</emphasis>!</para> <para>The applications to which FreeBSD can be put are truly limited only by your own imagination. From software development to factory @@ -207,7 +202,7 @@ <itemizedlist> <listitem> - <para><emphasis remap=bf>Internet Services:</emphasis> The + <para><emphasis>Internet Services:</emphasis> The robust TCP/IP networking built into FreeBSD makes it an ideal platform for a variety of Internet services such as: <itemizedlist> @@ -246,7 +241,7 @@ </listitem> <listitem> - <para><emphasis remap=bf>Education:</emphasis> Are you a student + <para><emphasis>Education:</emphasis> Are you a student of computer science or a related engineering field? There is no better way of learning about operating systems, computer architecture and networking than the hands on, under the hood @@ -258,7 +253,7 @@ </listitem> <listitem> - <para><emphasis remap=bf>Research:</emphasis> With source code + <para><emphasis>Research:</emphasis> With source code for the entire system available, FreeBSD is an excellent platform for research in operating systems as well as other branches of computer science. FreeBSD's freely available @@ -269,7 +264,7 @@ </listitem> <listitem> - <para><emphasis remap=bf>Networking:</emphasis> Need a new + <para><emphasis>Networking:</emphasis> Need a new router? A name server (DNS)? A firewall to keep people out of your internal network? FreeBSD can easily turn that unused 386 or 486 PC sitting in the corner into an advanced router @@ -277,7 +272,7 @@ </listitem> <listitem> - <para><emphasis remap=bf>X Window workstation:</emphasis> + <para><emphasis>X Window workstation:</emphasis> FreeBSD is a fine choice for an inexpensive X terminal solution, either using the freely available XFree86 server or one of the excellent commercial servers provided by X Inside. @@ -289,7 +284,7 @@ </listitem> <listitem> - <para><emphasis remap=bf>Software Development:</emphasis> The + <para><emphasis>Software Development:</emphasis> The basic FreeBSD system comes with a full compliment of development tools including the renowned GNU C/C++ compiler and debugger.</para> @@ -453,8 +448,8 @@ <para> <variablelist> - <varlistentry><term><emphasis remap=bf>The CVS - repository</emphasis><anchor + <varlistentry><term>The CVS + repository<anchor id="development-cvs-repository"></term> <listitem> <para>The central source tree for FreeBSD is maintained by @@ -468,8 +463,8 @@ </listitem> </varlistentry> - <varlistentry><term><emphasis remap=bf>The committers - list</emphasis><anchor id="development-committers"></term> + <varlistentry><term>The committers + list<anchor id="development-committers"></term> <listitem> <para>The <xref linkend="staff-committers" remap="committers"> @@ -483,8 +478,8 @@ </listitem> </varlistentry> - <varlistentry><term><emphasis remap=bf>The FreeBSD core - team</emphasis><anchor id="development-core"></term> + <varlistentry><term>The FreeBSD core + team<anchor id="development-core"></term> <listitem> <para>The <xref linkend="staff-core" remap="FreeBSD core @@ -512,14 +507,13 @@ <quote>board of directors</quote> analogy above is not actually very accurate, and it may be more suitable to say that these are the people who gave up their lives in favor - of FreeBSD against their better judgement! <emphasis - remap=tt>;)</emphasis></para> + of FreeBSD against their better judgement! <!-- smiley --><emphasis>;)</emphasis></para> </note> </listitem> </varlistentry> - <varlistentry><term><emphasis remap=bf>Outside - contributors</emphasis></term> + <varlistentry><term>Outside + contributors</term> <listitem> <para>Last, but definitely not least, the largest group of @@ -534,7 +528,7 @@ those who have contributed something which made its way into our source tree is a long and growing one, so why not join it by contributing something back to FreeBSD today? - <emphasis remap=tt>:-)</emphasis></para> + <!-- smiley --><emphasis>:-)</emphasis></para> <para>Providing code is not the only way of contributing to the project; for a more complete list of things that need @@ -616,7 +610,7 @@ manuals with any HTML capable browser using the following URLs:</para> - <para> + <variablelist> <varlistentry><term>The FreeBSD handbook</term> <listitem> @@ -634,7 +628,7 @@ </listitem> </varlistentry> </variablelist> - </para> + <para>You can also visit the master (and most frequently updated) copies at <ulink @@ -671,7 +665,7 @@ connection, via anonymous ftp or NFS.</para> <para>Regardless of the installation media you choose, you can get - started by creating the <emphasis remap=bf>installation + started by creating the <emphasis>installation disk</emphasis> as described below. Booting your computer into the FreeBSD installer, even if you aren't planning on installing FreeBSD right away, will provide important information about compatibility @@ -688,10 +682,11 @@ FreeBSD"> in the Appendix.</para> - <para>So, to get the show on the road, follow these steps: - <orderedlist> + <para>So, to get the show on the road, follow these steps:</para> + + <procedure> - <listitem> + <step> <para>Review the <xref linkend="install-hw" remap="supported configurations"> section of this installation guide to be sure that your hardware is supported by FreeBSD. It may be helpful @@ -699,9 +694,9 @@ SCSI controllers, Ethernet adapters or sound cards. This list should include relevant configuration parameters such as interrupts (IRQ) and IO port addresses.</para> - </listitem> + </step> - <listitem> + <step> <para>If you're installing FreeBSD from CDROM media then you have several different installation options: <itemizedlist> @@ -742,9 +737,9 @@ </itemizedlist> </para> - </listitem> + </step> - <listitem> + <step> <para>If you don't have a CDROM distribution then simply download the <ulink URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/&rel.current;-RELEASE/floppies/boot.flp">installation boot disk image</ulink> file to your hard drive, being sure to tell your browser to <emphasis>save</emphasis> rather than <emphasis>display</emphasis> the file.</para> @@ -753,20 +748,21 @@ <para>This disk image can only be used with 1.44 megabyte 3.5 inch floppy disks.</para> </note> - </listitem> + </step> - <listitem> + <step> <para>Make the installation boot disk from the image file: <itemizedlist> <listitem> <para>If you are using MS-DOS then download <ulink URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/tools/fdimage.exe">fdimage.exe</ulink> or get it from <filename>tools\fdimage.exe</filename> on the CDROM and then run it like so: + <informalexample> <screen><prompt>E:\></prompt> <userinput>tools\fdimage floppies\boot.flp a:</userinput></screen> </informalexample> The <emphasis>fdimage</emphasis> - program will format the A: drive and then copy the - boot.flp image onto it (assuming that you're at the top + program will format the <devicename>A:</devicename> drive and then copy the + <filename>boot.flp</filename> image onto it (assuming that you're at the top level of a FreeBSD distribution and the floppy images live in the floppies subdirectory, as is typically the case).</para> @@ -775,20 +771,21 @@ <listitem> <para>If you are using a UNIX system to create the floppy image: + <informalexample> <screen>&prompt.root; <userinput>dd if=boot.flp of=<replaceable>disk_device</replaceable></userinput></screen> </informalexample> where <replaceable>disk_device</replaceable> is the <filename>/dev</filename> entry for the floppy drive. On FreeBSD systems, this is <filename>/dev/rfd0</filename> - for the A: drive and <filename>/dev/rfd1</filename> for - the B: drive.</para> + for the <devicename>A:</devicename> drive and <filename>/dev/rfd1</filename> for + the <devicename>B:</devicename> drive.</para> </listitem> </itemizedlist> </para> - </listitem> + </step> - <listitem> + <step> <para>With the installation disk in the A: drive, reboot your computer. You should get a boot prompt something like this: <informalexample> @@ -805,17 +802,16 @@ Boot: boots, it probes your computer to determine what hardware is installed. The results of this probing is displayed on the screen.</para> - </listitem> + </step> - <listitem> + <step> <para>When the booting process is finished, The main FreeBSD installation menu will be displayed.</para> - </listitem> + </step> - </orderedlist> - </para> + </procedure> - <para><emphasis remap=bf>If something goes wrong...</emphasis></para> + <para><emphasis>If something goes wrong...</emphasis></para> <para>Due to limitations of the PC architecture, it is impossible for probing to be 100 percent reliable. In the event that your hardware @@ -826,8 +822,8 @@ Boot: indeed supported by FreeBSD.</para> <para>If your hardware is supported, reset the computer and when the - <emphasis remap=tt>Boot:</emphasis> prompt comes up, type - <option>-c</option>. This puts FreeBSD into a configuration mode + <prompt>Boot:</prompt> prompt comes up, type + <literal>-c</literal>. This puts FreeBSD into a configuration mode where you can supply hints about your hardware. The FreeBSD kernel on the installation disk is configured assuming that most hardware devices are in their factory default configuration in terms of IRQs, @@ -842,7 +838,7 @@ Boot: <para>In the configuration mode, you can:</para> - <para> + <itemizedlist> <listitem> @@ -860,13 +856,13 @@ Boot: </listitem> </itemizedlist> - </para> - <para>While at the <emphasis remap=tt>config></emphasis> prompt, type + + <para>While at the <prompt>config></prompt> prompt, type <command>help</command> for more information on the available commands. After adjusting the kernel to match how you have your hardware configured, type <command>quit</command> at - the <emphasis remap=tt>config></emphasis> prompt to continue + the <prompt>config></prompt> prompt to continue booting with the new settings.</para> <para>After FreeBSD has been installed, changes made in the @@ -901,7 +897,7 @@ Boot: <sect2> <title>Disk Controllers</title> - <para> + <itemizedlist> <listitem> @@ -1022,7 +1018,7 @@ Boot: </listitem> </itemizedlist> - </para> + <para>With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including Disks, tape drives @@ -1031,7 +1027,7 @@ Boot: <para>The following CD-ROM type systems are supported at this time:</para> - <para> + <itemizedlist> <listitem> @@ -1057,7 +1053,7 @@ Boot: </listitem> </itemizedlist> - </para> + </sect2> @@ -1065,7 +1061,7 @@ Boot: id="install-nics"> <title>Ethernet cards</title> - <para> + <itemizedlist> <listitem> @@ -1238,7 +1234,7 @@ Boot: </listitem> </itemizedlist> - </para> + <note> <para>FreeBSD does not currently support @@ -1252,7 +1248,7 @@ Boot: id="install-misc"> <title>Miscellaneous devices</title> - <para> + <itemizedlist> <listitem> @@ -1328,7 +1324,7 @@ Boot: </listitem> </itemizedlist> - </para> + <para>FreeBSD does not currently support IBM's microchannel (MCA) bus.</para> @@ -1361,7 +1357,7 @@ Boot: <note> <para>If you are running FreeBSD 2.1-RELEASE and have an IDE - CDROM, use the inst_ide.bat or atapiflp.bat batch files + CDROM, use the <filename>inst_ide.bat</filename> or <filename>atapiflp.bat</filename> batch files instead.</para> </note> @@ -1423,7 +1419,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <para>You will need, at minimum, as many 1.44MB or 1.2MB floppies as it takes to hold all files in the bin (binary distribution) directory. If you are preparing these floppies under DOS, then - THESE floppies *must* be formatted using the MS-DOS FORMAT + THESE floppies <emphasis>must</emphasis> be formatted using the MS-DOS FORMAT command. If you are using Windows, use the Windows File Manager format command.</para> @@ -1440,14 +1436,14 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent following sequence of commands (for a 3.5" 1.44MB floppy disk) illustrates:</para> - <para> + <informalexample> <screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput> &prompt.root; <userinput>disklabel -w -r fd0.1440 floppy3</userinput> &prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/rfd0</userinput> </screen> </informalexample> - </para> + <note> <para>Use <literal>fd0.1200</literal> and @@ -1482,12 +1478,13 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent the CDROM must be partially reproduced within this directory so we suggest using the DOS <command>xcopy</command> command. For example, to prepare for a minimal installation of FreeBSD: + <informalexample> <screen><prompt>C:\></prompt> <userinput>MD C:\FREEBSD</userinput> <prompt>C:\></prompt> <userinput>XCOPY /S E:\BIN C:\FREEBSD\BIN\</userinput> <prompt>C:\></prompt> <userinput>XCOPY /S E:\MANPAGES C:\FREEBSD\MANPAGES\</userinput></screen> - </informalexample> assuming that <filename>C:</filename> - is where you have free space and <filename>E:</filename> + </informalexample> assuming that <devicename>C:</devicename> + is where you have free space and <devicename>E:</devicename> is where your CDROM is mounted.</para> <para>For as many <abbrev>DISTS</abbrev> you wish to install from MS-DOS (and you @@ -1505,6 +1502,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent program expects the files to be simply tar'ed onto the tape, so after getting all of the files for distribution you are interested in, simply tar them onto the tape with a command like: + <informalexample> <screen>&prompt.root; <userinput>cd /freebsd/distdir</userinput> &prompt.root; <userinput>tar cvf /dev/rwt0 dist1 ... dist2</userinput></screen> @@ -1531,7 +1529,8 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <title>Before installing over a network</title> <para>You can do network installations over 3 types of - communications links: + communications links:</para> + <variablelist> <varlistentry><term>Serial port</term> <listitem> @@ -1557,7 +1556,6 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent </listitem> </varlistentry> </variablelist> - </para> <para>SLIP support is rather primitive, and limited primarily to hard-wired links, such as a serial cable running between a laptop @@ -1633,7 +1631,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <para>In order for NFS installation to work, the server must support subdir mounts, e.g., if your FreeBSD &rel.current; distribution directory lives on: - <filename>ziggy:/usr/archive/stuff/FreeBSD</filename> Then ziggy + <filename>ziggy:/usr/archive/stuff/FreeBSD</filename> Then <hostid>ziggy</hostid> will have to allow the direct mounting of <filename>/usr/archive/stuff/FreeBSD</filename>, not just <filename>/usr</filename> or @@ -1662,15 +1660,15 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent a direct IP address, so the following would work in the absence of a name server:</para> - <para> + <informalexample> <screen><userinput>ftp://165.113.121.81/pub/FreeBSD/&rel.current;-RELEASE</userinput></screen> </informalexample> - </para> + <para>There are two FTP installation modes you can use:</para> - <para> + <variablelist> <varlistentry><term>FTP Active</term> <listitem> @@ -1692,7 +1690,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent </listitem> </varlistentry> </variablelist> - </para> + <note> <para>Active and passive modes are not the same as a <quote>proxy</quote> @@ -1703,13 +1701,14 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <para>For a proxy FTP server, you should usually give name of the server you really want as a part of the username, after an @-sign. The proxy server then 'fakes' the real server. An - example: Say you want to install from ftp.freebsd.org, using the - proxy FTP server foo.bar.com, listening on port 1234.</para> + example: Say you want to install from <hostid>ftp.freebsd.org</hostid>, using the + proxy FTP server <hostid>foo.bar.com</hostid>, listening on port 1234.</para> <para>In this case, you go to the options menu, set the FTP username to ftp@ftp.freebsd.org, and the password to your e-mail address. As your installation media, you specify FTP (or passive FTP, if the proxy support it), and the URL + <informalexample> <screen><userinput>ftp://foo.bar.com:1234/pub/FreeBSD</userinput></screen> </informalexample> <filename>/pub/FreeBSD</filename> from <hostid>ftp.freebsd.org</hostid> is proxied @@ -1747,7 +1746,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <para>Meanwhile, you may also find the following <quote>typical installation sequence</quote> to be helpful:</para> - <para> + <orderedlist> <listitem> @@ -1762,7 +1761,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <listitem> <para>Press F1. You should see some basic usage instructions on the menu system and general navigation. If you have not used - this menu system before then PLEASE read this thoroughly!</para> + this menu system before then <emphasis>please</emphasis> read this thoroughly!</para> </listitem> <listitem> @@ -1793,7 +1792,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent </listitem> </orderedlist> - </para> + </sect1> @@ -1804,7 +1803,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent MS-DOS. Here are some commonly asked questions about installing FreeBSD on such systems.</para> - <para><emphasis remap=bf>Help! I have no space! Do I need to delete + <para><emphasis>Help! I have no space! Do I need to delete everything first?</emphasis></para> <para>If your machine is already running MS-DOS and has little or no @@ -1823,26 +1822,26 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent much free space you will need for the kind of installation you want.</para> - <para><emphasis remap=bf>Can I use compressed MS-DOS filesystems from + <para><emphasis>Can I use compressed MS-DOS filesystems from FreeBSD?</emphasis></para> <para>No. If you are using a utility such as Stacker(tm) or DoubleSpace(tm), FreeBSD will only be able to use whatever portion of the filesystem you leave uncompressed. The rest of the filesystem will show up as one large file (the stacked/dblspaced - file!). <emphasis remap=bf>Do not remove that file!</emphasis> You + file!). <emphasis>Do not remove that file!</emphasis> You will probably regret it greatly!</para> <para>It is probably better to create another uncompressed MS-DOS primary partition and use this for communications between MS-DOS and FreeBSD.</para> - <para><emphasis remap=bf>Can I mount my MS-DOS extended + <para><emphasis>Can I mount my MS-DOS extended partitions?</emphasis></para> <para>Yes. DOS extended partitions are mapped in at the end of the - other <quote>slices</quote> in FreeBSD, e.g. your <filename>D:</filename> drive might be <filename>/dev/sd0s5</filename>, - your <filename>E:</filename> drive <filename>/dev/sd0s6</filename>, and so on. This example assumes, of + other <quote>slices</quote> in FreeBSD, e.g. your <devicename>D:</devicename> drive might be <filename>/dev/sd0s5</filename>, + your <devicename>E:</devicename> drive <filename>/dev/sd0s6</filename>, and so on. This example assumes, of course, that your extended partition is on SCSI drive 0. For IDE drives, substitute <filename>wd</filename> for <filename>sd</filename> appropriately. You otherwise mount extended partitions exactly like you would mount any other DOS @@ -1852,7 +1851,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <screen>&prompt.root; <userinput>mount -t msdos /dev/sd0s5 /dos_d</userinput></screen> </informalexample> - <para><emphasis remap=bf>Can I run MS-DOS binaries under + <para><emphasis>Can I run MS-DOS binaries under FreeBSD?</emphasis></para> <para>BSDI has donated their DOS emulator to the BSD world and this @@ -1881,6 +1880,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent operation and various arguments. These manuals can be view with the <command>man</command> command. Use of the <command>man</command> command is simple: + <informalexample> <screen>&prompt.user; <userinput>man <replaceable>command</replaceable></userinput> </screen> @@ -1892,7 +1892,8 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent </informalexample> </para> - <para>The online manual is divided up into numbered sections: + <para>The online manual is divided up into numbered sections:</para> + <orderedlist> <listitem> @@ -1927,45 +1928,50 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <para>System maintenance and operation commands</para> </listitem> - </orderedlist> in some cases, the same topic may appear in more than + </orderedlist> + + <para>In some cases, the same topic may appear in more than one section of the on-line manual. For example, there is a - <emphasis remap=tt><command>chmod</command></emphasis> - user command and a <emphasis - remap=tt><function>chmod()</function></emphasis> system call. In - this case, you can tell the <emphasis remap=tt><emphasis - remap=bf>man</emphasis></emphasis> command which one you want by + <command>chmod</command> + user command and a <function>chmod()</function> system call. In + this case, you can tell the <command>man</command> command which one you want by specifying the section: + <informalexample> <screen>&prompt.user; <userinput>man 1 chmod</userinput></screen> </informalexample> which will display the manual page for the user - command <emphasis remap=tt><emphasis - remap=bf>chmod</emphasis></emphasis>. References to a + command <command>chmod</command>. References to a particular section of the on-line manual are traditionally placed in parenthesis in written documentation, so <citerefentry<refentrytitle>chmod</refentrytitle><manvolnum>1</manvolnum></citerefentry> refers to the - <emphasis remap=tt><command>chmod</command></emphasis> + <command>chmod</command> user command and <citerefentry><refentrytitle>chmod</refentrytitle><manvolnum>2</manvolnum></citerefentry> refers to the system call.</para> <para>This is fine if you know the name of the command and simply wish to know how to use it, but what if you cannot recall the command - name? You can use <emphasis remap=tt><emphasis - remap=bf>man</emphasis></emphasis> to search for keywords in the - command <emphasis>descriptions</emphasis> by using the <emphasis - remap=tt><option>-k</option></emphasis> switch: + name? You can use <command>man</command> to search for keywords in the + command <emphasis>descriptions</emphasis> by using the + <option>-k</option> switch:</para> + <informalexample> <screen>&prompt.user; <userinput>man -k mail</userinput></screen> - </informalexample> With this command you will be presented with a + </informalexample> + + <para>With this command you will be presented with a list of commands that have the keyword <quote>mail</quote> in their descriptions. - This is actually functionally equivalent to using the <emphasis - remap=tt><command>apropos</command></emphasis> + This is actually functionally equivalent to using the <command>apropos</command> command.</para> <para>So, you are looking at all those fancy commands in <filename>/usr/bin</filename> but do not even have the faintest idea what most of them actually do? Simply do a + <informalexample> <screen>&prompt.user; <userinput>cd /usr/bin; man -f *</userinput></screen> - </informalexample> or + </informalexample> + + or + <informalexample> <screen>&prompt.user; <userinput>cd /usr/bin; whatis *</userinput></screen> </informalexample> which does the same thing.</para> @@ -1979,14 +1985,17 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <para>FreeBSD includes many applications and utilities produced by the Free Software Foundation (FSF). In addition to man pages, these programs come with more extensive hypertext documents called - <emphasis>info</emphasis> files which can be viewed with the + <quote>info</quote> files which can be viewed with the <command>info</command> command or, if you installed <command>emacs</command>, the info mode of <command>emacs</command>.</para> <para>To use the <citerefentry><refentrytitle>info</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, simply type: + <informalexample> <screen>&prompt.user; <userinput>info</userinput></screen> - </informalexample> For a brief introduction, type <userinput>h</userinput>. For a quick + </informalexample> + + For a brief introduction, type <userinput>h</userinput>. For a quick command reference, type <userinput>?</userinput>.</para> </sect1> @@ -2016,13 +2025,13 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent they have an unfortunate tendency to triumphantly announce that your system is something you have never heard of and then ask you lots of questions that sound like a final exam in system-level Unix - programming (<quote>Does your system's gethitlist function return a const + programming (<literal>Does your system's gethitlist function return a const pointer to a fromboz or a pointer to a const fromboz? Do you have Foonix style unacceptable exception handling? And if not, why - not?</quote>).</para> + not?</literal>).</para> <para>Fortunately, with the Ports collection, all the hard work - involved has already been done, and you can just type 'make install' + involved has already been done, and you can just type <command>make install</command> and get a working program.</para> @@ -2033,7 +2042,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent and system utilities, but a lot of popular programs are not in the base system, for good reasons:-</para> - <para> + <orderedlist> <listitem> @@ -2065,7 +2074,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent </listitem> </orderedlist> - </para> + <para>Obviously it would be unreasonable to expect everyone to port their favourite programs by hand (not to mention a tremendous amount @@ -2116,8 +2125,10 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <application>ElectricFence</application>, a useful tool for developers, as the skeleton is more straightforward than most.</para> - <para><emphasis>Note</emphasis> if you are trying this at home, you + <note> + <para>If you are trying this at home, you will need to be root.</para> + </note> <informalexample> <screen>&prompt.root; <userinput>cd /usr/ports/devel/ElectricFence</userinput> @@ -2144,7 +2155,8 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc <para>If you tried this yourself, you may well have got something like this at the start:-</para> - <para><anchor id="ports-fetch"> <informalexample> + <para><anchor id="ports-fetch"> + <informalexample> <screen>&prompt.root; <userinput>make install</userinput> >> ElectricFence-2.0.5.tar.gz doesn't seem to exist on this system. >> Attempting to fetch from ftp://ftp.doc.ic.ac.uk/Mirrors/sunsite.unc.edu/pub/Linux/devel/lang/c/.</screen> @@ -2159,60 +2171,60 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc <para>Let's go through this and see what the <command>make</command> program was doing.</para> - <para> - <orderedlist> + + <procedure> - <listitem> + <step> <para>Locate the source code <xref linkend="ports-tarball" remap="tarball."> If it is not available locally, try to grab it from an FTP site.</para> - </listitem> + </step> - <listitem> + <step> <para>Run a <xref linkend="ports-checksum" remap="checksum"> test on the tarball to make sure it has not been tampered with, accidentally truncated, downloaded in ASCII mode, struck by neutrinos while in transit, etc.</para> - </listitem> + </step> - <listitem> + <step> <para>Extract the tarball into a temporary work directory.</para> - </listitem> + </step> - <listitem> + <step> <para>Apply any <xref linkend="ports-patch" remap="patches"> needed to get the source to compile and run under FreeBSD.</para> - </listitem> + </step> - <listitem> + <step> <para>Run any configuration script required by the build process and correctly answer any questions it asks.</para> - </listitem> + </step> - <listitem> + <step> <para>(Finally!) Compile the code.</para> - </listitem> + </step> - <listitem> + <step> <para>Install the program executable and other supporting files, man pages, etc. under the <filename>/usr/local</filename> hierarchy, where they will not get mixed up with system programs. This also makes sure that all the ports you install will go in the same place, instead of being flung all over your system.</para> - </listitem> + </step> - <listitem> + <step> <para>Register the installation in a database. This means that, if you do not like the program, you can cleanly <xref linkend="ports-remove" remap="remove"> all traces of it from your system.</para> - </listitem> + </step> - </orderedlist> - </para> + </procedure> + - <para>Scroll up to the make output and see if you can match these + <para>Scroll up to the <command>make</command> output and see if you can match these steps to it. And if you were not impressed before, you should be by now!</para> @@ -2272,7 +2284,7 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc &prompt.root; <userinput>make install</userinput></screen> </informalexample> - <para>(yes, that really is a dot on its own after the cp command and + <para>(yes, that really is a dot on its own after the <command>cp</command> command and not a mistake. It is Unix-ese for <quote>the current directory</quote>)</para> @@ -2344,7 +2356,7 @@ password. Remember to use binary (also known as image) mode!] </informalexample> <para>What happened here? We connected to the FTP server in the - usual way and went to its databases sub-directory. When we gave it + usual way and went to its <filename>databases</filename> sub-directory. When we gave it the command <command>get gnats.tar</command>, the FTP server <xref linkend="ports-tarball" remap="tarred"> up the gnats directory for us.</para> @@ -2437,14 +2449,14 @@ do-install: the benefit of human readers (as in most Unix script files).</para> - <para>`DISTNAME" specifies the name of the <xref + <para><literal>DISTNAME</literal> specifies the name of the <xref linkend="ports-tarball" remap="tarball">, but without the extension.</para> - <para>`CATEGORIES" states what kind of program this is. In + <para><literal>CATEGORIES</literal> states what kind of program this is. In this case, a utility for developers.</para> - <para>`MASTER_SITES" is the URL(s) of the master FTP site, + <para><literal>MASTER_SITES</literal> is the URL(s) of the master FTP site, which is used to retrieve the <xref linkend="ports-tarball" remap="tarball"> if it is not available on the local system. This is a site which is regarded as reputable, and is normally the @@ -2452,12 +2464,12 @@ do-install: as any software is "officially" distributed on the Internet).</para> - <para>`MAINTAINER" is the email address of the person who is + <para><literal>MAINTAINER</literal> is the email address of the person who is responsible for updating the skeleton if, for example a new version of the program comes out.</para> <para>Skipping over the next few lines for a minute, the line - <literallayout> .include <bsd.port.mk> </literallayout> says + <literal>.include <bsd.port.mk></literal> says that the other statements and commands needed for this port are in a standard file called <filename>bsd.port.mk</filename>. As these are the same for all ports, there is no point in duplicating @@ -2503,7 +2515,7 @@ do-install: <para>This program contains three quite useful files:-</para> - <para> + <itemizedlist> <listitem> @@ -2521,7 +2533,7 @@ do-install: </listitem> </itemizedlist> - </para> + </sect2> </sect1> @@ -2532,7 +2544,7 @@ do-install: <para>Oh. You can do one of four (4) things :</para> - <para> + <orderedlist> <listitem> @@ -2542,7 +2554,7 @@ do-install: </listitem> <listitem> - <para>Gripe. This is done by e-mail *ONLY*! Send such e-mail to + <para>Gripe. This is done by e-mail <emphasis>only</emphasis>! Send such e-mail to the &a.ports; and please include the name/version of the port, where you got both the port source & distfile(s) from, and what the text of the error was.</para> @@ -2566,7 +2578,7 @@ do-install: </listitem> </orderedlist> - </para> + </sect1> @@ -2610,7 +2622,7 @@ do-install: <para>A. Several reasons:-</para> - <para> + <orderedlist> <listitem> @@ -2647,11 +2659,11 @@ do-install: <listitem> <para>If you ain't got the source, it ain't software! - ;-)</para> + <!-- smiley -->;-)</para> </listitem> </orderedlist> - </para> + </listitem> <listitem> @@ -2753,7 +2765,7 @@ do-install: <filename>/u/people/guests/wurzburger</filename>, but it does not seem to work.</para> - <para>A. You can use the PORTSDIR and PREFIX variables to tell + <para>A. You can use the <makevar>PORTSDIR</makevar> and <makevar>PREFIX</makevar> variables to tell the ports mechanism to use different directories. For instance,</para> @@ -2819,8 +2831,8 @@ do-install: tell the port to fetch them from servers other than ones listed in the MASTER_SITES?</para> - <para>A. Yes. If you know, for example, ftp.FreeBSD.ORG is much - closer than sites listed in MASTER_SITES, do as following + <para>A. Yes. If you know, for example, <hostid>ftp.FreeBSD.ORG</hostid> is much + closer than sites listed in <makevar>MASTER_SITES</makevar>, do as following example. <informalexample> @@ -2851,11 +2863,11 @@ do-install: <listitem> <para>Q. I am trying to make my own port and I want to be able to stop it compiling until I have had a chance to see if my - patches worked properly. Is there something like 'make - extract', but for patches?</para> + patches worked properly. Is there something like <command>make + extract</command>, but for patches?</para> <para>A. Yep, <command>make patch</command> is what you want. You will probably - find the PATCH_DEBUG option useful as well. And by the way, + find the <makevar>PATCH_DEBUG</makevar> option useful as well. And by the way, thank you for your efforts!</para> </listitem> @@ -2864,7 +2876,7 @@ do-install: Is this true? How can I make sure that I compile ports with the right settings?</para> - <para>A. Yes, with version 2.6.3 of gcc (the version shipped + <para>A. Yes, with version 2.6.3 of <command>gcc</command> (the version shipped with FreeBSD 2.1.0 and 2.1.5), the <option>-O2</option> option could result in buggy code unless you used the <option>-fno-strength-reduce</option> option as well. (Most of the ports don't use <option>-O2</option>). You @@ -2877,7 +2889,7 @@ do-install: <para>or by editing <filename>/etc/make.conf</filename>, but unfortunately not all ports respect this. The surest way is to - do 'make configure', then go into the source directory and + do <command>make configure</command>, then go into the source directory and inspect the Makefiles by hand, but this can get tedious if the source has lots of sub-directories, each with their own Makefiles.</para> @@ -2891,19 +2903,20 @@ do-install: </listitem> <listitem> - <para>Q. I went to install the 'foo' port but the system - suddenly stopped compiling it and starting compiling the 'bar' + <para>Q. I went to install the <literal>foo</literal> port but the system + suddenly stopped compiling it and starting compiling the + <literal>bar</literal> port. What's going on?</para> - <para>A. The 'foo' port needs something that is supplied with - 'bar' - for instance, if 'foo' uses graphics, 'bar' might have - a library with useful graphics processing routines. Or 'bar' - might be a tool that is needed to compile the 'foo' + <para>A. The <literal>foo</literal> port needs something that is supplied with + <literal>bar</literal> - for instance, if <literal>foo</literal> uses graphics, <literal>bar</literal> might have + a library with useful graphics processing routines. Or <literal>bar</literal> + might be a tool that is needed to compile the <literal>foo</literal> port.</para> </listitem> <listitem> - <para><anchor id="ports-remove"> Q. I installed the grizzle + <para><anchor id="ports-remove"> Q. I installed the <literal>grizzle</literal> program from the ports and frankly it is a complete waste of disk space. I want to delete it but I do not know where it put all the files. Any clues?</para> @@ -3007,7 +3020,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> <listitem> - <para>Q. At work, we are using frobble, which is in your ports + <para>Q. At work, we are using <literal>frobble</literal>, which is in your ports collection, but we have altered it quite a bit to get it to do what we need. Is there any way of making our own packages, so we can distribute it more easily around our sites?</para> @@ -3074,7 +3087,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <para>Building a custom kernel is one of the most important rites of passage every Unix system administrator must endure. This process, while time-consuming, will provide many benefits to your FreeBSD - system. Unlike the GENERIC kernel, which must support every + system. Unlike the <literal>GENERIC</literal> kernel, which must support every possible SCSI and network card, along with tons of other rarely used hardware support, a custom kernel only contains support for <emphasis>your</emphasis> PC's hardware. This has a number of @@ -3120,7 +3133,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc subdirectories here representing different parts of the kernel, but the most important, for our purposes, are <filename>i386/conf</filename>, where you will edit your custom - kernel configuration, and <emphasis remap=tt>compile</emphasis>, + kernel configuration, and <filename>compile</filename>, which is the staging area where your kernel will be built. Notice the logical organization of the directory tree, with each supported device, filesystem, and option in its own subdirectory. Also, @@ -3140,6 +3153,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <para>Next, move to the <filename>i386/conf</filename> directory and copy the <filename>GENERIC</filename> configuration file to the name you want to give your kernel. For example: + <informalexample> <screen>&prompt.root; <userinput>cd /usr/src/sys/i386/conf</userinput> &prompt.root; <userinput>cp GENERIC MYKERNEL</userinput></screen> @@ -3186,6 +3200,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <para>When you are finished, type the following to compile and install your kernel: + <informalexample> <screen>&prompt.root; <userinput>/usr/sbin/config MYKERNEL</userinput> &prompt.root; <userinput>cd ../../compile/MYKERNEL</userinput> @@ -3255,7 +3270,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <para>These keywords are required in every kernel you build.</para> - <para> + <variablelist> <varlistentry><term>machine "i386"</term> <listitem> @@ -3271,13 +3286,12 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> </varlistentry> - <varlistentry><term>cpu "<symbol>cpu_type</symbol>"</term> + <varlistentry><term>cpu "<replaceable>cpu_type</replaceable>"</term> <listitem> <para>The next keyword is <literal>cpu</literal>, which includes support for each CPU supported by FreeBSD. - The possible values of <emphasis - remap=tt><replaceable>cpu_type</replaceable></emphasis> + The possible values of <replaceable>cpu_type</replaceable> include: <itemizedlist> @@ -3298,24 +3312,22 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> </itemizedlist> and multiple instances of the <literal>cpu</literal> line may be present with - different values of <emphasis - remap=tt><replaceable>cpu_type</replaceable></emphasis> + different values of <replaceable>cpu_type</replaceable> as are present in the <filename>GENERIC</filename> kernel. For a custom kernel, it is best to specify only the cpu you have. If, for example, you have an Intel Pentium, use - <symbol>I586_CPU</symbol> for <emphasis - remap=tt><replaceable>cpu_type</replaceable></emphasis>.</para> + <literal>I586_CPU</literal> for <replaceable>cpu_type</replaceable>.</para> </listitem> </varlistentry> - <varlistentry><term>ident <symbol>machine_name</symbol></term> + <varlistentry><term>ident <replaceable>machine_name</replaceable></term> <listitem> <para>Next, we have <literal>ident</literal>, which is the identification of the kernel. You should - change this from <filename>GENERIC</filename> to whatever + change this from <literal>GENERIC</literal> to whatever you named your kernel, in this example, - <filename>MYKERNEL</filename>. The value you put in + <literal>MYKERNEL</literal>. The value you put in <literal>ident</literal> will print when you boot up the kernel, so it is useful to give a kernel a different name if you want to keep it separate from your @@ -3326,32 +3338,32 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <para>Since this name is passed to the C compiler as a <option>-D</option> switch, do not use names like - <option>DEBUG</option>, or something that could be + <literal>DEBUG</literal>, or something that could be confused with another machine or CPU name, like <literal>vax</literal>.</para> </listitem> </varlistentry> - <varlistentry><term>maxusers <emphasis>number</emphasis></term> + <varlistentry><term>maxusers <replaceable>number</replaceable></term> <listitem> <para>This file sets the size of a number of important system tables. This number is supposed to be roughly equal to the number of simultaneous users you expect to have on your machine. However, under normal - circumstances, you will want to set <literal>maxusers</literal> to at least four, + circumstances, you will want to set + <literal>maxusers</literal> to at least <literal>4</literal>, especially if you are using the X Window System or compiling software. The reason is that the most important table set by <literal>maxusers</literal> is the - maximum number of processes, which is set to <emphasis - remap=bf><emphasis remap=tt>20 + 16 * - maxusers</emphasis></emphasis>, so if you set - <literal>maxusers</literal> to one, then you + maximum number of processes, which is set to <literal>20 + 16 * + maxusers</literal>, so if you set + <literal>maxusers</literal> to <literal>1</literal>, then you can only have 36 simultaneous processes, including the 18 or so that the system starts up at boot time, and the 15 or so you will probably create when you start the X Window - System. Even a simple task like reading a <command>man</command> page will start up nine + System. Even a simple task like reading a man page will start up nine processes to filter, decompress, and view it. Setting - <literal>maxusers</literal> to 4 will allow you + <literal>maxusers</literal> to <literal>4</literal> will allow you to have up to 84 simultaneous processes, which should be enough for anyone. If, however, you see the dreaded <errorname>proc table full</errorname> error when trying to start another @@ -3375,16 +3387,16 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> </varlistentry> - <varlistentry><term>config <symbol>kernel_name</symbol> root on - <symbol>root_device</symbol></term> + <varlistentry><term>config <replaceable>kernel_name</replaceable> root on + <replaceable>root_device</replaceable></term> <listitem> <para>This line specifies the location and name of the kernel. Traditionally the kernel is called <filename>vmunix</filename> but in FreeBSD, it is aptly named <filename>kernel</filename>. You should always use - <filename>kernel</filename> for - <symbol>kernel_name</symbol> because changing it will + <literal>kernel</literal> for + <replaceable>kernel_name</replaceable> because changing it will render numerous system utilities inoperative. The second part of the line specifies the disk and partition where the root filesystem and kernel can be found. Typically @@ -3394,7 +3406,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> </varlistentry> </variablelist> - </para> + </sect2> @@ -3419,7 +3431,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc come with FreeBSD are <emphasis>not</emphasis> very accurate. If you do not have a math co-processor, and you need the best accuracy, I recommend that you change - this option to <symbol>GPL_MATH_EMULATE</symbol> to use + this option to <literal>GPL_MATH_EMULATE</literal> to use the superior GNU math support, which is not included by default for licensing reasons.</para> </note> @@ -3510,7 +3522,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc Loadable Kernel Module directory <filename>/lkm</filename> the first time you mount a partition of that type.</para> - <para> + <variablelist> <varlistentry><term>options FFS</term> <listitem> @@ -3535,8 +3547,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc formatted hard drive partition at boot time, you can safely comment this out. It will be automatically loaded the first time you mount a DOS partition, as described - above. Also, the excellent <emphasis - remap=tt>mtools</emphasis> software (in the ports + above. Also, the excellent <application>mtools</application> software (in the ports collection) allows you to access DOS floppies without having to mount and unmount them (and does not require MSDOSFS at all).</para> @@ -3575,7 +3586,8 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc store temporary data here. To mount an MFS RAM disk on <filename>/tmp</filename>, add the following line to <filename>/etc/fstab</filename> and then reboot or type - <command>mount /tmp</command>: + <command>mount /tmp</command>: + <programlisting> /dev/wd1s2b /tmp mfs rw 0 0 </programlisting> @@ -3585,6 +3597,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <para>Replace the <filename>/dev/wd1s2b</filename> with the name of your swap partition, which will be listed in your <filename>/etc/fstab</filename> as follows: + <programlisting> /dev/wd1s2b none swap sw 0 0 </programlisting> @@ -3622,7 +3635,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> </varlistentry> </variablelist> - </para> + </sect2> @@ -3635,7 +3648,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc remap="SCSI"> controllers and <xref linkend="kernelconfig-network" remap="network"> cards.</para> - <para> + <variablelist> <varlistentry><term>controller isa0</term> <listitem> @@ -3657,8 +3670,9 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <varlistentry><term>controller fdc0</term> <listitem> - <para>Floppy drive controller: <literal>fd0</literal> is the <filename>A:</filename> floppy drive, and - <literal>fd1</literal> is the <filename>B:</filename> drive. + <para>Floppy drive controller: <literal>fd0</literal> is the + <devicename>A:</devicename> floppy drive, and + <literal>fd1</literal> is the <devicename>B:</devicename> drive. <literal>ft0</literal> is a QIC-80 tape drive attached to the floppy controller. Comment out any lines corresponding to devices you do not have.</para> @@ -3760,7 +3774,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> </varlistentry> </variablelist> - </para> + </sect2> @@ -3771,7 +3785,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <para>This section describes the various SCSI controllers and devices supported by FreeBSD.</para> - <para> + <variablelist> <varlistentry><term>SCSI Controllers</term> <listitem> @@ -3915,11 +3929,11 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <para>If you want to <quote>wire down</quote> specific target IDs to particular devices, refer to the appropriate section of - the LINT kernel config file.</para> + the <filename>LINT</filename> kernel config file.</para> </listitem> </varlistentry> </variablelist> - </para> + </sect2> @@ -3931,7 +3945,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc XSERVER option and optionally, a bus mouse or PS/2 mouse device.</para> - <para> + <variablelist> <varlistentry><term>device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr</term> @@ -3939,9 +3953,9 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <para><literal>sc0</literal> is the default console driver, which resembles an SCO console. Since most full-screen programs access the console through a terminal - database library like <emphasis>termcap</emphasis>, it + database library like <filename>termcap</filename>, it should not matter much whether you use this or <literal>vt0</literal>, the VT220 compatible console - driver. When you log in, set your TERM variable to + driver. When you log in, set your <envar>TERM</envar> variable to <quote>scoansi</quote> if full-screen programs have trouble running under this console.</para> </listitem> @@ -3953,17 +3967,16 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <listitem> <para>This is a VT220-compatible console driver, backwards compatible to VT100/102. It works well on some laptops - which have hardware incompatibilities with <literal>sc0</literal>. Also, set your TERM variable - to <quote>vt100</quote> or <quote>vt220</quote> when you log in. This driver + which have hardware incompatibilities with <literal>sc0</literal>. Also, set your <envar>TERM</envar> variable + to <literal>vt100</literal> or <literal>vt220</literal> when you log in. This driver might also prove useful when connecting to a large number of different machines over the network, where the - <emphasis>termcap</emphasis> or - <emphasis>terminfo</emphasis> entries for the <emphasis - remap=tt>sc0</emphasis> device are often not available - -- <quote>vt100</quote> should be available on virtually any + <filename>termcap</filename> or + <filename>terminfo</filename> entries for the <devicename>sc0</devicename> device are often not available + -- <literal>vt100</literal> should be available on virtually any platform.</para> - <para> + <variablelist> <varlistentry><term>options "PCVT_FREEBSD=210"</term> <listitem> @@ -3975,14 +3988,13 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <listitem> <para>Only applicable with the <literal>vt0</literal> console driver. This - includes code required to run the <emphasis - remap=tt>XFree86</emphasis> X Window Server + includes code required to run the <application>XFree86</application> X Window Server under the <literal>vt0</literal> console driver.</para> </listitem> </varlistentry> </variablelist> - </para> + </listitem> </varlistentry> @@ -4012,7 +4024,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> </varlistentry> </variablelist> - </para> + </sect2> @@ -4026,13 +4038,12 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc remap="Dialup access"> provides extensive detail on serial port configuration for use with such devices.</para> - <para> + <variablelist> <varlistentry><term>device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr<anchor id="kernelconfig-serial"></term> <listitem> - <para><emphasis remap=tt>sio0</emphasis> through <emphasis - remap=tt>sio3</emphasis> are the four serial ports + <para><literal>sio0</literal> through <literal>sio3</literal> are the four serial ports referred to as COM1 through COM4 in the MS-DOS world. Note that if you have an internal modem on COM4 and a serial port at COM2 you will have to change the IRQ of the @@ -4058,15 +4069,14 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc lptintr</term> <listitem> - <para><emphasis remap=tt>lpt0</emphasis> through <emphasis - remap=tt>lpt2</emphasis> are the three printer ports you + <para><literal>lpt0</literal> through <literal>lpt2</literal> are the three printer ports you could conceivably have. Most people just have one, though, so feel free to comment out the other two lines if you do not have them.</para> </listitem> </varlistentry> </variablelist> - </para> + </sect2> @@ -4079,7 +4089,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc if you do not have an Ethernet card, pay attention to the mandatory options and the dial-up networking support.</para> - <para> + <variablelist> <varlistentry><term>options INET</term> <listitem> @@ -4099,7 +4109,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc out all of these lines. Otherwise, you will want to leave in support for your particular Ethernet card(s):</para> - <para> + <variablelist> <varlistentry><term>device de0</term> <listitem> @@ -4235,7 +4245,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> </varlistentry> </variablelist> - </para> + <note> <para>With certain cards (notably the NE2000) you will @@ -4265,14 +4275,14 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </varlistentry> <varlistentry><term>pseudo-device sl - <emphasis>number</emphasis></term> + <replaceable>number</replaceable></term> <listitem> <para><literal>sl</literal> is for SLIP (Serial Line Internet Protocol) support. This has been almost entirely supplanted by PPP, which is easier to set up, better suited for modem-to-modem connections, as well as - more powerful. The <emphasis>number</emphasis> after + more powerful. The <replaceable>number</replaceable> after <literal>sl</literal> specifies how many simultaneous SLIP sessions to support. This handbook has more information on setting up a SLIP <xref @@ -4283,25 +4293,24 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </varlistentry> <varlistentry><term>pseudo-device ppp - <emphasis>number</emphasis></term> + <replaceable>number</replaceable></term> <listitem> <para><literal>ppp</literal> is for kernel-mode PPP (Point-to-Point Protocol) support for dial-up Internet connections. There is also version of PPP implemented as a - user application that uses the <emphasis - remap=tt>tun</emphasis> and offers more flexibility and + user application that uses the <devicename>tun</devicename> and offers more flexibility and features such as demand dialing. If you still want to use this PPP driver, read the <xref linkend="ppp" remap="kernel-mode PPP"> section of the handbook. As with the <literal>sl</literal> device, - <emphasis>number</emphasis> specifies how many + <replaceable>number</replaceable> specifies how many simultaneous PPP connections to support.</para> </listitem> </varlistentry> <varlistentry><term>pseudo-device tun - <emphasis>number</emphasis></term> + <replaceable>number</replaceable></term> <listitem> <para><literal>tun</literal> is used by the @@ -4316,7 +4325,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </varlistentry> <varlistentry><term>pseudo-device bpfilter - <emphasis>number</emphasis></term> + <replaceable>number</replaceable></term> <listitem> <para>Berkeley packet filter. This pseudo-device allows @@ -4326,7 +4335,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc examined with the <citerefentry><refentrytitle>tcpdump</refentrytitle><manvolnum>1</manvolnum></citerefentry> program. Note that implementation of this capability can seriously compromise your overall network security. The - <emphasis>number</emphasis> after bpfilter is the number + <replaceable>number</replaceable> after bpfilter is the number of interfaces that can be examined simultaneously. Optional, not recommended except for those who are fully aware of the potential pitfalls. Not all network cards @@ -4334,7 +4343,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> </varlistentry> </variablelist> - </para> + </sect2> @@ -4346,7 +4355,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc copy the appropriate lines from the LINT kernel (which contains support for <emphasis>every</emphasis> device) as follows:</para> - <para> + <variablelist> <varlistentry><term>controller snd0</term> <listitem> @@ -4457,7 +4466,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> </varlistentry> </variablelist> - </para> + <note> <para>There is some additional documentation in @@ -4478,7 +4487,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc remap="network-related"> pseudo-devices are in that section, while the remainder are here.</para> - <para> + <variablelist> <varlistentry><term>pseudo-device gzip</term> <listitem> @@ -4498,7 +4507,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </varlistentry> <varlistentry><term>pseudo-device pty - <emphasis>number</emphasis><anchor + <replaceable>number</replaceable><anchor id="kernelconfig-ptys"></term> <listitem> @@ -4507,23 +4516,23 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc by incoming <command>telnet</command> and <command>rlogin</command> sessions, xterm, and some other applications such as emacs. The - <emphasis>number</emphasis> indicates the number of + <replaceable>number</replaceable> indicates the number of <literal>pty</literal>s to create. If you need - more than GENERIC default of 16 simultaneous xterm windows + more than <filename>GENERIC</filename> default of 16 simultaneous xterm windows and/or remote logins, be sure to increase this number accordingly, up to a maximum of 64.</para> </listitem> </varlistentry> <varlistentry><term>pseudo-device snp - <emphasis>number</emphasis></term> + <replaceable>number</replaceable></term> <listitem> <para>Snoop device. This pseudo-device allows one terminal session to watch another using the <citerefentry><refentrytitle>watch</refentrytitle><manvolnum>8</manvolnum></citerefentry> command. Note that implementation of this capability has important security - and privacy implications. The <emphasis>number</emphasis> + and privacy implications. The <replaceable>number</replaceable> after snp is the total number of simultaneous snoop sessions. Optional.</para> </listitem> @@ -4541,12 +4550,12 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </varlistentry> <varlistentry><term>pseudo-device ccd - <emphasis>number</emphasis></term> + <replaceable>number</replaceable></term> <listitem> <para>Concatenated disks. This pseudo-device allows you to concatenate multiple disk partitions into one large - <quote>meta</quote>-disk. The <emphasis>number</emphasis> after ccd + <quote>meta</quote>-disk. The <replaceable>number</replaceable> after ccd is the total number of concatenated disks (not total number of disks that can be concatenated) that can be created. (See <citerefentry><refentrytitle>ccd</refentrytitle><manvolnum>4</manvolnum></citerefentry> and @@ -4555,7 +4564,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> </varlistentry> </variablelist> - </para> + </sect2> @@ -4568,7 +4577,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc handbook or the LINT kernel (which contains support for <emphasis>every</emphasis> device):</para> - <para> + <variablelist> <varlistentry><term>device joy0 at isa? port "IO_GAME"</term> <listitem> @@ -4586,8 +4595,8 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <filename>/usr/games/piano</filename> which lets you play songs using the keyboard as a simple piano (this file only exists if you have installed the - <emphasis>games</emphasis> package). Also, the excellent - text role-playing game NetHack (in the ports collection) + <literal>games</literal> package). Also, the excellent + text role-playing game <application>NetHack</application> (in the ports collection) can be configured to use this device to play songs when you play musical instruments in the game.</para> @@ -4596,7 +4605,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc </listitem> </varlistentry> </variablelist> - </para> + </sect2> </sect1> @@ -4618,14 +4627,16 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <para>Suppose you add the IDE CD-ROM support to the kernel. The line to add is: + <programlisting> controller wcd0 </programlisting> This means that you should look for some entries that start with <filename>wcd0</filename> in the <filename>/dev</filename> directory, possibly followed by a letter, - such as <token>c</token>, or preceded by the letter <token>r</token>, which means a <quote>raw</quote> + such as <literal>c</literal>, or preceded by the letter <literal>r</literal>, which means a <quote>raw</quote> device. It turns out that those files are not there, so I must change to the <filename>/dev</filename> directory and type: + <informalexample> <screen>&prompt.root; <userinput>sh MAKEDEV wcd0</userinput></screen> </informalexample> When this script finishes, you will find that @@ -4633,6 +4644,7 @@ controller wcd0 you know that it executed correctly.</para> <para>For sound cards, the command: + <informalexample> <screen>&prompt.root; <userinput>sh MAKEDEV snd0</userinput></screen> </informalexample> creates the appropriate entries.</para> @@ -4645,7 +4657,7 @@ controller wcd0 fbtab</command> for more information.</para> </note> - <para>Follow this simple procedure for any other non-GENERIC devices + <para>Follow this simple procedure for any other non-<filename>GENERIC</filename> devices which do not have entries.</para> <note> @@ -4665,7 +4677,7 @@ controller wcd0 <para>There are four categories of trouble that can occur when building a custom kernel. They are:</para> - <para> + <variablelist> <varlistentry><term>Config command fails</term> <listitem> @@ -4676,6 +4688,7 @@ controller wcd0 number that it had trouble with, so you can quickly skip to it with <command>vi</command>. For example, if you see: + <informalexample> <screen>config: line 17: syntax error</screen> </informalexample> you can skip to the problem in <command>vi</command> by typing <COMMAND>17G</COMMAND> in command mode. @@ -4720,7 +4733,7 @@ controller wcd0 <note> <para>If you are having trouble building a kernel, make sure - to keep a GENERIC, or some other kernel that is known to + to keep a <filename>GENERIC</filename>, or some other kernel that is known to work on hand as a different name that will not get erased on the next build. You cannot rely on <filename>kernel.old</filename> because when installing a @@ -4732,17 +4745,19 @@ controller wcd0 properly. The proper command to <quote>unlock</quote> the kernel file that <command>make</command> installs (in order to move another kernel back permanently) is: - <informalexample> - <screen>&prompt.root; <userinput>chflags noschg /kernel</userinput></screen> - </informalexample> And, if you want to + + <informalexample> + <screen>&prompt.root; <userinput>chflags noschg /kernel</userinput></screen> + </informalexample> And, if you want to <quote>lock</quote> your new kernel into place, or any file for that matter, so that it cannot be moved or tampered with: - <informalexample> - <screen>&prompt.root; <userinput>chflags schg /kernel</userinput></screen> - </informalexample> - </para> - </note> + + <informalexample> + <screen>&prompt.root; <userinput>chflags schg /kernel</userinput></screen> + </informalexample> + </para> + </note> </listitem> </varlistentry> @@ -4754,8 +4769,7 @@ controller wcd0 for example, an experimental <quote>2.2.0</quote> kernel on a 2.1.0-RELEASE system, many system-status commands like <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> and <citerefentry><refentrytitle>vmstat</refentrytitle><manvolnum>8</manvolnum></citerefentry> - will not work any more. You must recompile the <emphasis - remap=tt>libkvm</emphasis> library as well as these + will not work any more. You must recompile the <filename>libkvm</filename> library as well as these utilities. This is one reason it is not normally a good idea to use a different version of the kernel from the rest of the operating system.</para> @@ -4763,7 +4777,7 @@ controller wcd0 </varlistentry> </variablelist> - </para> + </sect1> </chapter> @@ -4802,8 +4816,7 @@ controller wcd0 add-on library the DES-based password hash. The password-scrambling function was moved out of the C library to a separate library, called <filename>libcrypt</filename> because the name of - the C function to implement it is <emphasis - remap=tt>crypt</emphasis>. In FreeBSD 1.x and some pre-release + the C function to implement it is <function>crypt</function>. In FreeBSD 1.x and some pre-release 2.0 snapshots, the non-regulated scrambler uses an insecure function written by Nate Williams; in subsequent releases this was replaced by a mechanism using the RSA Data Security, Inc., MD5 one-way hash @@ -4812,13 +4825,10 @@ controller wcd0 many other countries.</para> <para>Meanwhile, work was also underway on the DES-based password hash - function. First, a version of the <emphasis - remap=tt>crypt</emphasis> function which was written outside the + function. First, a version of the <function>crypt</function> function which was written outside the US was imported, thus synchronizing the US and non-US code. Then, - the library was modified and split into two; the DES <emphasis - remap=tt>libcrypt</emphasis> contains only the code involved in - performing the one-way password hash, and a separate <emphasis - remap=tt>libcipher</emphasis> was created with the entry points + the library was modified and split into two; the DES <filename>libcrypt</filename> contains only the code involved in + performing the one-way password hash, and a separate <filename>libcipher</filename> was created with the entry points to actually perform encryption. The code was partitioned in this way to make it easier to get an export license for the compiled library.</para> @@ -4830,22 +4840,21 @@ controller wcd0 <para>It is fairly easy to recognize whether a particular password string was created using the DES- or MD5-based hash function. MD5 - password strings always begin with the characters <quote><token>$1$</token></quote>. DES password strings do not + password strings always begin with the characters <literal>$1$</literal>. DES password strings do not have any particular identifying characteristics, but they are shorter than MD5 passwords, and are coded in a 64-character - alphabet which does not include the <quote><token>$</token></quote> character, so a relatively short + alphabet which does not include the <literal>$</literal> character, so a relatively short string which doesn't begin with a dollar sign is very likely a DES password.</para> <para>Determining which library is being used on your system is fairly easy for most programs, except for those like <command>init</command> which are statically linked. (For those programs, the only way is to try them on a known password - and see if it works.) Programs which use <emphasis - remap=tt>crypt</emphasis> are linked against <filename>libcrypt</filename>, which for each type of library is + and see if it works.) Programs which use <function>crypt</function> are linked against <filename>libcrypt</filename>, which for each type of library is a symbolic link to the appropriate implementation. For example, on a system using the DES versions:</para> - <para> + <informalexample> <screen>&prompt.user;<userinput> cd /usr/lib</userinput> &prompt.user; <userinput>ls -l /usr/lib/libcrypt*</userinput> @@ -4853,7 +4862,7 @@ lrwxr-xr-x 1 bin bin 13 Sep 5 12:50 libcrypt.a -> libdescrypt.a lrwxr-xr-x 1 bin bin 18 Sep 5 12:50 libcrypt.so.2.0 -> libdescrypt.so.2.0 lrwxr-xr-x 1 bin bin 15 Sep 5 12:50 libcrypt_p.a -> libdescrypt_p.a</screen> </informalexample> - </para> + <para>On a system using the MD5-based libraries, the same links will be present, but the target will be <filename>libscrypt</filename> @@ -4947,7 +4956,7 @@ lrwxr-xr-x 1 bin bin 15 Sep 5 12:50 libcrypt_p.a -> libdescrypt_p.a</scre a machine), use the <command>keyinit</command> command without any parameters while logged in as yourself:</para> - <para> + <informalexample> <screen>&prompt.user; keyinit Updating wollman: ) these will not appear if you @@ -4960,10 +4969,10 @@ If you are using telnet or rlogin exit with no password and use keyinit -s. wollman s/key is 99 ha73896 ) discussed below SAG HAS FONT GOUT FATE BOOM )</screen> </informalexample> - </para> - <para>There is a lot of information here. At the`Enter secret - password:' prompt, you should enter some password or phrase (I use + + <para>There is a lot of information here. At the<prompt>Enter secret + password:</prompt> prompt, you should enter some password or phrase (I use phrases of minimum seven words) which will be needed to generate login keys. The line starting `ID' gives the parameters of your particular S/Key instance: your login name, the iteration count, @@ -4989,7 +4998,7 @@ HAS FONT GOUT FATE BOOM )</screen> insecure connection (to the machine you are initializing), use the <command>keyinit -s</command> command:</para> - <para> + <informalexample> <screen>&prompt.user; <userinput>keyinit -s</userinput> Updating wollman: Old key: kh94741 @@ -4998,34 +5007,34 @@ Reminder you need the 6 English words from the skey command. <prompt>Enter new key [default kh94742]:</prompt> s/key 100 kh94742</screen> </informalexample> - </para> - <para>To accept the default seed (which the `keyinit' program - confusingly calls a `key'), press return. Then move over to your + + <para>To accept the default seed (which the <command>keyinit</command> program + confusingly calls a <literal>key</literal>), press return. Then move over to your secure connection or S/Key desk accessory, and give it the same parameters:</para> - <para> + <informalexample> <screen>&prompt.user; <userinput>key 100 kh94742</userinput> Reminder - Do not use this program while logged in via telnet or rlogin. <prompt>Enter secret password:</prompt> ) I typed my secret password HULL NAY YANG TREE TOUT VETO</screen> </informalexample> - </para> + <para>Now switch back over to the insecure connection, and copy the one-time password generated by <command>key</command> over to the <command>keyinit</command> program:</para> - <para> + <informalexample> <screen><prompt>s/key access password:</prompt> <userinput>HULL NAY YANG TREE TOUT VETO</userinput> ID wollman s/key is 100 kh94742 HULL NAY YANG TREE TOUT VETO</screen> </informalexample> - </para> + <para>The rest of the description from the previous section applies here as well.</para> @@ -27995,7 +28004,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. # Date created: 5 December 1994 # Whom: asami # -# $Id: book.sgml,v 1.36 1998-10-21 21:53:36 nik Exp $ +# $Id: book.sgml,v 1.37 1998-10-21 21:58:40 nik Exp $ # DISTNAME= oneko-1.1b |