diff options
| author | Nik Clayton <nik@FreeBSD.org> | 1998-10-26 23:54:18 +0000 |
|---|---|---|
| committer | Nik Clayton <nik@FreeBSD.org> | 1998-10-26 23:54:18 +0000 |
| commit | de52a66a3c46f2f586f79f82ee51081fc5eea533 (patch) | |
| tree | 3607874fbd442f3bd475d3de843259a1e72f984e /en_US.ISO8859-1 | |
| parent | 0992677d94b6cbf2718241eb26c601ca256bf47b (diff) | |
Notes
Diffstat (limited to 'en_US.ISO8859-1')
| -rw-r--r-- | en_US.ISO8859-1/books/handbook/book.sgml | 690 |
1 files changed, 345 insertions, 345 deletions
diff --git a/en_US.ISO8859-1/books/handbook/book.sgml b/en_US.ISO8859-1/books/handbook/book.sgml index 7c962f339c..48c3bd02b1 100644 --- a/en_US.ISO8859-1/books/handbook/book.sgml +++ b/en_US.ISO8859-1/books/handbook/book.sgml @@ -131,7 +131,7 @@ <listitem> <para>Demand paged <emphasis>virtual memory</emphasis> - and <quote>merged VM/buffer cache</quote> design efficiently satisfies + and “merged VM/buffer cache” design efficiently satisfies applications with large appetites for memory while still maintaining interactive response to other users.</para> </listitem> @@ -277,7 +277,7 @@ one of the excellent commercial servers provided by X Inside. Unlike an X terminal, FreeBSD allows many applications to be run locally, if desired, thus relieving the burden on a - central server. FreeBSD can even boot <quote>diskless</quote>, making + central server. FreeBSD can even boot “diskless”, making individual workstations even cheaper and easier to administer.</para> </listitem> @@ -304,29 +304,29 @@ <para><emphasis>Contributed by &a.jkh;</emphasis>.</para> <para>The FreeBSD project had its genesis in the early part of 1993, - partially as an outgrowth of the <quote>Unofficial 386BSD Patchkit</quote> by the + partially as an outgrowth of the “Unofficial 386BSD Patchkit” by the patchkit's last 3 coordinators: Nate Williams, Rod Grimes and myself.</para> <para>Our original goal was to produce an intermediate snapshot of 386BSD in order to fix a number of problems with it that the patchkit mechanism just was not capable of solving. Some of you may - remember the early working title for the project being <QUOTE>386BSD 0.5</QUOTE> - or <quote>386BSD Interim</quote> in reference to that fact.</para> + remember the early working title for the project being &LDQUO;386BSD 0.5&RDQUO; + or “386BSD Interim” in reference to that fact.</para> <para>386BSD was Bill Jolitz's operating system, which had been up to that point suffering rather severely from almost a year's worth of neglect. As the patchkit swelled ever more uncomfortably with each passing day, we were in unanimous agreement that something had to be done and decided to try and assist Bill by providing this interim - <quote>cleanup</quote> snapshot. Those plans came to a rude halt when Bill + “cleanup” snapshot. Those plans came to a rude halt when Bill Jolitz suddenly decided to withdraw his sanction from the project and without any clear indication of what would be done instead.</para> <para>It did not take us long to decide that the goal remained worthwhile, even without Bill's support, and so we adopted the name - <quote>FreeBSD</quote>, coined by David Greenman. Our initial objectives were + “FreeBSD”, coined by David Greenman. Our initial objectives were set after consulting with the system's current users and, once it became clear that the project was on the road to perhaps even becoming a reality, I contacted Walnut Creek CDROM with an eye @@ -341,7 +341,7 @@ <para>The first CDROM (and general net-wide) distribution was FreeBSD 1.0, released in December of 1993. This was based on the - 4.3BSD-Lite (<quote>Net/2</quote>) tape from U.C. Berkeley, with many components + 4.3BSD-Lite (“Net/2”) tape from U.C. Berkeley, with many components also provided by 386BSD and the Free Software Foundation. It was a fairly reasonable success for a first offering, and we followed it with the highly successful FreeBSD 1.1 release in May of @@ -351,9 +351,9 @@ the horizon as Novell and U.C. Berkeley settled their long-running lawsuit over the legal status of the Berkeley Net/2 tape. A condition of that settlement was U.C. Berkeley's concession that - large parts of Net/2 were <quote>encumbered</quote> code and the property of + large parts of Net/2 were “encumbered” code and the property of Novell, who had in turn acquired it from AT&T some time - previously. What Berkeley got in return was Novell's <quote>blessing</quote> + previously. What Berkeley got in return was Novell's “blessing” that the 4.4BSD-Lite release, when it was finally released, would be declared unencumbered and all existing Net/2 users would be strongly encouraged to switch. This included FreeBSD, and the project was @@ -364,7 +364,7 @@ <para>FreeBSD then set about the arduous task of literally re-inventing itself from a completely new and rather incomplete set - of 4.4BSD-Lite bits. The <quote>Lite</quote> releases were light in part because + of 4.4BSD-Lite bits. The “Lite” releases were light in part because Berkeley's CSRG had removed large chunks of code required for actually constructing a bootable running system (due to various legal requirements) and the fact that the Intel port of 4.4 was @@ -384,7 +384,7 @@ this branch (RELENG_2_1_0).</para> <para>FreeBSD 2.2 was branched from the development mainline - (<quote>-current</quote>) in November 1996 as the RELENG_2_2 branch, and the + (“-current”) in November 1996 as the RELENG_2_2 branch, and the first full release (2.2.1) was released in April, 1997. Further releases along the 2.2 branch were done in the Summer and Fall of '97, the latest being 2.2.6 which appeared in late March of '98. @@ -406,7 +406,7 @@ us have a significant investment in the code (and project) and would certainly not mind a little financial compensation now and then, but we're definitely not prepared to insist on it. We believe that our - first and foremost <quote>mission</quote> is to provide code to any and all + first and foremost “mission” is to provide code to any and all comers, and for whatever purpose, so that the code gets the widest possible use and provides the widest possible benefit. This is, I believe, one of the most fundamental goals of Free Software and one @@ -465,7 +465,7 @@ <para>The <xref linkend="staff-committers" remap="committers"> are the people who have <emphasis>write</emphasis> access to the CVS tree, and are thus authorized to make modifications - to the FreeBSD source (the term <quote>committer</quote> comes from the + to the FreeBSD source (the term “committer” comes from the <citerefentry><refentrytitle>cvs</refentrytitle><manvolnum>1</manvolnum></citerefentry> <command>commit</command> command, which is used to bring new changes into the CVS repository). The best way of making submissions for review by the committers list is to @@ -497,9 +497,9 @@ <note> <para>Most members of the core team are volunteers when it comes to FreeBSD development and do not benefit from the - project financially, so <quote>commitment</quote> should also not be - misconstrued as meaning <quote>guaranteed support.</quote> The - <quote>board of directors</quote> analogy above is not + project financially, so “commitment” should also not be + misconstrued as meaning “guaranteed support.” The + “board of directors” 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! <!-- smiley --><emphasis>;)</emphasis></para> @@ -584,7 +584,7 @@ The list of ports ranges from http (WWW) servers, to games, languages, editors and almost everything in between. The entire ports collection requires approximately 26MB of storage, all ports - being expressed as <quote>deltas</quote> to their original sources. This + being expressed as “deltas” to their original sources. This makes it much easier for us to update ports, and greatly reduces the disk space demands made by the older 1.0 ports collection. To compile a port, you simply change to the directory of the program @@ -593,7 +593,7 @@ full original distribution for each port you build is retrieved dynamically off the CDROM or a local ftp site, so you need only enough disk space to build the ports you want. (Almost) every port - is also provided as a pre-compiled <quote>package</quote> which can be installed + is also provided as a pre-compiled “package” which can be installed with a simple command (pkg_add) by those who do not wish to compile their own ports from source.</para> @@ -959,7 +959,7 @@ Boot: <para>Buslogic 545S & 545c</para> <note> - <para>Buslogic was formerly known as <quote>Bustek</quote>.</para> + <para>Buslogic was formerly known as “Bustek”.</para> </note> </listitem> @@ -985,7 +985,7 @@ Boot: </listitem> <listitem> - <para>NCR5380/NCR53400 (<quote>ProAudio Spectrum</quote>) SCSI + <para>NCR5380/NCR53400 (“ProAudio Spectrum”) SCSI controller.</para> </listitem> @@ -1279,7 +1279,7 @@ Boot: </listitem> <listitem> - <para>Decision-Computer Intl. <quote>Eight-Serial</quote> 8 port serial + <para>Decision-Computer Intl. “Eight-Serial” 8 port serial cards using shared IRQ.</para> </listitem> @@ -1393,7 +1393,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <para>Anyone with network connectivity to your machine (and permission to log into it) can now chose a Media type of FTP and type in: <userinput>ftp://<replaceable>your - machine</replaceable></userinput> after picking <quote>Other</quote> in + machine</replaceable></userinput> after picking “Other” in the ftp sites menu.</para> </sect2> @@ -1454,7 +1454,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <filename>a:\bin\bin.ab</filename>, and so on.</para> <para>Once you come to the Media screen of the install, select - <quote>Floppy</quote> and you will be prompted for the rest.</para> + “Floppy” and you will be prompted for the rest.</para> </sect2> @@ -1557,7 +1557,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent only choice. Make sure that you have your service provider's information handy as you will need to know it fairly soon in the installation process. You will need to know how to dial your ISP - using the <quote>AT commands</quote> specific to your modem, as the PPP + using the “AT commands” specific to your modem, as the PPP dialer provides only a very simple terminal emulator. If you're using PAP or CHAP, you'll need to type the necessary <command>set authname</command> and <command>set authkey</command> commands before typing <command>term</command>. @@ -1569,7 +1569,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <para>If a hard-wired connection to another FreeBSD (2.0R or later) machine is available, you might also consider installing over a - <quote>laplink</quote> parallel port cable. The data rate over the parallel + “laplink” parallel port cable. The data rate over the parallel port is much higher than what is typically possible over a serial line (up to 50k/sec), thus resulting in a quicker installation.</para> @@ -1608,7 +1608,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent FreeBSD distribution files you want onto a server somewhere and then point the NFS media selection at it.</para> - <para>If this server supports only <quote>privileged port</quote> access (as + <para>If this server supports only “privileged port” access (as is generally the default for Sun workstations), you will need to set this option in the Options menu before installation can proceed.</para> @@ -1645,7 +1645,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <para>If you are installing from some other FTP site not listed in this menu, or you are having troubles getting your name server configured properly, you can also specify your own URL by - selecting the <quote>Other</quote> choice in that menu. A URL can also be + selecting the “Other” choice in that menu. A URL can also be a direct IP address, so the following would work in the absence of a name server:</para> @@ -1661,7 +1661,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <variablelist> <varlistentry><term>FTP Active</term> <listitem> - <para>For all FTP transfers, use <quote>Active</quote> mode. This + <para>For all FTP transfers, use “Active” mode. This will not work through firewalls, but will often work with older ftp servers that do not support passive mode. If your connection hangs with passive mode (the @@ -1672,7 +1672,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <varlistentry><term>FTP Passive</term> <listitem> - <para>For all FTP transfers, use <quote>Passive</quote> mode. This + <para>For all FTP transfers, use “Passive” mode. This allows the user to pass through firewalls that do not allow incoming connections on random port addresses.</para> @@ -1682,7 +1682,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent <note> - <para>Active and passive modes are not the same as a <quote>proxy</quote> + <para>Active and passive modes are not the same as a “proxy” connection, where a proxy FTP server is listening and forwarding FTP requests!</para> </note> @@ -1729,12 +1729,12 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent if it does not then we would like to know what you found most confusing. Send your comments to the &a.doc;. It is the objective of the FreeBSD installation program (sysinstall) to be - self-documenting enough that painful <quote>step-by-step</quote> guides are no + self-documenting enough that painful “step-by-step” guides are no longer necessary. It may take us a little while to reach that objective, but that is the objective!</para> - <para>Meanwhile, you may also find the following <quote>typical - installation sequence</quote> to be helpful:</para> + <para>Meanwhile, you may also find the following “typical + installation sequence” to be helpful:</para> <orderedlist> @@ -1830,7 +1830,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent 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 <devicename>D:</devicename> drive might be <filename>/dev/sd0s5</filename>, + other “slices” 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 @@ -1946,7 +1946,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent </informalexample> <para>With this command you will be presented with a - list of commands that have the keyword <quote>mail</quote> in their descriptions. + list of commands that have the keyword “mail” in their descriptions. This is actually functionally equivalent to using the <command>apropos</command> command.</para> @@ -1972,7 +1972,7 @@ 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 - <quote>info</quote> files which can be viewed with the + “info” 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> @@ -2001,7 +2001,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent tricky business, as anyone who has tried it will know. You may be lucky enough to find that the program you want will compile cleanly on your system, install itself in all the right places and run flawlessly - <quote>out of the box</quote>, but this is unfortunately rather rare. With most + “out of the box”, but this is unfortunately rather rare. With most programs, you will find yourself doing a fair bit of head-scratching, and there are quite a few programs that will result in premature greying, or even chronic alopecia...</para> @@ -2042,8 +2042,8 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent </listitem> <listitem> - <para>Programs which fall into the <quote>I must have a look at that - when I get a spare minute</quote> category, rather than + <para>Programs which fall into the “I must have a look at that + when I get a spare minute” category, rather than system-critical ones (some languages, perhaps).</para> </listitem> @@ -2068,8 +2068,8 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent ingenious way of using standard tools that would automate the process.</para> - <para>Incidentally, this is an excellent illustration of how <quote>the - Unix way</quote> works in practice by combining a set of simple but very + <para>Incidentally, this is an excellent illustration of how “the + Unix way” works in practice by combining a set of simple but very flexible tools into something very powerful.</para> </sect1> @@ -2103,8 +2103,8 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/devel/ElectricFence">the FTP site</ulink>) and expect to find all sorts of pointy-headed rocket science lurking there, you may be disappointed by the one or two rather unexciting-looking files and directories you find there. (We will discuss in a minute how to go about <xref linkend="ports-getting" remap="Getting a port">).</para> - <para><quote>How on earth can this do anything?</quote> I hear you cry. <quote>There - is no source code there!</quote></para> + <para>“How on earth can this do anything?” I hear you cry. “There + is no source code there!”</para> <para>Fear not, gentle reader, all will become clear (hopefully). Let's see what happens if we try and install a port. I have chosen @@ -2228,8 +2228,8 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc <sect2 id="ports-cd"> <title>Compiling ports from CDROM</title> - <para>If you answered yes to the question <quote>Do you want to link the - ports collection to your CDROM</quote> during the FreeBSD installation, + <para>If you answered yes to the question “Do you want to link the + ports collection to your CDROM” during the FreeBSD installation, the initial setting up will already have been done for you.</para> <para>If not, make sure the <emphasis>FreeBSD</emphasis> CDROM is in @@ -2269,8 +2269,8 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc </informalexample> <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> + not a mistake. It is Unix-ese for “the current + directory”)</para> <para>and the ports make mechanism will automatically compile and install all the ports in the databases directory for you!</para> @@ -2278,7 +2278,7 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc <para>If you do not like this method, here is a completely different way of doing it:-</para> - <para>Create a <quote>link tree</quote> to it using the + <para>Create a “link tree” to it using the <citerefentry><refentrytitle>lndir</refentrytitle><manvolnum>1</manvolnum></citerefentry> command that comes with the <emphasis>XFree86</emphasis> distribution. Find a location with some free space, create a directory there and then cd to it. Then @@ -2547,7 +2547,7 @@ do-install: <listitem> <para>Grab the pre-compiled package from a ftp server. The - <quote>master</quote> package collection is on FreeBSD's FTP server in + “master” package collection is on FreeBSD's FTP server in the <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/packages/">packages directory</ulink>, though check your local mirror first, @@ -2582,8 +2582,8 @@ do-install: modems??!</para> <para>A. Ah. You must be thinking of the serial ports on the - back of your computer. We are using <quote>port</quote> here to mean the - result of <quote>porting</quote> a program from one version of Unix to + back of your computer. We are using “port” here to mean the + result of “porting” a program from one version of Unix to another. (It is an unfortunate bad habit of computer people to use the same word to refer to several completely different things).</para> @@ -2651,9 +2651,9 @@ do-install: <para>A. A patch is a small (usually) file that specifies how to go from one version of a file to another. It contains text - that says, in effect, things like <quote>delete line 23</quote>, <quote>add - these two lines after line 468</quote> or <quote>change line 197 to - this</quote>. Also known as a <quote>diff</quote>, since it is generated by a + that says, in effect, things like “delete line 23”, “add + these two lines after line 468” or “change line 197 to + this”. Also known as a “diff”, since it is generated by a program of that name.</para> </listitem> @@ -2970,8 +2970,8 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc and a half ports. Did something go wrong?</para> <para>A. No, the problem is that some of the ports need to ask - you questions that we cannot answer for you (eg <quote>Do you want - to print on A4 or US letter sized paper?</quote>) and they need to + you questions that we cannot answer for you (eg “Do you want + to print on A4 or US letter sized paper?”) and they need to have someone on hand to answer them.</para> </listitem> @@ -3900,7 +3900,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc regardless of how many of them are hooked up to the SCSI bus(es), and which target IDs they have.</para> - <para>If you want to <quote>wire down</quote> specific target IDs to + <para>If you want to “wire down” specific target IDs to particular devices, refer to the appropriate section of the <filename>LINT</filename> kernel config file.</para> </listitem> @@ -3929,7 +3929,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc 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 <envar>TERM</envar> variable to - <quote>scoansi</quote> if full-screen programs have trouble running + “scoansi” if full-screen programs have trouble running under this console.</para> </listitem> </varlistentry> @@ -4222,7 +4222,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <note> <para>With certain cards (notably the NE2000) you will have to change the port and/or IRQ since there is no - <quote>standard</quote> location for these cards.</para> + “standard” location for these cards.</para> </note> </listitem> </varlistentry> @@ -4483,7 +4483,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <listitem> <para><literal>pty</literal> is a - <quote>pseudo-terminal</quote> or simulated login port. It is used + “pseudo-terminal” or simulated login port. It is used by incoming <command>telnet</command> and <command>rlogin</command> sessions, xterm, and some other applications such as emacs. The @@ -4526,7 +4526,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <listitem> <para>Concatenated disks. This pseudo-device allows you to concatenate multiple disk partitions into one large - <quote>meta</quote>-disk. The <replaceable>number</replaceable> after ccd + “meta”-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 @@ -4584,7 +4584,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc <sect1 id="kernelconfig-nodes"> <title>Making Device Nodes</title> - <para>Almost every device in the kernel has a corresponding <quote>node</quote> + <para>Almost every device in the kernel has a corresponding “node” entry in the <filename>/dev</filename> directory. These nodes look like regular files, but are actually special entries into the kernel which programs use to access the device. The shell script @@ -4603,7 +4603,7 @@ 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 <literal>c</literal>, or preceded by the letter <literal>r</literal>, which means a <quote>raw</quote> + such as <literal>c</literal>, or preceded by the letter <literal>r</literal>, which means a “raw” device. It turns out that those files are not there, so I must change to the <filename>/dev</filename> directory and type: @@ -4710,14 +4710,14 @@ controller wcd0 non-functional. Also, as soon as possible, move the working kernel to the proper <filename>kernel</filename> location or commands such as <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> will not work - properly. The proper command to <quote>unlock</quote> the + properly. The proper command to “unlock” 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 - <quote>lock</quote> your new kernel into place, or any + “lock” your new kernel into place, or any file for that matter, so that it cannot be moved or tampered with: @@ -4734,7 +4734,7 @@ controller wcd0 <listitem> <para>If you have installed a different version of the kernel from the one that the system utilities have been built with, - for example, an experimental <quote>2.2.0</quote> kernel on a + for example, an experimental “2.2.0” 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 <filename>libkvm</filename> library as well as these @@ -4764,7 +4764,7 @@ controller wcd0 from being easily exposed, passwords have traditionally been scrambled in some way. Starting with Bell Labs' Seventh Edition Unix, passwords were encrypted using what the security people call a - <quote>one-way hash function</quote>. That is to say, the password is + “one-way hash function”. That is to say, the password is transformed in such a way that the original password cannot be regained except by brute-force searching the space of possible passwords. Unfortunately, the only secure method that was available @@ -4854,14 +4854,14 @@ lrwxr-xr-x 1 bin bin 15 Sep 5 12:50 libcrypt_p.a -> libdescrypt_p.a</scre <para>There are three different sorts of passwords which we will talk about in the discussion below. The first is your usual UNIX-style - or Kerberos password; we will call this a <quote>UNIX password</quote>. The + or Kerberos password; we will call this a “UNIX password”. The second sort is the one-time password which is generated by the S/Key <command>key</command> program and accepted by the <command>keyinit</command> program and the login - prompt; we will call this a <quote>one-time password</quote>. The final sort + prompt; we will call this a “one-time password”. The final sort of password is the secret password which you give to the <command>key</command> program (and sometimes the <command>keyinit</command> program) which it uses to generate - one-time passwords; we will call it a <quote>secret password</quote> or just - unqualified <quote>password</quote>.</para> + one-time passwords; we will call it a “secret password” or just + unqualified “password”.</para> <para>The secret password does not necessarily have anything to do with your UNIX password (while they can be the same, this is not @@ -4871,9 +4871,9 @@ lrwxr-xr-x 1 bin bin 15 Sep 5 12:50 libcrypt_p.a -> libdescrypt_p.a</scre completely independently of the UNIX password system.</para> <para>There are in addition two other sorts of data involved in the - S/Key system; one is called the <quote>seed</quote> or (confusingly) <quote>key</quote>, + S/Key system; one is called the “seed” or (confusingly) “key”, and consists of two letters and five digits, and the other is the - <quote>iteration count</quote> and is a number between 100 and 1. S/Key + “iteration count” and is a number between 100 and 1. S/Key constructs a one-time password from these components by concatenating the seed and the secret password, then applying a one-way hash (the RSA Data Security, Inc., MD4 secure hash function) @@ -5248,7 +5248,7 @@ ARC.NASA.GOV trident.arc.nasa.gov</screen> <para>The first line names the realm in which this system works. The other lines contain realm/host entries. The first item on a line is a realm, and the second is a host in that realm that is acting - as a <quote>key distribution centre</quote>. The words <literal>admin server</literal> + as a “key distribution centre”. The words <literal>admin server</literal> following a hosts name means that host also provides an administrative database server. For further explanation of these terms, please consult the Kerberos man pages.</para> @@ -5686,7 +5686,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen> <note> <para>People often think that having a firewall between your - companies internal network and the <quote>Big Bad Internet</quote> + companies internal network and the “Big Bad Internet” will solve all your security problems.</para> <para>It may help, but a poorly setup firewall system is more of a @@ -5747,7 +5747,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen> packet, to forward the packet, or even to send an ICMP message back to the originator. Only the first match counts, as the rules are searched in order. Hence, the list of rules can be - referred to as a <quote>rule chain</quote>.</para> + referred to as a “rule chain”.</para> <para>The packet matching criteria varies depending on the software used, but typically you can specify rules which depend @@ -5774,7 +5774,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen> <para>Proxy servers are normally more secure than normal servers, and often have a wider variety of authentication mechanisms - available, including <quote>one-shot</quote> password systems so that even + available, including “one-shot” password systems so that even if someone manages to discover what password you used, they will not be able to use it to gain access to your systems as the password instantly expires. As they do not actually give users @@ -6096,7 +6096,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen> matched. <option><replaceable>mask-pattern</replaceable></option> is an IP address which will be logically AND'ed with the address given. The keyword <literal>any</literal> may be used to - specify <quote>any IP address</quote>.</para> + specify “any IP address”.</para> <para>The port numbers to be blocked are specified as: @@ -6622,7 +6622,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen> <xref linkend="printing-advanced-network-net-if" remap="Printers With Networked Data Stream Interaces">.</para> - <para>Although this section is called <quote>Simple Printer Setup,</quote> it is + <para>Although this section is called “Simple Printer Setup,” it is actually fairly complex. Getting the printer to work with your computer and the LPD spooler is the hardest part. The advanced options like header pages and accounting are fairly easy once you @@ -6671,7 +6671,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen> configuration exceedingly simple.</para> <para>Parallel interfaces are sometimes known as - <quote>Centronics</quote> interfaces, named after the connector type + “Centronics” interfaces, named after the connector type on the printer.</para> </listitem> @@ -6751,7 +6751,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen> instructions that came with the printer, the computer, or both should give you complete guidance.</para> - <para>If you are unsure what the <quote>proper serial cable</quote> is, you + <para>If you are unsure what the “proper serial cable” is, you may wish to try one of the following alternatives: <itemizedlist> @@ -6759,7 +6759,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen> <para>A <emphasis>modem</emphasis> cable connects each pin of the connector on one end of the cable straight through to its corresponding pin of the connector on the other - end. This type of cable is also known as a <quote>DTE-to-DCE</quote> + end. This type of cable is also known as a “DTE-to-DCE” cable.</para> </listitem> @@ -6768,7 +6768,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen> pins straight through, swaps others (send data to receive data, for example), and shorts some internally in each connector hood. This type of cable is also known as a - <quote>DTE-to-DTE</quote> cable.</para> + “DTE-to-DTE” cable.</para> </listitem> <listitem> @@ -6788,7 +6788,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen> the printer can support. Choose 7 or 8 data bits; none, even, or odd parity; and 1 or 2 stop bits. Also choose a flow control protocol: either none, or XON/XOFF (also known as - <quote>in-band</quote> or <quote>software</quote>) + “in-band” or “software”) flow control. Remember these settings for the software configuration that follows.</para> @@ -7837,8 +7837,8 @@ exit 2 </listitem> </varlistentry> - <varlistentry><term>It produced the <quote>staircase - effect.</quote></term> + <varlistentry><term>It produced the “staircase + effect.”</term> <listitem> <para>You got the following on paper: @@ -7968,7 +7968,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ lines of text were printed on top of each other on one line.</para> - <para>This problem is the <quote>opposite</quote> of the staircase + <para>This problem is the “opposite” of the staircase effect, described above, and is much rarer. Somewhere, the LF characters that FreeBSD uses to end a line are being treated as CR characters to return the print @@ -8203,7 +8203,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\ <para>When you print with <citerefentry> <refentrytitle>lpr</refentrytitle></citerefentry>, the data you wish to print is put together in a package called a - <quote>print job</quote>, which is sent to the LPD spooling + “print job”, which is sent to the LPD spooling system. Each printer has a queue of jobs, and your job waits in that queue along with other jobs from yourself and from other users. The printer prints those jobs in a first-come, first-served @@ -8228,7 +8228,7 @@ active kelly 9 /etc/host.conf, /etc/hosts.equiv 88 bytes 3rd mary 11 ... 78519 bytes</screen> </informalexample> This shows three jobs in the queue for <literal>bamboo</literal>. The first job, submitted by - user kelly, got assigned <quote>job number</quote> 9. Every + user kelly, got assigned “job number” 9. Every job for a printer gets a unique job number. Most of the time you can ignore the job number, but you will need it if you want to cancel the job; see section @@ -8240,7 +8240,7 @@ active kelly 9 /etc/host.conf, /etc/hosts.equiv 88 bytes <refentrytitle>lpr</refentrytitle></citerefentry> command line are treated as part of a single job. It is the currently active job (note the word <literal>active</literal> - under the <quote>Rank</quote> column), which means the printer should be + under the “Rank” column), which means the printer should be currently printing that job. The second job consists of data passed as the standard input to the</para> @@ -8932,8 +8932,8 @@ cfA013rose dequeued <para>Section <xref linkend="printing-advanced-filters" remap="How Filters Work">, tries to give an overview of a filter's role in the printing process. You should read this - section to get an understanding of what is happening <quote>under - the hood</quote> when LPD uses filters. This knowledge could help + section to get an understanding of what is happening “under + the hood” when LPD uses filters. This knowledge could help you anticipate and debug problems you might encounter as you install more and more filters on each of your printers.</para> </listitem> @@ -9524,8 +9524,8 @@ exit 2 Interleaf desktop publishing program), but will never print plot files. You could install a Printerleaf conversion filter under the <literal>gf</literal> capability and then - educate your users that <command>lpr -g</command> mean <quote>print - Printerleaf files.</quote></para> + educate your users that <command>lpr -g</command> mean “print + Printerleaf files.”</para> </sect4> @@ -9982,8 +9982,8 @@ exit 0 <para>In the <xref linkend="printing-simple" remap="Simple Printer Setup">, we turned off header pages by - specifying <literal>sh</literal> (meaning <quote>suppress - header</quote>) in the <filename>/etc/printcap</filename> file. To + specifying <literal>sh</literal> (meaning “suppress + header”) in the <filename>/etc/printcap</filename> file. To enable header pages for a printer, just remove the <literal>sh</literal> capability.</para> <para>Sounds too easy, right?</para> @@ -10134,7 +10134,7 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995 accounting, and it is not provided with any <emphasis>user or host</emphasis> information or an accounting file, so it has no idea whom to charge for printer use. It is also not enough - to just <quote>add one page</quote> to the text filter or any of the + to just “add one page” to the text filter or any of the conversion filters (which do have user and host information) since users can suppress header pages with <command>lpr -h</command>. They could still be charged for header pages @@ -10344,7 +10344,7 @@ done remap="How Filters Work">).</para> <para>As we have mentioned before, the above scheme, though fairly - simple, disables the <quote>suppress header page</quote> option (the + simple, disables the “suppress header page” option (the <option>-h</option> option) to <command>lpr</command>. If users wanted to save a tree (or a few pennies, if you charge for header pages), they would not be able to do so, since every filter's going to print a header page @@ -10408,7 +10408,7 @@ done <listitem> <para>It might support a data stream network connection. - In this case, you <quote>attach</quote> the printer to one host + In this case, you “attach” the printer to one host on the network by making that host responsible for spooling jobs and sending them to the printer. Section <xref @@ -10964,7 +10964,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ your systems, they can use your printers from their own departmental systems. If you would rather allow them to use <emphasis>only</emphasis> your printers and not your - compute resources, you can give them <quote>token</quote> accounts, + compute resources, you can give them “token” accounts, with no home directory and a useless shell like <filename>/usr/bin/false</filename>.</para> @@ -11024,7 +11024,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ printers. Like disk quotas, the accounting is immediate. You can prevent users from printing when their account goes in the red, and might provide a way for users to check and - adjust their <quote>print quotas.</quote> But this method requires some + adjust their “print quotas.” But this method requires some database code to track users and their quotas.</para> </listitem> @@ -11291,8 +11291,8 @@ total 337.00 154 $ 6.74</screen> you have learned just about everything there is to know about the LPD spooling system that comes with FreeBSD. You can probably appreciate many of its shortcomings, which naturally leads to the - question: <quote>What other spooling systems are out there (and work with - FreeBSD)?</quote></para> + question: “What other spooling systems are out there (and work with + FreeBSD)?”</para> <para>Unfortunately, I have located only <emphasis>two</emphasis> alternatives—and they are almost identical to each other! They @@ -11343,8 +11343,8 @@ total 337.00 154 $ 6.74</screen> <varlistentry><term>LPRng</term> <listitem> - <para>LPRng, which purportedly means <quote>LPR: the Next - Generation</quote> is a complete rewrite of PLP. Patrick Powell + <para>LPRng, which purportedly means “LPR: the Next + Generation” is a complete rewrite of PLP. Patrick Powell and Justin Mason (the principal maintainer of PLP) collaborated to make LPRng. The main site for LPRng is <ulink @@ -11716,7 +11716,7 @@ Disk quotas for user test (uid 1002): <para>I have had fairly good luck building workstation and server configurations with the following components. I can't guarantee that you will too, nor that any of the companies here will remain - <quote>best buys</quote> forever. I will try, when I can, to keep this list + “best buys” forever. I will try, when I can, to keep this list up-to-date but cannot obviously guarantee that it will be at any given time.</para> @@ -11786,8 +11786,8 @@ Disk quotas for user test (uid 1002): <title>Disk drives</title> <para>In this particular game of Russian roulette, I'll make few - specific recommendations except to say <quote>SCSI over IDE whenever - you can afford it.</quote> Even in small desktop configurations, SCSI + specific recommendations except to say “SCSI over IDE whenever + you can afford it.” Even in small desktop configurations, SCSI often makes more sense since it allows you to easily migrate drives from server to desktop as falling drive prices make it economical to do so. If you have more than one machine to @@ -12034,7 +12034,7 @@ Disk quotas for user test (uid 1002): replace the PCI bus arbiter (appears on Intel Altair board and several other Intel server group MB's). And of course Intel's official answer, move to the Triton - chip set, we <quote>fixed it there</quote>.</para> + chip set, we “fixed it there”.</para> </listitem> </varlistentry> @@ -12134,8 +12134,8 @@ Disk quotas for user test (uid 1002): <para>Pentium class machines use different clock speeds for the various parts of the system. These being the speed of the CPU, external memory bus, and the PCI bus. It is not always - true that a <quote>faster</quote> processor will make a system faster than - a <quote>slower</quote> one, due to the various clock speeds used. Below is + true that a “faster” processor will make a system faster than + a “slower” one, due to the various clock speeds used. Below is a table showing the differences:</para> <informaltable frame="none"> @@ -12271,7 +12271,7 @@ Disk quotas for user test (uid 1002): <para>In 1997, there have been reports of the AMD K6 seg faulting during heavy compilation. That problem has been fixed in 3Q '97. According to reports, K6 chips with date mark - <quote>9733</quote> or larger (i.e., manufactured in the 33rd week of '97 + “9733” or larger (i.e., manufactured in the 33rd week of '97 or later) do not have this bug.</para> </sect4> @@ -12380,7 +12380,7 @@ Disk quotas for user test (uid 1002): <para>Synchronous serial transmission requires that the sender and receiver share a clock with one another, or that the sender provide a strobe or other timing signal so that the - receiver knows when to <quote>read</quote> the next bit of the data. In + receiver knows when to “read” the next bit of the data. In most forms of serial Synchronous communication, if there is no data available at a given instant to transmit, a fill character must be sent instead so that data is always being @@ -12431,7 +12431,7 @@ Disk quotas for user test (uid 1002): data are sent, with the Least Significant Bit (LSB) being sent first. Each bit in the transmission is transmitted for exactly the same amount of time as all of the other bits, and - the receiver <quote>looks</quote> at the wire at approximately halfway + the receiver “looks” at the wire at approximately halfway through the period assigned to each bit to determine if the bit is a <literal>1</literal> or a <literal>0</literal>. For example, if it takes two seconds to send each bit, the receiver will examine the signal to @@ -12439,7 +12439,7 @@ Disk quotas for user test (uid 1002): then it will wait two seconds and then examine the value of the next bit, and so on.</para> - <para>The sender does not know when the receiver has <quote>looked</quote> at + <para>The sender does not know when the receiver has “looked” at the value of the bit. The sender only knows when the clock says to begin transmitting the next bit of the word.</para> @@ -12469,7 +12469,7 @@ Disk quotas for user test (uid 1002): for the new word can be sent as soon as the Stop Bit for the previous word has been sent.</para> - <para>Because asynchronous data is <quote>self synchronizing</quote>, if + <para>Because asynchronous data is “self synchronizing”, if there is no data to transmit, the transmission line can be idle.</para> @@ -12509,7 +12509,7 @@ Disk quotas for user test (uid 1002): <para>In RS232-C, a value of <literal>1</literal> is called a <literal>Mark</literal> and a value of <literal>0</literal> is called a <literal>Space</literal>. When a communication line - is idle, the line is said to be <quote>Marking</quote>, or transmitting + is idle, the line is said to be “Marking”, or transmitting continuous <literal>1</literal> values.</para> <para>The Start bit always has a value of <literal>0</literal> (a Space). The @@ -12572,8 +12572,8 @@ Disk quotas for user test (uid 1002): Attention or Interrupt signal and sometimes is accepted as a substitute for the ASCII CONTROL-C character.</para> - <para>Marks and Spaces are also equivalent to <quote>Holes</quote> and <quote>No - Holes</quote> in paper tape systems.</para> + <para>Marks and Spaces are also equivalent to “Holes” and “No + Holes” in paper tape systems.</para> <note> <para>Breaks cannot be generated from paper tape or from any @@ -13075,7 +13075,7 @@ INS8250 -> INS8250B <para>An improved version of the INS8250 using XMOS technology with various functional flaws corrected. The INS8250A was used initially in PC clone - computers by vendors who used <quote>clean</quote> BIOS designs. + computers by vendors who used “clean” BIOS designs. Because of the corrections in the chip, this part could not be used with a BIOS compatible with the INS8250 or INS8250B.</para> @@ -13226,7 +13226,7 @@ INS8250 -> INS8250B <para>The <replaceable>g</replaceable> is the product grade field. If an <literal>I</literal> precedes the package-type letter, it indicates an - <quote>industrial</quote> grade part, which has higher specs than a + “industrial” grade part, which has higher specs than a standard part but not as high as Military Specification (Milspec) component. This is an optional field.</para> @@ -13241,7 +13241,7 @@ INS8250 -> INS8250B <para>Over the years, the 8250, 8250A, 16450 and 16550 have been licensed or copied by other chip vendors. In the case of the - 8250, 8250A and 16450, the exact circuit (the <quote>megacell</quote>) was + 8250, 8250A and 16450, the exact circuit (the “megacell”) was licensed to many vendors, including Western Digital and Intel. Other vendors reverse-engineered the part or produced emulations that had similar behavior.</para> @@ -13263,7 +13263,7 @@ INS8250 -> INS8250B market comparisons even though the effective performance may be lowered by this action.</para> - <para>A common misconception is that all parts with <quote>16550A</quote> + <para>A common misconception is that all parts with “16550A” written on them are identical in performance. There are differences, and in some cases, outright flaws in most of these 16550A clones.</para> @@ -14253,7 +14253,7 @@ INS8250 -> INS8250B </variablelist> - <para>In addition to these <quote>dumb</quote> UARTs, many vendors produce + <para>In addition to these “dumb” UARTs, many vendors produce intelligent serial communication boards. This type of design usually provides a microprocessor that interfaces with several UARTs, processes and buffers the data, and then alerts the @@ -15368,7 +15368,7 @@ disk wd3 at wdc1 drive 1 or whatever. Do yourself a favor and stick to this rule. It will save you endless grief, because wrong termination has the potential to introduce highly mysterious bugs. (Note the - <quote>potential</quote> here; the nastiest part is that it may or may not + “potential” here; the nastiest part is that it may or may not work.)</para> <para>A common pitfall is to have an internal (flat) cable in a @@ -15504,7 +15504,7 @@ disk wd3 at wdc1 drive 1 internal narrow connector). Don't do that. It may appear to work if you are really lucky, but I can almost guarantee that your system will stop functioning at the most unfortunate - moment (this is also known as <quote>Murphy's law</quote>).</para> + moment (this is also known as “Murphy's law”).</para> <para>You might notice that the terminator issue discussed earlier becomes rather hairy if your bus is not linear. Also, @@ -15595,7 +15595,7 @@ disk wd3 at wdc1 drive 1 others partitions. Using fdisk you should be able to see all partitions.</para> - <para>You might have heard some talk of <quote>lying</quote> devices? Older + <para>You might have heard some talk of “lying” devices? Older FreeBSD kernels used to report the geometry of SCSI disks when booting. An example from one of my systems:</para> @@ -15735,9 +15735,9 @@ device cd0 at scbus? [the first ever CD-ROM found, no wiring] <emphasis>only</emphasis> attach them when they match the target ID and LUN specified on the corresponding bus.</para> - <para>Wired down devices get <quote>first shot</quote> at the unit numbers so - the first non <quote>wired down</quote> device, is allocated the unit - number one greater than the highest <quote>wired down</quote> unit number + <para>Wired down devices get “first shot” at the unit numbers so + the first non “wired down” device, is allocated the unit + number one greater than the highest “wired down” unit number for that kind of device. So, if you had a SCSI tape at target ID 2 it would be configured as st2, as the tape at target ID 6 is wired down to unit number 1.</para> @@ -15754,7 +15754,7 @@ device cd0 at scbus? [the first ever CD-ROM found, no wiring] <para>Below is another example of a kernel config file as used by FreeBSD version < 2.0.5. The difference with the first - example is that devices are not <quote>wired down</quote>. <quote>Wired down</quote> + example is that devices are not “wired down”. “Wired down” means that you specify which SCSI target belongs to which device.</para> @@ -15795,7 +15795,7 @@ device cd0 #Only need one of these, the code dynamically grows devices of a specific type (e.g. sd disks) are found than are configured in the booting kernel, the system will simply allocate more devices, incrementing the unit number starting - at the last number <quote>wired down</quote>. If there are no <quote>wired down</quote> + at the last number “wired down”. If there are no “wired down” devices then counting starts at unit 0.</para> <para>Use <command>man 4 scsi</command> to check for @@ -15841,7 +15841,7 @@ options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device correctly is no easy task. Some vendors do a better job then others.</para> - <para>This is exactly where the <quote>rogue</quote> devices come into view. + <para>This is exactly where the “rogue” devices come into view. Rogues are devices that are recognized by the FreeBSD kernel as behaving slightly (...) non-standard. Rogue devices are reported by the kernel when booting. An example for two of my @@ -15939,13 +15939,13 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen> TCQ function is indispensable to take advantage of the device's inherent parallelism.</para> - <para>Each I/O request is uniquely identified by a <quote>tag</quote> (hence + <para>Each I/O request is uniquely identified by a “tag” (hence the name tagged command queuing) and this tag is used by FreeBSD to see which I/O in the device drivers queue is reported as complete by the device.</para> <para>It should be noted however that TCQ requires device driver - support and that some devices implemented it <quote>not quite right</quote> + support and that some devices implemented it “not quite right” in their firmware. This problem bit me once, and it leads to highly mysterious problems. In such cases, try to disable TCQ.</para> @@ -16134,40 +16134,40 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <itemizedlist> <listitem> - <para><quote>SCSI: Understanding the Small Computer System - Interface</quote>, written by NCR Corporation. Available from: + <para>“SCSI: Understanding the Small Computer System + Interface”, written by NCR Corporation. Available from: Prentice Hall, Englewood Cliffs, NJ, 07632 Phone: (201) 767-5937 ISBN 0-13-796855-8</para> </listitem> <listitem> - <para><quote>Basics of SCSI</quote>, a SCSI tutorial written by Ancot + <para>“Basics of SCSI”, a SCSI tutorial written by Ancot Corporation Contact Ancot for availability information at: Phone: (415) 322-5322 Fax: (415) 322-0455</para> </listitem> <listitem> - <para><quote>SCSI Interconnection Guide Book</quote>, an AMP publication + <para>“SCSI Interconnection Guide Book”, an AMP publication (dated 4/93, Catalog 65237) that lists the various SCSI connectors and suggests cabling schemes. Available from AMP at (800) 522-6752 or (717) 564-0100</para> </listitem> <listitem> - <para><quote>Fast Track to SCSI</quote>, A Product Guide written by + <para>“Fast Track to SCSI”, A Product Guide written by Fujitsu. Available from: Prentice Hall, Englewood Cliffs, NJ, 07632 Phone: (201) 767-5937 ISBN 0-13-307000-X</para> </listitem> <listitem> - <para><quote>The SCSI Bench Reference</quote>, <quote>The SCSI Encyclopedia</quote>, - and the <quote>SCSI Tutor</quote>, ENDL Publications, 14426 Black + <para>“The SCSI Bench Reference”, “The SCSI Encyclopedia”, + and the “SCSI Tutor”, ENDL Publications, 14426 Black Walnut Court, Saratoga CA, 95070 Phone: (408) 867-6642</para> </listitem> <listitem> - <para><quote>Zadian SCSI Navigator</quote> (quick ref. book) and - <quote>Discover the Power of SCSI</quote> (First book along with a + <para>“Zadian SCSI Navigator” (quick ref. book) and + “Discover the Power of SCSI” (First book along with a one-hour video and tutorial book), Zadian Software, Suite 214, 1210 S. Bascom Ave., San Jose, CA 92128, (408) 293-0800</para> @@ -16250,7 +16250,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed ones. Today's top-of-line 5,400RPM drives can sustain a throughput comparable to 7,200RPM drives of one or two model generations ago. The number to find on the spec sheet for - bandwidth is <quote>internal data (or transfer) rate</quote>. It is + bandwidth is “internal data (or transfer) rate”. It is usually in megabits/sec so divide it by 8 and you'll get the rough approximation of how much megabytes/sec you can get out of the drive.</para> @@ -16302,8 +16302,8 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <title>Form factor</title> <para>Most SCSI drives sold today are of 3.5" form factor. They - come in two different heights; 1.6" (<quote>half-height</quote>) or 1" - (<quote>low-profile</quote>). The half-height drive is the same height as a + come in two different heights; 1.6" (“half-height”) or 1" + (“low-profile”). The half-height drive is the same height as a CD-ROM drive. However, don't forget the spacing rule mentioned in the previous section. If you have three standard 3.5" drive bays, you will not be able to put three half-height @@ -16326,7 +16326,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>On the other hand, if you need to connect many drives, going for Fast-wide SCSI may not be a bad idea. That will have the same max bandwidth as Ultra (narrow) SCSI, while - electronically it's much easier to get it <quote>right</quote>. My advice + electronically it's much easier to get it “right”. My advice would be: if you want to connect many disks, get wide SCSI drives; they usually cost a little more but it may save you down the road. (Besides, if you can't afford the cost @@ -16339,7 +16339,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed serious about building a large storage system, get SCA drives and a good SCA enclosure (dual power supply with at least one extra fan). They are more electronically sound than 68-pin - counterparts because there is no <quote>stub</quote> of the SCSI bus inside + counterparts because there is no “stub” of the SCSI bus inside the disk canister as in arrays built from 68-pin drives. They are easier to install too (you just need to screw the drive in the canister, instead of trying to squeeze in your fingers in @@ -16558,7 +16558,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>If you have a SCSI-2 controller, short jumper 6. Otherwise, the drive behaves are a SCSI-1 device. When - operating as a SCSI-1 device, this drive, <quote>locks</quote> the SCSI bus + operating as a SCSI-1 device, this drive, “locks” the SCSI bus during some tape operations, including: fsf, rewind, and rewoffl.</para> @@ -17251,7 +17251,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" will not write 60MB (DC600 cartridge) tapes. In order to overwrite 120 and 150 tapes reliably, first erase (<command>mt erase</command>) the tape. 120 and 150 tapes used a wider track (fewer tracks per tape) than 525MB tapes. - The <quote>extra</quote> width of the previous tracks is not overwritten, + The “extra” width of the previous tracks is not overwritten, as a result the new data lies in a band surrounded on both sides by the previous data unless the tape have been erased.</para> @@ -17410,7 +17410,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>QIC-150 tapes and drives are, perhaps, the most common tape drive and media around. QIC tape drives are the least - expensive <quote>serious</quote> backup drives. The downside is the cost + expensive “serious” backup drives. The downside is the cost of media. QIC tapes are expensive compared to 8mm or 4mm tapes, up to 5 times the price per GB data storage. But, if your needs can be satisfied with a half-dozen tapes, QIC may @@ -17462,7 +17462,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" The cartridge has a swinging gate along one entire side of the cartridge. The drive mechanism opens this gate to extract the tape leader. The tape leader has an oval hole in it which the - drive uses to <quote>hook</quote> the tape. The take-up spool is located + drive uses to “hook” the tape. The take-up spool is located inside the tape drive. All the other tape cartridges listed here (9 track tapes are the only exception) have both the supply and take-up spools located inside the tape cartridge @@ -17639,10 +17639,10 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> number of large disks is the length of time required to backup to data directly to tape exceeds the amount of time available for the task. Amanda solves this problem. Amanda can use a - <quote>holding disk</quote> to backup several filesystems at the same time. - Amanda creates <quote>archive sets</quote>: a group of tapes used over a + “holding disk” to backup several filesystems at the same time. + Amanda creates “archive sets”: a group of tapes used over a period of time to create full backups of all the filesystems - listed in Amanda's configuration file. The <quote>archive set</quote> also + listed in Amanda's configuration file. The “archive set” also contains nightly incremental (or differential) backups of all the filesystems. Restoring a damaged filesystem requires the most recent full backup and the incremental backups.</para> @@ -17658,18 +17658,18 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> <sect4> <title>Do nothing</title> - <para><quote>Do nothing</quote> is not a computer program, but it is the most + <para>“Do nothing” is not a computer program, but it is the most widely used backup strategy. There are no initial costs. There is no backup schedule to follow. Just say no. If something happens to your data, grin and bear it!</para> <para>If your time and your data is worth little to nothing, - then <quote>Do nothing</quote> is the most suitable backup program for your + then “Do nothing” is the most suitable backup program for your computer. But beware, Unix is a useful tool, you may find that within six months you have a collection of files that are valuable to you.</para> - <para><quote>Do nothing</quote> is the correct backup method for + <para>“Do nothing” is the correct backup method for <filename>/usr/obj</filename> and other directory trees that can be exactly recreated by your computer. An example is the files that comprise these handbook pages-they have been @@ -18383,7 +18383,7 @@ XkbKeymap "xfree86(ru)" <para>When you change the settings to this device, the settings are in effect until the device is closed. When it is reopened, it goes back to the default set. To make changes to the default set, you - can open and adjust the settings of the <quote>initial state</quote> device. + can open and adjust the settings of the “initial state” device. For example, to turn on <acronym>CLOCAL</acronym> mode, 8 bits, and <emphasis>XON/XOFF</emphasis> flow control by default for ttyd5, do:</para> @@ -18397,7 +18397,7 @@ XkbKeymap "xfree86(ru)" It can still change these settings to its liking, though.</para> <para>You can also prevent certain settings from being changed by an - application by making adjustments to the <quote>lock state</quote> device. For + application by making adjustments to the “lock state” device. For example, to lock the speed of <filename>ttyd5</filename> to 57600 bps, do</para> @@ -18480,7 +18480,7 @@ XkbKeymap "xfree86(ru)" <para>Dumb terminals are specialized pieces of hardware that let you connect to computers over serial lines. They are called - <quote>dumb</quote> because they have only enough computational power to + “dumb” because they have only enough computational power to display, send, and receive text. You cannot run any programs on them. It is the computer to which you connect them that has all the power to run text editors, compilers, email, games, and so @@ -18584,9 +18584,9 @@ XkbKeymap "xfree86(ru)" <title>Null-modem cables</title> <para>A null-modem cable passes some signals straight through, - like <quote>signal ground,</quote> but switches other signals. For - example, the <quote>send data</quote> pin on one end goes to the - <quote>receive data</quote> pin on the other end.</para> + like “signal ground,” but switches other signals. For + example, the “send data” pin on one end goes to the + “receive data” pin on the other end.</para> <para>If you like making your own cables, here is a table showing a recommended way to construct a null-modem cable for @@ -18682,8 +18682,8 @@ XkbKeymap "xfree86(ru)" <title>Standard RS-232C Cables</title> <para>A standard serial cable passes all the RS-232C signals - straight-through. That is, the <quote>send data</quote> pin on one end - of the cable goes to the <quote>send data</quote> pin on the other end. + straight-through. That is, the “send data” pin on one end + of the cable goes to the “send data” pin on the other end. This is the type of cable to connect a modem to your FreeBSD system, and the type of cable needed for some terminals.</para> @@ -18793,11 +18793,11 @@ XkbKeymap "xfree86(ru)" </step> <step> - <para>Set the port to <quote>on.</quote></para> + <para>Set the port to “on.”</para> </step> <step> - <para>Specify whether the port should be <quote>secure.</quote></para> + <para>Specify whether the port should be “secure.”</para> </step> <step> @@ -18971,7 +18971,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on will ignore that). The last field tells whether the port is secure.</para> - <para>What does <quote>secure</quote> mean?</para> + <para>What does “secure” mean?</para> <para>It means that the root account (or any account with a user ID of 0) may login on the port. Insecure ports do not allow @@ -18997,7 +18997,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on <para>Which should you use?</para> - <para>Just use <quote>insecure.</quote> Use <quote>insecure</quote> + <para>Just use “insecure.” Use “insecure” <emphasis>even</emphasis> for terminals <emphasis>not</emphasis> in public user areas or behind locked doors. It is quite easy to login and use <command>su</command> if you need @@ -19107,8 +19107,8 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <listitem> <para>Switch the terminal (or the terminal emulation - software) from <quote>half duplex</quote> or <quote>local echo</quote> to <quote>full - duplex.</quote></para> + software) from “half duplex” or “local echo” to “full + duplex.”</para> </listitem> </varlistentry> </variablelist> @@ -19200,9 +19200,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom a good reference.</para> <para>When talking about communications data rates, the author - does not use the term <quote>baud</quote>. Baud + does not use the term “baud”. Baud refers to the number of electrical state transitions that may be - made in a period of time, while <quote>bps</quote> (bits per second) is the <quote>correct</quote> + made in a period of time, while “bps” (bits per second) is the “correct” term to use (at least it does not seem to bother the curmudgeons quite a much).</para> @@ -19390,7 +19390,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom serial ports, known in the PC-DOS world as <devicename>COM1:</devicename>, <devicename>COM2:</devicename>, <devicename>COM3:</devicename>, and <devicename>COM4:</devicename>. FreeBSD can presently also handle - <quote>dumb</quote> multiport serial interface cards, such as the Boca Board + “dumb” multiport serial interface cards, such as the Boca Board 1008 and 2016 (please see the manual page <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for kernel configuration information if you have a multiport serial card). The default kernel only looks for the standard COM ports, though.</para> @@ -19427,9 +19427,9 @@ sio3: type 16550A</screen> your system.</para> <para>Please see the BSD System Manager's Manual chapter on - <quote>Building Berkeley Kernels with Config</quote> [the source for which is - in <filename>/usr/src/share/doc/smm</filename>] and <quote>FreeBSD - Configuration Options</quote> [in <filename>/sys/conf/options</filename> + “Building Berkeley Kernels with Config” [the source for which is + in <filename>/usr/src/share/doc/smm</filename>] and “FreeBSD + Configuration Options” [in <filename>/sys/conf/options</filename> and in <filename>/sys/<replaceable>arch</replaceable>/conf/options.<replaceable>arch</replaceable></filename>, with <emphasis>arch</emphasis> for example being <filename>i386</filename>] for more information on configuring and building kernels. You may have to unpack the kernel source distribution if have not installed the system sources already (<filename>srcdist/srcsys.??</filename> in FreeBSD 1.1, <filename>srcdist/sys.??</filename> in FreeBSD 1.1.5.1, or the entire source distribution in FreeBSD 2.0) to be able to configure and build kernels.</para> @@ -19474,7 +19474,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr <para>When you are finished adjusting the kernel configuration file, use the program <command>config</command> as documented - in <quote>Building Berkeley Kernels with Config</quote> and the + in “Building Berkeley Kernels with Config” and the <citerefentry><refentrytitle>config</refentrytitle><manvolnum>8</manvolnum></citerefentry> manual page to prepare a kernel building directory, then build, install, and test the new kernel.</para> @@ -19484,8 +19484,8 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr <sect2> <title>Device Special Files</title> - <para>Most devices in the kernel are accessed through <quote>device - special files</quote>, which are located in the + <para>Most devices in the kernel are accessed through “device + special files”, which are located in the <filename>/dev</filename> directory. The <devicename>sio</devicename> devices are accessed through the <filename>/dev/ttyd<replaceable>?</replaceable></filename> (dial-in) and <filename>/dev/cua0<replaceable>?</replaceable></filename> (call-out) devices. On FreeBSD @@ -19584,11 +19584,11 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen> sees junk, it is assumed that they know they should press the <literal><Enter></literal> key until they see a recognizable prompt. If the data rates do not match, <command>getty</command> sees anything the user types as - <quote>junk</quote>, tries going to the next speed and gives the + “junk”, tries going to the next speed and gives the <prompt>login:</prompt> prompt again. This procedure can continue ad nauseum, but normally only takes a keystroke or two before the user sees a good prompt. Obviously, this login sequence - does not look as clean as the former <quote>locked-speed</quote> method, but + does not look as clean as the former “locked-speed” method, but a user on a low-speed connection should receive better interactive response from full-screen programs.</para> @@ -19670,11 +19670,11 @@ uq|V19200|High Speed Modem at 19200,8-bit:\ Kbps (for a V.32bis connection), then cycles through 9600 bps (for V.32), 2400 bps, 1200 bps, 300 bps, and back to 19.2 Kbps. Communications rate cycling is implemented with the - <literal>nx=</literal> (<quote>next - table</quote>) capability. Each of the lines uses a - <literal>tc=</literal> (<quote>table - continuation</quote>) entry to pick up the rest of the - <quote>standard</quote> settings for a particular data rate.</para> + <literal>nx=</literal> (“next + table”) capability. Each of the lines uses a + <literal>tc=</literal> (“table + continuation”) entry to pick up the rest of the + “standard” settings for a particular data rate.</para> <para>If you have a 28.8 Kbps modem and/or you want to take advantage of compression on a 14.4 Kbps modem, you need to use @@ -19701,7 +19701,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ <para>If you have a slow CPU or a heavily loaded system and you do not have 16550A-based serial ports, you may receive sio - <quote>silo</quote> errors at 57.6 Kbps.</para> + “silo” errors at 57.6 Kbps.</para> </sect4> </sect3> @@ -19789,7 +19789,7 @@ ttyd0 "/usr/libexec/getty std.19200" dialup on <title>Matching-Speed Config</title> <para>In a matching-speed configuration, your <filename>ttys</filename> entry needs to reference the - appropriate beginning <quote>auto-baud</quote> (sic) entry in + appropriate beginning “auto-baud” (sic) entry in <filename>/etc/gettytab</filename>. For example, if you added the above suggested entry for a matching-speed modem that starts at 19.2 Kbps (the <filename>gettytab</filename> entry @@ -20227,7 +20227,7 @@ AT&B2&W <sect2 id="direct-at"> <title>How am I expected to enter these AT commands?</title> - <para>Make what is called a <quote>direct</quote> + <para>Make what is called a “direct” entry in your <filename>/etc/remote</filename> file. For example, if your modem is hooked up to the first serial port, <filename>/dev/cuaa0</filename>, then put in the following line:</para> @@ -20282,7 +20282,7 @@ pn=\@ <sect2> <title>How can I dial a phone number on the command line?</title> - <para>Put what is called a <quote>generic</quote> + <para>Put what is called a “generic” entry in your <filename>/etc/remote</filename> file. For example:</para> <programlisting> @@ -20385,11 +20385,11 @@ big-university 5551114 <title>Why do I have to hit CTRL+P twice to send CTRL+P once?</title> - <para>CTRL+P is the default <quote>force</quote> character, used to tell + <para>CTRL+P is the default “force” character, used to tell <command>tip</command> that the next character is literal data. You can set the force character to any other character with the <command>~s</command> escape, which - means <quote>set a variable.</quote></para> + means “set a variable.”</para> <para>Type <command>~sforce=<replaceable>single-char</replaceable></command> followed by a newline. <replaceable>single-char</replaceable> is any single character. @@ -20411,7 +20411,7 @@ force=<single-char> <sect2> <title>Suddenly everything I type is in UPPER CASE??</title> - <para>You must have pressed CTRL+A, <command>tip</command>'s <quote>raise character,</quote> specially + <para>You must have pressed CTRL+A, <command>tip</command>'s “raise character,” specially designed for people with broken caps-lock keys. Use <command>~s</command> as above and set the variable <literal>raisechar</literal> to something reasonable. In fact, you can set it to the same as the force character, if you never expect to use either @@ -20540,7 +20540,7 @@ raisechar=^^ <listitem> <para>The IP address of your ISP's gateway. The gateway is the machine to which you will connect and will be set up as - your <quote>default route</quote>. If your + your “default route”. If your ISP hasn't given you this number, don't worry. We can make one up and your ISP's PPP server will tell us when we connect.</para> @@ -20857,7 +20857,7 @@ domain <replaceable>bar.com</replaceable> <listitem> <para>Identifies an entry for a provider called - <quote>provider</quote>.</para> + “provider”.</para> </listitem> </varlistentry> @@ -20922,7 +20922,7 @@ protocol: ppp</screen> link to another machine and the DSR modem signal is not available to indicate that the line is up. When data saturates the line, LQR packets are sometimes - <quote>missed</quote>, causing <command>ppp</command> to close the connection + “missed”, causing <command>ppp</command> to close the connection prematurely. Refusing to negotiate lqr is sometimes prudent (if you are going through a modem) as it avoids this whole mess. By default, <command>ppp</command> will not attempt to @@ -20941,7 +20941,7 @@ protocol: ppp</screen> their gateway (the machine to which you connect). If your ISP hasn't given you a gateway address, use <hostid role="netmask">10.0.0.2/0</hostid>. If you need - to use a <quote>guessed</quote> address, make sure that you create + to use a “guessed” address, make sure that you create an entry in <filename>/etc/ppp/ppp.linkup</filename> as per the instructions for <xref linkend="userppp-dynamicIP" remap="PPP and Dynamic @@ -20992,7 +20992,7 @@ protocol: ppp</screen> <para>If your service provider does not assign static IP numbers, <command>ppp</command> can be configured to negotiate - the local and remote addresses. This is done by <quote>guessing</quote> an + the local and remote addresses. This is done by “guessing” an IP number and allowing <command>ppp</command> to set it up correctly using the IP Configuration Protocol (IPCP) after connecting. The <filename>ppp.conf</filename> configuration is the same as <xref @@ -21425,7 +21425,7 @@ default: <para>PAP is less secure than CHAP, but security is not normally an issue here as passwords, although being sent as plain text with PAP, are being transmitted down a serial line only. - There's not much room for hackers to <quote>eavesdrop</quote>.</para> + There's not much room for hackers to “eavesdrop”.</para> <para>Referring back to the <xref linkend="userppp-staticIP" remap="PPP and Static IP addresses"> or <xref @@ -21619,7 +21619,7 @@ sendmail_flags="-bd" 4 !bg sendmail -bd -q30m </programlisting> - <para>If you don't like this, it is possible to set up a <quote>dfilter</quote> + <para>If you don't like this, it is possible to set up a “dfilter” to block SMTP traffic. Refer to the sample files for further details.</para> @@ -21763,12 +21763,12 @@ sendmail_flags="-bd" <orderedlist> <listitem> - <para>as a <quote>client</quote>, i.e. you want to connect your machine to + <para>as a “client”, i.e. you want to connect your machine to outside world via PPP serial connection or modem line.</para> </listitem> <listitem> - <para>as a <quote>server</quote>, i.e. your machine is located on the + <para>as a “server”, i.e. your machine is located on the network and used to connect other computers using PPP.</para> </listitem> @@ -22652,7 +22652,7 @@ sl1* 296 <Link> 0 0 0 0 <para>The <devicename>sl0</devicename> and <devicename>sl1</devicename> interfaces shown in <command>netstat -i</command>'s output indicate that there are two SLIP interfaces built into the kernel. (The asterisks after the <literal>sl0</literal> and <literal>sl1</literal> indicate that the interfaces are - <quote>down</quote>.)</para> + “down”.)</para> <para>However, FreeBSD's default kernels do not come configured to forward packets (ie, your FreeBSD machine will not act as a @@ -22779,7 +22779,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp <listitem> <para><option>noicmp</option> — disable ICMP - packets (so any <quote>ping</quote> packets will be dropped instead + packets (so any “ping” packets will be dropped instead of using up your bandwidth)</para> </listitem> @@ -22797,8 +22797,8 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp <para>Your choice of local and remote addresses for your SLIP links depends on whether you are going to dedicate a TCP/IP - subnet or if you are going to use <quote>proxy ARP</quote> on your SLIP - server (it is not <quote>true</quote> proxy ARP, but that is the + subnet or if you are going to use “proxy ARP” on your SLIP + server (it is not “true” proxy ARP, but that is the terminology used in this document to describe it). If you are not sure which method to select or how to assign IP addresses, please refer to the TCP/IP books referenced in the <xref @@ -22815,7 +22815,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp other routers to inform them about your SLIP server's route to the SLIP subnet.</para> - <para>Otherwise, if you will use the <quote>proxy ARP</quote> method, you + <para>Otherwise, if you will use the “proxy ARP” method, you will need to assign your SLIP client's IP addresses out of your SLIP server's Ethernet subnet, and you will also need to adjust your <filename>/etc/sliphome/slip.login</filename> and @@ -22849,7 +22849,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp the appropriate SLIP interface with the local and remote addresses and network mask of the SLIP interface.</para> - <para>If you have decided to use the <quote>proxy ARP</quote> method (instead + <para>If you have decided to use the “proxy ARP” method (instead of using a separate subnet for your SLIP clients), your <filename>/etc/sliphome/slip.login</filename> file will need to look something like this:</para> @@ -22879,7 +22879,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp <para>When using the example above, be sure to replace the Ethernet MAC address (<hostid role="mac">00:11:22:33:44:55</hostid>) with the MAC address of - your system's Ethernet card, or your <quote>proxy ARP</quote> will + your system's Ethernet card, or your “proxy ARP” will definitely not work! You can discover your SLIP server's Ethernet MAC address by looking at the results of running <command>netstat -i</command>; the second line of the output @@ -22904,7 +22904,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp <para>When you create <filename>/etc/sliphome/slip.login</filename> and <filename>/etc/sliphome/slip.logout</filename>, the - <quote>execute</quote> bit (ie, <command>chmod 755 + “execute” bit (ie, <command>chmod 755 /etc/sliphome/slip.login /etc/sliphome/slip.logout</command>) must be set, or <command>sliplogin</command> will be unable to execute @@ -22916,7 +22916,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp <title><filename>slip.logout</filename> Configuration</title> <para><filename>/etc/sliphome/slip.logout</filename> is not - strictly needed (unless you are implementing <quote>proxy ARP</quote>), but + strictly needed (unless you are implementing “proxy ARP”), but if you decide to create it, this is an example of a basic <filename>slip.logout</filename> script:</para> @@ -22934,7 +22934,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp /sbin/ifconfig sl$1 down </programlisting> - <para>If you are using <quote>proxy ARP</quote>, you will want to have + <para>If you are using “proxy ARP”, you will want to have <filename>/etc/sliphome/slip.logout</filename> remove the ARP entry for the SLIP client:</para> @@ -22955,7 +22955,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp </programlisting> <para>The <command>arp -d $5</command> removes the ARP entry - that the <quote>proxy ARP</quote> <filename>slip.login</filename> added + that the “proxy ARP” <filename>slip.login</filename> added when the SLIP client logged in.</para> <para>It bears repeating: make sure @@ -22969,7 +22969,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp <sect2> <title>Routing Considerations</title> - <para>If you are not using the <quote>proxy ARP</quote> method for routing + <para>If you are not using the “proxy ARP” method for routing packets between your SLIP clients and the rest of your network (and perhaps the Internet), you will probably either have to add static routes to your closest default router(s) to route your SLIP @@ -23004,7 +23004,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp You can use <command>gated</command> from the <xref linkend="ports" remap="ports collection"> or retrieve and build it yourself from <ulink - URL="ftp://ftp.gated.merit.edu/research.and.development/gated/">the GateD anonymous ftp site</ulink>; I believe the current version as of this writing is <filename>gated-R3_5Alpha_8.tar.Z</filename>, which includes support for FreeBSD <quote>out-of-the-box</quote>. Complete information and documentation on <command>gated</command> is available on the Web starting at <ulink URL="http://www.gated.merit.edu/">the Merit GateD Consortium</ulink>. Compile and install it, and then write a <filename>/etc/gated.conf</filename> file to configure your gated; here is a sample, similar to what the author used on a FreeBSD SLIP server:</para> + URL="ftp://ftp.gated.merit.edu/research.and.development/gated/">the GateD anonymous ftp site</ulink>; I believe the current version as of this writing is <filename>gated-R3_5Alpha_8.tar.Z</filename>, which includes support for FreeBSD “out-of-the-box”. Complete information and documentation on <command>gated</command> is available on the Web starting at <ulink URL="http://www.gated.merit.edu/">the Merit GateD Consortium</ulink>. Compile and install it, and then write a <filename>/etc/gated.conf</filename> file to configure your gated; here is a sample, similar to what the author used on a FreeBSD SLIP server:</para> <programlisting> # @@ -23111,15 +23111,15 @@ import proto rip interface ed { <para>For one machine to be able to find another, there must be a mechanism in place to describe how to get from one to the other. - This is called Routing. A <quote>route</quote> is a defined pair of addresses: - a <quote>destination</quote> and a <quote>gateway</quote>. The pair indicates that if you are + This is called Routing. A “route” is a defined pair of addresses: + a “destination” and a “gateway”. The pair indicates that if you are trying to get to this <emphasis>destination</emphasis>, send along through this <emphasis>gateway</emphasis>. There are three types of - destinations: individual hosts, subnets, and <quote>default</quote>. The - <quote>default route</quote> is used if none of the other routes apply. We will + destinations: individual hosts, subnets, and “default”. The + “default route” is used if none of the other routes apply. We will talk a little bit more about default routes later on. There are also three types of gateways: individual hosts, interfaces (also - called <quote>links</quote>), and ethernet hardware addresses.</para> + called “links”), and ethernet hardware addresses.</para> <sect2> @@ -23268,7 +23268,7 @@ host2.foobar.com link#1 UC 0 0 connect along that interface.</para> <para>If all known paths fail, the system has one last option: the - <quote>default</quote> route. This route is a + “default” route. This route is a special type of gateway route (usually the only one present in the system), and is always marked with a <literal>c</literal> in the flags field. For hosts on a local area network, this gateway is set to whatever machine has a @@ -23321,9 +23321,9 @@ host2.foobar.com link#1 UC 0 0 </tgroup> </informaltable> - <para>A common question is <quote>Why (or how) would we set the T1-GW to + <para>A common question is “Why (or how) would we set the T1-GW to be the default gateway for Local1, rather than the ISP server it - is connected to?</quote>.</para> + is connected to?”.</para> <para>Remember, since the PPP interface is using an address on the ISP's local network for your side of the connection, routes for @@ -23392,7 +23392,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) <para>There is a system (much like the distributed DNS information) that keeps track of all assigned address-spaces, and defines their - point of connection to the Internet Backbone. The <quote>Backbone</quote> are + point of connection to the Internet Backbone. The “Backbone” are the main trunk lines that carry Internet traffic across the country, and around the world. Each backbone machine has a copy of a master set of tables, which direct traffic for a particular @@ -23450,7 +23450,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) The only solution is often to reset the client, because the NFS situation cannot be resolved.</para> - <para>Though the <quote>correct</quote> solution is to get a higher performance and + <para>Though the “correct” solution is to get a higher performance and capacity Ethernet adapter for the FreeBSD system, there is a simple workaround that will allow satisfactory operation. If the FreeBSD system is the <emphasis>server</emphasis>, include the option <option>-w=1024</option> on the mount from @@ -23506,9 +23506,9 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0 <para>For anyone who cares, here is what happens when the failure occurs, which also explains why it is unrecoverable. NFS typically - works with a <quote>block</quote> size of 8k (though it may do fragments of + works with a “block” size of 8k (though it may do fragments of smaller sizes). Since the maximum Ethernet packet is around 1500 - bytes, the NFS <quote>block</quote> gets split into multiple Ethernet packets, + bytes, the NFS “block” gets split into multiple Ethernet packets, even though it is still a single unit to the upper-level code, and must be received, assembled, and <emphasis>acknowledged</emphasis> as a unit. The high-performance workstations can pump out the packets which @@ -23528,7 +23528,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0 <para>Overruns may still occur when a high-performance workstations is slamming data out to a PC system, but with the better cards, such - overruns are not guaranteed on NFS <quote>units</quote>. When an overrun occurs, + overruns are not guaranteed on NFS “units”. When an overrun occurs, the units affected will be retransmitted, and there will be a fair chance that they will be received, assembled, and acknowledged.</para> @@ -24138,7 +24138,7 @@ ISDN BRI line <title>Basic Information</title> <para>These are the major programs involved in an E-Mail exchange. A - <quote>mailhost</quote> is a server that is + “mailhost” is a server that is responsible for delivering and receiving all email for your host, and possibly your network.</para> @@ -24149,7 +24149,7 @@ ISDN BRI line <para>This is a program like <application >elm</application>, <application>pine</application>, <application>mail</application>, or something more sophisticated like a WWW browser. This program will simply pass off all e-mail - transactions to the local <quote>mailhost</quote> , + transactions to the local “mailhost” , either by calling <command>sendmail</command> or delivering it over TCP.</para> @@ -24239,7 +24239,7 @@ ISDN BRI line <sect2> <title>Basic</title> - <para>As your FreeBSD system comes <quote>out of the box</quote>[TM], you should + <para>As your FreeBSD system comes “out of the box”[TM], you should be able to send E-mail to external hosts as long as you have <filename>/etc/resolv.conf</filename> setup or are running a name server. If you want to have mail for your host delivered to your @@ -24336,7 +24336,7 @@ freefall CNAME www.FreeBSD.org <para>To setup up a network mailhost, you need to direct the mail from arriving at all the workstations. In other words, you want to hijack all mail for <hostid role="domainname">*.smallminingco.com - </hostid> and divert it to one machine, your <quote>mailhost</quote>.</para> + </hostid> and divert it to one machine, your “mailhost”.</para> <para>The network users on their workstations will most likely pick up their mail over POP or telnet.</para> @@ -24512,7 +24512,7 @@ uucp-dom:if-bus . uucp-dom:sax <para>As you can see, this is part of a real-life file. The first three lines handle special cases where domain-addressed mail should not be sent out to the default route, but instead to some - UUCP neighbor in order to <quote>shortcut</quote> the delivery path. The + UUCP neighbor in order to “shortcut” the delivery path. The next line handles mail to the local Ethernet domain that can be delivered using SMTP. Finally, the UUCP neighbors are mentioned in the .UUCP pseudo-domain notation, to allow for a @@ -24532,8 +24532,8 @@ uucp-dom:if-bus . uucp-dom:sax <para>Final hint: if you are uncertain whether some particular mail routing would work, remember the <option>-bt</option> option to <command>sendmail</command>. It starts <command>sendmail</command> - in <quote>address test - mode</quote>; simply enter <literal>0</literal>, followed by the address + in “address test + mode”; simply enter <literal>0</literal>, followed by the address you wish to test for the mail routing. The last line tells you the used internal mail agent, the destination host this agent will be called with, and the (possibly translated) address. Leave this @@ -24595,8 +24595,8 @@ domain foo.bar.edu </programlisting> into your <filename>/etc/resolv.conf</filename>. However, - make sure that the search order does not go beyond the <quote>boundary - between local and public administration</quote>, as RFC 1535 calls + make sure that the search order does not go beyond the “boundary + between local and public administration”, as RFC 1535 calls it.</para> </sect2> @@ -24624,7 +24624,7 @@ to /etc/sendmail.cf. <para>The sendmail FAQ is in <filename>/usr/src/usr.sbin/sendmail</filename> and is recommended - reading if you want to do any <quote>tweaking</quote> of your mail + reading if you want to do any “tweaking” of your mail setup.</para> </sect2> @@ -24762,7 +24762,7 @@ an A record in the DNS for "customer.com".</programlisting> <listitem> <para>Members of the FreeBSD group who are actively working on some part of the source tree and for whom keeping - <quote>current</quote> is an absolute requirement.</para> + “current” is an absolute requirement.</para> </listitem> <listitem> @@ -24802,8 +24802,8 @@ an A record in the DNS for "customer.com".</programlisting> </listitem> <listitem> - <para>In any way <quote>officially supported</quote> by us. We do our - best to help people genuinely in one of the 3 <quote>legitimate</quote> + <para>In any way “officially supported” by us. We do our + best to help people genuinely in one of the 3 “legitimate” FreeBSD-current categories, but we simply <emphasis>do not have the time</emphasis> to provide tech support for it. This is not because we are mean and nasty people who do not @@ -24835,9 +24835,9 @@ an A record in the DNS for "customer.com".</programlisting> probably end up stumbling over a lot of problems that others have already found and solved. Even more importantly, you will miss out on potentially critical information (e.g. - <quote>Yo, Everybody! Before you rebuild + “Yo, Everybody! Before you rebuild <filename>/usr/src</filename>, you <emphasis>must</emphasis> - rebuild the kernel or your system will crash horribly!</quote>). + rebuild the kernel or your system will crash horribly!”). The <email>cvs-all</email> mailing list will allow you to see the commit log entry for each change as it is made along with any pertinent information on possible @@ -24876,7 +24876,7 @@ subscribe cvs-all <listitem> <para>Use <command>ftp</command>. The source tree for FreeBSD-current is - always <quote>exported</quote> on: <ulink + always “exported” on: <ulink URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current">ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current</ulink> We also use <command>wu-ftpd</command> which allows compressed/tar'd grabbing of whole trees. e.g. you see:</para> <informalexample> @@ -25022,7 +25022,7 @@ subscribe freebsd-stable <listitem> <para>Use <command>ftp</command>. The source tree for FreeBSD-stable is - always <quote>exported</quote> on: <ulink + always “exported” on: <ulink URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-stable">ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-stable</ulink></para> <para>We also use <command>wu-ftpd</command> which allows @@ -25101,7 +25101,7 @@ subscribe freebsd-stable its previous run is executed several times a day on the master archive, any detected changes being compressed, stamped with a sequence-number and encoded for transmission over email (printable - ASCII only). Once received, these <quote>CTM deltas</quote> can then be handed + ASCII only). Once received, these “CTM deltas” can then be handed to the <citerefentry><refentrytitle>ctm_rmail</refentrytitle><manvolnum>1</manvolnum></citerefentry> utility which will automatically decode, verify and apply the changes to the user's copy of the sources. This process is far more efficient than <application>CVSup</application>, and places less strain on @@ -25112,8 +25112,8 @@ subscribe freebsd-stable wipe out portions of your archive, <application>CVSup</application> will detect and rebuild the damaged portions for you. <application>CTM</application> won't do this, and if you wipe some portion of your source tree out (and don't have it backed up) then - you will have to start from scratch (from the most recent CVS <quote>base - delta</quote>) and rebuild it all.</para> + you will have to start from scratch (from the most recent CVS “base + delta”) and rebuild it all.</para> <para>For more information on <application>CTM</application> and <application>CVSup</application>, please see one of the following sections:</para> @@ -25138,7 +25138,7 @@ subscribe freebsd-stable <title>Why should I use <application>CTM</application>?</title> <para><application>CTM</application> will give you a local copy of the - FreeBSD source trees. There are a number of <quote>flavors</quote> of the + FreeBSD source trees. There are a number of “flavors” of the tree available. Whether you wish to track the entire cvs tree or just one of the branches, <application>CTM</application> can provide you the information. If you are an active developer on FreeBSD, but @@ -25155,7 +25155,7 @@ subscribe freebsd-stable <para>You will also need to make yourself aware of the various caveats related to working directly from the development sources rather than a pre-packaged release. This is particularly - true if you choose the <quote>current</quote> sources. It is recommended + true if you choose the “current” sources. It is recommended that you read <xref linkend="current" remap="Staying current with FreeBSD">.</para> @@ -25167,7 +25167,7 @@ subscribe freebsd-stable <para>You will need two things: The <application>CTM</application> program and the initial deltas to feed it (to get up to - <quote>current</quote> levels).</para> + “current” levels).</para> <para>The <application>CTM</application> program has been part of FreeBSD ever since version 2.0 was released, and lives in @@ -25181,7 +25181,7 @@ subscribe freebsd-stable <para><ulink URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm">ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm</ulink></para> - <para>The <quote>deltas</quote> you feed <application>CTM</application> can be had + <para>The “deltas” you feed <application>CTM</application> can be had two ways, FTP or e-mail. If you have general FTP access to the Internet then the following FTP sites support access to <application>CTM</application>:</para> @@ -25198,9 +25198,9 @@ subscribe freebsd-stable <para>If you may wish to get your deltas via email:</para> <para>Send email to &a.majordomo; to subscribe to one of the - <application>CTM</application> distribution lists. <quote>ctm-cvs-cur</quote> - supports the entire cvs tree. <quote>ctm-src-cur</quote> supports the head - of the development branch. <quote>ctm-src-2_2</quote> supports the 2.2 + <application>CTM</application> distribution lists. “ctm-cvs-cur” + supports the entire cvs tree. “ctm-src-cur” supports the head + of the development branch. “ctm-src-2_2” supports the 2.2 release branch, etc. (If you do not know how to subscribe yourself using majordomo, send a message first containing the word <literal>help</literal> — it will send you back usage @@ -25235,21 +25235,21 @@ subscribe freebsd-stable produced subsequently to it.</para> <para>First you should determine what you already have. Everyone - can start from an <quote>empty</quote> directory. However, since the trees + can start from an “empty” directory. However, since the trees are many tens of megabytes, you should prefer to start from something already at hand. If you have a RELEASE CD, you can copy or extract an initial source from it. This will save a significant transfer of data.</para> <para>Once you identify a suitable starting point, you must use an - initial <quote>transition</quote> delta to transform your starting point + initial “transition” delta to transform your starting point into a <application>CTM</application> supported tree.</para> <para>You can recognize these transition deltas by the <literal>X</literal> appended to the number (<filename>src-cur.3210XEmpty.gz</filename> for instance). The designation following the <filename>X</filename> - corresponds to the origin of your initial <quote>seed</quote>. <filename>Empty</filename> is + corresponds to the origin of your initial “seed”. <filename>Empty</filename> is an empty directory, <filename>R225</filename> would designate the 2.2.5 release, etc. As a rule a base transition from <filename>Empty</filename> is producted every 100 deltas. By the way, they are large! 25 to 30 @@ -25287,7 +25287,7 @@ subscribe freebsd-stable information.</para> <para>I would also be very happy if somebody could help with the - <quote>user interface</quote> portions, as I have realized that I cannot + “user interface” portions, as I have realized that I cannot make up my mind on what options should do what, how and when...</para> @@ -25409,8 +25409,8 @@ subscribe freebsd-stable <sect3> <title>Miscellaneous stuff</title> - <para>All the <quote>DES infected</quote> (e.g. export controlled) source is - not included. You will get the <quote>international</quote> version only. + <para>All the “DES infected” (e.g. export controlled) source is + not included. You will get the “international” version only. If sufficient interest appears, we will set up a <literal>sec-cur</literal> sequence too. There is a sequence of deltas for the <literal>ports</literal> collection too, but interest has not been all that high yet. @@ -25659,7 +25659,7 @@ subscribe freebsd-stable <para>Each remaining line describes a set of files that the user wishes to receive. The line begins with the name of a - <quote>collection</quote>, a logical grouping of files defined by the server. + “collection”, a logical grouping of files defined by the server. The name of the collection tells the server which files you want. After the collection name come zero or more fields, separated by white space. These fields answer the questions @@ -25698,7 +25698,7 @@ subscribe freebsd-stable <para>Which files do you want to receive?<anchor id="cvsup-config-files"></para> <para>The files available via <application>CVSup</application> are organized into named - groups called <quote>collections</quote>. The collections that are + groups called “collections”. The collections that are available are described <xref linkend="cvsup-collec" remap="here">. In this example, we wish to receive the entire main source tree for the FreeBSD system. There is @@ -25959,7 +25959,7 @@ cvs-crypto <para>Where should <command>cvsup</command> maintain its status files?<anchor id="cvsup-config-status"></para> <para>The cvsup client maintains certain status files in - what is called the <quote>base</quote> directory. These files help + what is called the “base” directory. These files help <application>CVSup</application> to work more efficiently, by keeping track of which updates you have already received. We will use the standard base directory, <filename>/usr/local/etc/cvsup</filename>:</para> @@ -26046,7 +26046,7 @@ cvs-crypto <para>where <filename><replaceable>supfile</replaceable></filename> is of course the name of the supfile you have just created. Assuming you are running under X11, <command>cvsup</command> will display a GUI window with some buttons to do the usual - things. Press the <quote>go</quote> button, and watch it run.</para> + things. Press the “go” button, and watch it run.</para> <para>Since you are updating your actual <filename>/usr/src</filename> tree in this example, you will need to run the program as <username>root</username> so that <command>cvsup</command> @@ -27433,7 +27433,7 @@ cvs-crypto somewhat trickier affair and depends a lot on how far out of date you are with the current state of the core FreeBSD development. There is a special on-going release of FreeBSD known as - <quote>FreeBSD-current</quote> which is made available in a variety of ways + “FreeBSD-current” which is made available in a variety of ways for the convenience of developers working actively on the system. See <xref linkend="current" remap="Staying current with FreeBSD"> for more information @@ -27449,7 +27449,7 @@ cvs-crypto <para>Assuming that you can manage to secure fairly up-to-date sources to base your changes on, the next step is to produce a set of diffs to send to the FreeBSD maintainers. This is done with - the <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, with the <quote>context diff</quote> + the <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, with the “context diff” form being preferred. For example:</para> <para><informalexample> @@ -27517,7 +27517,7 @@ cvs-crypto <listitem> <para>The BSD copyright. This copyright is most preferred due - to its <quote>no strings attached</quote> nature and general + to its “no strings attached” nature and general attractiveness to commercial enterprises. Far from discouraging such commercial use, the FreeBSD Project actively encourages such participation by commercial @@ -27526,7 +27526,7 @@ cvs-crypto </listitem> <listitem> - <para>The GNU Public License, or <QUOTE>GPL</QUOTE>. This license is not + <para>The GNU Public License, or &LDQUO;GPL&RDQUO;. This license is not quite as popular with us due to the amount of extra effort demanded of anyone using the code for commercial purposes, but given the sheer quantity of GPL'd code we currently @@ -27549,7 +27549,7 @@ cvs-crypto authors are always encouraged to make such changes available through their own channels.</para> - <para>To place a <quote>BSD-style</quote> copyright on your work, include the + <para>To place a “BSD-style” copyright on your work, include the following text at the very beginning of every source code file you wish to protect, replacing the text between the <literal>%%</literal> with the appropriate information.</para> @@ -27599,7 +27599,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. part of FreeBSD's growth and of great usefulness to those who would not otherwise know where to turn for it. All ported software is organized into a carefully organized hierarchy known - as <quote>the ports collection</quote>. The collection enables a new user to + as “the ports collection”. The collection enables a new user to get a quick and complete overview of what is available for FreeBSD in an easy-to-compile form. It also saves considerable space by not actually containing the majority of the sources being ported, @@ -27882,7 +27882,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. <note> <para>Note that 2.2-STABLE sometimes identifies itself as - <quote>2.2.5-STABLE</quote> after the 2.2.5-RELEASE. The pattern used to + “2.2.5-STABLE” after the 2.2.5-RELEASE. The pattern used to be year followed by the month, but we decided to change it to a more straightforward major/minor system starting from 2.2. This is because the parallel development on several @@ -27930,7 +27930,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. # Date created: 5 December 1994 # Whom: asami # -# $Id: book.sgml,v 1.53 1998-10-26 23:53:47 nik Exp $ +# $Id: book.sgml,v 1.54 1998-10-26 23:54:16 nik Exp $ # DISTNAME= oneko-1.1b @@ -28079,8 +28079,8 @@ lib/X11/oneko/mouse.xpm <literal>ports</literal> and class <literal>change-request</literal>). There is no need to upload the package, we will build it by ourselves. We will take a look, get back to you if necessary, and put it in the - tree. Your name will also appear in the list of <quote>Additional - FreeBSD contributors</quote> on the FreeBSD Handbook and other files. + tree. Your name will also appear in the list of “Additional + FreeBSD contributors” on the FreeBSD Handbook and other files. Isn't that great?!? <!-- smiley -->:)</para> </sect4> @@ -28207,7 +28207,7 @@ lib/X11/oneko/mouse.xpm your <filename>Makefile</filename>.</para> <note> - <para>The <quote>main</quote> targets (e.g., <maketarget>extract</maketarget>, <maketarget>configure</maketarget>, etc.) do nothing more than + <para>The “main” targets (e.g., <maketarget>extract</maketarget>, <maketarget>configure</maketarget>, etc.) do nothing more than make sure all the stages up to that one is completed and call the real targets or scripts, and they are not intended to be changed. If you want to fix the extraction, fix @@ -28233,7 +28233,7 @@ lib/X11/oneko/mouse.xpm <para>If you cannot find a ftp/http site that is well-connected to the net, or can only find sites that have irritatingly - non-standard formats, we can <quote>house</quote> it ourselves by putting + non-standard formats, we can “house” it ourselves by putting it on <filename>ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/LOCAL_PORTS/</filename> as the last resort. Please refer to this location as <makevar>${MASTER_SITE_LOCAL}</makevar>. Send mail to the &a.ports;if you are not sure what to do.</para> @@ -28264,7 +28264,7 @@ lib/X11/oneko/mouse.xpm interaction/customization to compile or install, you should take a look at one of Larry Wall's classic <application>Configure</application> scripts and perhaps do something similar yourself. The goal of the - new ports collection is to make each port as <quote>plug-and-play</quote> + new ports collection is to make each port as “plug-and-play” as possible for the end-user while using a minimum of disk space.</para> @@ -28316,7 +28316,7 @@ lib/X11/oneko/mouse.xpm <para>If your port requires user input to build, configure or install, then set <makevar>IS_INTERACTIVE</makevar> in your - Makefile. This will allow <quote>overnight builds</quote> to skip your port + Makefile. This will allow “overnight builds” to skip your port if the user sets the variable <envar>BATCH</envar> in his environment (and if the user sets the variable <envar>INTERACTIVE</envar>, then <emphasis>only</emphasis> @@ -28604,7 +28604,7 @@ BUILD_DEPENDS= unzip:${PORTSDIR}/archivers/unzip found.</para> <note> - <para><quote>build</quote> here means everything from extracting to + <para>“build” here means everything from extracting to compilation. The dependency is checked from within the <maketarget>extract</maketarget> target.</para> </note> @@ -29064,7 +29064,7 @@ diff -u -r1.15 PLIST <orderedlist> <listitem> - <para>If the port has a <quote>do not sell for profit</quote> type of + <para>If the port has a “do not sell for profit” type of license, set the variable <makevar>NO_CDROM</makevar>. We will make sure such ports won't go into the CD-ROM come release time. The distfile and package will still be @@ -29083,7 +29083,7 @@ diff -u -r1.15 PLIST <listitem> <para>If the port has legal restrictions on who can use it - (e.g., crypto stuff) or has a <quote>no commercial use</quote> license, + (e.g., crypto stuff) or has a “no commercial use” license, set the variable <makevar>RESTRICTED</makevar> to be the string describing the reason why. For such ports, the distfiles/packages will not be available even from our ftp @@ -29291,7 +29291,7 @@ MAN8= baz.8 <para>If your port needs to determine if it should install or not, you can create a <filename>pkg/REQ</filename> - <quote>requirements</quote> script. It will be invoked automatically at + “requirements” script. It will be invoked automatically at installation/deinstallation time to determine whether or not installation/deinstallation should proceed. See man <citerefentry><refentrytitle>pkg_create</refentrytitle><manvolnum>1</manvolnum></citerefentry> and man @@ -29475,7 +29475,7 @@ post-install: files). See man <citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry> for details, the rule governing <filename>/usr</filename> pretty much applies to <filename>/usr/local</filename> too. The - exception are ports dealing with USENET <quote>news</quote>. They may use + exception are ports dealing with USENET “news”. They may use <filename>${PREFIX}/news</filename> as a destination for their files.</para> @@ -29506,8 +29506,8 @@ lib/libtcl80.so.1.0 arguments to your <filename>Makefile</filename> or <filename>pkg/PLIST</filename>. This will reset the shared library cache to the contents of <filename>/usr/lib</filename> only, and will royally screw up - the user's machine (<quote>Help, xinit does not run anymore after I - install this port!</quote>). Anybody who does this will be shot and + the user's machine (“Help, xinit does not run anymore after I + install this port!”). Anybody who does this will be shot and cut into 65,536 pieces by a rusty knife and have his liver chopped out by a bunch of crows and will eternally rot to death in the deepest bowels of hell (not necessarily in that @@ -31810,12 +31810,12 @@ MAINTAINER= email-addresses advantages and drawbacks. No clear winner has emerged.</para> <para>Since this is the case, after some debate one of these methods - has been selected as the <quote>official</quote> method and will be required for + has been selected as the “official” method and will be required for future imports of software of this kind. Furthermore, it is strongly suggested that existing contributed software converge on this model over time, as it has significant advantages over the old method, including the ability to easily obtain diffs relative to the - <quote>official</quote> versions of the source by everyone (even without cvs + “official” versions of the source by everyone (even without cvs access). This will make it significantly easier to return changes to the primary developers of the contributed software.</para> @@ -31858,11 +31858,11 @@ MAINTAINER= email-addresses as possible. The 'easy-import' tool on freefall will assist in doing the import, but if there are any doubts on how to go about it, it is imperative that you ask first and not blunder ahead and hope - it <quote>works out</quote>. CVS is not forgiving of import accidents and a fair + it “works out”. CVS is not forgiving of import accidents and a fair amount of effort is required to back out major mistakes.</para> <para>Because of some unfortunate design limitations with CVS's vendor - branches, it is required that <quote>official</quote> patches from the vendor be + branches, it is required that “official” patches from the vendor be applied to the original distributed sources and the result re-imported onto the vendor branch again. Official patches should never be patched into the FreeBSD checked out version and @@ -32006,7 +32006,7 @@ obrien@freebsd.org - 30 March 1997 well. Any version number after the <replaceable>y</replaceable> (ie. the third digit) is totally ignored when comparing shared lib version numbers to decide which library to link with. Given two shared libraries that differ - only in the <quote>micro</quote> revision, <command>ld.so</command> will link with the higher one. + only in the “micro” revision, <command>ld.so</command> will link with the higher one. Ie: if you link with <filename>libfoo.so.3.3.3</filename>, the linker only records <literal>3.3</literal> in the headers, and will link with anything starting with <replaceable>libfoo.so.3</replaceable>.<replaceable>(anything >= @@ -32014,7 +32014,7 @@ obrien@freebsd.org - 30 March 1997 <note> <para><command>ld.so</command> will always use the highest - <quote>minor</quote> revision. Ie: it will use <filename>libc.so.2.2</filename> + “minor” revision. Ie: it will use <filename>libc.so.2.2</filename> in preference to <filename>libc.so.2.0</filename>, even if the program was initially linked with <filename>libc.so.2.0</filename>.</para> @@ -32048,8 +32048,8 @@ obrien@freebsd.org - 30 March 1997 <para>The use of kernel options is basically described in the <xref linkend="kernelconfig-options" remap="kernel configuration"> - section. There's also an explanation of <quote>historic</quote> and - <quote>new-style</quote> options. The ultimate goal is to eventually turn all + section. There's also an explanation of “historic” and + “new-style” options. The ultimate goal is to eventually turn all the supported options in the kernel into new-style ones, so for people who correctly did a <command>make depend</command> in their kernel compile directory after running @@ -32097,7 +32097,7 @@ obrien@freebsd.org - 30 March 1997 piece of code.</para> <para>People familiar with the C language will immediately recognize - that everything could be counted as a <quote>config option</quote> where there + that everything could be counted as a “config option” where there is at least a single <literal>#ifdef</literal> referencing it... However, it's unlikely that many people would put</para> @@ -32231,7 +32231,7 @@ options notyet,notdef <note> <para>In the following, the term <command>kgdb</command> refers to - <command>gdb</command> run in <quote>kernel debug mode</quote>. This can be + <command>gdb</command> run in “kernel debug mode”. This can be accomplished by either starting the <command>gdb</command> with the option <option>-k</option>, or by linking and starting it under the name <command>kgdb</command>. This is not being done by @@ -32377,7 +32377,7 @@ options notyet,notdef <varlistentry><term>line 6:</term> <listitem> <para>This is a dump taken from within DDB (see below), hence - the panic comment <quote>because you said to!</quote>, and a rather + the panic comment “because you said to!”, and a rather long stack trace; the initial reason for going into DDB has been a page fault trap though.</para> @@ -32402,7 +32402,7 @@ options notyet,notdef have a new core dump handy <g>, my kernel has not panicked for a rather long time.) From looking at the code in source line 403, there is a high probability that either - the pointer access for <quote>tp</quote> was messed up, or the array + the pointer access for “tp” was messed up, or the array access was out of bounds.</para> </listitem> @@ -32958,7 +32958,7 @@ linux <para>It is no longer necessary to specify <literal>options LINUX</literal> or <literal>options COMPAT_LINUX</literal>. Linux emulation is done with an LKM - (<quote>Loadable Kernel Module</quote>) so it can be installed on the fly + (“Loadable Kernel Module”) so it can be installed on the fly without having to reboot. You will need the following things in your startup files, however: <orderedlist> @@ -33043,7 +33043,7 @@ options LINUX <sect3> <title>Installing libraries manually</title> - <para>If you do not have the <quote>ports</quote> distribution, you can + <para>If you do not have the “ports” distribution, you can install the libraries by hand instead. You will need the Linux shared libraries that the program depends on and the runtime linker. Also, you will need to create a "shadow root" @@ -33061,7 +33061,7 @@ options LINUX <para>FreeBSD-2.2-RELEASE and later works slightly differently with respect to <command>/compat/linux</command>. On -CURRENT, all files, not just - libraries, are searched for from the <quote>shadow root</quote> + libraries, are searched for from the “shadow root” <filename>/compat/linux</filename>.</para> <para>Generally, you will need to look for the shared libraries @@ -33328,7 +33328,7 @@ multi on <para>Linux is distributed by several groups that make their own set of binaries that they distribute. Each distribution has its own - name, like <quote>Slackware</quote> or <quote>Yggdrasil</quote>. The distributions are + name, like “Slackware” or “Yggdrasil”. The distributions are available on a lot of ftp sites. Sometimes the files are unpacked, and you can get the individual files you need, but mostly they are stored in distribution sets, usually consisting of subdirectories @@ -33365,7 +33365,7 @@ multi on <para>For simplicity, let us concentrate on Slackware here. This distribution consists of a number of subdirectories, containing separate packages. Normally, they are controlled by an install - program, but you can retrieve files <quote>by hand</quote> too. First of all, + program, but you can retrieve files “by hand” too. First of all, you will need to look in the <filename>contents</filename> subdir of the distribution. You will find a lot of small text files here describing the contents of the separate packages. The fastest way @@ -33411,7 +33411,7 @@ multi on <para>So, in this case, you will need the packages ldso, shlibs, xf_lib and oldlibs. In each of the contents-files for these packages, look for a line saying <literal>PACKAGE LOCATION</literal>, it will - tell you on which <quote>disk</quote> the package is, in our case it will tell + tell you on which “disk” the package is, in our case it will tell us in which subdirectory we need to look. For our example, we would find the following locations:</para> @@ -33433,7 +33433,7 @@ multi on </tgroup> </informaltable> - <para>The locations called <quote>disk<replaceable>XX</replaceable></quote> refer to the <filename>slakware/<replaceable>XX</replaceable></filename> + <para>The locations called “disk<replaceable>XX</replaceable>” refer to the <filename>slakware/<replaceable>XX</replaceable></filename> subdirectories of the distribution, others may be found in the <filename>contrib</filename> subdirectory. In this case, we could now retrieve the packages we need by retrieving the @@ -33512,12 +33512,12 @@ multi on <title>Obtaining your Mathematica Password</title> <para>Before you can run Mathematica you will have to obtain a - password from Wolfram that corresponds to your <quote>machine - ID</quote>.</para> + password from Wolfram that corresponds to your “machine + ID”.</para> <para>Once you have installed the linux compatibility runtime - libraries and unpacked the mathematica you can obtain the <quote>machine - ID</quote> by running the program <command>mathinfo</command> in the Install directory.</para> + libraries and unpacked the mathematica you can obtain the “machine + ID” by running the program <command>mathinfo</command> in the Install directory.</para> <informalexample> <screen>&prompt.root; <userinput>cd /usr/local/Mathematica/Install</userinput> @@ -33526,14 +33526,14 @@ LINUX: 'ioctl' fd=5, typ=0x89(), num=0x27 not implemented richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> </informalexample> - <para>So, for example, the <quote>machine ID</quote> of <hostid>richc</hostid> is + <para>So, for example, the “machine ID” of <hostid>richc</hostid> is <literal>9845-03452-90255</literal>. You can ignore the message about the ioctl that is not implemented. It will not prevent Mathematica from running in any way and you can safely ignore it, though you will see the message every time you run Mathematica.</para> <para>When you register with Wolfram, either by email, phone or fax, - you will give them the <quote>machine ID</quote> and they will respond with a + you will give them the “machine ID” and they will respond with a corresponding password consisting of groups of numbers. You need to add them both along with the machine name and license number in your mathpass file.</para> @@ -33697,7 +33697,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> <variablelist> <varlistentry><term>Biosboot</term> <listitem> - <para>Biosboot is our <quote>bootblocks</quote>. It consists of two + <para>Biosboot is our “bootblocks”. It consists of two files which will be installed in the first 8Kbytes of the floppy or hard-disk slice to be booted from.</para> @@ -33762,7 +33762,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> <para>While this is technically possible, it is not particular useful because of the <acronym>FAT</acronym> filesystem's inability to deal with links, device nodes and other such - <quote>UNIXisms</quote>.</para> + “UNIXisms”.</para> </listitem> </varlistentry> @@ -34008,7 +34008,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> bus control signals -MEMR (Memory Read), -MEMW (Memory Write), -IOR (I/O Read), and -IOW (I/O Write).</para> - <para>The 8237 DMA is known as a <quote>fly-by</quote> DMA controller. This + <para>The 8237 DMA is known as a “fly-by” DMA controller. This means that the data being moved from one location to another does not pass through the DMA chip and is not stored in the DMA chip. Subsequently, the DMA can only transfer data between an I/O port and @@ -34018,7 +34018,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> <note> <para>The 8237 does allow two channels to be connected together to allow memory-to-memory DMA operations in a - non-<quote>fly-by</quote> mode, but nobody in the PC industry uses + non-“fly-by” mode, but nobody in the PC industry uses this scarce resource this way since it is faster to move data between memory locations using the CPU.</para> </note> @@ -34061,7 +34061,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> instruction that must read something from memory that is not in the internal processor cache or pipeline.</para> - <para>Now that the DMA <quote>is in charge</quote>, the DMA activates its + <para>Now that the DMA “is in charge”, the DMA activates its -MEMR, -MEMW, -IOR, -IOW output signals, and the address outputs from the DMA are set to 0x3456, which will be used to direct the byte that is about to transferred to a specific memory @@ -34153,8 +34153,8 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> the upper bits of the address to be read to or written from. Whenever a DMA channel is active, the contents of that latch are written to the address bus and kept there until the DMA operation - for the channel ends. IBM called these latches <quote>Page - Registers</quote>.</para> + for the channel ends. IBM called these latches “Page + Registers”.</para> <para>So for our example above, the DMA would put the 0x3456 part of the address on the bus, and the Page Register for DMA channel 2 @@ -34170,8 +34170,8 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> are probably not intended.</para> <note> - <para><quote>Physical</quote> 64K boundaries should not be - confused with 8086-mode 64K <quote>Segments</quote>, which are + <para>“Physical” 64K boundaries should not be + confused with 8086-mode 64K “Segments”, which are created by mathematically adding a segment register with an offset register. Page Registers have no address overlap and are mathematically OR-ed together.</para> @@ -34196,8 +34196,8 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> peripheral, the data must be first copied from where it resides into a buffer located below 16Meg, and then the DMA can copy the data from the buffer to the hardware. In FreeBSD, these reserved - buffers are called <quote>Bounce Buffers</quote>. In the MS-DOS world, they - are sometimes called <quote>Smart Buffers</quote>.</para> + buffers are called “Bounce Buffers”. In the MS-DOS world, they + are sometimes called “Smart Buffers”.</para> <note> <para>A new implementation of the 8237, called the 82374, allows @@ -34264,7 +34264,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> bus, but then the attached peripheral device is responsible for placing the addressing information on the bus instead of the DMA. This is also used to implement a - technique known as <quote>Bus Mastering</quote>.</para> + technique known as “Bus Mastering”.</para> <para>When a DMA channel in Cascade Mode receives control of the bus, the DMA does not place addresses and I/O control @@ -34317,7 +34317,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> <para>The Dynamic RAM used in all PCs for main memory must be accessed frequently to keep the bits stored in the - components <quote>charged</quote>. Dynamic RAM essentially consists of + components “charged”. Dynamic RAM essentially consists of millions of capacitors with each one holding one bit of data. These capacitors are charged with power to represent a <literal>1</literal> or drained to represent a <literal>0</literal>. Because @@ -34331,7 +34331,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> refresh memory, the contents of memory will become corrupted in just a few milliseconds.</para> - <para>Since memory read and write cycles <quote>count</quote> as + <para>Since memory read and write cycles “count” as refresh cycles (a dynamic RAM refresh cycle is actually an incomplete memory read cycle), as long as the peripheral controller continues reading or writing data to sequential @@ -34359,8 +34359,8 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> operations.</para> <para>This technique is frequently used on audio devices - that have small or no hardware <quote>sample</quote> buffers. There - is additional CPU overhead to manage this <quote>circular</quote> + that have small or no hardware “sample” buffers. There + is additional CPU overhead to manage this “circular” buffer, but in some cases this may be the only way to eliminate the latency that occurs when the DMA counter reaches zero and the DMA stops transfers until it is @@ -34377,7 +34377,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> <title>Programming the DMA</title> <para>The DMA channel that is to be programmed should always be - <quote>masked</quote> before loading any settings. This is because the + “masked” before loading any settings. This is because the hardware might unexpectedly assert the DRQ for that channel, and the DMA might respond, even though not all of the parameters have been loaded or updated.</para> @@ -34398,7 +34398,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> ports.</para> <para>Once all the settings are ready, the DMA channel can be - un-masked. That DMA channel is now considered to be <quote>armed</quote>, + un-masked. That DMA channel is now considered to be “armed”, and will respond when the DRQ line for that channel is asserted.</para> @@ -36819,7 +36819,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> </listitem> <listitem> - <para>Wells, Bill. <quote>Writing Serial Drivers for UNIX</quote>. + <para>Wells, Bill. “Writing Serial Drivers for UNIX”. <emphasis>Dr. Dobb's Journal</emphasis>. 19(15), December 1994. pp68-71, 97-99.</para> </listitem> @@ -36842,8 +36842,8 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> </listitem> <listitem> - <para>Jolitz, William. <quote>Porting UNIX to the - 386</quote>. <emphasis>Dr. + <para>Jolitz, William. “Porting UNIX to the + 386”. <emphasis>Dr. Dobb's Journal</emphasis>. January 1991-July 1992.</para> </listitem> @@ -37071,7 +37071,7 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255</screen> as a means of following the latest developments. Electronic resources are the best, if not often the only, way stay informed of the latest advances. Since FreeBSD is a volunteer effort, the user community - itself also generally serves as a <quote>technical support department</quote> of + itself also generally serves as a “technical support department” of sorts, with electronic mail and USENET news being the most effective way of reaching that community.</para> @@ -37502,7 +37502,7 @@ help <para>Again, we would like to request that you keep discussion in the technical mailing lists on a technical track. - If you are only interested in the <quote>high points</quote> then it is + If you are only interested in the “high points” then it is suggested that you join freebsd-announce, which is intended only for infrequent traffic.</para> @@ -37682,7 +37682,7 @@ help mailing list for users of freebsd-current. It includes warnings about new features coming out in -current that will affect the users, and instructions on steps that must - be taken to remain -current. Anyone running <quote>current</quote> must + be taken to remain -current. Anyone running “current” must subscribe to this list. This is a technical mailing list for which strictly technical content is expected.</para> </listitem> @@ -37713,7 +37713,7 @@ help mailing list for users of freebsd-stable. It includes warnings about new features coming out in -stable that will affect the users, and instructions on steps that must - be taken to remain -stable. Anyone running <quote>stable</quote> + be taken to remain -stable. Anyone running “stable” should subscribe to this list. This is a technical mailing list for which strictly technical content is expected.</para> @@ -37861,9 +37861,9 @@ help <listitem> <para><emphasis>Discussion of - <quote>ports</quote></emphasis></para> + “ports”</emphasis></para> - <para>Discussions concerning FreeBSD's <quote>ports collection</quote> + <para>Discussions concerning FreeBSD's “ports collection” (<filename>/usr/ports</filename>), proposed ports, modifications to ports collection infrastructure and general coordination efforts. This is a technical mailing list for which @@ -37878,7 +37878,7 @@ help <para>This is the mailing list for questions about FreeBSD. You - should not send <quote>how to</quote> questions to the technical lists + should not send “how to” questions to the technical lists unless you consider the question to be pretty technical.</para> </listitem> @@ -38246,8 +38246,8 @@ help <sect1 id="staff-core"> <title>The FreeBSD Core Team</title> - <para>The FreeBSD core team constitutes the project's <quote>Board of - Directors</quote>, responsible for deciding the project's overall goals + <para>The FreeBSD core team constitutes the project's “Board of + Directors”, responsible for deciding the project's overall goals and direction as well as managing <xref linkend="staff-who" remap="specific areas"> of the FreeBSD project landscape.</para> |