From 7cfb0ff20baf4f2ed457c591e5c792962760742e Mon Sep 17 00:00:00 2001 From: Chris Costello Date: Sun, 7 Nov 1999 01:54:56 +0000 Subject: [PATCH] Rid blank lines of whitespace. (Translation teams: You can ignore this commit.) --- .../articles/contributing/article.sgml | 74 ++--- .../kerneldebug/chapter.sgml | 40 +-- .../developers-handbook/policies/chapter.sgml | 38 +-- .../handbook/advanced-networking/chapter.sgml | 44 +-- .../books/handbook/backups/chapter.sgml | 22 +- .../books/handbook/basics/chapter.sgml | 8 +- .../books/handbook/contrib/chapter.sgml | 74 ++--- .../books/handbook/cutting-edge/chapter.sgml | 190 ++++++------- .../books/handbook/eresources/chapter.sgml | 106 +++---- .../books/handbook/hw/chapter.sgml | 262 +++++++++--------- .../books/handbook/install/chapter.sgml | 162 +++++------ .../books/handbook/introduction/chapter.sgml | 44 +-- .../books/handbook/kernelconfig/chapter.sgml | 136 ++++----- .../books/handbook/kerneldebug/chapter.sgml | 40 +-- .../books/handbook/kernelopts/chapter.sgml | 30 +- .../books/handbook/l10n/chapter.sgml | 28 +- .../books/handbook/linuxemu/chapter.sgml | 42 +-- .../books/handbook/mail/chapter.sgml | 8 +- .../books/handbook/mirrors/chapter.sgml | 114 ++++---- .../books/handbook/pgpkeys/chapter.sgml | 4 +- .../books/handbook/policies/chapter.sgml | 38 +-- .../books/handbook/ppp-and-slip/chapter.sgml | 136 ++++----- .../books/handbook/printing/chapter.sgml | 222 +++++++-------- .../books/handbook/security/chapter.sgml | 90 +++--- .../books/handbook/serialcomms/chapter.sgml | 192 ++++++------- .../books/handbook/staff/chapter.sgml | 54 ++-- .../handbook/advanced-networking/chapter.sgml | 44 +-- .../books/handbook/backups/chapter.sgml | 22 +- .../books/handbook/basics/chapter.sgml | 8 +- .../books/handbook/contrib/chapter.sgml | 74 ++--- .../books/handbook/cutting-edge/chapter.sgml | 190 ++++++------- .../books/handbook/eresources/chapter.sgml | 106 +++---- .../books/handbook/hw/chapter.sgml | 262 +++++++++--------- .../books/handbook/install/chapter.sgml | 162 +++++------ .../books/handbook/internals/chapter.sgml | 130 ++++----- .../books/handbook/introduction/chapter.sgml | 44 +-- .../books/handbook/kernelconfig/chapter.sgml | 136 ++++----- .../books/handbook/kerneldebug/chapter.sgml | 40 +-- .../books/handbook/kernelopts/chapter.sgml | 30 +- .../books/handbook/l10n/chapter.sgml | 28 +- .../books/handbook/linuxemu/chapter.sgml | 42 +-- .../books/handbook/mail/chapter.sgml | 8 +- .../books/handbook/mirrors/chapter.sgml | 114 ++++---- .../books/handbook/pgpkeys/chapter.sgml | 4 +- .../books/handbook/policies/chapter.sgml | 38 +-- .../books/handbook/ppp-and-slip/chapter.sgml | 136 ++++----- .../books/handbook/printing/chapter.sgml | 222 +++++++-------- .../books/handbook/quotas/chapter.sgml | 38 +-- .../books/handbook/security/chapter.sgml | 90 +++--- .../books/handbook/serialcomms/chapter.sgml | 192 ++++++------- .../books/handbook/staff/chapter.sgml | 54 ++-- 51 files changed, 2206 insertions(+), 2206 deletions(-) diff --git a/en_US.ISO8859-1/articles/contributing/article.sgml b/en_US.ISO8859-1/articles/contributing/article.sgml index 0dfffb1af5..5e2db53dfa 100644 --- a/en_US.ISO8859-1/articles/contributing/article.sgml +++ b/en_US.ISO8859-1/articles/contributing/article.sgml @@ -1,7 +1,7 @@ @@ -50,7 +50,7 @@ interested in working on one of the tasks you see here, send mail to the coordinator listed by clicking on their names. If no coordinator has been appointed, maybe you would like to volunteer? - + High priority tasks @@ -69,7 +69,7 @@ - + Filesystem problems. Overall coordination: &a.fs; @@ -88,7 +88,7 @@ - + Implement Int13 vm86 disk driver. Coordinator: &a.hackers; @@ -129,11 +129,11 @@ - + Kernel issues. Overall coordination: &a.hackers; - + Add more pro-active security infrastructure. Overall coordination: &a.security; @@ -214,7 +214,7 @@ - + PCMCIA/PCCARD. Coordinators: &a.msmith; and &a.phk; @@ -248,7 +248,7 @@ - + Advanced Power Management. Coordinators: &a.msmith; and &a.phk; @@ -292,17 +292,17 @@ network cards. The same thing for NDIS drivers and NetWare SCSI drivers. - + An "upgrade system" option that works on Linux boxes instead of just previous rev FreeBSD boxes. - + Symmetric Multiprocessing with kernel preemption (requires kernel preemption). - + A concerted effort at support for portable computers. This is somewhat handled by changing PCMCIA bridging rules and power @@ -334,21 +334,21 @@ the latest release from it and report any failures in the process. - + Read the freebsd-bugs mailing list. There might be a problem you can comment constructively on or with patches you can test. Or you could even try to fix one of the problems yourself. - + Read through the FAQ and Handbook periodically. If anything is badly explained, out of date or even just completely wrong, let us know. Even better, send us a fix (SGML is not difficult to learn, but there is no objection to ASCII submissions). - + Help translate FreeBSD documentation into your native language (if not already available) — just send an email to &a.doc; @@ -357,7 +357,7 @@ by doing this — in fact, the documentation most in need of translation is the installation instructions. - + Read the freebsd-questions mailing list and &ng.misc occasionally (or even regularly). It can be very satisfying to @@ -365,19 +365,19 @@ sometimes you may even learn something new yourself! These forums can also be a source of ideas for things to work on. - + If you know of any bugfixes which have been successfully applied to -current but have not been merged into -stable after a decent interval (normally a couple of weeks), send the committer a polite reminder. - + Move contributed software to src/contrib in the source tree. - + Make sure code in src/contrib is up to date. @@ -386,23 +386,23 @@ Look for year 2000 bugs (and fix any you find!) - + Build the source tree (or just part of it) with extra warnings enabled and clean up the warnings. - + Fix warnings for ports which do deprecated things like using gets() or including malloc.h. - + If you have contributed any ports, send your patches back to the original author (this will make your life easier when they bring out the next version) - + Suggest further tasks for this list! @@ -434,7 +434,7 @@ Contributions to the system generally fall into one or more of the following 6 categories: - + Bug reports and general commentary @@ -508,7 +508,7 @@ &prompt.user; diff -c oldfile newfile or - + &prompt.user; diff -c -r olddir newdir would generate such a set of context diffs for the given source file @@ -567,7 +567,7 @@ participation by commercial interests who might eventually be inclined to invest something of their own into FreeBSD. - + The GNU Public License, or “GPL”. This license is not quite as popular with us due to the amount of extra effort @@ -637,7 +637,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. <anchor id="donations">Donating funds - + While the FreeBSD Project is not a 501(c)(3) (charitable) corporation and hence cannot offer special tax incentives for any donations made, any such donations will be gratefully accepted on @@ -660,12 +660,12 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Concord CA, 94520 - + (currently using the Walnut Creek CDROM address until a PO box can be opened) - + Wire transfers may also be sent directly to: - +
Bank Of America Concord Main Office @@ -676,7 +676,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Routing #: 121-000-358 Account #: 01411-07441 (FreeBSD, Inc.)
- + Any correspondence related to donations should be sent to &a.jkh, either via email or to the FreeBSD, Inc. postal address given above. @@ -688,7 +688,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Donating hardware - + Donations of hardware in any of the 3 following categories are also gladly accepted by the FreeBSD Project: @@ -722,7 +722,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Donating Internet access - + We can always use new mirror sites for FTP, WWW or cvsup. If you would like to be such a mirror, please contact the FreeBSD project administrators @@ -783,7 +783,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Direct funding: - + The following individuals and businesses have generously contributed direct funding to the project: @@ -897,11 +897,11 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Hardware contributors: - + The following individuals and businesses have generously contributed hardware for testing and device driver development/support: - + Walnut Creek CDROM for providing the Pentium P5-90 and @@ -968,7 +968,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Special contributors: - + Walnut Creek CDROM @@ -1069,7 +1069,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4.4BSD-Lite release provided by the Computer Science Research Group (CSRG) at the University of California, Berkeley and associated academic contributors. - + There are also portions of NetBSD and OpenBSD that have been integrated into FreeBSD as well, and we would therefore like to thank all the contributors to NetBSD and OpenBSD for their work. diff --git a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml index 1ebf9d9620..ce7b253523 100644 --- a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml +++ b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml @@ -1,7 +1,7 @@ @@ -55,7 +55,7 @@ some programs will drastically increase, and since the whole kernel is loaded entirely at boot time and cannot be swapped out later, several megabytes of physical memory will be wasted. - + If you are testing a new kernel, for example by typing the new kernel's name at the boot prompt, but need to boot a different one in order to get your system up and running again, boot it only into single @@ -186,7 +186,7 @@ line 20: - + This is the location of function trap() in the stack trace. @@ -195,7 +195,7 @@ line 36: - + Force usage of a new stack frame; this is no longer necessary now. The stack frames are supposed to point to the right @@ -210,7 +210,7 @@ line 52: - + The pointer looks suspicious, but happens to be a valid address. @@ -219,7 +219,7 @@ line 56: - + However, it obviously points to garbage, so we have found our error! (For those unfamiliar with that particular piece of code: @@ -251,7 +251,7 @@ What do you do if a kernel dumped core but you did not expect it, and it is therefore not compiled using config -g? Not everything is lost here. Do not panic! - + Of course, you still need to enable crash dumps. See above on the options you have to specify in order to do this. @@ -271,14 +271,14 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols - + Go and examine the dump as described above. The debugging symbols might be incomplete for some places, as can be seen in the stack trace in the example above where some functions are displayed without line numbers and argument lists. If you need more debugging symbols, remove the appropriate object files and repeat the kgdb session until you know enough. - + All this is not guaranteed to work, but it will do it fine in most cases. @@ -290,14 +290,14 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols - + If you need to do low-level debugging on your kernel, there is an on-line debugger available called DDB. It allows to setting breakpoints, single-stepping kernel functions, examining and changing kernel variables, etc. However, it cannot access kernel source files, and only has access to the global and static symbols, not to the full debug information like kgdb. - + To configure your kernel to include DDB, add the option line @@ -318,7 +318,7 @@ options DDB right at the boot prompt. The kernel will start up in debug mode and enter DDB prior to any device probing. Hence you can even debug the device probe/attach functions. - + The second scenario is a hot-key on the keyboard, usually Ctrl-Alt-ESC. For syscons, this can be remapped; some of the distributed maps do this, so watch out. There is an option available @@ -327,11 +327,11 @@ options DDB in the kernel config file). It is not the default since there are a lot of crappy serial adapters around that gratuitously generate a BREAK condition, for example when pulling the cable. - + The third way is that any panic condition will branch to DDB if the kernel is configured to use it. For this reason, it is not wise to configure a kernel with DDB for a machine running unattended. - + The DDB commands roughly resemble some gdb commands. The first thing you probably need to do is to set a breakpoint: @@ -344,7 +344,7 @@ options DDB a-f need to be preceded with 0x (this is optional for other numbers). Simple expressions are allowed, for example: function-name + 0x103. - + To continue the operation of an interrupted kernel, simply type: @@ -419,11 +419,11 @@ options DDB specifies the size of the data to be written, the first following expression is the address to write to and the remainder is interpreted as data to write to successive memory locations. - + If you need to know the current registers, use: show reg - + Alternatively, you can display a single register value by e.g. p $eax @@ -468,7 +468,7 @@ options DDB is the final way out of disaster and almost the same as hitting the Big Red Button. - + If you need a short command summary, simply type: help @@ -493,7 +493,7 @@ options DDB with all the symbols in it, and the other one is the target machine that simply runs a similar copy of the very same kernel (but stripped of the debugging information). - + You should configure the kernel in question with config -g, include into the configuration, and compile it as usual. This gives a large blurb of a binary, due to the @@ -573,7 +573,7 @@ text_addr = 0xf5109020? (y or n) y Debugging a Console Driver - + Since you need a console driver to run DDB on, things are more complicated if the console driver itself is failing. You might remember the use of a serial console (either with modified boot blocks, or by diff --git a/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml index a161306857..084c8f7c50 100644 --- a/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml +++ b/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml @@ -1,7 +1,7 @@ @@ -20,27 +20,27 @@ If a particular portion of the FreeBSD distribution is being maintained by a person or group of persons, they can communicate this fact to the world by adding a - + MAINTAINER= email-addresses - + line to the Makefiles covering this portion of the source tree. - + The semantics of this are as follows: The maintainer owns and is responsible for that code. This means that he is responsible for fixing bugs and answer problem reports pertaining to that piece of the code, and in the case of contributed software, for tracking new versions, as appropriate. - + Changes to directories which have a maintainer defined shall be sent to the maintainer for review before being committed. Only if the maintainer does not respond for an unacceptable period of time, to several emails, will it be acceptable to commit changes without review by the maintainer. However, it is suggested that you try and have the changes reviewed by someone else if at all possible. - + It is of course not acceptable to add a person or group as maintainer unless they agree to assume this duty. On the other hand it doesn't have to be a committer and it can easily be a group of @@ -58,11 +58,11 @@ MAINTAINER= email-addresses actively being maintained outside the FreeBSD project. For historical reasons, we call this contributed software. Some examples are perl, gcc and patch. - + Over the last couple of years, various methods have been used in dealing with this type of software and all have some number of advantages and drawbacks. No clear winner has emerged. - + Since this is the case, after some debate one of these methods has been selected as the “official” method and will be required for future imports of software of this kind. Furthermore, it is @@ -72,7 +72,7 @@ MAINTAINER= email-addresses “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. - + Ultimately, however, it comes down to the people actually doing the work. If using this model is particularly unsuited to the package being dealt with, exceptions to these rules may be granted only with the @@ -93,28 +93,28 @@ MAINTAINER= email-addresses The Tcl embedded programming language will be used as example of how this model works: - + src/contrib/tcl contains the source as distributed by the maintainers of this package. Parts that are entirely not applicable for FreeBSD can be removed. In the case of Tcl, the mac, win and compat subdirectories were eliminated before the import - + src/lib/libtcl contains only a "bmake style" Makefile that uses the standard bsd.lib.mk makefile rules to produce the library and install the documentation. - + src/usr.bin/tclsh contains only a bmake style Makefile which will produce and install the tclsh program and its associated man-pages using the standard bsd.prog.mk rules. - + src/tools/tools/tcl_bmake contains a couple of shell-scripts that can be of help when the tcl software needs updating. These are not part of the built or installed software. - + The important thing here is that the src/contrib/tcl directory is created according to the rules: It is supposed to contain the sources as distributed (on a @@ -133,7 +133,7 @@ MAINTAINER= email-addresses be patched into the FreeBSD checked out version and "committed", as this destroys the vendor branch coherency and makes importing future versions rather difficult as there will be conflicts. - + Since many packages contain files that are meant for compatibility with other architectures and environments that FreeBSD, it is permissible to remove parts of the distribution tree that are of no @@ -148,7 +148,7 @@ MAINTAINER= email-addresses check in such utilities (as necessary) in the src/tools directory along with the port itself so that it is available to future maintainers. - + In the src/contrib/tcl level directory, a file called FREEBSD-upgrade should be added and it should states things like: @@ -177,7 +177,7 @@ MAINTAINER= email-addresses with the contributed source. Rather you should cvs add FREEBSD-upgrade ; cvs ci after the initial import. Example wording from src/contrib/cpio is below: - + This directory contains virgin sources of the original distribution files on a "vendor" branch. Do not, under any circumstances, attempt to upgrade @@ -316,12 +316,12 @@ obrien@FreeBSD.org - 30 March 1997 Contributed by &a.asami;, &a.peter;, and &a.obrien; 9 December 1996. - + If you are adding shared library support to a port or other piece of software that doesn't have one, the version numbers should follow these rules. Generally, the resulting numbers will have nothing to do with the release version of the software. - + The three principles of shared library building are: diff --git a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml index 877739cdb0..31568a1eb7 100644 --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml @@ -1,7 +1,7 @@ @@ -12,7 +12,7 @@ Contributed by &a.gryphon;. 6 October 1995. - + 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 “route” is a defined pair of addresses: a @@ -25,7 +25,7 @@ We will talk a little bit more about default routes later on. There are also three types of gateways: individual hosts, interfaces (also called “links”), and ethernet hardware addresses. - + An example @@ -325,7 +325,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) can lead to serious network problems, particularly with NFS. This difficulty is not specific to FreeBSD, but FreeBSD systems are affected by it. - + The problem nearly always occurs when (FreeBSD) PC systems are networked with high-performance workstations, such as those made by Silicon Graphics, Inc., and Sun Microsystems, Inc. The NFS mount will @@ -336,7 +336,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) many systems, there is no way to shut down the client gracefully once this problem has manifested itself. The only solution is often to reset the client, because the NFS situation cannot be resolved. - + 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 @@ -347,13 +347,13 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) specified using the fourth field of the fstab entry on the client for automatic mounts, or by using the parameter of the mount command for manual mounts. - + It should be noted that there is a different problem, sometimes mistaken for this one, when the NFS servers and clients are on different networks. If that is the case, make certain that your routers are routing the necessary UDP information, or you will not get anywhere, no matter what else you are doing. - + In the following examples, fastws is the host (interface) name of a high-performance workstation, and freebox is the host (interface) name of a FreeBSD @@ -364,7 +364,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) cases, note that additional options, such as or and may be desirable in your application. - + Examples for the FreeBSD system (freebox) as the client: in /etc/fstab on freebox: @@ -387,7 +387,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0 Nearly any 16-bit Ethernet adapter will allow operation without the above restrictions on the read or write size. - + For anyone who cares, here is what happens when the failure occurs, which also explains why it is unrecoverable. NFS typically works with a “block” size of 8k (though it may do fragments of smaller @@ -407,7 +407,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0 By keeping the unit size below the Ethernet packet size limitation, we ensure that any complete Ethernet packet received can be acknowledged individually, avoiding the deadlock situation. - + 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 “units”. When an overrun @@ -425,7 +425,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0 allow you to boot your FreeBSD machine over the network and run FreeBSD without having a disk on your client. Under 2.0 it is now possible to have local swap. Swapping over NFS is also still supported. - + Supported Ethernet cards include: Western Digital/SMC 8003, 8013, 8216 and compatibles; NE1000/NE2000 and compatibles (requires recompile) @@ -451,7 +451,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0 - + Set up a bootp server to provide the client with IP, gateway, netmask. @@ -467,7 +467,7 @@ diskless:\ :gw=192.1.2.5:\ :vm=rfc1048: - + Set up a TFTP server (on same machine as bootp server) to provide booting information to client. The name of this file is @@ -572,7 +572,7 @@ hostname myclient.mydomain rootfs 192.1.2.3:/rootfs/myclient hostname myclient.mydomain - + Ensure that your NFS server has exported the root (and swap if applicable) filesystems to your client, and that the client has @@ -610,7 +610,7 @@ hostname myclient.mydomain &prompt.root; chmod 0600 /swapfs/swap.192.1.2.4 - + Unpack the root filesystem in the directory the client will use for its root filesystem (/rootfs/myclient @@ -634,7 +634,7 @@ hostname myclient.mydomain - + Run netboot.com on the client or make an EPROM from the netboot.rom file @@ -671,7 +671,7 @@ hostname myclient.mydomain A good resource for information on ISDN technology and hardware is Dan Kegel's ISDN Page. - + A quick simple roadmap to ISDN follows: @@ -734,7 +734,7 @@ hostname myclient.mydomain In case you are interested in adding support for a different ISDN protocol, a currently unsupported ISDN PC card or otherwise enhancing isdn4bsd, please get in touch with hm@kts.org. - + A majordomo maintained mailing list is available. To join the list, send mail to majordomo@FreeBSD.org and specify: @@ -782,7 +782,7 @@ subscribe freebsd-isdn Motorola BitSurfer and Bitsurfer Pro - + Adtran @@ -857,7 +857,7 @@ subscribe freebsd-isdn Branch office or Home network - + Network is 10 Base T Ethernet. Connect router to network cable with AUI/10BT transceiver, if necessary. @@ -880,9 +880,9 @@ ISDN BRI line Head office or other lan - + Network is Twisted Pair Ethernet. - + -------Novell Server diff --git a/en_US.ISO8859-1/books/handbook/backups/chapter.sgml b/en_US.ISO8859-1/books/handbook/backups/chapter.sgml index 6a805f7ec4..4bc1417737 100644 --- a/en_US.ISO8859-1/books/handbook/backups/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/backups/chapter.sgml @@ -1,7 +1,7 @@ @@ -337,7 +337,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready 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! - + If your time and your data is worth little to nothing, then “Do nothing” is the most suitable backup program for your computer. But beware, Unix is a useful tool, you may find that within @@ -377,7 +377,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready Before the Disaster - + There are only four steps that you need to perform in preparation for any disaster that may occur. @@ -581,14 +581,14 @@ echo "The floppy has been unmounted and is now ready."]]> After the Disaster - + The key question is: did your hardware survive? You have been doing regular backups so there is no need to worry about the software. - + If the hardware has been damaged. First, replace those parts that have been damaged. - + If your hardware is okay, check your floppies. If you are using a custom boot floppy, boot single-user (type -s at the boot: prompt). Skip the following @@ -605,7 +605,7 @@ echo "The floppy has been unmounted and is now ready."]]> located in /mnt2/stand. Recover each filesystem separately. - + Try to &man.mount.8; (e.g. mount /dev/da0a /mnt) the root partition of your first disk. If the disklabel was damaged, use &man.disklabel.8; to re-partition and @@ -617,7 +617,7 @@ echo "The floppy has been unmounted and is now ready."]]> /dev/sa0). Unmount the filesystem (e.g. umount /mnt) Repeat for each filesystem that was damaged. - + Once your system is running, backup your data onto new tapes. Whatever caused the crash or data loss may strike again. An another hour spent now, may save you from further distress later. @@ -625,7 +625,7 @@ echo "The floppy has been unmounted and is now ready."]]> * I did not prepare for the Disaster, What Now? - + @@ -645,11 +645,11 @@ echo "The floppy has been unmounted and is now ready."]]> The media is unreliable, especially over long periods of time - + Backing up and restoring is very slow - + They have a very limited capacity (the days of backing up an entire hard disk onto a dozen or so floppies has long since diff --git a/en_US.ISO8859-1/books/handbook/basics/chapter.sgml b/en_US.ISO8859-1/books/handbook/basics/chapter.sgml index e5fa0fe5da..391c3542d3 100644 --- a/en_US.ISO8859-1/books/handbook/basics/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/basics/chapter.sgml @@ -1,7 +1,7 @@ @@ -79,7 +79,7 @@ documentation, so &man.chmod.1; refers to the chmod user command and &man.chmod.2; refers to the system call. - + This is fine if you know the name of the command and simply wish to know how to use it, but what if you cannot recall the command name? You can use man to search for keywords in the command @@ -92,7 +92,7 @@ have the keyword “mail” in their descriptions. This is actually functionally equivalent to using the apropos command. - + So, you are looking at all those fancy commands in /usr/bin but do not even have the faintest idea what most of them actually do? Simply do a @@ -116,7 +116,7 @@ info command or, if you installed emacs, the info mode of emacs. - + To use the &man.info.1; command, simply type: &prompt.user; info diff --git a/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml b/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml index 0dfffb1af5..5e2db53dfa 100644 --- a/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml @@ -1,7 +1,7 @@ @@ -50,7 +50,7 @@ interested in working on one of the tasks you see here, send mail to the coordinator listed by clicking on their names. If no coordinator has been appointed, maybe you would like to volunteer? - + High priority tasks @@ -69,7 +69,7 @@ - + Filesystem problems. Overall coordination: &a.fs; @@ -88,7 +88,7 @@ - + Implement Int13 vm86 disk driver. Coordinator: &a.hackers; @@ -129,11 +129,11 @@ - + Kernel issues. Overall coordination: &a.hackers; - + Add more pro-active security infrastructure. Overall coordination: &a.security; @@ -214,7 +214,7 @@ - + PCMCIA/PCCARD. Coordinators: &a.msmith; and &a.phk; @@ -248,7 +248,7 @@ - + Advanced Power Management. Coordinators: &a.msmith; and &a.phk; @@ -292,17 +292,17 @@ network cards. The same thing for NDIS drivers and NetWare SCSI drivers. - + An "upgrade system" option that works on Linux boxes instead of just previous rev FreeBSD boxes. - + Symmetric Multiprocessing with kernel preemption (requires kernel preemption). - + A concerted effort at support for portable computers. This is somewhat handled by changing PCMCIA bridging rules and power @@ -334,21 +334,21 @@ the latest release from it and report any failures in the process. - + Read the freebsd-bugs mailing list. There might be a problem you can comment constructively on or with patches you can test. Or you could even try to fix one of the problems yourself. - + Read through the FAQ and Handbook periodically. If anything is badly explained, out of date or even just completely wrong, let us know. Even better, send us a fix (SGML is not difficult to learn, but there is no objection to ASCII submissions). - + Help translate FreeBSD documentation into your native language (if not already available) — just send an email to &a.doc; @@ -357,7 +357,7 @@ by doing this — in fact, the documentation most in need of translation is the installation instructions. - + Read the freebsd-questions mailing list and &ng.misc occasionally (or even regularly). It can be very satisfying to @@ -365,19 +365,19 @@ sometimes you may even learn something new yourself! These forums can also be a source of ideas for things to work on. - + If you know of any bugfixes which have been successfully applied to -current but have not been merged into -stable after a decent interval (normally a couple of weeks), send the committer a polite reminder. - + Move contributed software to src/contrib in the source tree. - + Make sure code in src/contrib is up to date. @@ -386,23 +386,23 @@ Look for year 2000 bugs (and fix any you find!) - + Build the source tree (or just part of it) with extra warnings enabled and clean up the warnings. - + Fix warnings for ports which do deprecated things like using gets() or including malloc.h. - + If you have contributed any ports, send your patches back to the original author (this will make your life easier when they bring out the next version) - + Suggest further tasks for this list! @@ -434,7 +434,7 @@ Contributions to the system generally fall into one or more of the following 6 categories: - + Bug reports and general commentary @@ -508,7 +508,7 @@ &prompt.user; diff -c oldfile newfile or - + &prompt.user; diff -c -r olddir newdir would generate such a set of context diffs for the given source file @@ -567,7 +567,7 @@ participation by commercial interests who might eventually be inclined to invest something of their own into FreeBSD. - + The GNU Public License, or “GPL”. This license is not quite as popular with us due to the amount of extra effort @@ -637,7 +637,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. <anchor id="donations">Donating funds - + While the FreeBSD Project is not a 501(c)(3) (charitable) corporation and hence cannot offer special tax incentives for any donations made, any such donations will be gratefully accepted on @@ -660,12 +660,12 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Concord CA, 94520 - + (currently using the Walnut Creek CDROM address until a PO box can be opened) - + Wire transfers may also be sent directly to: - +
Bank Of America Concord Main Office @@ -676,7 +676,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Routing #: 121-000-358 Account #: 01411-07441 (FreeBSD, Inc.)
- + Any correspondence related to donations should be sent to &a.jkh, either via email or to the FreeBSD, Inc. postal address given above. @@ -688,7 +688,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Donating hardware - + Donations of hardware in any of the 3 following categories are also gladly accepted by the FreeBSD Project: @@ -722,7 +722,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Donating Internet access - + We can always use new mirror sites for FTP, WWW or cvsup. If you would like to be such a mirror, please contact the FreeBSD project administrators @@ -783,7 +783,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Direct funding: - + The following individuals and businesses have generously contributed direct funding to the project: @@ -897,11 +897,11 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Hardware contributors: - + The following individuals and businesses have generously contributed hardware for testing and device driver development/support: - + Walnut Creek CDROM for providing the Pentium P5-90 and @@ -968,7 +968,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Special contributors: - + Walnut Creek CDROM @@ -1069,7 +1069,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4.4BSD-Lite release provided by the Computer Science Research Group (CSRG) at the University of California, Berkeley and associated academic contributors. - + There are also portions of NetBSD and OpenBSD that have been integrated into FreeBSD as well, and we would therefore like to thank all the contributors to NetBSD and OpenBSD for their work. diff --git a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml index 0034e018d9..06227ff201 100644 --- a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml @@ -1,7 +1,7 @@ @@ -46,7 +46,7 @@ part of the source tree and for whom keeping “current” is an absolute requirement. - + Members of the FreeBSD group who are active testers, willing to spend time working through problems in order to ensure that @@ -54,7 +54,7 @@ who wish to make topical suggestions on changes and the general direction of FreeBSD. - + Peripheral members of the FreeBSD (or some other) group who merely wish to keep an eye on things and use the current sources @@ -74,11 +74,11 @@ there is some cool new feature in there and you want to be the first on your block to have it. - + A quick way of getting bug fixes. - + In any way “officially supported” by us. We do our best to help people genuinely in one of the 3 @@ -125,7 +125,7 @@ subscribe cvs-all how to subscribe and unsubscribe to the various other mailing lists we support. - + Grab the sources from ftp.FreeBSD.org. You can do this in three @@ -174,7 +174,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + Essentially, if you need rapid on-demand access to the source and communications bandwidth is not a consideration, use @@ -249,7 +249,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzUsing FreeBSD-stable - + Join the &a.stable;. This will keep you informed of build-dependencies that may appear in stable @@ -274,7 +274,7 @@ subscribe cvs-all how to subscribe and unsubscribe to the various other mailing lists we support. - + If you are installing a new system and want it to be as stable as possible, you can simply grab the latest dated branch snapshot @@ -331,14 +331,14 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + Essentially, if you need rapid on-demand access to the source and communications bandwidth is not a consideration, use cvsup or ftp. Otherwise, use CTM. - + Before compiling stable, read the Makefile in /usr/src carefully. You should at least run @@ -356,14 +356,14 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzSynchronizing Source Trees over the Internet Contributed by &a.jkh;. - + There are various ways of using an Internet (or email) connection to stay up-to-date with any given area of the FreeBSD project sources, or all areas, depending on what interests you. The primary services we offer are Anonymous CVS, CVSup, and CTM. - + Anonymous CVS and CVSup use the pull model of updating sources. In the case of CVSup @@ -380,7 +380,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzCVSup can do this far more efficiently, but Anonymous CVS is easier to use. - + CTM, on the other hand, does not interactively compare the sources you have with those on the master archive or otherwise pull them across.. Instead, a script which @@ -404,7 +404,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + For more information on Anonymous CVS, CTM, and CVSup, please see one of the following sections: @@ -416,7 +416,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz <anchor id="anoncvs-intro">Introduction - + Anonymous CVS (or, as it is otherwise known, anoncvs) is a feature provided by the CVS utilities bundled with FreeBSD for synchronizing with a remote CVS @@ -454,7 +454,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz <anchor id="anoncvs-usage">Using Anonymous CVS - + Configuring &man.cvs.1; to use an Anonymous CVS repository is a simple matter of setting the CVSROOT environment variable to point to one of the FreeBSD project's @@ -467,7 +467,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + Since CVS allows one to “check out” virtually any version of the FreeBSD sources that ever existed (or, in some cases, will exist :), you need to be familiar with the @@ -481,7 +481,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + Here are the branch tags that users might be interested in: @@ -523,10 +523,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + Here are the revision tags that users might be interested in: - + RELENG_3_3_0_RELEASE @@ -659,7 +659,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + When you specify a branch tag, you normally receive the latest versions of the files on that line of development. If you wish to receive some past version, you can do so by specifying a date with @@ -669,7 +669,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Examples - + While it really is recommended that you read the manual page for &man.cvs.1; thoroughly before doing anything, here are some quick examples which essentially show how to use Anonymous @@ -684,7 +684,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzcvs co ls &prompt.user; cvs release -d ls - + Checking out the version of ls(1) in the 2.2-stable branch: @@ -694,7 +694,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzcvs co -rRELENG_2_2 ls &prompt.user; cvs release -d ls - + Creating a list of changes (as unidiffs) to &man.ls.1; @@ -716,10 +716,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Other Resources - + The following additional resources may be helpful in learning CVS: - + Why should I use <application>CTM</application>? - + CTM will give you a local copy of the FreeBSD source trees. There are a number of “flavors” of the tree available. Whether you wish to track the entire cvs @@ -781,7 +781,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz What do I need to use <application>CTM</application>? - + You will need two things: The CTM program and the initial deltas to feed it (to get up to “current” levels). @@ -807,7 +807,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/ or see section mirrors. - + FTP the relevant directory and fetch the README file, starting from there. @@ -880,9 +880,9 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Using <application>CTM</application> in your daily life - + To apply the deltas, simply say: - + &prompt.root; cd /where/ever/you/want/the/stuff &prompt.root; ctm -v -v /where/you/store/your/deltas/src-xxx.* @@ -918,7 +918,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Keeping your local changes - + As a developer one would like to experiment with and change files in the source tree. CTM supports local modifications in a limited way: before checking for the @@ -935,7 +935,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Other interesting <application>CTM</application> options - + Finding out exactly what would be touched by an update @@ -949,7 +949,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz:-). - + Making backups before updating @@ -961,7 +961,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzCTM delta to backup-file. - + Restricting the files touched by an update @@ -993,9 +993,9 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Future plans for <application>CTM</application> - + Tons of them: - + Use some kind of authentication into the CTM system, so as @@ -1007,7 +1007,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + The bad news is that I am very busy, so any help in doing this will be most welcome. And do not forget to tell me what you want also... @@ -1015,7 +1015,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Miscellaneous stuff - + All the “DES infected” (e.g. export controlled) source is not included. You will get the “international” version only. If sufficient interest @@ -1028,7 +1028,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Thanks! - + &a.bde; @@ -1081,7 +1081,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Introduction - + CVSup is a software package for distributing and updating source trees from a master CVS repository on a remote server host. The FreeBSD sources are maintained in a @@ -1119,7 +1119,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Installation - + The easiest way to install CVSup if you are running FreeBSD 2.2 or later is to use either the @@ -1178,16 +1178,16 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupd-bin-16.0.tar.gz (server). - + as well as from the many FreeBSD FTP mirror sites around the world. - + Most users will need only the client. These executables are entirely self-contained, and they will run on any version of FreeBSD from FreeBSD-2.1.0 to FreeBSD-current. In summary, your options for installing CVSup are: - + FreeBSD-2.2 or later: static binary, port, or @@ -1206,7 +1206,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz CVSup Configuration - + CVSup's operation is controlled by a configuration file called the supfile. Beginning with FreeBSD-2.2, there are some sample @@ -1214,7 +1214,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz/usr/share/examples/cvsup/. These examples are also available from ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/ if you are on a pre-2.2 system. - + The information in a supfile answers the following questions for cvsup: @@ -1244,7 +1244,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + In the following sections, we will construct a typical supfile by answering each of these questions in turn. First, we describe the overall structure of a @@ -1290,7 +1290,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzsupfile for receiving and updating the main source tree of FreeBSD-current. - + Which files do you want to receive? Running <application>CVSup</application> - + You are now ready to try an update. The command line for doing this is quite simple: @@ -1716,7 +1716,7 @@ cvs-crypto trial run without touching your precious files. Just create an empty directory somewhere convenient, and name it as an extra argument on the command line: - + &prompt.root; mkdir /var/tmp/dest &prompt.root; cvsup supfile /var/tmp/dest @@ -1750,7 +1750,7 @@ cvs-crypto There are plenty of other options available. For a brief list of them, type cvsup -H. For more detailed descriptions, see the manual page. - + Once you are satisfied with the way updates are working, you can arrange for regular runs of cvsup using &man.cron.8;. Obviously, you should not let cvsup use its GUI when running it from @@ -1773,7 +1773,7 @@ cvs-crypto ports-all. The other collections are used only by small groups of people for specialized purposes, and some mirror sites may not carry all of them. - + cvs-all release=cvs @@ -2459,7 +2459,7 @@ cvs-crypto For more information - + For the CVSup FAQ and other information about CVSup, see The CVSup Home Page. @@ -2477,14 +2477,14 @@ cvs-crypto Using <command>make world</command> to rebuild your system - + Contributed by &a.nik;. - + Once you have synchronised your local source tree against a particular version of FreeBSD (stable, current and so on) you must then use the source tree to rebuild the system. - + Take a backup @@ -2539,7 +2539,7 @@ cvs-crypto If your machine has a floating point unit (386DX, 486DX, Pentium and up class machines) then you can also uncomment the HAVE_FPU line.</para> @@ -2587,9 +2587,9 @@ cvs-crypto</programlisting> <para>If you are feeling particularly paranoid, you can check your system to see which files are owned by the group you are renaming or deleting.</para> - + <screen>&prompt.root; <userinput>find / -group <replaceable>GID</replaceable> -print</userinput></screen> - + <para>will show all files owned by group <replaceable>GID</replaceable> (which can be either a group name or a numeric group ID).</para> </tip> @@ -2609,7 +2609,7 @@ cvs-crypto</programlisting> <note> <title>Version 2.2.5 and above - + As described in more detail below, versions 2.2.5 and above of FreeBSD have separated the building process from the installing process. You can therefore build the new @@ -2618,9 +2618,9 @@ cvs-crypto As the superuser, you can execute - + &prompt.root; - + from a running system, which will drop it to single user mode. Alternatively, reboot the system, and at the boot prompt, enter @@ -2662,9 +2662,9 @@ cvs-crypto All versions - + You must be in the /usr/src directory, so - + &prompt.root; cd /usr/src (unless, of course, your source code is elsewhere, in which case @@ -2674,7 +2674,7 @@ cvs-crypto command reads instructions from the Makefile which describes how the programs that comprise FreeBSD should be rebuilt, the order they should be built in, and so on. - + The general format of the command line you will type is as follows; @@ -2695,7 +2695,7 @@ cvs-crypto is another way of specifying that profiled libaries should not be built, and corresponds with the - + NOPROFILE= true # Avoid compiling profiled libraries @@ -2719,7 +2719,7 @@ cvs-crypto Saving the output - + It's a good idea to save the output you get from running &man.make.1; to another file. If something goes wrong you will have a copy of the error message, and a complete list of where the @@ -2749,11 +2749,11 @@ Script done, … Version 2.2.2 and below - + /usr/src/Makefile contains the world target, which will rebuild the entire system and then install it. - + Use it like this. &prompt.root; make world @@ -2761,7 +2761,7 @@ Script done, … Version 2.2.5 and above - + Beginning with version 2.2.5 of FreeBSD (actually, it was first created on the -current branch, and then retrofitted to -stable midway between 2.2.2 and 2.2.5) the world @@ -2817,7 +2817,7 @@ Script done, … -current and above - + If you are tracking -current you can also pass the option to make. This lets make spawn several simultaneous processes. @@ -2837,7 +2837,7 @@ Script done, … If you have a multi-CPU machine and you are using an SMP configured kernel try values between 6 and 10 and see how they speed things up. - + Be aware that (at the time of writing) this is still experimental, and commits to the source tree may occasionally break this feature. If the world fails to compile using this parameter @@ -2849,7 +2849,7 @@ Script done, … Assuming everything goes well you have anywhere between an hour and a half and a day or so to wait. - + As a general rule of thumb, a 200MHz P6 with more than 32MB of RAM and reasonable SCSI disks will complete make world in about an hour and a half. A 32MB P133 will @@ -2881,14 +2881,14 @@ Script done, … Backup your existing <filename>/etc</filename> - + Although, in theory, nothing is going to touch this directory automatically, it is always better to be sure. So copy your existing /etc directory somewhere safe. Something like: - + &prompt.root; cp -Rp /etc /etc.old - + does a recursive copy, preserves times, ownerships on files and suchlike. @@ -2898,11 +2898,11 @@ Script done, … put this dummy directory in /var/tmp/root, and there are a number of subdirectories required under this as well. - + &prompt.root; mkdir /var/tmp/root &prompt.root; cd /usr/src/etc &prompt.root; make DESTDIR=/var/tmp/root distrib-dirs distribution - + This will build the necessary directory structure and install the files. A lot of the subdirectories that have been created under /var/tmp/root are empty and should be deleted. @@ -2945,15 +2945,15 @@ Script done, … Name the new root directory (<filename>/var/tmp/root</filename>)with a timestamp, so you can easily compare differences between versions - + Frequently remaking the world means that you have to update /etc frequently as well, which can be a bit of a chore. - + You can speed this process up by keeping a copy of the last set of changed files that you merged into /etc. The following procedure gives one idea of how to do this. - + Make the world as normal. When you want to update @@ -3013,7 +3013,7 @@ Script done, … to /etc. - + You can use &man.date.1; to automate the generation of the directory names. @@ -3026,7 +3026,7 @@ Script done, … DEVFS - + If you are using DEVFS then this is probably unnecessary. @@ -3036,7 +3036,7 @@ Script done, … Copy /var/tmp/root/dev/MAKEDEV to /dev. - + &prompt.root; cp /var/tmp/root/dev/MAKEDEV /dev @@ -3097,7 +3097,7 @@ Script done, … Source older than 2 April 1998 - + If your source code is older than 2nd April 1998, or the Makefile version is not 1.68 or higher (for FreeBSD current and 3.x systems) or 1.48.2.21 or higher (for 2.2.x @@ -3545,27 +3545,27 @@ Antonio Sue Blake, sue@welearn.com.au - + Brian Haskin, haskin@ptway.com - + Kees Jan Koster, kjk1@ukc.ac.uk - + A Joseph Kosy, koshy@india.hp.com - + Greg Lehey, grog@lemis.com - + Wes Peters, softweyr@xmission.com - + Joseph Stein, joes@wstein.com @@ -3573,12 +3573,12 @@ Antonio Studded, studded@dal.net - + Axel Thimm, Axel.Thimm@physik.fu-berlin.de - + Matthew Thyer, Matthew.Thyer@dsto.defence.gov.au diff --git a/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml b/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml index 50a8ab7dbc..fc9c7c3bc1 100644 --- a/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml @@ -1,7 +1,7 @@ @@ -32,7 +32,7 @@ questions to the appropriate mailing list you will reach both us and a concentrated FreeBSD audience, invariably assuring a better (or at least faster) response. - + The charters for the various lists are given at the bottom of this document. Please read the charter before joining or sending mail to any list. Most of our list subscribers now receive @@ -41,7 +41,7 @@ signal-to-noise ratio of the lists high. To do less would see the mailing lists ultimately fail as an effective communications medium for the project. - + Archives are kept for all of the mailing lists and can be searched using the FreeBSD World Wide Web server. The keyword searchable archive offers an @@ -354,7 +354,7 @@ be redistributed to mailing list members world-wide. To subscribe to a list, send mail to &a.majordomo; and include - + subscribe <listname> [<optional address>] @@ -416,7 +416,7 @@ help freebsd-chat@FreeBSD.org mailing list is freely available and should be used instead. - + No posting should be made to more than 2 mailing lists, and only to 2 when a clear and obvious need to post to both lists @@ -442,7 +442,7 @@ help therefore probably rate a warning (or ban) on that basis alone. - + Advertising of non-FreeBSD related products or services is strictly prohibited and will result in an immediate ban if it is @@ -463,7 +463,7 @@ help CMU/Transarc - + FREEBSD-ANNOUNCE @@ -478,7 +478,7 @@ help moderated mailing list. - + FREEBSD-ARCH @@ -521,7 +521,7 @@ help discussion has been resolved. - + FREEBSD-BUGS @@ -536,7 +536,7 @@ help interface to it. - + FREEBSD-CHAT @@ -555,7 +555,7 @@ help this -chat list. - + FREEBSD-CORE @@ -568,7 +568,7 @@ help scrutiny. - + FREEBSD-CURRENT @@ -584,7 +584,7 @@ help for which strictly technical content is expected. - + FREEBSD-CURRENT-DIGEST @@ -600,7 +600,7 @@ help to. - + FREEBSD-DOC @@ -614,7 +614,7 @@ help list; feel free to join and contribute! - + FREEBSD-FS @@ -639,7 +639,7 @@ help expected. - + FREEBSD-ISDN @@ -650,7 +650,7 @@ help development of ISDN support for FreeBSD. - + FREEBSD-JAVA @@ -662,7 +662,7 @@ help porting and maintenance of JDKs. - + FREEBSD-HACKERS @@ -678,7 +678,7 @@ help expected. - + FREEBSD-HACKERS-DIGEST @@ -717,7 +717,7 @@ help mirror sites. - + FREEBSD-INSTALL @@ -728,7 +728,7 @@ help development for the future releases. - + FREEBSD-ISP @@ -742,7 +742,7 @@ help expected. - + FREEBSD-NEWBIES @@ -761,7 +761,7 @@ help newbies. - + FREEBSD-PLATFORMS @@ -785,7 +785,7 @@ help Core Team Policy decisions. - + FREEBSD-PORTS @@ -800,7 +800,7 @@ help for which strictly technical content is expected. - + FREEBSD-QUESTIONS @@ -813,7 +813,7 @@ help technical. - + FREEBSD-QUESTIONS-DIGEST @@ -826,7 +826,7 @@ help message. The average digest size is about 40kB. - + FREEBSD-SCSI @@ -838,7 +838,7 @@ help which strictly technical content is expected. - + FREEBSD-SECURITY @@ -850,7 +850,7 @@ help list for which strictly technical content is expected. - + FREEBSD-SECURITY-NOTIFICATIONS @@ -861,7 +861,7 @@ help FreeBSD-security. - + FREEBSD-SMALL @@ -871,7 +871,7 @@ help list for which strictly technical content is expected. - + FREEBSD-STABLE @@ -887,7 +887,7 @@ help for which strictly technical content is expected. - + FREEBSD-USER-GROUPS @@ -923,7 +923,7 @@ help comp.unix.bsd.freebsd.announce - + comp.unix.bsd.freebsd.misc @@ -938,62 +938,62 @@ help comp.unix - + comp.unix.questions - + comp.unix.admin - + comp.unix.programmer - + comp.unix.shell - + comp.unix.user-friendly - + comp.security.unix - + comp.sources.unix - + comp.unix.advocacy - + comp.unix.misc - + comp.bugs.4bsd - + comp.bugs.4bsd.ucb-fixes - + comp.unix.bsd @@ -1009,37 +1009,37 @@ help comp.windows.x.i386unix - + comp.windows.x - + comp.windows.x.apps - + comp.windows.x.announce - + comp.windows.x.intrinsics - + comp.windows.x.motif - + comp.windows.x.pex - + comp.emulators.ms-windows.wine @@ -1332,7 +1332,7 @@ help Read-only cvs, personal webspace, email &a.brian - + dogma.freebsd-uk.eu.org Telnet/FTP/SSH diff --git a/en_US.ISO8859-1/books/handbook/hw/chapter.sgml b/en_US.ISO8859-1/books/handbook/hw/chapter.sgml index ce754facda..2b76420280 100644 --- a/en_US.ISO8859-1/books/handbook/hw/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/hw/chapter.sgml @@ -1,7 +1,7 @@ @@ -39,7 +39,7 @@ independent. Please check with the FreeBSD hardware guide to make sure that your chosen configuration is supported before making any purchases. - + The Pentium Systems @@ -70,7 +70,7 @@ Motherboards - + For Pentium Pro (P6) systems, I'm quite fond of the Tyan S1668 dual-processor motherboard as well as the Intel PR440FX motherboard @@ -89,7 +89,7 @@ url="http://www.asus.com.tw/Products/Motherboard/Pentium/P55tp4/index.html">P55T2P4 motherboard appears to be a good choice for mid-to-high range Pentium server and workstation systems. - + Those wishing to build more fault-tolerant systems should also be sure to use Parity memory or, for truly 24/7 applications, ECC memory. @@ -136,7 +136,7 @@ Disk drives - + In this particular game of Russian roulette, I'll make few specific recommendations except to say “SCSI over IDE whenever you can afford it.” Even in small desktop configurations, SCSI @@ -150,7 +150,7 @@ CDROM drives - + My SCSI preferences extend to SCSI CDROM drives as well, and while the Toshiba drives have always been favourites of mine (in whatever speed is hot that @@ -170,7 +170,7 @@ CD Recordable (WORM) drives - + At the time of this writing, FreeBSD supports 3 types of CDR drives (though I believe they all ultimately come from Phillips anyway): The Phillips CDD 522 (Acts like a Plasmon), the PLASMON @@ -186,7 +186,7 @@ Tape drives - + I've had pretty good luck with both 8mm drives from Video Cards - + If you can also afford to buy a commercial X server for US$99 from Xi Graphics, Inc. (formerly X Inside, Inc) then I can heartily recommend the @@ -212,7 +212,7 @@ excellent with the XFree86 server, which is now at version 3.3.2. - + You also certainly can't go wrong with one of Number 9's cards — their S3 Vision 868 and 968 based cards (the 9FX series) also being quite @@ -223,7 +223,7 @@ Monitors - + I have had very good luck with the Sony Multiscan 17seII monitors, as have I with the Viewsonic @@ -238,7 +238,7 @@ Networking - + I can recommend the Intel EtherExpress Pro/100B card first and foremost, followed by the SMC Ultra 16 controller for any @@ -258,7 +258,7 @@ Serial - + If you're looking for high-speed serial networking solutions, then Digi International makes the Audio - + I currently use a Creative Labs AWE32 though just about anything from Creative Labs will generally work these days. This is not to say that other types @@ -297,7 +297,7 @@ Video - + For video capture, there are two good choices — any card based on the Brooktree BT848 chip, such as the Hauppage or WinTV boards, will work very nicely with FreeBSD. Another board which @@ -322,31 +322,31 @@ * ISA - + * EISA - + * VLB - + PCI - + Contributed by &a.obrien; from postings by &a.rgrimes;. 25 April 1995. - + Continuing updates by &a.jkh;. Last update on 26 August 1996. - + Of the Intel PCI chip sets, the following list describes various types of known-brokenness and the degree of breakage, listed from worst to best. @@ -458,7 +458,7 @@ P6 class (Pentium Pro/Pentium II) - + Both the Pentium Pro and Pentium II work fine with FreeBSD. In fact, our main ftp site ftp.FreeBSD.org (also known @@ -470,7 +470,7 @@ Pentium class - + The Intel Pentium (P54C), Pentium MMX (P55C), AMD K6 and Cyrix/IBM 6x86MX processors are all reported to work with FreeBSD. I will not go into details of which processor is faster than what, @@ -486,7 +486,7 @@ good heatsink/fans (you can get the list of certified parts from their web pages). - + Clock speeds @@ -628,7 +628,7 @@ 166, 200 and 233, with the exception that at a multiplier of 3 or more the CPU starves for memory. - + The AMD K6 Bug @@ -642,13 +642,13 @@ * 486 class - + * 386 class - + @@ -698,10 +698,10 @@ The UART: What it is and how it works - + Copyright © 1996 &a.uhclem;, All Rights Reserved. 13 January 1996. - + The Universal Asynchronous Receiver/Transmitter (UART) controller is the key component of the serial communications subsystem of a computer. The UART takes bytes of data and transmits @@ -760,7 +760,7 @@ support Synchronous operations. This mode is described here for comparison purposes only. - + Asynchronous Serial Transmission @@ -827,7 +827,7 @@ if there is no data to transmit, the transmission line can be idle. - + Other UART Functions @@ -844,7 +844,7 @@ extra signals. The function of each of these additional signals is defined in the EIA RS232-C standard. - + The RS232-C and V.24 Standards @@ -1251,7 +1251,7 @@ - + Bits, Baud and Symbols @@ -1344,7 +1344,7 @@ provides. Modems operating at 28,800 and higher speeds have variable Symbol rates, but the technique is the same. - + The IBM Personal Computer UART @@ -1572,7 +1572,7 @@ INS8250 -> INS8250B called a PC16550DN or PC16550DIN. - + Other Vendors and Similar UARTs @@ -1765,7 +1765,7 @@ INS8250 -> INS8250B Error (6)...Timeout interrupt failed: IIR = c1 LSR = 61 - + 8250/16450/16550 Registers @@ -2530,7 +2530,7 @@ INS8250 -> INS8250B - + Beyond the 16550A UART @@ -2622,7 +2622,7 @@ device sio11 at isa? port 0x138 tty flags 0xb05 irq 9 vector siointr< represent the last SIO port, in this case 11 so flags are 0xb05. - + Boca 16 @@ -2910,7 +2910,7 @@ sio2: type 16550A (multiport master) cy driver instead of the usual sio driver used by other multiport cards. Configuration is a simple matter of: - + Add the cy device to your Configuring the <devicename>si</devicename> driver - + Contributed by &a.nsayer;. 25 March 1998. @@ -2966,7 +2966,7 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure si driver. A single machine can have up to 4 host cards. The following host cards are supported: - + ISA SI/XIO host card (2 versions) EISA SI/XIO host card @@ -2986,7 +2986,7 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure You can attach up to 4 external modules to each host card. The external modules contain either 4 or 8 serial ports. They come in the following varieties: - + SI 4 or 8 port modules. Up to 57600 bps on each port supported. @@ -3006,7 +3006,7 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure device si0 at isa? tty iomem 0xd0000 irq 11 - + Valid IRQ numbers are 9, 10, 11, 12 and 15 for SX ISA host cards and 11, 12 and 15 for SI/XIO ISA host cards. @@ -3033,7 +3033,7 @@ device si0 If you want login prompts to appear on these ports, you will need to add lines like this to /etc/ttys: - + ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure @@ -3112,7 +3112,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure Concepts of ESDI - + Physical connections @@ -3133,7 +3133,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure feature(?) left over from the WD1003 standard that reserves only a single bit for device addressing. - + Device addressing @@ -3148,7 +3148,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure PC with its two drives/controller maximum the first drive is drive 0, the second is drive 1. - + Termination @@ -3168,10 +3168,10 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure Using ESDI disks with FreeBSD - + Why is ESDI such a pain to get working in the first place? - + People who tried ESDI disks with FreeBSD are known to have developed a profound sense of frustration. A combination of factors works against you to produce effects that are hard to understand @@ -3193,7 +3193,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure consult your controller and drive documentation to see if things match. - + Stay on track @@ -3213,7 +3213,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure work. Give it a try or get another more capable controller. - + Hard or soft sectoring @@ -3243,7 +3243,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure FreeBSD because you need to re-run the low-level format after each change. - + Low level formatting @@ -3266,7 +3266,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure this waste space, it also and more importantly causes you grief with bad144 (see the section on bad144). - + Translations @@ -3342,7 +3342,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure or whatever it may be called by the controller manufacturer when you want to use the disk for FreeBSD. - + Bad block handling @@ -3384,7 +3384,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure contains the root filesystem. - + Kernel configuration @@ -3415,7 +3415,7 @@ disk wd3 at wdc1 drive 1 Particulars on ESDI hardware - + Adaptec 2320 controllers @@ -3455,7 +3455,7 @@ disk wd3 at wdc1 drive 1 All variations should be capable of using 1:1 interleaving. Use 1:1, FreeBSD is fast enough to handle it. - + Western Digital WD1007 controllers @@ -3470,7 +3470,7 @@ disk wd3 at wdc1 drive 1 role="fqdn">www.wdc.com Running this formatted my drive just fine. - + Ultrastor U14F controllers @@ -3503,7 +3503,7 @@ disk wd3 at wdc1 drive 1 Thanks to... - + Andrew Gordon for sending me an Adaptec 2320 controller and ESDI disk for testing. @@ -3599,7 +3599,7 @@ disk wd3 at wdc1 drive 1 Components of SCSI - + As said before, SCSI devices are smart. The idea is to put the knowledge about intimate hardware details onto the SCSI device itself. In this way, the host system does not have to worry about @@ -3629,7 +3629,7 @@ disk wd3 at wdc1 drive 1 SCSI bus types - + From an electrical point of view, there are two incompatible bus types: single-ended and differential. This means that there are two different main groups of SCSI devices and controllers, which cannot @@ -3662,8 +3662,8 @@ disk wd3 at wdc1 drive 1 etc. - - + + With a minor amount of imagination one can usually imagine what is meant. @@ -3685,7 +3685,7 @@ disk wd3 at wdc1 drive 1 width is negotiated between the devices. You have to watch your device addressing closely when mixing wide and narrow. - + Single ended buses @@ -3730,7 +3730,7 @@ disk wd3 at wdc1 drive 1 accordance with the SCSI standard. For Fast-20 and 40 do not even think about buses like this. - + Differential buses @@ -3759,7 +3759,7 @@ disk wd3 at wdc1 drive 1 differential. The software interface to the host is identical for both. - + Terminators @@ -3839,7 +3839,7 @@ disk wd3 at wdc1 drive 1 termination as necessary. At any rate, consult your documentation! - + Terminator power @@ -3872,7 +3872,7 @@ disk wd3 at wdc1 drive 1 In newer designs auto-restoring fuses that 'reset' themselves after some time are sometimes used. - + Device addressing @@ -3955,7 +3955,7 @@ disk wd3 at wdc1 drive 1 Using SCSI with FreeBSD - + About translations, BIOSes and magic... @@ -4048,7 +4048,7 @@ sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors) to know about this disk, (e.g. it is not a booting disk) to supply a fictitious geometry that is convenient. - + SCSI subsystem design @@ -4069,7 +4069,7 @@ sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors) banging and more high level stuff. Adding support for another piece of hardware is a much more manageable problem. - + Kernel configuration @@ -4214,7 +4214,7 @@ device cd0 #Only need one of these, the code dynamically growsman 4 ahc for info on the Adaptec 294x driver. - + Tuning your SCSI kernel setup @@ -4239,7 +4239,7 @@ options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device - + Rogue SCSI devices @@ -4284,7 +4284,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue in the next release of FreeBSD. Other Mumbletech owners will be grateful to you. - + Multiple LUN devices @@ -4321,7 +4321,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue the table and acts accordingly. See the source for more info. - + Tagged command queueing @@ -4347,7 +4347,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue leads to highly mysterious problems. In such cases, try to disable TCQ. - + Busmaster host adapters @@ -4385,7 +4385,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Tracking down problems - + The following list is an attempt to give a guideline for the most common SCSI problems and their solutions. It is by no means complete. @@ -4449,7 +4449,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Further reading - + If you intend to do some serious SCSI hacking, you might want to have the official standard at hand: @@ -4464,7 +4464,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed(212) 642-4900 - + You can also buy many ANSI standards and most committee draft documents from Global Engineering Documents, @@ -4478,13 +4478,13 @@ options "TUNE_1542" #dynamic tune of bus DMA speed(303) 792- 2192 - + Many X3T10 draft documents are available electronically on the SCSI BBS (719-574-0424) and on the ncrinfo.ncr.com anonymous ftp site. Latest X3T10 committee documents are: - + AT Attachment (ATA or IDE) [X3.221-1994] @@ -4511,10 +4511,10 @@ options "TUNE_1542" #dynamic tune of bus DMA speed - + Other publications that might provide you with additional information are: - + “SCSI: Understanding the Small Computer System @@ -4556,13 +4556,13 @@ options "TUNE_1542" #dynamic tune of bus DMA speed - + On Usenet the newsgroups comp.periphs.scsi and comp.periphs are noteworthy places to look for more info. You can also find the SCSI-Faq there, which is posted periodically. - + Most major SCSI device and host adapter suppliers operate ftp sites and/or BBS systems. They may be valuable sources of information about the devices you own. @@ -4574,19 +4574,19 @@ options "TUNE_1542" #dynamic tune of bus DMA speed * SCSI - + * IDE - + * Floppy - + @@ -4596,7 +4596,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed SCSI hard drives - + Contributed by &a.asami;. 17 February 1998. @@ -4610,7 +4610,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed - + Rotational speed @@ -4670,7 +4670,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed - + Form factor @@ -4682,7 +4682,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed - + Interface @@ -4722,7 +4722,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed * IDE hard drives - + @@ -4735,7 +4735,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed General tape access commands - + &man.mt.1; provides generic access to the tape drives. Some of the more common commands are rewind, erase, and status. See the @@ -4744,7 +4744,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Controller Interfaces - + There are several different interfaces that support tape drives. The interfaces are SCSI, IDE, Floppy and Parallel Port. A wide variety of tape drives are available for these interfaces. @@ -4755,18 +4755,18 @@ options "TUNE_1542" #dynamic tune of bus DMA speed SCSI drives - + The &man.st.4; driver provides support for 8mm (Exabyte), 4mm (DAT: Digital Audio Tape), QIC (Quarter-Inch Cartridge), DLT (Digital Linear Tape), QIC Minicartridge and 9-track (remember the big reels that you see spinning in Hollywood computer rooms) tape drives. See the &man.st.4; manual page for a detailed description. - + The drives listed below are currently being used by members of the FreeBSD community. They are not the only drives that will work with FreeBSD. They just happen to be the ones that we use. - + 4mm (DAT: Digital Audio Tape) @@ -4791,7 +4791,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedWangtek 6200 - + 8mm (Exabyte) @@ -4801,7 +4801,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedEXB-8505 - + QIC (Quarter-Inch Cartridge) @@ -4832,13 +4832,13 @@ options "TUNE_1542" #dynamic tune of bus DMA speedWangtek 5525ES - + DLT (Digital Linear Tape) Digital TZ87 - + Mini-Cartridge @@ -4847,7 +4847,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedExabyte 2501 - + Autoloaders/Changers @@ -4858,25 +4858,25 @@ options "TUNE_1542" #dynamic tune of bus DMA speed * IDE drives - + Floppy drives - + Conner 420R * Parallel port drives - + Detailed Information - + Archive Anaconda 2750 @@ -4922,14 +4922,14 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Reported by: &a.jmb; - + Archive Python 28454 @@ -4981,7 +4981,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedData transfer rate is 800kB/s. - + Archive Viper 60 @@ -5000,7 +5000,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Philippe Regnauld regnauld@hsc.fr - + Archive Viper 150 @@ -5062,7 +5062,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedProduction of this drive has been discontinued. - + Conner 420R @@ -5080,7 +5080,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Mark Hannon mark@seeware.DIALix.oz.au - + Conner CTMS 3200 @@ -5099,7 +5099,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Thomas S. Traylor tst@titan.cs.mci.com - + <ulink url="http://www.digital.com/info/Customer-Update/931206004.txt.html">DEC TZ87</ulink> @@ -5122,7 +5122,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: &a.wilko; - + <ulink url="http://www.Exabyte.COM:80/Products/Minicartridge/2501/Rfeatures.html">Exabyte EXB-2501</ulink> @@ -5165,7 +5165,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Bob Beaulieu ez@eztravel.com - + Exabyte EXB-8200 @@ -5193,7 +5193,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Mike Smith msmith@atrad.adelaide.edu.au - + Exabyte EXB-8500 @@ -5209,7 +5209,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Greg Lehey grog@lemis.de - + <ulink url="http://www.Exabyte.COM:80/Products/8mm/8505XL/Rfeatures.html">Exabyte EXB-8505</ulink> @@ -5230,7 +5230,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Glen Foster gfoster@gfoster.com - + Hewlett-Packard HP C1533A @@ -5314,7 +5314,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: &a.se; - + Hewlett-Packard HP 1534A @@ -5346,7 +5346,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by Gary Crutcher gcrutchr@nightflight.com - + Hewlett-Packard HP C1553A Autoloading DDS2 @@ -5414,7 +5414,7 @@ esac scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" - + Hewlett-Packard HP 35450A @@ -5433,7 +5433,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Reported by: mark thompson mark.a.thompson@pobox.com - + Hewlett-Packard HP 35470A @@ -5461,7 +5461,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" dawes@rf900.physics.usyd.edu.au (9 09) - + Hewlett-Packard HP 35480A @@ -5497,7 +5497,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" lost. The problem has not be analyzed or resolved at this time. - + <ulink url="http://www.sel.sony.com/SEL/ccpg/storage/tape/t5000.html">Sony SDT-5000</ulink> @@ -5531,7 +5531,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Reported by: &a.jmz; - + Tandberg TDC 3600 @@ -5556,7 +5556,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Reported by: Michael Smith msmith@atrad.adelaide.edu.au - + Tandberg TDC 3620 @@ -5580,7 +5580,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Reported by: &a.jhs; - + Tandberg TDC 4222 @@ -5608,7 +5608,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Reported by: &a.joerg; - + Wangtek 5525ES @@ -5643,7 +5643,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Andrew.Gordon@net-tel.co.uk M75D - + Wangtek 6200 @@ -5664,7 +5664,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" * Problem drives - + diff --git a/en_US.ISO8859-1/books/handbook/install/chapter.sgml b/en_US.ISO8859-1/books/handbook/install/chapter.sgml index 8fa4033111..6dc238ab49 100644 --- a/en_US.ISO8859-1/books/handbook/install/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/install/chapter.sgml @@ -1,7 +1,7 @@ @@ -111,7 +111,7 @@ live in the floppies subdirectory, as is typically the case). - + If you are using a UNIX system to create the floppy images: @@ -199,7 +199,7 @@ After adjusting the kernel to match how you have your hardware configured, type Q to continue booting with the new settings. - + After FreeBSD has been installed, changes made in the configuration mode will be permanent so you do not have to reconfigure every time you boot. Even so, it is likely that you will want to build a custom kernel @@ -215,16 +215,16 @@ 386sx is not recommended). Support for generic IDE or ESDI drive configurations, various SCSI controller, network and serial cards is also provided. - + A minimum of four megabytes of RAM is required to run FreeBSD. To run the X Window System, eight megabytes of RAM is the recommended minimum. - + Following is a list of all disk controllers and Ethernet cards currently known to work with FreeBSD. Other configurations may very well work, and we have simply not received any indication of this. - + Disk Controllers @@ -232,15 +232,15 @@ WD1003 (any generic MFM/RLL) - + WD1007 (any generic IDE/ESDI) - + IDE - + ATA @@ -403,7 +403,7 @@ - + DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers are supported. The DPT @@ -415,7 +415,7 @@ SMART, SMART-2/E, Smart-2/P, SMART-2SL, Smart Array 3200, Smart Array 3100ES and Smart Array 221. - + SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI @@ -451,12 +451,12 @@ - + QLogic 1020, 1040, 1040B, 1080, 1240 and 2100 SCSI and Fibre Channel Adapters - + DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -478,21 +478,21 @@ SoundBlaster SCSI and ProAudio Spectrum SCSI (cd) - + Mitsumi (all models) proprietary interface (mcd) - + Matsushita/Panasonic (Creative) CR-562/CR-563 proprietary interface (matcd) - + Sony proprietary interface (scd) - + ATAPI IDE interface (wcd) @@ -506,15 +506,15 @@ Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). - + NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. - + UltraStor 14F, 24F and 34F SCSI controllers. - + Seagate ST01/02 SCSI controllers. @@ -522,7 +522,7 @@ Future Domain 8xx/950 series SCSI controllers. - + WD7000 SCSI controller. @@ -531,11 +531,11 @@ Adaptec 1510 series ISA SCSI controllers (not for bootable devices) - + Adaptec 152x series ISA SCSI controllers - + Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. @@ -550,22 +550,22 @@ Allied-Telesis AT1700 and RE2000 cards - + SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra and 9432TX based cards are also supported. - + DEC EtherWORKS III NICs (DE203, DE204, and DE205) - + DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) - + DEC DC21040/DC21041/DC21140 based NICs: @@ -643,75 +643,75 @@ DEC FDDI (DEFPA/DEFEA) NICs - + Fujitsu FMV-181 and FMV-182 - + Fujitsu MB86960A/MB86965A - + Intel EtherExpress - + Intel EtherExpress Pro/100B 100Mbit. - + Isolan AT 4141-0 (16 bit) - + Isolink 4110 (8 bit) - + Lucent WaveLAN wireless networking interface. - + Novell NE1000, NE2000, and NE2100 ethernet interface. - + 3Com 3C501 cards - + 3Com 3C503 Etherlink II - + 3Com 3c505 Etherlink/+ - + 3Com 3C507 Etherlink 16/TP - + 3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III - + 3Com 3C590, 3C595 Etherlink III - + 3Com 3C90x cards. - + HP PC Lan Plus (27247B and 27252A) - + Toshiba ethernet cards - + PCMCIA ethernet cards from IBM and National Semiconductor are also supported. @@ -732,71 +732,71 @@ AST 4 port serial card using shared IRQ. - + ARNET 8 port serial card using shared IRQ. - + BOCA IOAT66 6 port serial card using shared IRQ. - + BOCA 2016 16 port serial card using shared IRQ. - + Cyclades Cyclom-y Serial Board. - + STB 4 port card using shared IRQ. - + SDL Communications Riscom/8 Serial Board. - + SDL Communications RISCom/N2 and N2pci sync serial cards. - + Digiboard Sync/570i high-speed sync serial card. - + Decision-Computer Intl. “Eight-Serial” 8 port serial cards using shared IRQ. - + Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound, Gravis UltraSound MAX and Roland MPU-401 sound cards. - + Matrox Meteor video frame grabber. - + Creative Labs Video spigot frame grabber. - + Omnimedia Talisman frame grabber. - + Brooktree BT848 chip based frame grabbers. - + X-10 power controllers. - + PC joystick and speaker. @@ -947,7 +947,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent c:\freebsd — the BIN dist is only the minimal requirement. - + Before installing from QIC/SCSI Tape @@ -974,7 +974,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent installation probe may otherwise fail to find it. - + Before installing over a network @@ -989,7 +989,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent SLIP or PPP - + Parallel port @@ -997,7 +997,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent PLIP (laplink cable) - + Ethernet @@ -1062,7 +1062,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent Preparing for NFS installation - + NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution files you want onto a server somewhere and then point the NFS media selection at it. @@ -1094,7 +1094,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent Preparing for FTP Installation - + FTP installation may be done from any mirror site containing a reasonably up-to-date version of FreeBSD &rel.current;. A full menu of reasonable choices from almost anywhere in the world is provided @@ -1134,13 +1134,13 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent - + Active and passive modes are not the same as a “proxy” connection, where a proxy FTP server is listening and forwarding FTP requests! - + For a proxy FTP server, you should usually give name of the server you really want as a part of the username, after an @-sign. The proxy server then 'fakes' the real server. An example: Say you @@ -1170,14 +1170,14 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent Once you have taken note of the appropriate preinstallation steps, you should be able to install FreeBSD without any further trouble. - + Should this not be true, then you may wish to go back and re-read the relevant preparation section above for the installation media type you are trying to use, perhaps there is a helpful hint there that you missed the first time? If you are having hardware trouble, or FreeBSD refuses to boot at all, read the Hardware Guide provided on the boot floppy for a list of possible solutions. - + The FreeBSD boot floppies contain all the on-line documentation you should need to be able to navigate through an installation and if it does not then we would like to know what you found most confusing. Send @@ -1186,10 +1186,10 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent 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! - + Meanwhile, you may also find the following “typical installation sequence” to be helpful: - + Boot the kern.flp floppy and, when asked, @@ -1243,7 +1243,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent Many FreeBSD users wish to install FreeBSD on PCs inhabited by MS-DOS. Here are some commonly asked questions about installing FreeBSD on such systems. - + Help! I have no space! Do I need to delete everything first? @@ -1252,7 +1252,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent find the FIPS utility, provided in the tools directory on the FreeBSD CDROM or on the various FreeBSD ftp sites, to be quite useful. - + FIPS allows you to split an existing MS-DOS partition into two pieces, preserving the original partition and allowing you to install onto the second free piece. You first defragment your MS-DOS partition, @@ -1262,24 +1262,24 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent See the Distributions menu for an estimation of how much free space you will need for the kind of installation you want. - + Can I use compressed MS-DOS filesystems from FreeBSD? - + No. If you are using a utility such as Stacker(tm) or DoubleSpace(tm), FreeBSD will only be able to use whatever portion of the filesystem you leave uncompressed. The rest of the filesystem will show up as one large file (the stacked/dblspaced file!). Do not remove that file! You will probably regret it greatly! - + It is probably better to create another uncompressed MS-DOS primary partition and use this for communications between MS-DOS and FreeBSD. - + Can I mount my MS-DOS extended partitions? - + Yes. DOS extended partitions are mapped in at the end of the other “slices” in FreeBSD, e.g. your D: drive might be /dev/da0s5, your @@ -1289,7 +1289,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent da appropriately. You otherwise mount extended partitions exactly like you would mount any other DOS drive, e.g.: - + &prompt.root; mount -t msdos /dev/da0s5 /dos_d diff --git a/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml b/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml index b2e28e9bf1..8a2df78d1d 100644 --- a/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml @@ -1,7 +1,7 @@ @@ -27,7 +27,7 @@ architecture. FreeBSD provides you with many advanced features previously available only on much more expensive systems. These features include: - + Preemptive multitasking with @@ -139,7 +139,7 @@ the commercial giants struggle to field PC operating systems with such features, performance and reliability, FreeBSD can offer them now! - + The applications to which FreeBSD can be put are truly limited only by your own imagination. From software development to factory automation, inventory control to azimuth correction of remote satellite @@ -149,7 +149,7 @@ applications developed by research centers and universities around the world, often available at little to no cost. Commercial applications are also available and appearing in greater numbers every day. - + Because the source code for FreeBSD itself is generally available, the system can also be customized to an almost unheard of degree for special applications or projects, and in ways not generally possible @@ -188,7 +188,7 @@ And more... - + With FreeBSD, you can easily start out small with an inexpensive 386 class PC and upgrade all the way up to a quad-processor Xeon with RAID storage as your enterprise @@ -271,7 +271,7 @@ 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. - + It did not take us long to decide that the goal remained worthwhile, even without Bill's support, and so we adopted the name “FreeBSD”, coined by David Greenman. Our initial objectives @@ -285,14 +285,14 @@ Walnut Creek CDROM's almost unprecedented degree of faith in what was, at the time, a completely unknown project, it is quite unlikely that FreeBSD would have gotten as far, as fast, as it has today. - + 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 (“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 1994. - + Around this time, some rather unexpected storm clouds formed on 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 @@ -306,7 +306,7 @@ 1994 to stop shipping its own Net/2 based product. Under the terms of that agreement, the project was allowed one last release before the deadline, that release being FreeBSD 1.1.5.1. - + 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 “Lite” releases were light in part because @@ -319,7 +319,7 @@ rough around the edges, the release was a significant success and was followed by the more robust and easier to install FreeBSD 2.0.5 release in June of 1995. - + We released FreeBSD 2.1.5 in August of 1996, and it appeared to be popular enough among the ISP and commercial communities that another release along the 2.1-stable branch was merited. This was FreeBSD @@ -327,7 +327,7 @@ development on 2.1-stable. Now in maintenance mode, only security enhancements and other critical bug fixes will be done on this branch (RELENG_2_1_0). - + FreeBSD 2.2 was branched from the development mainline (“-current”) in November 1996 as the RELENG_2_2 branch, and the first full release (2.2.1) was released in April, 1997. Further @@ -362,7 +362,7 @@ provides the widest possible benefit. This is, I believe, one of the most fundamental goals of Free Software and one that we enthusiastically support. - + That code in our source tree which falls under the GNU General Public License (GPL) or Library General Public License (LGPL) comes with slightly more strings attached, though at least on the side of enforced access @@ -389,10 +389,10 @@ to distribute their own patches or work-in-progress sources. The &a.announce; is also available to those wishing to make other FreeBSD users aware of major areas of work. - + Useful things to know about the FreeBSD project and its development process, whether working independently or in close cooperation: - + The CVS repository The FreeBSD core team - + The FreeBSD core team would be equivalent to the board of directors if the FreeBSD Project @@ -468,7 +468,7 @@ Outside contributors - + Last, but definitely not least, the largest group of developers are the users themselves who provide feedback and @@ -515,7 +515,7 @@ Alpha based computer systems. It is based primarily on software from U.C. Berkeley's CSRG group, with some enhancements from NetBSD, OpenBSD, 386BSD, and the Free Software Foundation. - + Since our release of FreeBSD 2.0 in late 94, the performance, feature set, and stability of FreeBSD has improved dramatically. The largest change is a revamped virtual memory system with a merged VM/file @@ -526,12 +526,12 @@ an improved SCSI subsystem, ISDN support, support for ATM, FDDI, Fast and Gigabit Ethernet (1000Mbit) adapters, improved support for the latest Adaptec controllers and many hundreds of bug fixes. - + We have also taken the comments and suggestions of many of our users to heart and have attempted to provide what we hope is a more sane and easily understood installation process. Your feedback on this (constantly evolving) process is especially welcome! - + In addition to the base distributions, FreeBSD offers a new ported software collection with hundreds of commonly sought-after programs. By mid-September 1999, there were more than 2600 ports! The list of @@ -550,7 +550,7 @@ 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. - + A number of additional documents which you may find very helpful in the process of installing and using FreeBSD may now also be found in the /usr/share/doc directory on any machine running @@ -569,7 +569,7 @@ The FreeBSD FAQ - + file:/usr/share/doc/FAQ/FAQ.html @@ -589,7 +589,7 @@ outside the U.S.) exportable European distribution of DES for our non-U.S. users also exists and is described in the FreeBSD FAQ. - + If password security for FreeBSD is all you need, and you have no requirement for copying encrypted passwords from different hosts (Suns, DEC machines, etc) into FreeBSD password entries, then FreeBSD's MD5 diff --git a/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml b/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml index ebc543fdf4..014292ce36 100644 --- a/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml @@ -1,7 +1,7 @@ @@ -68,7 +68,7 @@ while everything outside the i386 directory is common to all platforms which FreeBSD could potentially be ported to. - + If there is not a /usr/src/sys directory on your system, then the @@ -90,7 +90,7 @@ maintaining multiple FreeBSD machines with different hardware, it is a good idea to name it after your machine's hostname. We will call it MYKERNEL for the purpose of this example. - + You must execute these and all of the following commands under the root account or you will get permission denied @@ -107,7 +107,7 @@ comment lines at the top to reflect your configuration or the changes you have made to differentiate it from GENERIC. - + If you have build a kernel under SunOS or some other BSD operating system, much of this file will be very familiar to you. If you are coming from some other operating system such as DOS, on the other hand, @@ -169,14 +169,14 @@ directory as GENERIC. If you are in doubt as to the purpose or necessity of a line, check first in LINT. - + The kernel is currently being moved to a better organization of the option handling. Traditionally, each option in the config file was simply converted into a switch for the CFLAGS line of the kernel Makefile. Naturally, this caused a creeping optionism, with nobody really knowing which option has been referenced in what files. - + In the new scheme, every #ifdef that is intended to be dependent upon an option gets this option out of an opt_foo.h declaration @@ -226,7 +226,7 @@ alpha. - + cpu "cpu_type" @@ -277,7 +277,7 @@ cpu_type. - + ident machine_name @@ -302,7 +302,7 @@ vax. - + maxusers number @@ -344,7 +344,7 @@ - + config kernel_name root on @@ -393,7 +393,7 @@ - + options "COMPAT_43" @@ -402,7 +402,7 @@ will act strangely if you comment this out. - + options UCONSOLE @@ -414,7 +414,7 @@ as any console messages sent by the kernel. - + options SYSVSHM @@ -427,7 +427,7 @@ definitely want to include this. - + options SYSVSEM @@ -436,7 +436,7 @@ only adds a few hundred bytes to the kernel. - + options SYSVMSG @@ -476,7 +476,7 @@ from the hard disk. - + options NFS @@ -486,7 +486,7 @@ out. - + options MSDOSFS @@ -501,7 +501,7 @@ all). - + options "CD9660" @@ -512,7 +512,7 @@ data CD). Audio CD's do not need this filesystem. - + options PROCFS @@ -523,7 +523,7 @@ what processes are running. - + options MFS @@ -557,7 +557,7 @@ - + options "EXT2FS" @@ -568,7 +568,7 @@ the two systems. - + options QUOTA @@ -600,7 +600,7 @@ run FreeBSD at this time. - + controller eisa0 @@ -609,7 +609,7 @@ EISA bus. - + controller pci0 @@ -619,7 +619,7 @@ ISA bus. - + controller fdc0 @@ -638,7 +638,7 @@ - + controller wdc0 @@ -652,7 +652,7 @@ all six lines, for example). - + device acd0 @@ -665,7 +665,7 @@ line options ATAPI. - + device npx0 at isa? port "IO_NPX" irq 13 vector npxintr @@ -677,7 +677,7 @@ optional. - + device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr @@ -686,7 +686,7 @@ Wangtek and Archive QIC-02/QIC-36 tape drive support - + Proprietary CD-ROM support @@ -848,7 +848,7 @@ - + options SCSI_DELAY=15000 @@ -861,7 +861,7 @@ your SCSI devices, you will have to raise it back up. - + controller scbus0 @@ -871,7 +871,7 @@ and the following three lines, out. - + device da0 @@ -879,7 +879,7 @@ Support for SCSI hard drives. - + device sa0 @@ -887,7 +887,7 @@ Support for SCSI tape drives. - + device cd0 @@ -895,7 +895,7 @@ Support for SCSI CD-ROM drives. - + device ch0 @@ -904,7 +904,7 @@ as tape libraries. - + device pass0 @@ -1056,7 +1056,7 @@ - + device mse0 at isa? port 0x23c tty irq 5 vector ms @@ -1073,7 +1073,7 @@ - + device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr @@ -1122,7 +1122,7 @@ used. - + controller ppbus0 @@ -1130,7 +1130,7 @@ Provides support for the parallel port bus. - + device ppc0 at isa? port? tty irq 7 @@ -1138,7 +1138,7 @@ ISA-bus parallel port interface. - + device lpt0 at ppbus? @@ -1173,7 +1173,7 @@ your PC) so this is essentially mandatory. - + Ethernet cards @@ -1362,7 +1362,7 @@ back at you through this pseudo-device. Mandatory. - + pseudo-device ether @@ -1372,7 +1372,7 @@ code. - + pseudo-device sl number @@ -1389,7 +1389,7 @@ linkend="slips">server. - + pseudo-device ppp number @@ -1407,7 +1407,7 @@ simultaneous PPP connections to support. - + pseudo-device tun number @@ -1422,7 +1422,7 @@ for more information. - + pseudo-device bpfilter number @@ -1463,7 +1463,7 @@ pcm. - + device pas0 at isa? port 0x388 irq 10 drq 6 vector pasintr @@ -1472,7 +1472,7 @@ ProAudioSpectrum digital audio and MIDI. - + device sb0 at isa? port 0x220 irq 7 conflicts drq 1 vector sbintr @@ -1488,7 +1488,7 @@ - + device sbxvi0 at isa? drq 5 @@ -1502,7 +1502,7 @@ - + device sbmidi0 at isa? port 0x330 @@ -1512,7 +1512,7 @@ compile. - + device gus0 at isa? port 0x220 irq 10 drq 1 vector gusintr @@ -1521,7 +1521,7 @@ Gravis Ultrasound. - + device mss0 at isa? port 0x530 irq 10 drq 1 vector adintr @@ -1530,7 +1530,7 @@ Microsoft Sound System. - + device opl0 at isa? port 0x388 conflicts @@ -1542,7 +1542,7 @@ (in the ports collection). - + device mpu0 at isa? port 0x330 irq 6 drq 0 @@ -1551,7 +1551,7 @@ Roland MPU-401 stand-alone card. - + device uart0 at isa? port 0x330 irq 5 vector "m6850intr" @@ -1560,7 +1560,7 @@ Stand-alone 6850 UART for MIDI. - + device pca0 at isa? port "IO_TIMER1" tty @@ -1619,7 +1619,7 @@ - + pseudo-device log @@ -1628,7 +1628,7 @@ messages. Mandatory. - + pseudo-device pty number - + pseudo-device snp number @@ -1660,7 +1660,7 @@ of simultaneous snoop sessions. Optional. - + pseudo-device vn @@ -1672,7 +1672,7 @@ Optional. - + pseudo-device ccd number @@ -1707,7 +1707,7 @@ PC joystick device. - + pseudo-device speaker @@ -1745,7 +1745,7 @@ of them, so when you add support for a new device, it pays to make sure that the appropriate entries are in this directory, and if not, add them. Here is a simple example: - + Suppose you add the IDE CD-ROM support to the kernel. The line to add is: @@ -1764,7 +1764,7 @@ device acd0 When this script finishes, you will find that there are now acd0c and racd0c entries in /dev so you know that it executed correctly. - + For sound cards, the command: &prompt.root; sh MAKEDEV snd0 @@ -1833,7 +1833,7 @@ device acd0 Kernel will not boot - + If your new kernel does not boot, or fails to recognize your devices, do not panic! Fortunately, BSD has an excellent mechanism @@ -1881,7 +1881,7 @@ device acd0 Kernel works, but ps does not work any more! - + If you have installed a different version of the kernel from the one that the system utilities have been built with, for diff --git a/en_US.ISO8859-1/books/handbook/kerneldebug/chapter.sgml b/en_US.ISO8859-1/books/handbook/kerneldebug/chapter.sgml index 1ebf9d9620..ce7b253523 100644 --- a/en_US.ISO8859-1/books/handbook/kerneldebug/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/kerneldebug/chapter.sgml @@ -1,7 +1,7 @@ @@ -55,7 +55,7 @@ some programs will drastically increase, and since the whole kernel is loaded entirely at boot time and cannot be swapped out later, several megabytes of physical memory will be wasted. - + If you are testing a new kernel, for example by typing the new kernel's name at the boot prompt, but need to boot a different one in order to get your system up and running again, boot it only into single @@ -186,7 +186,7 @@ line 20: - + This is the location of function trap() in the stack trace. @@ -195,7 +195,7 @@ line 36: - + Force usage of a new stack frame; this is no longer necessary now. The stack frames are supposed to point to the right @@ -210,7 +210,7 @@ line 52: - + The pointer looks suspicious, but happens to be a valid address. @@ -219,7 +219,7 @@ line 56: - + However, it obviously points to garbage, so we have found our error! (For those unfamiliar with that particular piece of code: @@ -251,7 +251,7 @@ What do you do if a kernel dumped core but you did not expect it, and it is therefore not compiled using config -g? Not everything is lost here. Do not panic! - + Of course, you still need to enable crash dumps. See above on the options you have to specify in order to do this. @@ -271,14 +271,14 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols - + Go and examine the dump as described above. The debugging symbols might be incomplete for some places, as can be seen in the stack trace in the example above where some functions are displayed without line numbers and argument lists. If you need more debugging symbols, remove the appropriate object files and repeat the kgdb session until you know enough. - + All this is not guaranteed to work, but it will do it fine in most cases. @@ -290,14 +290,14 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols - + If you need to do low-level debugging on your kernel, there is an on-line debugger available called DDB. It allows to setting breakpoints, single-stepping kernel functions, examining and changing kernel variables, etc. However, it cannot access kernel source files, and only has access to the global and static symbols, not to the full debug information like kgdb. - + To configure your kernel to include DDB, add the option line @@ -318,7 +318,7 @@ options DDB right at the boot prompt. The kernel will start up in debug mode and enter DDB prior to any device probing. Hence you can even debug the device probe/attach functions. - + The second scenario is a hot-key on the keyboard, usually Ctrl-Alt-ESC. For syscons, this can be remapped; some of the distributed maps do this, so watch out. There is an option available @@ -327,11 +327,11 @@ options DDB in the kernel config file). It is not the default since there are a lot of crappy serial adapters around that gratuitously generate a BREAK condition, for example when pulling the cable. - + The third way is that any panic condition will branch to DDB if the kernel is configured to use it. For this reason, it is not wise to configure a kernel with DDB for a machine running unattended. - + The DDB commands roughly resemble some gdb commands. The first thing you probably need to do is to set a breakpoint: @@ -344,7 +344,7 @@ options DDB a-f need to be preceded with 0x (this is optional for other numbers). Simple expressions are allowed, for example: function-name + 0x103. - + To continue the operation of an interrupted kernel, simply type: @@ -419,11 +419,11 @@ options DDB specifies the size of the data to be written, the first following expression is the address to write to and the remainder is interpreted as data to write to successive memory locations. - + If you need to know the current registers, use: show reg - + Alternatively, you can display a single register value by e.g. p $eax @@ -468,7 +468,7 @@ options DDB is the final way out of disaster and almost the same as hitting the Big Red Button. - + If you need a short command summary, simply type: help @@ -493,7 +493,7 @@ options DDB with all the symbols in it, and the other one is the target machine that simply runs a similar copy of the very same kernel (but stripped of the debugging information). - + You should configure the kernel in question with config -g, include into the configuration, and compile it as usual. This gives a large blurb of a binary, due to the @@ -573,7 +573,7 @@ text_addr = 0xf5109020? (y or n) y Debugging a Console Driver - + Since you need a console driver to run DDB on, things are more complicated if the console driver itself is failing. You might remember the use of a serial console (either with modified boot blocks, or by diff --git a/en_US.ISO8859-1/books/handbook/kernelopts/chapter.sgml b/en_US.ISO8859-1/books/handbook/kernelopts/chapter.sgml index de1012a5e7..b133e948f2 100644 --- a/en_US.ISO8859-1/books/handbook/kernelopts/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/kernelopts/chapter.sgml @@ -1,7 +1,7 @@ @@ -41,39 +41,39 @@ #ifndef THIS_OPTION #define THIS_OPTION (some_default_value) #endif /* THIS_OPTION */ - + This way, an administrator mentioning another value for the option in his config file will take the default out of effect, and replace it with his new value. Clearly, the new value will be substituted into the source code during the preprocessor run, so it must be a valid C expression in whatever context the default value would have been used. - + It is also possible to create value-less options that simply enable or disable a particular piece of code by embracing it in - + #ifdef THAT_OPTION [your code here] #endif - + Simply mentioning THAT_OPTION in the config file (with or without any value) will then turn on the corresponding piece of code. - + People familiar with the C language will immediately recognize that everything could be counted as a “config option” where there is at least a single #ifdef referencing it... However, it's unlikely that many people would put - + options notyet,notdef - + in their config file, and then wonder why the kernel compilation falls over. :-) - + Clearly, using arbitrary names for the options makes it very hard to track their usage throughout the kernel source tree. That is the rationale behind the new-style option scheme, where @@ -83,7 +83,7 @@ options notyet,notdef the usual Makefile dependencies could be applied, and make can determine what needs to be recompiled once an option has been changed. - + The old-style option mechanism still has one advantage for local options or maybe experimental options that have a short anticipated lifetime: since it is easy to add a new #ifdef to the @@ -104,7 +104,7 @@ options notyet,notdef e. g. sys/i386/conf/options.i386), and select an opt_foo.h file where your new option would best go into. - + If there is already something that comes close to the purpose of the new option, pick this. For example, options modifying the overall behaviour of the SCSI subsystem can go into @@ -113,7 +113,7 @@ options notyet,notdef implies its value will go into the corresponding file opt_foo.h. This can be overridden on the right-hand side of a rule by specifying another filename. - + If there is no opt_foo.h already available for the intended new option, invent a new name. Make it @@ -122,12 +122,12 @@ options notyet,notdef file. &man.config.8; will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves.. - + Packing too many options into a single opt_foo.h will cause too many kernel files to be rebuilt when one of the options has been changed in the config file. - + Finally, find out which kernel files depend on the new option. Unless you have just invented your option, and it does not exist anywhere yet, &prompt.user; find /usr/src/sys -name @@ -139,7 +139,7 @@ options notyet,notdef the regular include files, if the defaults are of the form #ifndef NEW_OPTION #define NEW_OPTION (something) #endif in the regular header. - + Adding an option that overrides something in a system header file (i.e., a file sitting in /usr/include/sys/) is almost always a mistake. diff --git a/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml b/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml index da83fe2442..a520480abf 100644 --- a/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml @@ -1,7 +1,7 @@ @@ -30,7 +30,7 @@ options "SC_MOUSE_CHAR=0x03" to move character codes used for mouse cursor off KOI8-R pseudographics range. - + Russian console entry in /etc/rc.conf should looks like: @@ -59,7 +59,7 @@ font8x8=cp866-8x8 Shift+CapsLock. CapsLock LED will indicate RUS mode, not CapsLock mode. - + For each ttyv? entry in /etc/ttys change terminal type from @@ -83,7 +83,7 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure LANG for POSIX &man.setlocale.3; family functions; - + MM_CHARSET for applications MIME character set. @@ -97,17 +97,17 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure Login Class Method - + First of all check your /etc/login.conf have russian login class, this entry may looks like: - + russian:Russian Users Accounts:\ :charset=KOI8-R:\ :lang=ru_RU.KOI8-R:\ :tc=default: - + How to do it with &man.vipw.8; @@ -118,7 +118,7 @@ russian:Russian Users Accounts:\ user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh - + How to do it with &man.adduser.8; @@ -153,7 +153,7 @@ defaultclass = russian - + How to do it with &man.pw.8; @@ -166,12 +166,12 @@ defaultclass = russian Shell Startup Files Method - + If you don't want to use login class method for some reasons, just set this two environment variables in the following shell startup files: - + /etc/profile: @@ -189,7 +189,7 @@ setenv LANG ru_RU.KOI8-R setenv MM_CHARSET KOI8-R - + Alternatively you can add this instructions to @@ -259,7 +259,7 @@ lp|Russian local line printer:\ less than 3.3 first). - + Go to /usr/ports/russian/X.language directory and say @@ -281,7 +281,7 @@ FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/100dpi" If you use high resolution video mode, swap 75 dpi and 100 dpi lines. - + To activate Russian keyboard add diff --git a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml index 6078b29aa4..a95f3724d0 100644 --- a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml @@ -1,7 +1,7 @@ @@ -19,16 +19,16 @@ &rel.current;-RELEASE is vastly more capable and runs all these as well as Oracle8, WordPerfect, StarOffice, Acrobat, Quake, Abuse, IDL, and netrek for Linux and a whole host of other programs. - + There are some Linux-specific operating system features that are not supported on FreeBSD. Linux binaries will not work on FreeBSD if they overly use the Linux /proc filesystem (which is different from the optional FreeBSD /proc filesystem) or i386-specific calls, such as enabling virtual 8086 mode. - + Depending on which version of FreeBSD you are running, how you get Linux mode up will vary somewhat: - + Installing Linux Mode in 3.0-RELEASE and later @@ -210,7 +210,7 @@ linux Installing using the linux_base port - + Most Linux applications use shared libraries, so you are still not done until you install the shared libraries. It is possible to do this by hand, however, it is vastly simpler to just grab the @@ -231,7 +231,7 @@ linux Installing libraries manually - + 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. @@ -262,7 +262,7 @@ linux How to install additional shared libraries - + What if you install the linux_base port and your application still complains about missing shared libraries? How do you know which shared libraries Linux binaries need, and where to @@ -281,7 +281,7 @@ linux libXt.so.3 (DLL Jump 3.1) => /usr/X11/lib/libXt.so.3.1.0 libX11.so.3 (DLL Jump 3.1) => /usr/X11/lib/libX11.so.3.1.0 libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 - + You would need to get all the files from the last column, and put them under /compat/linux, with the names in the first column as symbolic links pointing to them. This means you @@ -321,7 +321,7 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 /compat/linux/lib/libc.so.4.6.29 /compat/linux/lib/libc.so.4 -> libc.so.4.6.29 - + The symbolic link mechanism is only needed for Linux binaries. The FreeBSD runtime linker takes care @@ -333,7 +333,7 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 Configuring the <filename>ld.so</filename> — for FreeBSD 2.2-RELEASE and later - + This section applies only to FreeBSD 2.2-RELEASE and later. Those running 2.1-STABLE should skip this section. @@ -350,7 +350,7 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 extra files you need from various ftp sites. Information on where to look for the various files is appended below. For now, let us assume you know where to get the files. - + Retrieve the following files (all from the same ftp site to avoid any version mismatches), and install them under /compat/linux (i.e. @@ -402,7 +402,7 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 the names of all the shared libraries and should be rerun to recreate this file whenever you install additional shared libraries. - + On 2.1-STABLE do not install /compat/linux/etc/ld.so.cache or run ldconfig; in 2.1-STABLE the syscalls are @@ -471,10 +471,10 @@ Abort Configuring the host name resolver If DNS does not work or you get the messages - + resolv+: "bind" is an invalid keyword resolv+: "hosts" is an invalid keyword - + then you need to configure a /compat/linux/etc/host.conf file containing: @@ -526,7 +526,7 @@ multi on sunsite.unc.edu:/pub/Linux/distributions - + tsx-11.mit.edu:/pub/linux/distributions @@ -538,11 +538,11 @@ multi on ftp.luth.se:/pub/linux/distributions - + ftp.demon.co.uk:/pub/unix/linux - + src.doc.ic.ac.uk:/packages/linux/distributions @@ -666,15 +666,15 @@ multi on slakware/a2/ldso.tgz - + slakware/a2/shlibs.tgz - + slakware/x6/oldlibs.tgz - + slakware/x9/xf_lib.tgz @@ -705,7 +705,7 @@ multi on DOS the cost of upgrading to the Linux version at the time this was written, March 1996, was $45.00. It can be ordered directly from Wolfram at (217) 398-6500 and paid for by credit card. - + Unpacking the Mathematica distribution diff --git a/en_US.ISO8859-1/books/handbook/mail/chapter.sgml b/en_US.ISO8859-1/books/handbook/mail/chapter.sgml index ddf08a6149..1b96df4f34 100644 --- a/en_US.ISO8859-1/books/handbook/mail/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/mail/chapter.sgml @@ -1,7 +1,7 @@ @@ -25,7 +25,7 @@ These are the major programs involved in an E-Mail exchange. A “mailhost” is a server that is responsible for delivering and receiving all email for your host, and possibly your network. - + User program @@ -94,7 +94,7 @@ This handbook section has a complete reference on the Ports system. - + Modify /etc/inetd.conf to load the POP server. @@ -123,7 +123,7 @@ your own domain smallminingco.com - + Get mail delivered to the current DNS name for your host. Ie: dorm6.ahouse.school.edu diff --git a/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml b/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml index c1e4a2467b..8a1103abb4 100644 --- a/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml @@ -1,7 +1,7 @@ @@ -98,7 +98,7 @@ Australia - + In case of problems, please contact the hostmaster hostmaster@au.FreeBSD.org for this domain. @@ -129,7 +129,7 @@ Brazil - + In case of problems, please contact the hostmaster hostmaster@br.FreeBSD.org for this domain. @@ -175,7 +175,7 @@ Canada - + In case of problems, please contact the hostmaster hostmaster@ca.FreeBSD.org for this domain. @@ -211,7 +211,7 @@ In case of problems, please contact the hostmaster hostmaster@cz.FreeBSD.org for this domain. - + Denmark - + In case of problems, please contact the hostmaster hostmaster@dk.FreeBSD.org for this domain. @@ -243,7 +243,7 @@ Estonia - + In case of problems, please contact the hostmaster hostmaster@ee.FreeBSD.org for this domain. @@ -259,7 +259,7 @@ Finland - + In case of problems, please contact the hostmaster hostmaster@fi.FreeBSD.org for this domain. @@ -275,7 +275,7 @@ France - + In case of problems, please contact the hostmaster hostmaster@fr.FreeBSD.org for this domain. @@ -305,7 +305,7 @@ Germany - + In case of problems, please contact the mirrors admins de-bsd-hubs@de.freebsd.org for this domain. @@ -351,7 +351,7 @@ Hong Kong - + @@ -365,7 +365,7 @@ Ireland - + In case of problems, please contact the hostmaster hostmaster@ie.FreeBSD.org for this domain. @@ -381,7 +381,7 @@ Israel - + In case of problems, please contact the hostmaster hostmaster@il.FreeBSD.org for this domain. @@ -402,7 +402,7 @@ Japan - + In case of problems, please contact the hostmaster hostmaster@jp.FreeBSD.org for this domain. @@ -443,7 +443,7 @@ Korea - + In case of problems, please contact the hostmaster hostmaster@kr.FreeBSD.org for this domain. @@ -481,7 +481,7 @@ Netherlands - + In case of problems, please contact the hostmaster hostmaster@nl.FreeBSD.org for this domain. @@ -497,7 +497,7 @@ New Zealand - + In case of problems, please contact the hostmaster hostmaster@nz.FreeBSD.org for this domain. @@ -512,7 +512,7 @@ Poland - + In case of problems, please contact the hostmaster hostmaster@pl.FreeBSD.org for this domain. @@ -528,7 +528,7 @@ Portugal - + In case of problems, please contact the hostmaster hostmaster@pt.FreeBSD.org for this domain. @@ -549,7 +549,7 @@ Russia - + In case of problems, please contact the hostmaster hostmaster@ru.FreeBSD.org for this domain. @@ -595,7 +595,7 @@ South Africa - + In case of problems, please contact the hostmaster hostmaster@za.FreeBSD.org for this domain. @@ -621,7 +621,7 @@ Slovak Republic - + In case of problems, please contact the hostmaster hostmaster@sk.FreeBSD.org for this domain. @@ -635,7 +635,7 @@ Slovenia - + In case of problems, please contact the hostmaster hostmaster@si.FreeBSD.org for this domain. @@ -651,7 +651,7 @@ Spain - + In case of problems, please contact the hostmaster hostmaster@es.FreeBSD.org for this domain. @@ -666,7 +666,7 @@ Sweden - + In case of problems, please contact the hostmaster hostmaster@se.FreeBSD.org for this domain. @@ -723,7 +723,7 @@ Thailand - + @@ -736,7 +736,7 @@ Ukraine - + @@ -749,7 +749,7 @@ UK - + In case of problems, please contact the hostmaster hostmaster@uk.FreeBSD.org for this domain. @@ -780,7 +780,7 @@ USA - + In case of problems, please contact the hostmaster hostmaster@FreeBSD.org for this domain. @@ -829,7 +829,7 @@ South Africa - + Hostmaster hostmaster@internat.FreeBSD.org for this domain. @@ -850,7 +850,7 @@ Brazil - + Hostmaster hostmaster@br.FreeBSD.org for this domain. @@ -866,7 +866,7 @@ Finland - + @@ -885,7 +885,7 @@ CTM/FreeBSD is available via anonymous FTP from the following mirror sites. If you choose to obtain CTM via anonymous FTP, please try to use a site near you. - + In case of problems, please contact &a.phk;. @@ -904,7 +904,7 @@ Germany, Trier - + @@ -917,7 +917,7 @@ South Africa, backup server for old deltas - + @@ -930,7 +930,7 @@ Taiwan/R.O.C, Chiayi - + @@ -982,7 +982,7 @@ Australia - + @@ -995,7 +995,7 @@ Brazil - + @@ -1057,7 +1057,7 @@ Denmark - + @@ -1083,7 +1083,7 @@ Finland - + @@ -1114,7 +1114,7 @@ Germany - + @@ -1137,7 +1137,7 @@ Iceland - + @@ -1150,7 +1150,7 @@ Japan - + @@ -1184,7 +1184,7 @@ Korea - + @@ -1198,7 +1198,7 @@ Netherlands - + @@ -1216,7 +1216,7 @@ Norway - + @@ -1229,7 +1229,7 @@ Poland - + @@ -1242,7 +1242,7 @@ Russia - + @@ -1260,7 +1260,7 @@ Slovak Republic - + @@ -1291,7 +1291,7 @@ South Africa - + @@ -1322,7 +1322,7 @@ Sweden - + @@ -1335,7 +1335,7 @@ Taiwan - + @@ -1359,7 +1359,7 @@ Ukraine - + @@ -1373,7 +1373,7 @@ United Kingdom - + @@ -1391,7 +1391,7 @@ USA - + @@ -1453,7 +1453,7 @@ - + The following CVSup site is especially designed for CTM users. Unlike the other CVSup mirrors, it is kept up-to-date by CTM. @@ -1508,7 +1508,7 @@ Sweden - + The path to the files are: /afs/stacken.kth.se/ftp/pub/FreeBSD/ diff --git a/en_US.ISO8859-1/books/handbook/pgpkeys/chapter.sgml b/en_US.ISO8859-1/books/handbook/pgpkeys/chapter.sgml index 66ca51dce0..9f97eb14ff 100644 --- a/en_US.ISO8859-1/books/handbook/pgpkeys/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/pgpkeys/chapter.sgml @@ -1,7 +1,7 @@ @@ -317,7 +317,7 @@ Sb97WRLEYDi686osaGfsuKNA87Rm+q5F+jxeUV4w4szoqp60gGvCbD0KCB2hWraP =QoiM -----END PGP PUBLIC KEY BLOCK----- - + &a.jdp; diff --git a/en_US.ISO8859-1/books/handbook/policies/chapter.sgml b/en_US.ISO8859-1/books/handbook/policies/chapter.sgml index a161306857..084c8f7c50 100644 --- a/en_US.ISO8859-1/books/handbook/policies/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/policies/chapter.sgml @@ -1,7 +1,7 @@ @@ -20,27 +20,27 @@ If a particular portion of the FreeBSD distribution is being maintained by a person or group of persons, they can communicate this fact to the world by adding a - + MAINTAINER= email-addresses - + line to the Makefiles covering this portion of the source tree. - + The semantics of this are as follows: The maintainer owns and is responsible for that code. This means that he is responsible for fixing bugs and answer problem reports pertaining to that piece of the code, and in the case of contributed software, for tracking new versions, as appropriate. - + Changes to directories which have a maintainer defined shall be sent to the maintainer for review before being committed. Only if the maintainer does not respond for an unacceptable period of time, to several emails, will it be acceptable to commit changes without review by the maintainer. However, it is suggested that you try and have the changes reviewed by someone else if at all possible. - + It is of course not acceptable to add a person or group as maintainer unless they agree to assume this duty. On the other hand it doesn't have to be a committer and it can easily be a group of @@ -58,11 +58,11 @@ MAINTAINER= email-addresses actively being maintained outside the FreeBSD project. For historical reasons, we call this contributed software. Some examples are perl, gcc and patch. - + Over the last couple of years, various methods have been used in dealing with this type of software and all have some number of advantages and drawbacks. No clear winner has emerged. - + Since this is the case, after some debate one of these methods has been selected as the “official” method and will be required for future imports of software of this kind. Furthermore, it is @@ -72,7 +72,7 @@ MAINTAINER= email-addresses “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. - + Ultimately, however, it comes down to the people actually doing the work. If using this model is particularly unsuited to the package being dealt with, exceptions to these rules may be granted only with the @@ -93,28 +93,28 @@ MAINTAINER= email-addresses The Tcl embedded programming language will be used as example of how this model works: - + src/contrib/tcl contains the source as distributed by the maintainers of this package. Parts that are entirely not applicable for FreeBSD can be removed. In the case of Tcl, the mac, win and compat subdirectories were eliminated before the import - + src/lib/libtcl contains only a "bmake style" Makefile that uses the standard bsd.lib.mk makefile rules to produce the library and install the documentation. - + src/usr.bin/tclsh contains only a bmake style Makefile which will produce and install the tclsh program and its associated man-pages using the standard bsd.prog.mk rules. - + src/tools/tools/tcl_bmake contains a couple of shell-scripts that can be of help when the tcl software needs updating. These are not part of the built or installed software. - + The important thing here is that the src/contrib/tcl directory is created according to the rules: It is supposed to contain the sources as distributed (on a @@ -133,7 +133,7 @@ MAINTAINER= email-addresses be patched into the FreeBSD checked out version and "committed", as this destroys the vendor branch coherency and makes importing future versions rather difficult as there will be conflicts. - + Since many packages contain files that are meant for compatibility with other architectures and environments that FreeBSD, it is permissible to remove parts of the distribution tree that are of no @@ -148,7 +148,7 @@ MAINTAINER= email-addresses check in such utilities (as necessary) in the src/tools directory along with the port itself so that it is available to future maintainers. - + In the src/contrib/tcl level directory, a file called FREEBSD-upgrade should be added and it should states things like: @@ -177,7 +177,7 @@ MAINTAINER= email-addresses with the contributed source. Rather you should cvs add FREEBSD-upgrade ; cvs ci after the initial import. Example wording from src/contrib/cpio is below: - + This directory contains virgin sources of the original distribution files on a "vendor" branch. Do not, under any circumstances, attempt to upgrade @@ -316,12 +316,12 @@ obrien@FreeBSD.org - 30 March 1997 Contributed by &a.asami;, &a.peter;, and &a.obrien; 9 December 1996. - + If you are adding shared library support to a port or other piece of software that doesn't have one, the version numbers should follow these rules. Generally, the resulting numbers will have nothing to do with the release version of the software. - + The three principles of shared library building are: diff --git a/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml b/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml index 9e35438dd1..1ff8c615df 100644 --- a/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml @@ -1,7 +1,7 @@ @@ -36,13 +36,13 @@ ppp program can be run as and when desired. No PPP interface needs to be compiled into the kernel, as the program can use the generic tunnel device to get data into and out of the kernel. - + From here on out, user ppp will be referred to simply as ppp unless a distinction needs to be made between it and any other PPP client/server software such as pppd. Unless otherwise stated, all commands in this section should be executed as root. - + There are a large number of enhancements in version 2 of ppp. You can discover what version you have by running ppp with no arguments and typing show version at the prompt. It is a simple @@ -66,13 +66,13 @@ Your ISPs phone number(s). - + Your login name and password. This can be either a regular unix style login/password pair, or a PPP PAP or CHAP login/password pair. - + The IP addresses of one or more nameservers. Normally, you will be given two IP numbers. You must have @@ -100,7 +100,7 @@ This IP number is referred to as HISADDR by ppp. - + Your ISP's netmask. If your ISP hasn't given you this information, you can safely use a netmask of mtu 1500 Edit the <filename>/etc/host.conf</filename> file - + This file should contain the following two lines (in this order): @@ -247,7 +247,7 @@ bind Edit the <filename>/etc/hosts</filename>(5) file - + This file should contain the IP addresses and names of machines on your network. At a bare minimum it should contain entries for the machine which will be running ppp. Assuming that your machine @@ -258,7 +258,7 @@ bind 127.0.0.1 localhost 10.0.0.1 foo.bar.com foo - + The first line defines the alias localhost as a synonym for the current machine. Regardless of your own IP address, the IP address for this line should always be Edit the <filename>/etc/resolv.conf</filename> file - + /etc/resolv.conf tells the resolver how to behave. If you are running your own DNS, you may leave this file empty. Normally, you will need to enter the following @@ -294,7 +294,7 @@ domain bar.com and is probably unnecessary. Refer to the resolv.conf manual page for details of other possible entries in this file. - + If you are running PPP version 2 or greater, the enable dns command will tell PPP to request that your ISP confirms the nameserver values. If your ISP supplies different @@ -322,17 +322,17 @@ domain bar.com PPP and Static IP addresses - + You will need to create a configuration file called /etc/ppp/ppp.conf. It should look similar to the example below. - + Lines that end in a : start in the first column, all other lines should be indented as shown using spaces or tabs. - + 1 default: 2 set device /dev/cuaa0 @@ -498,21 +498,21 @@ protocol: ppp - + It is not necessary to add an entry to ppp.linkup when you have a static IP address as your routing table entries are already correct before you connect. You may however wish to create an entry to invoke programs after connection. This is explained later with the sendmail example. - + Example configuration files can be found in the /etc/ppp directory. PPP and Dynamic IP addresses - + If your service provider does not assign static IP numbers, ppp can be configured to negotiate the local and remote addresses. This is done by “guessing” an IP @@ -549,7 +549,7 @@ protocol: ppp - + If you are running version 1.x of PPP, you will also need to create an entry in /etc/ppp/ppp.linkup. ppp.linkup is used after a connection has been @@ -599,7 +599,7 @@ protocol: ppp - + See the pmdemand entry in the files /etc/ppp/ppp.conf.sample and /etc/ppp/ppp.linkup.sample for a detailed @@ -619,7 +619,7 @@ protocol: ppp This section describes setting up ppp in a server role. - + When you configure ppp to receive incoming calls on a machine connected to a LAN, you must decide if you wish to forward packets to the LAN. If you do, you should allocate the @@ -661,7 +661,7 @@ gateway=YES AutoPPP for more information on mgetty. - + PPP permissions @@ -683,7 +683,7 @@ allow users fred mary If this command is used in the default section, it gives the specified users access to everything. - + Setting up a PPP shell for dynamic-IP users @@ -729,7 +729,7 @@ pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup/etc/motd from being displayed. - + Setting up a PPP shell for static-IP users @@ -751,7 +751,7 @@ pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialupmary's shell should be /etc/ppp/ppp-mary). - + Setting up ppp.conf for dynamic-IP users @@ -782,7 +782,7 @@ ttyd1: unique IP address from your pool of IP addresses for dynamic users. - + Setting up <filename>ppp.conf</filename> for static-IP users @@ -820,7 +820,7 @@ sam: mary: add 203.14.103.0 netmask 255.255.255.0 HISADDR - + More on <command>mgetty</command>, AutoPPP, and MS extensions @@ -921,7 +921,7 @@ set nbns 203.14.100.5 PAP and CHAP authentication - + Some ISPs set their system up so that the authentication part of your connection is done using either of the PAP or CHAP authentication mechanisms. If this is the case, your ISP will not @@ -996,7 +996,7 @@ set nbns 203.14.100.5 Changing your <command>ppp</command> configuration on the fly - + It is possible to talk to the ppp program while it is running in the background, but only if a suitable diagnostic port has been set up. To do this, add the following line @@ -1004,7 +1004,7 @@ set nbns 203.14.100.5 set server /var/run/ppp-tun%d DiagnosticPassword 0177 - + This will tell PPP to listen to the specified unix-domain socket, asking clients for the specified password before allowing access. The %d in the name is replaced with the @@ -1123,29 +1123,29 @@ sendmail_flags="-bd" Ensure that the tun device is built into your kernel. - + Ensure that the tunX device file is available in the /dev directory. - + Create an entry in /etc/ppp/ppp.conf. The pmdemand example should suffice for most ISPs. - + If you have a dynamic IP address, create an entry in /etc/ppp/ppp.linkup. - + Update your /etc/rc.conf (or sysconfig) file. - + Create a start_if.tun0 script if you require demand dialing. @@ -1159,34 +1159,34 @@ sendmail_flags="-bd" Ensure that the tun device is built into your kernel. - + Ensure that the tunX device file is available in the /dev directory. - + Create an entry in /etc/passwd (using the &man.vipw.8; program). - + Create a profile in this users home directory that runs ppp -direct direct-server or similar. - + Create an entry in /etc/ppp/ppp.conf. The direct-server example should suffice. - + Create an entry in /etc/ppp/ppp.linkup. - + Update your /etc/rc.conf (or sysconfig) file. @@ -1219,9 +1219,9 @@ sendmail_flags="-bd" Before you start setting up PPP on your machine make sure that pppd is located in /usr/sbin and directory /etc/ppp exists. - + pppd can work in two modes: - + as a “client”, i.e. you want to connect your machine @@ -1237,10 +1237,10 @@ sendmail_flags="-bd" In both cases you will need to set up an options file (/etc/ppp/options or ~/.ppprc if you have more then one user on your machine that uses PPP). - + You also will need some modem/serial software (preferably kermit) so you can dial and establish connection with remote host. - + Working as a PPP client @@ -1272,11 +1272,11 @@ defaultroute # put this if you want that PPP server will be your enter your user name and password (or whatever is needed to enable PPP on the remote host) - + Exit kermit (without hanging up the line). - + enter: @@ -1654,12 +1654,12 @@ exit 1 Setting up a SLIP Client Contributed by &a.asami; 8 Aug 1995. - + The following is one way to set up a FreeBSD machine for SLIP on a static host network. For dynamic hostname assignments (i.e., your address changes each time you dial up), you probably need to do something much fancier. - + First, determine which serial port your modem is connected to. I have a symbolic link to /dev/modem from /dev/cuaa1, and only use the modem name in my @@ -1681,7 +1681,7 @@ pseudo-device sl 1 in your kernel's config file. It is included in the GENERIC kernel, so this will not be a problem unless you deleted it. - + Things you have to do only once @@ -1707,7 +1707,7 @@ pseudo-device sl 1 in your /etc/host.conf. Otherwise, funny things may happen. - + Edit the file /etc/rc.conf. Note that you should edit the file /etc/sysconfig @@ -1757,7 +1757,7 @@ defaultrouter=slip-gateway - + Make a file /etc/resolv.conf which contains: @@ -1821,7 +1821,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a am just too lazy. - + Leave the kermit there (you can suspend it by z) and as root, type: @@ -1835,7 +1835,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a - + How to shutdown the connection @@ -1869,12 +1869,12 @@ output ***\x0d, echo \x0aCONNECTED\x0a slattach (I have no idea why this can be fatal, but adding this flag solved the problem for at least one person) - + Using instead of (might be hard to see the difference on some fonts). - + Try ifconfig sl0 to see your interface status. I get: @@ -1925,7 +1925,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438 not answer all of your questions, and the author cannot be responsible if you damage your system or lose data due to attempting to follow the suggestions here. - + This guide was originally written for SLIP Server services on a FreeBSD 1.x system. It has been modified to reflect changes in the pathnames and the removal of the SLIP interface compression flags in @@ -1933,7 +1933,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438 between FreeBSD versions. If you do encounter mistakes in this document, please email the author with enough information to help correct the problem. - + Prerequisites @@ -1981,7 +1981,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438 An Example of a SLIP Server Login - + For example, if a SLIP user ID were Shelmerg, Shelmerg's entry in /etc/master.passwd would look something like @@ -2107,10 +2107,10 @@ pseudo-device sl 2 <filename>slip.hosts</filename> Configuration - + /etc/sliphome/slip.hosts contains lines which have at least four items, separated by whitespace: - + SLIP user's login ID @@ -2129,7 +2129,7 @@ pseudo-device sl 2 Network mask - + The local and remote addresses may be host names (resolved to IP addresses by /etc/hosts or by the domain name service, depending on your specifications in @@ -2147,7 +2147,7 @@ pseudo-device sl 2 Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp At the end of the line is one or more of the options. - + — no header compression @@ -2168,7 +2168,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp - + Note that sliplogin under early releases of FreeBSD 2 ignored the options that FreeBSD 1.x recognized, so the options , , @@ -2208,7 +2208,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp <filename>slip.login</filename> Configuration - + The typical /etc/sliphome/slip.login file looks like this: @@ -2288,7 +2288,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp <filename>slip.logout</filename> Configuration - + /etc/sliphome/slip.logout is not strictly needed (unless you are implementing “proxy ARP”), but if you decide to create it, this is an example of a basic @@ -2351,7 +2351,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp Static Routes - + Adding static routes to your nearest default routers can be troublesome (or impossible, if you do not have authority to do so...). If you have a multiple-router network in your organization, @@ -2364,7 +2364,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp Running <command>gated</command> - + An alternative to the headaches of static routes is to install gated on your FreeBSD SLIP server and configure it to use the appropriate routing protocols (RIP/OSPF/BGP/EGP) to @@ -2462,7 +2462,7 @@ import proto rip interface ed { - + Piero Serini diff --git a/en_US.ISO8859-1/books/handbook/printing/chapter.sgml b/en_US.ISO8859-1/books/handbook/printing/chapter.sgml index 22ac77e354..172951b3c8 100644 --- a/en_US.ISO8859-1/books/handbook/printing/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/printing/chapter.sgml @@ -1,7 +1,7 @@ @@ -23,10 +23,10 @@ What the Spooler Does - + LPD controls everything about a host's printers. It is responsible for a number of things: - + It controls access to attached printers and printers attached to @@ -155,13 +155,13 @@ accept data to print instead of a serial or parallel interface, see Printers With Networked Data Stream Interaces. - + 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 get the printer working. - + Hardware Setup @@ -177,7 +177,7 @@ Ports and Cables - + Nearly all printers you can get for a PC today support one or both of the following interfaces: @@ -251,7 +251,7 @@ Parallel Ports - + To hook up a printer using a parallel interface, connect the Centronics cable between the printer and the computer. The instructions that came with the printer, the computer, or both @@ -264,12 +264,12 @@ Serial Ports - + To hook up a printer using a serial interface, connect the proper serial cable between the printer and the computer. The instructions that came with the printer, the computer, or both should give you complete guidance. - + If you are unsure what the “proper serial cable” is, you may wish to try one of the following alternatives: @@ -339,7 +339,7 @@ Communications gives some suggestions on how to do this. - + Set up LPD for the printer by modifying the file /etc/printcap. Section Kernel Configuration - + The operating system kernel is compiled to work with a specific set of devices. The serial or parallel interface for your printer is a part of that set. Therefore, it might be necessary to add @@ -365,22 +365,22 @@ Where N is the number of the serial port, starting from zero. If you see output similar to the following: - + sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A then the kernel supports the port. - + To find out if the kernel supports a parallel interface, type: - + &prompt.root; dmesg | grep lptN Where N is the number of the parallel port, starting from zero. If you see output similar to the following lpt0 at 0x378-0x37f on isa then the kernel supports the port. - + You might have to reconfigure your kernel in order for the operating system to recognize and use the parallel or serial port you are using for the printer. @@ -436,7 +436,7 @@ sio2: type 16550A - + Setting the Communication Mode for the Parallel Port @@ -535,7 +535,7 @@ device lpt0 at isa? port? tty vector lptintr your system boots. See &man.lptcontrol.8; for more information. - + Checking Printer Communications @@ -722,7 +722,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none Enabling the Spooler: The <filename>/etc/printcap</filename> File - + At this point, your printer should be hooked up, your kernel configured to communicate with it (if necessary), and you have been able to send some simple data to the printer. Now, we are ready to @@ -743,7 +743,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none The simple spooler configuration consists of the following steps: - + Pick a name (and a few convenient aliases) for the printer, @@ -792,7 +792,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none linkend="printing-troubleshooting">Troubleshooting. - + Language-based printers, such as PostScript printers, cannot directly print plain text. The simple setup outlined above and @@ -800,7 +800,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none installing such a printer you will print only files that the printer can understand. - + Users often expect that they can print plain text to any of the printers installed on your system. Programs that interface to LPD to do their printing usually make the same assumption. If you are @@ -861,7 +861,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4: S, panasonic, and Panasonic KX-P4455 PostScript v51.4. - + Suppressing Header Pages @@ -893,7 +893,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ single TAB. Every line in an entry except the last ends in a backslash character. - + Making the Spooling Directory @@ -1108,7 +1108,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ :sh:sd=/var/spool/lpd/bamboo:\ :lp=/dev/ttyd5:fs#0x82000c1:xs#0x820: - + Installing the Text Filter @@ -1174,7 +1174,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ :lp=/dev/ttyd5:fs#0x82000e1:xs#0x820:\ :if=/usr/local/libexec/if-simple: - + Trying It Out @@ -1224,7 +1224,7 @@ $%&'()*+,-./01234567 If the printer did not work, see the next section, Troubleshooting. - + Troubleshooting @@ -1533,7 +1533,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\ This section tells you how to use printers you have setup with FreeBSD. Here is an overview of the user-level commands: - + &man.lpr.1; @@ -1545,7 +1545,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\ &man.lpq.1; - + Check printer queues @@ -1553,7 +1553,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\ &man.lprm.1; - + Remove jobs from a printer's queue @@ -1597,7 +1597,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\ To select a specific printer, type: &prompt.user; lpr -P printer-name filename ... - + This example prints a long listing of the current directory to the printer named rattan: @@ -1676,7 +1676,7 @@ kelly: 2nd [job 010rose] mary: 3rd [job 011rose] /home/orchid/mary/research/venus/alpha-regio/mapping 78519 bytes - + Removing Jobs @@ -1707,7 +1707,7 @@ mary: 3rd [job 011rose] you. - + lprm user @@ -1717,7 +1717,7 @@ mary: 3rd [job 011rose] users' jobs; you can remove only your own jobs. - + lprm @@ -1771,7 +1771,7 @@ cfA013rose dequeued Formatting and Conversion Options - + The following &man.lpr.1; options control formatting of the files in the job. Use these options if the job does not contain plain text or if you want plain text formatted through the @@ -1796,7 +1796,7 @@ cfA013rose dequeued linkend="printing-advanced-convfilters">Conversion Filters gives details. - + @@ -1919,7 +1919,7 @@ cfA013rose dequeued Job Handling Options - + The following options to &man.lpr.1; tell LPD to handle the job specially: @@ -1999,7 +1999,7 @@ cfA013rose dequeued Header Page Options - + These options to &man.lpr.1; adjust the text that normally appears on a job's header page. If header pages are suppressed for the destination printer, these options have no effect. See section @@ -2059,11 +2059,11 @@ cfA013rose dequeued Start and stop the printers - + Enable and disable their queues - + Rearrange the order of the jobs in each queue. @@ -2102,7 +2102,7 @@ cfA013rose dequeued still submit jobs if the queue's enabled. - + clean printer-name @@ -2116,7 +2116,7 @@ cfA013rose dequeued removes them. - + disable printer-name @@ -2134,7 +2134,7 @@ cfA013rose dequeued enable command. - + down printer-name message @@ -2148,7 +2148,7 @@ cfA013rose dequeued status. - + enable printer-name @@ -2158,7 +2158,7 @@ cfA013rose dequeued the printer will not print anything until it is started. - + help command-name @@ -2170,7 +2170,7 @@ cfA013rose dequeued commands available. - + restart printer-name @@ -2185,7 +2185,7 @@ cfA013rose dequeued start. - + start printer-name @@ -2195,7 +2195,7 @@ cfA013rose dequeued queue. - + stop printer-name @@ -2207,7 +2207,7 @@ cfA013rose dequeued queue. - + topq printer-name job-or-username @@ -2222,7 +2222,7 @@ cfA013rose dequeued printer-name. - + up printer-name @@ -2249,7 +2249,7 @@ cfA013rose dequeued This section describes filters for printing specially formatted files, header pages, printing across networks, and restricting and accounting for printer usage. - + Filters @@ -2301,7 +2301,7 @@ cfA013rose dequeued should do to overcome this problem. I recommend reading this section if you have a PostScript printer. - + PostScript is a popular output format for many programs. Even some people (myself included) write PostScript code directly. But @@ -2333,7 +2333,7 @@ cfA013rose dequeued linkend="printing-advanced-header-pages">Header Pages), you can probably skip that section altogether. - + Section lpf: a Text Filter describes lpf, a fairly @@ -2348,7 +2348,7 @@ cfA013rose dequeued How Filters Work - + As mentioned before, a filter is an executable program started by LPD to handle the device-dependent part of communicating with the printer. @@ -2370,10 +2370,10 @@ cfA013rose dequeued if filter (this is mostly true: see Output Filters for details). - + There are three kinds of filters you can specify in /etc/printcap: - + The text filter, confusingly called the @@ -2514,7 +2514,7 @@ cfA013rose dequeued arguments. - + Filters should also exit with the following exit status: @@ -2546,13 +2546,13 @@ cfA013rose dequeued - + The text filter that comes with the FreeBSD release, /usr/libexec/lpr/lpf, takes advantage of the page width and length arguments to determine when to send a form feed and how to account for printer usage. It uses the login, host, and accounting file arguments to make the accounting entries. - + If you are shopping for filters, see if they are LPD-compatible. If they are, they must support the argument lists described above. If you plan on writing filters for general use, then have them @@ -2561,7 +2561,7 @@ cfA013rose dequeued Accommodating Plain Text Jobs on PostScript Printers - + If you are the only user of your computer and PostScript (or other language-based) printer, and you promise to never send plain text to your printer and to never use features of various programs @@ -2579,7 +2579,7 @@ cfA013rose dequeued will convert the text into PostScript and print the result. How do we do this? - + If you have got a serial printer, a great way to do it is to install lprps. lprps is a PostScript printer filter which performs two-way communication with @@ -2649,7 +2649,7 @@ fi Simulating PostScript on Non-PostScript Printers - + PostScript is the de facto standard for high quality typesetting and printing. PostScript is, however, an expensive standard. Thankfully, Alladin @@ -2737,7 +2737,7 @@ exit 2 Conversion Filters - + After completing the simple setup described in Simple Printer Setup, the first thing you will probably want to do is install conversion filters for @@ -2777,7 +2777,7 @@ exit 2 text, the filter converts the file into a format the printer can understand. - + Which Conversions Filters Should I Install? @@ -2869,7 +2869,7 @@ exit 2 lpr -g mean “print Printerleaf files.” - + Installing Conversion Filters @@ -3129,7 +3129,7 @@ dvilj2p -M1 -q -e- dfhp$$.dvi cleanup exit 0 - + Automated Conversion: An Alternative To Conversion Filters @@ -3161,7 +3161,7 @@ exit 0 Output Filters - + The LPD spooling system supports one other type of filter that we have not yet explored: an output filter. An output filter is intended for printing plain text only, like the text filter, but @@ -3197,7 +3197,7 @@ exit 0 question. - + Do not be seduced by an output filter's simplicity. If you would like each file in a job to start on a different page an output filter will not work. Use a text filter (also @@ -3244,7 +3244,7 @@ exit 0 <command>lpf</command>: a Text Filter - + The program /usr/libexec/lpr/lpf that comes with FreeBSD binary distribution is a text filter (input filter) that can indent output (job submitted with lpr @@ -3298,15 +3298,15 @@ exit 0 Enabling Header Pages - + In the Simple Printer Setup, we turned off header pages by specifying sh (meaning “suppress header”) in the /etc/printcap file. To enable header pages for a printer, just remove the sh capability. - + Sounds too easy, right? - + You are right. You might have to provide an output filter to send initialization strings to the printer. Here is an example output filter for Hewlett Packard PCL-compatible @@ -3357,7 +3357,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ Controlling Header Pages - + By enabling header pages, LPD will produce a long header, a full page of large letters identifying the user, host, and job. Here is an example (kelly printed the job @@ -3424,7 +3424,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995 - + Also by default, LPD prints the header page first, then the job. To reverse that, specify hl (header last) in /etc/printcap. @@ -3432,13 +3432,13 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995 Accounting for Header Pages - + Using LPD's built-in header pages enforces a particular paradigm when it comes to printer accounting: header pages must be free of charge. Why? - + Because the output filter is the only external program that will have control when the header page is printed that could do accounting, and it is not provided with any user or @@ -3458,9 +3458,9 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995 header pages with lpr -h, they will still get them and be charged for them since LPD does not pass any knowledge of the option to any of the filters. - + So, what are your options? - + You can: @@ -3501,7 +3501,7 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995 Header Pages on PostScript Printers - + As described above, LPD can generate a plain text header page suitable for many printers. Of course, PostScript cannot directly print plain text, so the header page feature of LPD is @@ -3684,7 +3684,7 @@ done linkend="printing-advanced-network-rm">Printers Installed on Remote Hosts tells how to do this. - + Accessing a printer attached directly to a network. The printer has a network interface in addition (or in place of) a @@ -3716,7 +3716,7 @@ done Printers Installed on Remote Hosts - + The LPD spooling system has built-in support for sending jobs to other hosts also running LPD (or are compatible with LPD). This feature enables you to install a printer on one host and make it @@ -3745,7 +3745,7 @@ done Then, on the other hosts you want to have access to the printer, make an entry in their /etc/printcap files with the following: - + Name the entry anything you want. For simplicity, though, @@ -3779,7 +3779,7 @@ done That is it. You do not need to list conversion filters, page dimensions, or anything else in the /etc/printcap file. - + Here is an example. The host rose has two printers, bamboo and rattan. We will enable users on the host orchid to print to those printers. @@ -3789,7 +3789,7 @@ done Pages). It already had the entry for the printer teak; we have added entries for the two printers on the host rose: - + # # /etc/printcap for host orchid - added (remote) printers on rose @@ -3840,7 +3840,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ Printers with Networked Data Stream Interfaces - + Often, when you buy a network interface card for a printer, you can get two versions: one which emulates a spooler (the more expensive version), or one which just lets you send data to it as if @@ -3920,7 +3920,7 @@ exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100 Restricting Multiple Copies - + The LPD system makes it easy for users to print multiple copies of a file. Users can print jobs with lpr -#5 (for example) and get five copies of each file in the job. Whether @@ -3933,8 +3933,8 @@ exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100-# option, they will see: lpr: multiple copies are not allowed - - + + Note that if you have set up access to a printer remotely (see section Printers Installed on Remote Hosts), you need the @@ -3971,7 +3971,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ /etc/printcap (and while we are at it, let us disable multiple copies for the printer teak): - + # # /etc/printcap for host orchid - no multiple copies for local @@ -4002,7 +4002,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ Restricting Access To Printers - + You can control who can print to what printers by using the UNIX group mechanism and the rg capability in /etc/printcap. Just place the users you want @@ -4014,7 +4014,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ lpr: Not a member of the restricted group if they try to print to the controlled printer. - + As with the sc (suppress multiple copies) capability, you need to specify rg on remote hosts that also have access to your printers, if you feel it is @@ -4058,7 +4058,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ Controlling Sizes of Jobs Submitted - + If you have many users accessing the printers, you probably need to put an upper limit on the sizes of the files users can submit to print. After all, there is only so much free space on the @@ -4076,7 +4076,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ The limit applies to files in a job, and not the total job size. - + LPD will not refuse a file that is larger than the limit you place on a printer. Instead, it will queue as much of the file up to the limit, which will then get printed. The rest will be @@ -4128,7 +4128,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ Restricting Jobs from Remote Printers - + The LPD spooling system provides several ways to restrict print jobs submitted from remote hosts: @@ -4296,7 +4296,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ Quick and Dirty Printer Accounting - + FreeBSD comes with two programs that can get you set up with simple periodic accounting right away. They are the text filter lpf, described in section af capability in /etc/printcap, and if not specified as an absolute path, is relative to the spooling directory. - + LPD starts lpf with page width and length arguments (from the pw and pl capabilities). lpf uses these arguments to @@ -4353,7 +4353,7 @@ rose:root 26.00 12 $ 0.52 total 337.00 154 $ 6.74 These are the arguments &man.pac.8; expects: - + @@ -4427,7 +4427,7 @@ total 337.00 154 $ 6.74 - + In the default summary that &man.pac.8; produces, you see the number of pages printed by each user from various hosts. If, at your site, host does not matter (because users can use any host), @@ -4458,7 +4458,7 @@ total 337.00 154 $ 6.74 makes each page cost one dollar and fifty cents. You can really rake in the profits by using this option. - + Finally, running pac -s will save the summary information in a summary accounting file, which is named the same as the printer's accounting file, but with _sum @@ -4470,7 +4470,7 @@ total 337.00 154 $ 6.74 How Can You Count Pages Printed? - + In order to perform even remotely accurate accounting, you need to be able to determine how much paper a job uses. This is the essential problem of printer accounting. @@ -4488,20 +4488,20 @@ total 337.00 154 $ 6.74 to examine lpf's source code. How do you handle other file formats, though? - + Well, for DVI-to-LaserJet or DVI-to-PostScript conversion, you can have your filter parse the diagnostic output of dvilj or dvips and look to see how many pages were converted. You might be able to do similar things with other file formats and conversion programs. - + But these methods suffer from the fact that the printer may not actually print all those pages. For example, it could jam, run out of toner, or explode—and the user would still get charged. So, what can you do? - + There is only one sure way to do accurate accounting. Get a printer that can tell you how much paper it uses, and attach it via a serial line or @@ -4528,15 +4528,15 @@ total 337.00 154 $ 6.74 many of its shortcomings, which naturally leads to the question: “What other spooling systems are out there (and work with FreeBSD)?” - + Unfortunately, I have located only two alternatives—and they are almost identical to each other! They are: - + PLP, the Portable Line Printer Spooler System - + PLP was based on software developed by Patrick Powell and then maintained by an Internet-wide group of developers. The main site @@ -4579,7 +4579,7 @@ total 337.00 154 $ 6.74 LPRng - + LPRng, which purportedly means “LPR: the Next Generation” is a complete rewrite of PLP. Patrick Powell @@ -4596,12 +4596,12 @@ total 337.00 154 $ 6.74 I would like to thank the following people who have assisted in the development of this document: - + Daniel Eischen deischen@iworks.interworks.org - + For providing a plethora of HP filter programs for perusal. @@ -4610,7 +4610,7 @@ total 337.00 154 $ 6.74 &a.jehamby; - + For the Ghostscript-to-HP filter. @@ -4618,7 +4618,7 @@ total 337.00 154 $ 6.74 &a.jfieber; - + For debugging why printing from Windows 95 to a FreeBSD system simulating a PostScript printer with Ghostscript didn't @@ -4641,7 +4641,7 @@ total 337.00 154 $ 6.74 My wife, Mary Kelly urquhart@argyre.colorado.edu - + For allowing me to spend more time with FreeBSD than with her. diff --git a/en_US.ISO8859-1/books/handbook/security/chapter.sgml b/en_US.ISO8859-1/books/handbook/security/chapter.sgml index 8aba1b63ad..579dbfe39c 100644 --- a/en_US.ISO8859-1/books/handbook/security/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/security/chapter.sgml @@ -1,7 +1,7 @@ @@ -12,7 +12,7 @@ Contributed by &a.wollman; 24 September 1995. - + In order to protect the security of passwords on UN*X systems from being easily exposed, passwords have traditionally been scrambled in some way. Starting with Bell Labs' Seventh Edition Unix, passwords were @@ -27,7 +27,7 @@ available, because national governments in many places like to place restrictions on cross-border transport of DES and other encryption software. - + So, the FreeBSD team was faced with a dilemma: how could we provide compatibility with all those UNIX systems out there while still not running afoul of the law? We decided to take a dual-track approach: we @@ -43,7 +43,7 @@ Because neither of these functions involve encryption, they are believed to be exportable from the US and importable into many other countries. - + Meanwhile, work was also underway on the DES-based password hash function. First, a version of the crypt function which was written outside the US was imported, thus synchronizing the US @@ -128,7 +128,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -> libdescrypt_p.a - + 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 “UNIX password”. The @@ -140,14 +140,14 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -> libdescrypt_p.akeyinit program) which it uses to generate one-time passwords; we will call it a “secret password” or just unqualified “password”. - + The secret password does not necessarily have anything to do with your UNIX password (while they can be the same, this is not recommended). While UNIX passwords are limited to eight characters in length, your S/Key secret password can be as long as you like; I use seven-word phrases. In general, the S/Key system operates completely independently of the UNIX password system. - + There are in addition two other sorts of data involved in the S/Key system; one is called the “seed” or (confusingly) “key”, and consists of two letters and five digits, and the @@ -165,7 +165,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -> libdescrypt_p.a - + There are four programs involved in the S/Key system which we will discuss below. The key program accepts an iteration count, a seed, and a secret password, and generates a one-time password. @@ -180,7 +180,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -> libdescrypt_p.alogin program is also capable of disallowing the use of UNIX passwords on connections coming from specified addresses. - + There are four different sorts of operations we will cover. The first is using the keyinit program over a secure connection to set up S/Key for the first time, or to change your @@ -193,7 +193,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -> libdescrypt_p.a - + Secure connection initialization @@ -294,7 +294,7 @@ s/key 92 hi52030 annotation (s/key required), indicating that only S/Key one-time passwords will be accepted. - + Generating a single one-time password @@ -415,16 +415,16 @@ permit port ttyd0 Services such as remote login, remote copy, secure inter-system file copying and other high-risk tasks are made considerably safer and more controllable. - + The following instructions can be used as a guide on how to set up Kerberos as distributed for FreeBSD. However, you should refer to the relevant manual pages for a complete description. - + In FreeBSD, the Kerberos is not that from the original 4.4BSD-Lite, distribution, but eBones, which had been previously ported to FreeBSD 1.1.5.1, and was sourced from outside the USA/Canada, and is thus available to system owners outside those countries. - + For those needing to get a legal foreign distribution of this software, please do not get it from a USA or Canada site. You will get that site in big trouble! A @@ -594,7 +594,7 @@ Principal's new key version = 1 Edit O.K. Principal name: <---- null entry here will cause an exit - + Creating the server file @@ -668,7 +668,7 @@ Principal's new key version = 1 Edit O.K. Principal name: <---- null entry here will cause an exit - + Testing it all out @@ -729,7 +729,7 @@ Verifying password New Password for jane: Password changed. - + Adding <command>su</command> privileges @@ -798,7 +798,7 @@ Principal: jane.root@GRONDAR.ZA Issued Expires Principal May 2 20:43:12 May 3 04:43:12 krbtgt.GRONDAR.ZA@GRONDAR.ZA - + Using other commands @@ -861,15 +861,15 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 Firewalls - + Contributed by &a.gpalmer; and &a.alex;. - + Firewalls are an area of increasing interest for people who are connected to the Internet, and are even finding applications on private networks to provide enhanced security. This section will hopefully explain what firewalls are, how to use them, and how to use the facilities provided in the FreeBSD kernel to implement them. - + People often think that having a firewall between your companies internal network and the “Big Bad Internet” will solve all @@ -883,7 +883,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 firewall to be impenetrable, you have just made the crackers job that bit easier. - + What is a firewall? @@ -912,7 +912,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 Packet filtering routers - + A router is a machine which forwards packets between two or more networks. A packet filtering router has an extra piece of code in its kernel, which compares each packet to a list of rules before @@ -968,7 +968,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 depends largely on what proxy software you choose. - + What does IPFW allow me to do? @@ -993,7 +993,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 IPFW, and the same commands and techniques should be used in this situation. - + Enabling IPFW on FreeBSD @@ -1027,7 +1027,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 happen. - + options IPFIREWALL_VERBOSE_LIMIT=10 @@ -1055,7 +1055,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 the firewall code automatically includes accounting facilities. - + Configuring IPFW @@ -1075,7 +1075,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 Altering the IPFW rules - + The syntax for this form of the command is: ipfw @@ -1088,10 +1088,10 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 addresses options - + There is one valid flag when using this form of the command: - + -N @@ -1101,7 +1101,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 - + The command given can be shortened to the shortest unique form. The valid commands are: @@ -1124,7 +1124,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 - + Previous versions of IPFW used separate firewall and accounting entries. The present version provides packet accounting with each firewall entry. @@ -1181,7 +1181,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 - + Each action will be recognized by the shortest unambiguous prefix. @@ -1221,9 +1221,9 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 - + The address specification is: - + from address/maskport @@ -1256,7 +1256,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 address:mask-pattern - + A valid hostname may be specified in place of the IP address. is a decimal number representing how many bits in the address mask should be set. @@ -1284,7 +1284,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 with a list, but the range must always be specified first. The options available are: - + frag @@ -1382,7 +1382,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 Listing the IPFW rules - + The syntax for this form of the command is: ipfw @@ -1391,7 +1391,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 -N l - + There are three valid flags when using this form of the command: @@ -1428,13 +1428,13 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 Flushing the IPFW rules - + The syntax for flushing the chain is: ipfw flush - + This causes all entries in the firewall chain to be removed except the fixed default policy enforced by the kernel (index 65535). Use caution when flushing rules, the default deny policy @@ -1444,21 +1444,21 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 Clearing the IPFW packet counters - + The syntax for clearing one or more packet counters is: ipfw zero index - + When used without an index argument, all packet counters are cleared. If an index is supplied, the clearing operation only affects a specific chain entry. - + Example commands for ipfw @@ -1554,7 +1554,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 where most of the security sensitive services are, like finger, SMTP (mail) and telnet. - + Block all incoming UDP traffic. There are very few useful services that travel over UDP, and what useful diff --git a/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml b/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml index 63d630b4d7..7e45aa5283 100644 --- a/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml @@ -1,7 +1,7 @@ @@ -15,7 +15,7 @@ This section should give you some general information about serial ports. If you do not find what you want here, check into the Terminal and Dialup sections of the handbook. - + The ttydX (or cuaaX) device is the regular device you will want to open for your applications. When a @@ -38,17 +38,17 @@ Now, an application will have these settings by default when it opens ttyd5. It can still change these settings to its liking, though. - + You can also prevent certain settings from being changed by an application by making adjustments to the “lock state” device. For example, to lock the speed of ttyd5 to 57600 bps, do &prompt.root; stty -f /dev/ttyld5 57600 - + Now, an application that opens ttyd5 and tries to change the speed of the port will be stuck with 57600 bps. - + Naturally, you should make the initial state and lock state devices writable only by root. The MAKEDEV script does not do @@ -59,12 +59,12 @@ Terminals Contributed by &a.kelly; 28 July 1996 - + Terminals provide a convenient and low-cost way to access the power of your FreeBSD system when you are not at the computer's console or on a connected network. This section describes how to use terminals with FreeBSD. - + Uses and Types of Terminals @@ -95,11 +95,11 @@ Dumb terminals - + PCs acting as terminals - + X terminals @@ -109,7 +109,7 @@ Dumb Terminals - + Dumb terminals are specialized pieces of hardware that let you connect to computers over serial lines. They are called “dumb” because they have only enough computational power @@ -132,7 +132,7 @@ PCs Acting As Terminals - + If a dumb terminal has just enough ability to display, send, and receive text, then certainly any spare personal computer can be a dumb terminal. All you need is @@ -147,7 +147,7 @@ X Terminals - + X terminals are the most sophisticated kind of terminal available. Instead of connecting to a serial port, they usually connect to a network like Ethernet. Instead of being relegated to @@ -170,7 +170,7 @@ Cables - + Because terminals use serial ports, you need to use serial—also known as RS-232C—cables to connect the terminal to the FreeBSD system. @@ -195,7 +195,7 @@ linkend="term-std">standard cable. - + Also, the serial port on both the terminal and your FreeBSD system must have connectors that will fit the cable you are using. @@ -299,7 +299,7 @@ hood. - + Standard RS-232C Cables @@ -314,12 +314,12 @@ Ports - + Serial ports are the devices through which data is transferred between the FreeBSD host computer and the terminal. This section describes the kinds of ports that exist and how they are addressed in FreeBSD. - + Kinds of Ports @@ -336,7 +336,7 @@ specifications on the kind of port in use. A visual inspection of the port often works, too. - + Port Names @@ -406,18 +406,18 @@ the /dev directory for the serial port if it is not already there. - + Specify that /usr/libexec/getty be run on the port, and specify the appropriate getty type from the /etc/gettytab file. - + Specify the default terminal type. - + Set the port to “on.” @@ -426,7 +426,7 @@ Specify whether the port should be “secure.” - + Force init to reread the /etc/ttys file. @@ -453,11 +453,11 @@ Adding an Entry to <filename>/etc/ttys</filename> - + First, you need to add an entry to the /etc/ttys file, unless one is already there. - + The /etc/ttys file lists all of the ports on your FreeBSD system where you want to allow logins. For example, the first virtual console ttyv0 has an entry in @@ -486,7 +486,7 @@ ttyd5 Specifying the <replaceable>getty</replaceable> Type - + Next, we need to specify what program will be run to handle the logins on a terminal. For FreeBSD, the standard program to do that is /usr/libexec/getty. It is what provides the @@ -529,7 +529,7 @@ ttyd5 "/usr/libexec/getty std.19200" Specifying the Default Terminal Type - + The third field in the /etc/ttys file lists the default terminal type for the port. For dialup ports, you typically put unknown or @@ -537,18 +537,18 @@ ttyd5 "/usr/libexec/getty std.19200" with practically any kind of terminal or software. For hardwired terminals, the terminal type does not change, so you can put a real terminal type in this field. - + Users will usually use the tset program in their .login or .profile files to check the terminal type and prompt for one if necessary. By setting a terminal type in the /etc/ttys file, users can forego such prompting. - + To find out what terminal types FreeBSD supports, see the file /usr/share/misc/termcap. It lists about 600 terminal types. You can add more if you wish. See the &man.termcap.5; manual page for information. - + In our example, the Wyse-50 is a Wyse-50 type of terminal (although it can emulate others, we will leave it in Wyse-50 mode). The 286 PC is running Procomm which will be set to emulate a VT-100. @@ -562,7 +562,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 Enabling the Port - + The next field in /etc/ttys, the fourth field, tells whether to enable the port. Putting on here will have the init @@ -582,7 +582,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on Specifying Secure Ports - + We have arrived at the last field (well, almost: there is an optional window specifier, but we will ignore that). The last field tells whether the port is secure. @@ -592,9 +592,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on 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 root to login. - + How do you use secure and insecure ports? - + By marking a port as insecure, the terminal to which it is connected will not allow root to login. People who know the root password to your FreeBSD system will first have to login using a @@ -613,7 +613,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on command records. Which should you use? - + Just use “insecure.” Use “insecure” even for terminals not in public user areas or behind locked doors. It is quite easy to login @@ -632,7 +632,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom Force <command>init</command> to Reread <filename>/etc/ttys</filename> - + When you boot FreeBSD, the first process, init, will read the /etc/ttys file and start the programs listed @@ -704,7 +704,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroomkill -HUP 1. - + Garbage appears instead of a login prompt @@ -716,7 +716,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom. - + Characters appear doubled; the password appears when typed @@ -744,7 +744,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom - + Prerequisites @@ -757,7 +757,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom FreeBSD Version - + First, it is assumed that you are using FreeBSD version 1.1 or higher (including versions 2.x). FreeBSD version 1.0 included two different serial drivers, which complicates the situation. Also, @@ -769,9 +769,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom Terminology - + A quick rundown of terminology: - + bps @@ -807,12 +807,12 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom - + If you need more information about these terms and data communications in general, the author remembers reading that The RS-232 Bible (anybody have an ISBN?) is a good reference. - + When talking about communications data rates, the author does not use the term “baud”. Baud refers to the number of electrical state transitions that may be made in a period of time, @@ -823,7 +823,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom External vs. Internal Modems - + External modems seem to be more convenient for dialup, because external modems often can be semi-permanently configured via parameters stored in non-volatile RAM and they usually provide @@ -842,7 +842,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroomModems and Cables A background knowledge of these items is assumed - + You know how to connect your modem to your computer so that @@ -861,7 +861,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom - + The first, connecting your modem, is usually simple — most straight-through serial cables work without any problems. You need to have a cable with appropriate connectors (DB-25 or DB-9, male or @@ -901,7 +901,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroomSignal Ground (SG) - + FreeBSD needs the RTS and CTS signals for flow-control at speeds above 2400bps, the CD signal to detect when a call has @@ -930,7 +930,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom Serial Interface Considerations - + FreeBSD supports NS8250-, NS16450-, NS16550-, and NS16550A-based EIA RS-232C (CCITT V.24) communications interfaces. The 8250 and 16450 devices have single-character buffers. The 16550 device @@ -1074,7 +1074,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr &man.config.8; manual page to prepare a kernel building directory, then build, install, and test the new kernel. - + Device Special Files @@ -1103,7 +1103,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr Making Device Special Files - + A shell script called MAKEDEV in the /dev directory manages the device special files. (The manual page for &man.MAKEDEV.8; on FreeBSD 1.1.5 is @@ -1195,12 +1195,12 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01 <filename>/etc/gettytab</filename> - + /etc/gettytab is a &man.termcap.5;-style file of configuration information for &man.getty.8;. Please see the &man.gettytab.5; manual page for complete information on the format of the file and the list of capabilities. - + Locked-Speed Config @@ -1208,7 +1208,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01 particular speed, you probably will not need to make any changes to /etc/gettytab. - + Matching-Speed Config @@ -1297,7 +1297,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ <filename>/etc/ttys</filename> - + /etc/ttys is the list of ttys for init to monitor. /etc/ttys also provides security information to @@ -1350,7 +1350,7 @@ ttyd0 "/usr/libexec/getty xxx" dialup on first time setting up the system, though, you may want to wait until your modem(s) are properly configured and connected before signaling init. - + Locked-Speed Config @@ -1370,7 +1370,7 @@ ttyd0 "/usr/libexec/getty std.19200" dialup on /etc/gettytab for your modem's data rate. - + Matching-Speed Config @@ -1391,7 +1391,7 @@ ttyd0 "/usr/libexec/getty V19200" dialup on <filename>/etc/rc.serial</filename> or <filename>/etc/rc.local</filename> - + High-speed modems, like V.32, V.32bis, and V.34 modems, need to use hardware (RTS/CTS) flow control. You can add stty commands to @@ -1447,28 +1447,28 @@ stty -f /dev/ttyd3 crtscts CD asserted when connected - + DTR asserted for operation; dropping DTR hangs up line & resets modem - + CTS transmitted data flow control - + Disable XON/XOFF flow control - + RTS received data flow control - + Quiet mode (no result codes) - + No command echo @@ -1497,32 +1497,32 @@ AT&C1&D2&H1&I0&R2&W Switch 1: UP — DTR Normal - + Switch 2: Do not care (Verbal Result Codes/Numeric Result Codes) - + Switch 3: UP — Suppress Result Codes - + Switch 4: DOWN — No echo, offline commands - + Switch 5: UP — Auto Answer - + Switch 6: UP — Carrier Detect Normal - + Switch 7: UP — Load NVRAM Defaults - + Switch 8: Do not care (Smart Mode/Dumb Mode) @@ -1537,7 +1537,7 @@ AT&C1&D2&H1&I0&R2&W Locked-speed Config - + For a locked-speed configuration, you will need to configure the modem to maintain a constant modem-to-computer data rate independent of the communications rate. On a USR Sportster 14,400 external @@ -1551,7 +1551,7 @@ AT&B1&W Matching-speed Config - + For a variable-speed configuration, you will need to configure your modem to adjust its serial port data rate to match the incoming call rate. On a USR Sportster 14,400 external modem, these commands @@ -1566,7 +1566,7 @@ AT&B2&W Checking the Modem's Configuration - + Most high-speed modems provide commands to view the modem's current operating parameters in a somewhat human-readable fashion. On the USR Sportster 14,400 external modems, the command @@ -1589,7 +1589,7 @@ AT&B2&W Checking out the FreeBSD system - + Hook up your modem to your FreeBSD system, boot the system, and, if your modem has status indication lights, watch to see whether the modem's DTR indicator lights when the @@ -1603,7 +1603,7 @@ AT&B2&W ax to see if FreeBSD is trying to run a getty process on the correct port. You should see a lines like this among the processes displayed: - + 114 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd0 115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd1 @@ -1635,7 +1635,7 @@ AT&B2&W Try Dialing In - + Try dialing into the system; be sure to use 8 bits, no parity, 1 stop bit on the remote system. If you do not get a prompt right away, or get garbage, try pressing <Enter> @@ -1649,7 +1649,7 @@ AT&B2&W If you still cannot get a login: prompt, check /etc/gettytab again and double-check that - + The initial capability name specified in @@ -1667,7 +1667,7 @@ AT&B2&W gettytab capability name - + If you dial but the modem on the FreeBSD system will not answer, make sure that the modem is configured to answer the phone when DTR is asserted. If the modem seems to be @@ -1715,7 +1715,7 @@ AT&B2&W the Internet if you have problems with PPP. If you need to ftp something and PPP is broken, use the terminal session to ftp it. Then use zmodem to transfer it to your machine. - + Why cannot I run <command>tip</command> or <command>cu</command>? @@ -2044,7 +2044,7 @@ raisechar=^^ cable and a null-modem adapter. See for a discussion on serial cables. - + Unplug your keyboard. @@ -2085,7 +2085,7 @@ raisechar=^^ not much good without the keyboard anyway. - + Plug a dumb terminal into COM1: (sio0). @@ -2175,7 +2175,7 @@ device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 If the flags were not set, you need to run UserConfig (on a different console) or recompile the kernel. - + Create boot.config in the root directory of the a partition on the boot drive. @@ -2259,7 +2259,7 @@ device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 serial port as the console only during the boot block; the boot loader will use the internal video display as the console. - + Boot the machine. @@ -2363,9 +2363,9 @@ boot: Case 1: You set the flags to 0x10 for sio0 - + device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 - + @@ -2426,7 +2426,7 @@ boot: Case 2: You set the flags to 0x30 for sio0 - + device sio0 at isa? port "IO_COM1" tty flags 0x30 irq 4 @@ -2493,13 +2493,13 @@ boot: Setting A Faster Serial Port Speed - + By default the serial port settings are set to 9600 baud, 8 bits, no parity, 1 stop bit. If you wish to change the speed, you need to recompile at least the boot blocks. Add the following line to /etc/make.conf and compile new boot blocks: - + BOOT_COMCONSOLE_SPEED=19200 If the serial console is configured in some other way than by @@ -2514,7 +2514,7 @@ boot: Using Serial Port Other Than <devicename>sio0</devicename> For The Console - + Using a port other than sio0 as the console requires some recompiling. If you want to use another serial port for whatever reasons, recompile the boot blocks, the @@ -2581,7 +2581,7 @@ boot: Entering the DDB Debugger from the Serial Line - + If you wish to drop into the kernel debugger from the serial console (useful for remote diagnostics, but also dangerous if you generate a spurious BREAK on the serial port!) then you should @@ -2593,7 +2593,7 @@ options DDB Getting a Login Prompt on the Serial Console - + While this is not required, you may wish to get a login prompt over the serial line, now that you can see boot messages and can enter the kernel debugging session @@ -2636,7 +2636,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure Setting Up the Serial Console - + You can easily specify the boot loader and the kernel to use the serial console by writing just one line in /boot/loader.rc: @@ -2651,7 +2651,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure the serial console as early as possible. Likewise, you can specify the internal console as: - + set console=vidconsole If you do not set the boot loader environment variable @@ -2674,11 +2674,11 @@ start console=comconsole or - + console=vidconsole See &man.loader.conf.5; for more information. - + At the moment, the boot loader has no option equivalent to the option in the boot block, and there is no @@ -2690,7 +2690,7 @@ start Using Serial Port Other than <devicename>sio0</devicename> for the Console - + You need to recompile the boot loader to use a serial port other than sio0 for the serial console. Follow the procedure described in . diff --git a/en_US.ISO8859-1/books/handbook/staff/chapter.sgml b/en_US.ISO8859-1/books/handbook/staff/chapter.sgml index 959beb8ba0..8894b17db9 100644 --- a/en_US.ISO8859-1/books/handbook/staff/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/staff/chapter.sgml @@ -1,7 +1,7 @@ @@ -12,7 +12,7 @@ Contributed by &a.gryphon;. 6 October 1995. - + 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 “route” is a defined pair of addresses: a @@ -25,7 +25,7 @@ We will talk a little bit more about default routes later on. There are also three types of gateways: individual hosts, interfaces (also called “links”), and ethernet hardware addresses. - + An example @@ -325,7 +325,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) can lead to serious network problems, particularly with NFS. This difficulty is not specific to FreeBSD, but FreeBSD systems are affected by it. - + The problem nearly always occurs when (FreeBSD) PC systems are networked with high-performance workstations, such as those made by Silicon Graphics, Inc., and Sun Microsystems, Inc. The NFS mount will @@ -336,7 +336,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) many systems, there is no way to shut down the client gracefully once this problem has manifested itself. The only solution is often to reset the client, because the NFS situation cannot be resolved. - + 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 @@ -347,13 +347,13 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) specified using the fourth field of the fstab entry on the client for automatic mounts, or by using the parameter of the mount command for manual mounts. - + It should be noted that there is a different problem, sometimes mistaken for this one, when the NFS servers and clients are on different networks. If that is the case, make certain that your routers are routing the necessary UDP information, or you will not get anywhere, no matter what else you are doing. - + In the following examples, fastws is the host (interface) name of a high-performance workstation, and freebox is the host (interface) name of a FreeBSD @@ -364,7 +364,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) cases, note that additional options, such as or and may be desirable in your application. - + Examples for the FreeBSD system (freebox) as the client: in /etc/fstab on freebox: @@ -387,7 +387,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0 Nearly any 16-bit Ethernet adapter will allow operation without the above restrictions on the read or write size. - + For anyone who cares, here is what happens when the failure occurs, which also explains why it is unrecoverable. NFS typically works with a “block” size of 8k (though it may do fragments of smaller @@ -407,7 +407,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0 By keeping the unit size below the Ethernet packet size limitation, we ensure that any complete Ethernet packet received can be acknowledged individually, avoiding the deadlock situation. - + 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 “units”. When an overrun @@ -425,7 +425,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0 allow you to boot your FreeBSD machine over the network and run FreeBSD without having a disk on your client. Under 2.0 it is now possible to have local swap. Swapping over NFS is also still supported. - + Supported Ethernet cards include: Western Digital/SMC 8003, 8013, 8216 and compatibles; NE1000/NE2000 and compatibles (requires recompile) @@ -451,7 +451,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0 - + Set up a bootp server to provide the client with IP, gateway, netmask. @@ -467,7 +467,7 @@ diskless:\ :gw=192.1.2.5:\ :vm=rfc1048: - + Set up a TFTP server (on same machine as bootp server) to provide booting information to client. The name of this file is @@ -572,7 +572,7 @@ hostname myclient.mydomain rootfs 192.1.2.3:/rootfs/myclient hostname myclient.mydomain - + Ensure that your NFS server has exported the root (and swap if applicable) filesystems to your client, and that the client has @@ -610,7 +610,7 @@ hostname myclient.mydomain &prompt.root; chmod 0600 /swapfs/swap.192.1.2.4 - + Unpack the root filesystem in the directory the client will use for its root filesystem (/rootfs/myclient @@ -634,7 +634,7 @@ hostname myclient.mydomain - + Run netboot.com on the client or make an EPROM from the netboot.rom file @@ -671,7 +671,7 @@ hostname myclient.mydomain A good resource for information on ISDN technology and hardware is Dan Kegel's ISDN Page. - + A quick simple roadmap to ISDN follows: @@ -734,7 +734,7 @@ hostname myclient.mydomain In case you are interested in adding support for a different ISDN protocol, a currently unsupported ISDN PC card or otherwise enhancing isdn4bsd, please get in touch with hm@kts.org. - + A majordomo maintained mailing list is available. To join the list, send mail to majordomo@FreeBSD.org and specify: @@ -782,7 +782,7 @@ subscribe freebsd-isdn Motorola BitSurfer and Bitsurfer Pro - + Adtran @@ -857,7 +857,7 @@ subscribe freebsd-isdn Branch office or Home network - + Network is 10 Base T Ethernet. Connect router to network cable with AUI/10BT transceiver, if necessary. @@ -880,9 +880,9 @@ ISDN BRI line Head office or other lan - + Network is Twisted Pair Ethernet. - + -------Novell Server diff --git a/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml b/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml index 6a805f7ec4..4bc1417737 100644 --- a/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml @@ -1,7 +1,7 @@ @@ -337,7 +337,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready 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! - + If your time and your data is worth little to nothing, then “Do nothing” is the most suitable backup program for your computer. But beware, Unix is a useful tool, you may find that within @@ -377,7 +377,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready Before the Disaster - + There are only four steps that you need to perform in preparation for any disaster that may occur. @@ -581,14 +581,14 @@ echo "The floppy has been unmounted and is now ready."]]> After the Disaster - + The key question is: did your hardware survive? You have been doing regular backups so there is no need to worry about the software. - + If the hardware has been damaged. First, replace those parts that have been damaged. - + If your hardware is okay, check your floppies. If you are using a custom boot floppy, boot single-user (type -s at the boot: prompt). Skip the following @@ -605,7 +605,7 @@ echo "The floppy has been unmounted and is now ready."]]> located in /mnt2/stand. Recover each filesystem separately. - + Try to &man.mount.8; (e.g. mount /dev/da0a /mnt) the root partition of your first disk. If the disklabel was damaged, use &man.disklabel.8; to re-partition and @@ -617,7 +617,7 @@ echo "The floppy has been unmounted and is now ready."]]> /dev/sa0). Unmount the filesystem (e.g. umount /mnt) Repeat for each filesystem that was damaged. - + Once your system is running, backup your data onto new tapes. Whatever caused the crash or data loss may strike again. An another hour spent now, may save you from further distress later. @@ -625,7 +625,7 @@ echo "The floppy has been unmounted and is now ready."]]> * I did not prepare for the Disaster, What Now? - + @@ -645,11 +645,11 @@ echo "The floppy has been unmounted and is now ready."]]> The media is unreliable, especially over long periods of time - + Backing up and restoring is very slow - + They have a very limited capacity (the days of backing up an entire hard disk onto a dozen or so floppies has long since diff --git a/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml b/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml index e5fa0fe5da..391c3542d3 100644 --- a/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml @@ -1,7 +1,7 @@ @@ -79,7 +79,7 @@ documentation, so &man.chmod.1; refers to the chmod user command and &man.chmod.2; refers to the system call. - + This is fine if you know the name of the command and simply wish to know how to use it, but what if you cannot recall the command name? You can use man to search for keywords in the command @@ -92,7 +92,7 @@ have the keyword “mail” in their descriptions. This is actually functionally equivalent to using the apropos command. - + So, you are looking at all those fancy commands in /usr/bin but do not even have the faintest idea what most of them actually do? Simply do a @@ -116,7 +116,7 @@ info command or, if you installed emacs, the info mode of emacs. - + To use the &man.info.1; command, simply type: &prompt.user; info diff --git a/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml b/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml index 0dfffb1af5..5e2db53dfa 100644 --- a/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml @@ -1,7 +1,7 @@ @@ -50,7 +50,7 @@ interested in working on one of the tasks you see here, send mail to the coordinator listed by clicking on their names. If no coordinator has been appointed, maybe you would like to volunteer? - + High priority tasks @@ -69,7 +69,7 @@ - + Filesystem problems. Overall coordination: &a.fs; @@ -88,7 +88,7 @@ - + Implement Int13 vm86 disk driver. Coordinator: &a.hackers; @@ -129,11 +129,11 @@ - + Kernel issues. Overall coordination: &a.hackers; - + Add more pro-active security infrastructure. Overall coordination: &a.security; @@ -214,7 +214,7 @@ - + PCMCIA/PCCARD. Coordinators: &a.msmith; and &a.phk; @@ -248,7 +248,7 @@ - + Advanced Power Management. Coordinators: &a.msmith; and &a.phk; @@ -292,17 +292,17 @@ network cards. The same thing for NDIS drivers and NetWare SCSI drivers. - + An "upgrade system" option that works on Linux boxes instead of just previous rev FreeBSD boxes. - + Symmetric Multiprocessing with kernel preemption (requires kernel preemption). - + A concerted effort at support for portable computers. This is somewhat handled by changing PCMCIA bridging rules and power @@ -334,21 +334,21 @@ the latest release from it and report any failures in the process. - + Read the freebsd-bugs mailing list. There might be a problem you can comment constructively on or with patches you can test. Or you could even try to fix one of the problems yourself. - + Read through the FAQ and Handbook periodically. If anything is badly explained, out of date or even just completely wrong, let us know. Even better, send us a fix (SGML is not difficult to learn, but there is no objection to ASCII submissions). - + Help translate FreeBSD documentation into your native language (if not already available) — just send an email to &a.doc; @@ -357,7 +357,7 @@ by doing this — in fact, the documentation most in need of translation is the installation instructions. - + Read the freebsd-questions mailing list and &ng.misc occasionally (or even regularly). It can be very satisfying to @@ -365,19 +365,19 @@ sometimes you may even learn something new yourself! These forums can also be a source of ideas for things to work on. - + If you know of any bugfixes which have been successfully applied to -current but have not been merged into -stable after a decent interval (normally a couple of weeks), send the committer a polite reminder. - + Move contributed software to src/contrib in the source tree. - + Make sure code in src/contrib is up to date. @@ -386,23 +386,23 @@ Look for year 2000 bugs (and fix any you find!) - + Build the source tree (or just part of it) with extra warnings enabled and clean up the warnings. - + Fix warnings for ports which do deprecated things like using gets() or including malloc.h. - + If you have contributed any ports, send your patches back to the original author (this will make your life easier when they bring out the next version) - + Suggest further tasks for this list! @@ -434,7 +434,7 @@ Contributions to the system generally fall into one or more of the following 6 categories: - + Bug reports and general commentary @@ -508,7 +508,7 @@ &prompt.user; diff -c oldfile newfile or - + &prompt.user; diff -c -r olddir newdir would generate such a set of context diffs for the given source file @@ -567,7 +567,7 @@ participation by commercial interests who might eventually be inclined to invest something of their own into FreeBSD. - + The GNU Public License, or “GPL”. This license is not quite as popular with us due to the amount of extra effort @@ -637,7 +637,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. <anchor id="donations">Donating funds - + While the FreeBSD Project is not a 501(c)(3) (charitable) corporation and hence cannot offer special tax incentives for any donations made, any such donations will be gratefully accepted on @@ -660,12 +660,12 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Concord CA, 94520 - + (currently using the Walnut Creek CDROM address until a PO box can be opened) - + Wire transfers may also be sent directly to: - +
Bank Of America Concord Main Office @@ -676,7 +676,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Routing #: 121-000-358 Account #: 01411-07441 (FreeBSD, Inc.)
- + Any correspondence related to donations should be sent to &a.jkh, either via email or to the FreeBSD, Inc. postal address given above. @@ -688,7 +688,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Donating hardware - + Donations of hardware in any of the 3 following categories are also gladly accepted by the FreeBSD Project: @@ -722,7 +722,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Donating Internet access - + We can always use new mirror sites for FTP, WWW or cvsup. If you would like to be such a mirror, please contact the FreeBSD project administrators @@ -783,7 +783,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Direct funding: - + The following individuals and businesses have generously contributed direct funding to the project: @@ -897,11 +897,11 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Hardware contributors: - + The following individuals and businesses have generously contributed hardware for testing and device driver development/support: - + Walnut Creek CDROM for providing the Pentium P5-90 and @@ -968,7 +968,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Special contributors: - + Walnut Creek CDROM @@ -1069,7 +1069,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4.4BSD-Lite release provided by the Computer Science Research Group (CSRG) at the University of California, Berkeley and associated academic contributors. - + There are also portions of NetBSD and OpenBSD that have been integrated into FreeBSD as well, and we would therefore like to thank all the contributors to NetBSD and OpenBSD for their work. diff --git a/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml b/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml index 0034e018d9..06227ff201 100644 --- a/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml @@ -1,7 +1,7 @@ @@ -46,7 +46,7 @@ part of the source tree and for whom keeping “current” is an absolute requirement. - + Members of the FreeBSD group who are active testers, willing to spend time working through problems in order to ensure that @@ -54,7 +54,7 @@ who wish to make topical suggestions on changes and the general direction of FreeBSD. - + Peripheral members of the FreeBSD (or some other) group who merely wish to keep an eye on things and use the current sources @@ -74,11 +74,11 @@ there is some cool new feature in there and you want to be the first on your block to have it. - + A quick way of getting bug fixes. - + In any way “officially supported” by us. We do our best to help people genuinely in one of the 3 @@ -125,7 +125,7 @@ subscribe cvs-all how to subscribe and unsubscribe to the various other mailing lists we support. - + Grab the sources from ftp.FreeBSD.org. You can do this in three @@ -174,7 +174,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + Essentially, if you need rapid on-demand access to the source and communications bandwidth is not a consideration, use @@ -249,7 +249,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzUsing FreeBSD-stable - + Join the &a.stable;. This will keep you informed of build-dependencies that may appear in stable @@ -274,7 +274,7 @@ subscribe cvs-all how to subscribe and unsubscribe to the various other mailing lists we support. - + If you are installing a new system and want it to be as stable as possible, you can simply grab the latest dated branch snapshot @@ -331,14 +331,14 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + Essentially, if you need rapid on-demand access to the source and communications bandwidth is not a consideration, use cvsup or ftp. Otherwise, use CTM. - + Before compiling stable, read the Makefile in /usr/src carefully. You should at least run @@ -356,14 +356,14 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzSynchronizing Source Trees over the Internet Contributed by &a.jkh;. - + There are various ways of using an Internet (or email) connection to stay up-to-date with any given area of the FreeBSD project sources, or all areas, depending on what interests you. The primary services we offer are Anonymous CVS, CVSup, and CTM. - + Anonymous CVS and CVSup use the pull model of updating sources. In the case of CVSup @@ -380,7 +380,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzCVSup can do this far more efficiently, but Anonymous CVS is easier to use. - + CTM, on the other hand, does not interactively compare the sources you have with those on the master archive or otherwise pull them across.. Instead, a script which @@ -404,7 +404,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + For more information on Anonymous CVS, CTM, and CVSup, please see one of the following sections: @@ -416,7 +416,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz <anchor id="anoncvs-intro">Introduction - + Anonymous CVS (or, as it is otherwise known, anoncvs) is a feature provided by the CVS utilities bundled with FreeBSD for synchronizing with a remote CVS @@ -454,7 +454,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz <anchor id="anoncvs-usage">Using Anonymous CVS - + Configuring &man.cvs.1; to use an Anonymous CVS repository is a simple matter of setting the CVSROOT environment variable to point to one of the FreeBSD project's @@ -467,7 +467,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + Since CVS allows one to “check out” virtually any version of the FreeBSD sources that ever existed (or, in some cases, will exist :), you need to be familiar with the @@ -481,7 +481,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + Here are the branch tags that users might be interested in: @@ -523,10 +523,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + Here are the revision tags that users might be interested in: - + RELENG_3_3_0_RELEASE @@ -659,7 +659,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + When you specify a branch tag, you normally receive the latest versions of the files on that line of development. If you wish to receive some past version, you can do so by specifying a date with @@ -669,7 +669,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Examples - + While it really is recommended that you read the manual page for &man.cvs.1; thoroughly before doing anything, here are some quick examples which essentially show how to use Anonymous @@ -684,7 +684,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzcvs co ls &prompt.user; cvs release -d ls - + Checking out the version of ls(1) in the 2.2-stable branch: @@ -694,7 +694,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzcvs co -rRELENG_2_2 ls &prompt.user; cvs release -d ls - + Creating a list of changes (as unidiffs) to &man.ls.1; @@ -716,10 +716,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Other Resources - + The following additional resources may be helpful in learning CVS: - + Why should I use <application>CTM</application>? - + CTM will give you a local copy of the FreeBSD source trees. There are a number of “flavors” of the tree available. Whether you wish to track the entire cvs @@ -781,7 +781,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz What do I need to use <application>CTM</application>? - + You will need two things: The CTM program and the initial deltas to feed it (to get up to “current” levels). @@ -807,7 +807,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/ or see section mirrors. - + FTP the relevant directory and fetch the README file, starting from there. @@ -880,9 +880,9 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Using <application>CTM</application> in your daily life - + To apply the deltas, simply say: - + &prompt.root; cd /where/ever/you/want/the/stuff &prompt.root; ctm -v -v /where/you/store/your/deltas/src-xxx.* @@ -918,7 +918,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Keeping your local changes - + As a developer one would like to experiment with and change files in the source tree. CTM supports local modifications in a limited way: before checking for the @@ -935,7 +935,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Other interesting <application>CTM</application> options - + Finding out exactly what would be touched by an update @@ -949,7 +949,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz:-). - + Making backups before updating @@ -961,7 +961,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzCTM delta to backup-file. - + Restricting the files touched by an update @@ -993,9 +993,9 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Future plans for <application>CTM</application> - + Tons of them: - + Use some kind of authentication into the CTM system, so as @@ -1007,7 +1007,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + The bad news is that I am very busy, so any help in doing this will be most welcome. And do not forget to tell me what you want also... @@ -1015,7 +1015,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Miscellaneous stuff - + All the “DES infected” (e.g. export controlled) source is not included. You will get the “international” version only. If sufficient interest @@ -1028,7 +1028,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Thanks! - + &a.bde; @@ -1081,7 +1081,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Introduction - + CVSup is a software package for distributing and updating source trees from a master CVS repository on a remote server host. The FreeBSD sources are maintained in a @@ -1119,7 +1119,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz Installation - + The easiest way to install CVSup if you are running FreeBSD 2.2 or later is to use either the @@ -1178,16 +1178,16 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupd-bin-16.0.tar.gz (server). - + as well as from the many FreeBSD FTP mirror sites around the world. - + Most users will need only the client. These executables are entirely self-contained, and they will run on any version of FreeBSD from FreeBSD-2.1.0 to FreeBSD-current. In summary, your options for installing CVSup are: - + FreeBSD-2.2 or later: static binary, port, or @@ -1206,7 +1206,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz CVSup Configuration - + CVSup's operation is controlled by a configuration file called the supfile. Beginning with FreeBSD-2.2, there are some sample @@ -1214,7 +1214,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz/usr/share/examples/cvsup/. These examples are also available from ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/ if you are on a pre-2.2 system. - + The information in a supfile answers the following questions for cvsup: @@ -1244,7 +1244,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz - + In the following sections, we will construct a typical supfile by answering each of these questions in turn. First, we describe the overall structure of a @@ -1290,7 +1290,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgzsupfile for receiving and updating the main source tree of FreeBSD-current. - + Which files do you want to receive? Running <application>CVSup</application> - + You are now ready to try an update. The command line for doing this is quite simple: @@ -1716,7 +1716,7 @@ cvs-crypto trial run without touching your precious files. Just create an empty directory somewhere convenient, and name it as an extra argument on the command line: - + &prompt.root; mkdir /var/tmp/dest &prompt.root; cvsup supfile /var/tmp/dest @@ -1750,7 +1750,7 @@ cvs-crypto There are plenty of other options available. For a brief list of them, type cvsup -H. For more detailed descriptions, see the manual page. - + Once you are satisfied with the way updates are working, you can arrange for regular runs of cvsup using &man.cron.8;. Obviously, you should not let cvsup use its GUI when running it from @@ -1773,7 +1773,7 @@ cvs-crypto ports-all. The other collections are used only by small groups of people for specialized purposes, and some mirror sites may not carry all of them. - + cvs-all release=cvs @@ -2459,7 +2459,7 @@ cvs-crypto For more information - + For the CVSup FAQ and other information about CVSup, see The CVSup Home Page. @@ -2477,14 +2477,14 @@ cvs-crypto Using <command>make world</command> to rebuild your system - + Contributed by &a.nik;. - + Once you have synchronised your local source tree against a particular version of FreeBSD (stable, current and so on) you must then use the source tree to rebuild the system. - + Take a backup @@ -2539,7 +2539,7 @@ cvs-crypto If your machine has a floating point unit (386DX, 486DX, Pentium and up class machines) then you can also uncomment the HAVE_FPU line.</para> @@ -2587,9 +2587,9 @@ cvs-crypto</programlisting> <para>If you are feeling particularly paranoid, you can check your system to see which files are owned by the group you are renaming or deleting.</para> - + <screen>&prompt.root; <userinput>find / -group <replaceable>GID</replaceable> -print</userinput></screen> - + <para>will show all files owned by group <replaceable>GID</replaceable> (which can be either a group name or a numeric group ID).</para> </tip> @@ -2609,7 +2609,7 @@ cvs-crypto</programlisting> <note> <title>Version 2.2.5 and above - + As described in more detail below, versions 2.2.5 and above of FreeBSD have separated the building process from the installing process. You can therefore build the new @@ -2618,9 +2618,9 @@ cvs-crypto As the superuser, you can execute - + &prompt.root; - + from a running system, which will drop it to single user mode. Alternatively, reboot the system, and at the boot prompt, enter @@ -2662,9 +2662,9 @@ cvs-crypto All versions - + You must be in the /usr/src directory, so - + &prompt.root; cd /usr/src (unless, of course, your source code is elsewhere, in which case @@ -2674,7 +2674,7 @@ cvs-crypto command reads instructions from the Makefile which describes how the programs that comprise FreeBSD should be rebuilt, the order they should be built in, and so on. - + The general format of the command line you will type is as follows; @@ -2695,7 +2695,7 @@ cvs-crypto is another way of specifying that profiled libaries should not be built, and corresponds with the - + NOPROFILE= true # Avoid compiling profiled libraries @@ -2719,7 +2719,7 @@ cvs-crypto Saving the output - + It's a good idea to save the output you get from running &man.make.1; to another file. If something goes wrong you will have a copy of the error message, and a complete list of where the @@ -2749,11 +2749,11 @@ Script done, … Version 2.2.2 and below - + /usr/src/Makefile contains the world target, which will rebuild the entire system and then install it. - + Use it like this. &prompt.root; make world @@ -2761,7 +2761,7 @@ Script done, … Version 2.2.5 and above - + Beginning with version 2.2.5 of FreeBSD (actually, it was first created on the -current branch, and then retrofitted to -stable midway between 2.2.2 and 2.2.5) the world @@ -2817,7 +2817,7 @@ Script done, … -current and above - + If you are tracking -current you can also pass the option to make. This lets make spawn several simultaneous processes. @@ -2837,7 +2837,7 @@ Script done, … If you have a multi-CPU machine and you are using an SMP configured kernel try values between 6 and 10 and see how they speed things up. - + Be aware that (at the time of writing) this is still experimental, and commits to the source tree may occasionally break this feature. If the world fails to compile using this parameter @@ -2849,7 +2849,7 @@ Script done, … Assuming everything goes well you have anywhere between an hour and a half and a day or so to wait. - + As a general rule of thumb, a 200MHz P6 with more than 32MB of RAM and reasonable SCSI disks will complete make world in about an hour and a half. A 32MB P133 will @@ -2881,14 +2881,14 @@ Script done, … Backup your existing <filename>/etc</filename> - + Although, in theory, nothing is going to touch this directory automatically, it is always better to be sure. So copy your existing /etc directory somewhere safe. Something like: - + &prompt.root; cp -Rp /etc /etc.old - + does a recursive copy, preserves times, ownerships on files and suchlike. @@ -2898,11 +2898,11 @@ Script done, … put this dummy directory in /var/tmp/root, and there are a number of subdirectories required under this as well. - + &prompt.root; mkdir /var/tmp/root &prompt.root; cd /usr/src/etc &prompt.root; make DESTDIR=/var/tmp/root distrib-dirs distribution - + This will build the necessary directory structure and install the files. A lot of the subdirectories that have been created under /var/tmp/root are empty and should be deleted. @@ -2945,15 +2945,15 @@ Script done, … Name the new root directory (<filename>/var/tmp/root</filename>)with a timestamp, so you can easily compare differences between versions - + Frequently remaking the world means that you have to update /etc frequently as well, which can be a bit of a chore. - + You can speed this process up by keeping a copy of the last set of changed files that you merged into /etc. The following procedure gives one idea of how to do this. - + Make the world as normal. When you want to update @@ -3013,7 +3013,7 @@ Script done, … to /etc. - + You can use &man.date.1; to automate the generation of the directory names. @@ -3026,7 +3026,7 @@ Script done, … DEVFS - + If you are using DEVFS then this is probably unnecessary. @@ -3036,7 +3036,7 @@ Script done, … Copy /var/tmp/root/dev/MAKEDEV to /dev. - + &prompt.root; cp /var/tmp/root/dev/MAKEDEV /dev @@ -3097,7 +3097,7 @@ Script done, … Source older than 2 April 1998 - + If your source code is older than 2nd April 1998, or the Makefile version is not 1.68 or higher (for FreeBSD current and 3.x systems) or 1.48.2.21 or higher (for 2.2.x @@ -3545,27 +3545,27 @@ Antonio Sue Blake, sue@welearn.com.au - + Brian Haskin, haskin@ptway.com - + Kees Jan Koster, kjk1@ukc.ac.uk - + A Joseph Kosy, koshy@india.hp.com - + Greg Lehey, grog@lemis.com - + Wes Peters, softweyr@xmission.com - + Joseph Stein, joes@wstein.com @@ -3573,12 +3573,12 @@ Antonio Studded, studded@dal.net - + Axel Thimm, Axel.Thimm@physik.fu-berlin.de - + Matthew Thyer, Matthew.Thyer@dsto.defence.gov.au diff --git a/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml b/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml index 50a8ab7dbc..fc9c7c3bc1 100644 --- a/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml @@ -1,7 +1,7 @@ @@ -32,7 +32,7 @@ questions to the appropriate mailing list you will reach both us and a concentrated FreeBSD audience, invariably assuring a better (or at least faster) response. - + The charters for the various lists are given at the bottom of this document. Please read the charter before joining or sending mail to any list. Most of our list subscribers now receive @@ -41,7 +41,7 @@ signal-to-noise ratio of the lists high. To do less would see the mailing lists ultimately fail as an effective communications medium for the project. - + Archives are kept for all of the mailing lists and can be searched using the FreeBSD World Wide Web server. The keyword searchable archive offers an @@ -354,7 +354,7 @@ be redistributed to mailing list members world-wide. To subscribe to a list, send mail to &a.majordomo; and include - + subscribe <listname> [<optional address>] @@ -416,7 +416,7 @@ help freebsd-chat@FreeBSD.org mailing list is freely available and should be used instead. - + No posting should be made to more than 2 mailing lists, and only to 2 when a clear and obvious need to post to both lists @@ -442,7 +442,7 @@ help therefore probably rate a warning (or ban) on that basis alone. - + Advertising of non-FreeBSD related products or services is strictly prohibited and will result in an immediate ban if it is @@ -463,7 +463,7 @@ help CMU/Transarc - + FREEBSD-ANNOUNCE @@ -478,7 +478,7 @@ help moderated mailing list. - + FREEBSD-ARCH @@ -521,7 +521,7 @@ help discussion has been resolved. - + FREEBSD-BUGS @@ -536,7 +536,7 @@ help interface to it. - + FREEBSD-CHAT @@ -555,7 +555,7 @@ help this -chat list. - + FREEBSD-CORE @@ -568,7 +568,7 @@ help scrutiny. - + FREEBSD-CURRENT @@ -584,7 +584,7 @@ help for which strictly technical content is expected. - + FREEBSD-CURRENT-DIGEST @@ -600,7 +600,7 @@ help to. - + FREEBSD-DOC @@ -614,7 +614,7 @@ help list; feel free to join and contribute! - + FREEBSD-FS @@ -639,7 +639,7 @@ help expected. - + FREEBSD-ISDN @@ -650,7 +650,7 @@ help development of ISDN support for FreeBSD. - + FREEBSD-JAVA @@ -662,7 +662,7 @@ help porting and maintenance of JDKs. - + FREEBSD-HACKERS @@ -678,7 +678,7 @@ help expected. - + FREEBSD-HACKERS-DIGEST @@ -717,7 +717,7 @@ help mirror sites. - + FREEBSD-INSTALL @@ -728,7 +728,7 @@ help development for the future releases. - + FREEBSD-ISP @@ -742,7 +742,7 @@ help expected. - + FREEBSD-NEWBIES @@ -761,7 +761,7 @@ help newbies. - + FREEBSD-PLATFORMS @@ -785,7 +785,7 @@ help Core Team Policy decisions. - + FREEBSD-PORTS @@ -800,7 +800,7 @@ help for which strictly technical content is expected. - + FREEBSD-QUESTIONS @@ -813,7 +813,7 @@ help technical. - + FREEBSD-QUESTIONS-DIGEST @@ -826,7 +826,7 @@ help message. The average digest size is about 40kB. - + FREEBSD-SCSI @@ -838,7 +838,7 @@ help which strictly technical content is expected. - + FREEBSD-SECURITY @@ -850,7 +850,7 @@ help list for which strictly technical content is expected. - + FREEBSD-SECURITY-NOTIFICATIONS @@ -861,7 +861,7 @@ help FreeBSD-security. - + FREEBSD-SMALL @@ -871,7 +871,7 @@ help list for which strictly technical content is expected. - + FREEBSD-STABLE @@ -887,7 +887,7 @@ help for which strictly technical content is expected. - + FREEBSD-USER-GROUPS @@ -923,7 +923,7 @@ help comp.unix.bsd.freebsd.announce - + comp.unix.bsd.freebsd.misc @@ -938,62 +938,62 @@ help comp.unix - + comp.unix.questions - + comp.unix.admin - + comp.unix.programmer - + comp.unix.shell - + comp.unix.user-friendly - + comp.security.unix - + comp.sources.unix - + comp.unix.advocacy - + comp.unix.misc - + comp.bugs.4bsd - + comp.bugs.4bsd.ucb-fixes - + comp.unix.bsd @@ -1009,37 +1009,37 @@ help comp.windows.x.i386unix - + comp.windows.x - + comp.windows.x.apps - + comp.windows.x.announce - + comp.windows.x.intrinsics - + comp.windows.x.motif - + comp.windows.x.pex - + comp.emulators.ms-windows.wine @@ -1332,7 +1332,7 @@ help Read-only cvs, personal webspace, email &a.brian - + dogma.freebsd-uk.eu.org Telnet/FTP/SSH diff --git a/en_US.ISO_8859-1/books/handbook/hw/chapter.sgml b/en_US.ISO_8859-1/books/handbook/hw/chapter.sgml index ce754facda..2b76420280 100644 --- a/en_US.ISO_8859-1/books/handbook/hw/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/hw/chapter.sgml @@ -1,7 +1,7 @@ @@ -39,7 +39,7 @@ independent. Please check with the FreeBSD hardware guide to make sure that your chosen configuration is supported before making any purchases. - + The Pentium Systems @@ -70,7 +70,7 @@ Motherboards - + For Pentium Pro (P6) systems, I'm quite fond of the Tyan S1668 dual-processor motherboard as well as the Intel PR440FX motherboard @@ -89,7 +89,7 @@ url="http://www.asus.com.tw/Products/Motherboard/Pentium/P55tp4/index.html">P55T2P4 motherboard appears to be a good choice for mid-to-high range Pentium server and workstation systems. - + Those wishing to build more fault-tolerant systems should also be sure to use Parity memory or, for truly 24/7 applications, ECC memory. @@ -136,7 +136,7 @@ Disk drives - + In this particular game of Russian roulette, I'll make few specific recommendations except to say “SCSI over IDE whenever you can afford it.” Even in small desktop configurations, SCSI @@ -150,7 +150,7 @@ CDROM drives - + My SCSI preferences extend to SCSI CDROM drives as well, and while the Toshiba drives have always been favourites of mine (in whatever speed is hot that @@ -170,7 +170,7 @@ CD Recordable (WORM) drives - + At the time of this writing, FreeBSD supports 3 types of CDR drives (though I believe they all ultimately come from Phillips anyway): The Phillips CDD 522 (Acts like a Plasmon), the PLASMON @@ -186,7 +186,7 @@ Tape drives - + I've had pretty good luck with both 8mm drives from Video Cards - + If you can also afford to buy a commercial X server for US$99 from Xi Graphics, Inc. (formerly X Inside, Inc) then I can heartily recommend the @@ -212,7 +212,7 @@ excellent with the XFree86 server, which is now at version 3.3.2. - + You also certainly can't go wrong with one of Number 9's cards — their S3 Vision 868 and 968 based cards (the 9FX series) also being quite @@ -223,7 +223,7 @@ Monitors - + I have had very good luck with the Sony Multiscan 17seII monitors, as have I with the Viewsonic @@ -238,7 +238,7 @@ Networking - + I can recommend the Intel EtherExpress Pro/100B card first and foremost, followed by the SMC Ultra 16 controller for any @@ -258,7 +258,7 @@ Serial - + If you're looking for high-speed serial networking solutions, then Digi International makes the Audio - + I currently use a Creative Labs AWE32 though just about anything from Creative Labs will generally work these days. This is not to say that other types @@ -297,7 +297,7 @@ Video - + For video capture, there are two good choices — any card based on the Brooktree BT848 chip, such as the Hauppage or WinTV boards, will work very nicely with FreeBSD. Another board which @@ -322,31 +322,31 @@ * ISA - + * EISA - + * VLB - + PCI - + Contributed by &a.obrien; from postings by &a.rgrimes;. 25 April 1995. - + Continuing updates by &a.jkh;. Last update on 26 August 1996. - + Of the Intel PCI chip sets, the following list describes various types of known-brokenness and the degree of breakage, listed from worst to best. @@ -458,7 +458,7 @@ P6 class (Pentium Pro/Pentium II) - + Both the Pentium Pro and Pentium II work fine with FreeBSD. In fact, our main ftp site ftp.FreeBSD.org (also known @@ -470,7 +470,7 @@ Pentium class - + The Intel Pentium (P54C), Pentium MMX (P55C), AMD K6 and Cyrix/IBM 6x86MX processors are all reported to work with FreeBSD. I will not go into details of which processor is faster than what, @@ -486,7 +486,7 @@ good heatsink/fans (you can get the list of certified parts from their web pages). - + Clock speeds @@ -628,7 +628,7 @@ 166, 200 and 233, with the exception that at a multiplier of 3 or more the CPU starves for memory. - + The AMD K6 Bug @@ -642,13 +642,13 @@ * 486 class - + * 386 class - + @@ -698,10 +698,10 @@ The UART: What it is and how it works - + Copyright © 1996 &a.uhclem;, All Rights Reserved. 13 January 1996. - + The Universal Asynchronous Receiver/Transmitter (UART) controller is the key component of the serial communications subsystem of a computer. The UART takes bytes of data and transmits @@ -760,7 +760,7 @@ support Synchronous operations. This mode is described here for comparison purposes only. - + Asynchronous Serial Transmission @@ -827,7 +827,7 @@ if there is no data to transmit, the transmission line can be idle. - + Other UART Functions @@ -844,7 +844,7 @@ extra signals. The function of each of these additional signals is defined in the EIA RS232-C standard. - + The RS232-C and V.24 Standards @@ -1251,7 +1251,7 @@ - + Bits, Baud and Symbols @@ -1344,7 +1344,7 @@ provides. Modems operating at 28,800 and higher speeds have variable Symbol rates, but the technique is the same. - + The IBM Personal Computer UART @@ -1572,7 +1572,7 @@ INS8250 -> INS8250B called a PC16550DN or PC16550DIN. - + Other Vendors and Similar UARTs @@ -1765,7 +1765,7 @@ INS8250 -> INS8250B Error (6)...Timeout interrupt failed: IIR = c1 LSR = 61 - + 8250/16450/16550 Registers @@ -2530,7 +2530,7 @@ INS8250 -> INS8250B - + Beyond the 16550A UART @@ -2622,7 +2622,7 @@ device sio11 at isa? port 0x138 tty flags 0xb05 irq 9 vector siointr< represent the last SIO port, in this case 11 so flags are 0xb05. - + Boca 16 @@ -2910,7 +2910,7 @@ sio2: type 16550A (multiport master) cy driver instead of the usual sio driver used by other multiport cards. Configuration is a simple matter of: - + Add the cy device to your Configuring the <devicename>si</devicename> driver - + Contributed by &a.nsayer;. 25 March 1998. @@ -2966,7 +2966,7 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure si driver. A single machine can have up to 4 host cards. The following host cards are supported: - + ISA SI/XIO host card (2 versions) EISA SI/XIO host card @@ -2986,7 +2986,7 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure You can attach up to 4 external modules to each host card. The external modules contain either 4 or 8 serial ports. They come in the following varieties: - + SI 4 or 8 port modules. Up to 57600 bps on each port supported. @@ -3006,7 +3006,7 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure device si0 at isa? tty iomem 0xd0000 irq 11 - + Valid IRQ numbers are 9, 10, 11, 12 and 15 for SX ISA host cards and 11, 12 and 15 for SI/XIO ISA host cards. @@ -3033,7 +3033,7 @@ device si0 If you want login prompts to appear on these ports, you will need to add lines like this to /etc/ttys: - + ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure @@ -3112,7 +3112,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure Concepts of ESDI - + Physical connections @@ -3133,7 +3133,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure feature(?) left over from the WD1003 standard that reserves only a single bit for device addressing. - + Device addressing @@ -3148,7 +3148,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure PC with its two drives/controller maximum the first drive is drive 0, the second is drive 1. - + Termination @@ -3168,10 +3168,10 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure Using ESDI disks with FreeBSD - + Why is ESDI such a pain to get working in the first place? - + People who tried ESDI disks with FreeBSD are known to have developed a profound sense of frustration. A combination of factors works against you to produce effects that are hard to understand @@ -3193,7 +3193,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure consult your controller and drive documentation to see if things match. - + Stay on track @@ -3213,7 +3213,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure work. Give it a try or get another more capable controller. - + Hard or soft sectoring @@ -3243,7 +3243,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure FreeBSD because you need to re-run the low-level format after each change. - + Low level formatting @@ -3266,7 +3266,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure this waste space, it also and more importantly causes you grief with bad144 (see the section on bad144). - + Translations @@ -3342,7 +3342,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure or whatever it may be called by the controller manufacturer when you want to use the disk for FreeBSD. - + Bad block handling @@ -3384,7 +3384,7 @@ ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure contains the root filesystem. - + Kernel configuration @@ -3415,7 +3415,7 @@ disk wd3 at wdc1 drive 1 Particulars on ESDI hardware - + Adaptec 2320 controllers @@ -3455,7 +3455,7 @@ disk wd3 at wdc1 drive 1 All variations should be capable of using 1:1 interleaving. Use 1:1, FreeBSD is fast enough to handle it. - + Western Digital WD1007 controllers @@ -3470,7 +3470,7 @@ disk wd3 at wdc1 drive 1 role="fqdn">www.wdc.com Running this formatted my drive just fine. - + Ultrastor U14F controllers @@ -3503,7 +3503,7 @@ disk wd3 at wdc1 drive 1 Thanks to... - + Andrew Gordon for sending me an Adaptec 2320 controller and ESDI disk for testing. @@ -3599,7 +3599,7 @@ disk wd3 at wdc1 drive 1 Components of SCSI - + As said before, SCSI devices are smart. The idea is to put the knowledge about intimate hardware details onto the SCSI device itself. In this way, the host system does not have to worry about @@ -3629,7 +3629,7 @@ disk wd3 at wdc1 drive 1 SCSI bus types - + From an electrical point of view, there are two incompatible bus types: single-ended and differential. This means that there are two different main groups of SCSI devices and controllers, which cannot @@ -3662,8 +3662,8 @@ disk wd3 at wdc1 drive 1 etc. - - + + With a minor amount of imagination one can usually imagine what is meant. @@ -3685,7 +3685,7 @@ disk wd3 at wdc1 drive 1 width is negotiated between the devices. You have to watch your device addressing closely when mixing wide and narrow. - + Single ended buses @@ -3730,7 +3730,7 @@ disk wd3 at wdc1 drive 1 accordance with the SCSI standard. For Fast-20 and 40 do not even think about buses like this. - + Differential buses @@ -3759,7 +3759,7 @@ disk wd3 at wdc1 drive 1 differential. The software interface to the host is identical for both. - + Terminators @@ -3839,7 +3839,7 @@ disk wd3 at wdc1 drive 1 termination as necessary. At any rate, consult your documentation! - + Terminator power @@ -3872,7 +3872,7 @@ disk wd3 at wdc1 drive 1 In newer designs auto-restoring fuses that 'reset' themselves after some time are sometimes used. - + Device addressing @@ -3955,7 +3955,7 @@ disk wd3 at wdc1 drive 1 Using SCSI with FreeBSD - + About translations, BIOSes and magic... @@ -4048,7 +4048,7 @@ sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors) to know about this disk, (e.g. it is not a booting disk) to supply a fictitious geometry that is convenient. - + SCSI subsystem design @@ -4069,7 +4069,7 @@ sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors) banging and more high level stuff. Adding support for another piece of hardware is a much more manageable problem. - + Kernel configuration @@ -4214,7 +4214,7 @@ device cd0 #Only need one of these, the code dynamically growsman 4 ahc for info on the Adaptec 294x driver. - + Tuning your SCSI kernel setup @@ -4239,7 +4239,7 @@ options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device - + Rogue SCSI devices @@ -4284,7 +4284,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue in the next release of FreeBSD. Other Mumbletech owners will be grateful to you. - + Multiple LUN devices @@ -4321,7 +4321,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue the table and acts accordingly. See the source for more info. - + Tagged command queueing @@ -4347,7 +4347,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue leads to highly mysterious problems. In such cases, try to disable TCQ. - + Busmaster host adapters @@ -4385,7 +4385,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Tracking down problems - + The following list is an attempt to give a guideline for the most common SCSI problems and their solutions. It is by no means complete. @@ -4449,7 +4449,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Further reading - + If you intend to do some serious SCSI hacking, you might want to have the official standard at hand: @@ -4464,7 +4464,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed(212) 642-4900 - + You can also buy many ANSI standards and most committee draft documents from Global Engineering Documents, @@ -4478,13 +4478,13 @@ options "TUNE_1542" #dynamic tune of bus DMA speed(303) 792- 2192 - + Many X3T10 draft documents are available electronically on the SCSI BBS (719-574-0424) and on the ncrinfo.ncr.com anonymous ftp site. Latest X3T10 committee documents are: - + AT Attachment (ATA or IDE) [X3.221-1994] @@ -4511,10 +4511,10 @@ options "TUNE_1542" #dynamic tune of bus DMA speed - + Other publications that might provide you with additional information are: - + “SCSI: Understanding the Small Computer System @@ -4556,13 +4556,13 @@ options "TUNE_1542" #dynamic tune of bus DMA speed - + On Usenet the newsgroups comp.periphs.scsi and comp.periphs are noteworthy places to look for more info. You can also find the SCSI-Faq there, which is posted periodically. - + Most major SCSI device and host adapter suppliers operate ftp sites and/or BBS systems. They may be valuable sources of information about the devices you own. @@ -4574,19 +4574,19 @@ options "TUNE_1542" #dynamic tune of bus DMA speed * SCSI - + * IDE - + * Floppy - + @@ -4596,7 +4596,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed SCSI hard drives - + Contributed by &a.asami;. 17 February 1998. @@ -4610,7 +4610,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed - + Rotational speed @@ -4670,7 +4670,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed - + Form factor @@ -4682,7 +4682,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed - + Interface @@ -4722,7 +4722,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed * IDE hard drives - + @@ -4735,7 +4735,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed General tape access commands - + &man.mt.1; provides generic access to the tape drives. Some of the more common commands are rewind, erase, and status. See the @@ -4744,7 +4744,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Controller Interfaces - + There are several different interfaces that support tape drives. The interfaces are SCSI, IDE, Floppy and Parallel Port. A wide variety of tape drives are available for these interfaces. @@ -4755,18 +4755,18 @@ options "TUNE_1542" #dynamic tune of bus DMA speed SCSI drives - + The &man.st.4; driver provides support for 8mm (Exabyte), 4mm (DAT: Digital Audio Tape), QIC (Quarter-Inch Cartridge), DLT (Digital Linear Tape), QIC Minicartridge and 9-track (remember the big reels that you see spinning in Hollywood computer rooms) tape drives. See the &man.st.4; manual page for a detailed description. - + The drives listed below are currently being used by members of the FreeBSD community. They are not the only drives that will work with FreeBSD. They just happen to be the ones that we use. - + 4mm (DAT: Digital Audio Tape) @@ -4791,7 +4791,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedWangtek 6200 - + 8mm (Exabyte) @@ -4801,7 +4801,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedEXB-8505 - + QIC (Quarter-Inch Cartridge) @@ -4832,13 +4832,13 @@ options "TUNE_1542" #dynamic tune of bus DMA speedWangtek 5525ES - + DLT (Digital Linear Tape) Digital TZ87 - + Mini-Cartridge @@ -4847,7 +4847,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedExabyte 2501 - + Autoloaders/Changers @@ -4858,25 +4858,25 @@ options "TUNE_1542" #dynamic tune of bus DMA speed * IDE drives - + Floppy drives - + Conner 420R * Parallel port drives - + Detailed Information - + Archive Anaconda 2750 @@ -4922,14 +4922,14 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Reported by: &a.jmb; - + Archive Python 28454 @@ -4981,7 +4981,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedData transfer rate is 800kB/s. - + Archive Viper 60 @@ -5000,7 +5000,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Philippe Regnauld regnauld@hsc.fr - + Archive Viper 150 @@ -5062,7 +5062,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedProduction of this drive has been discontinued. - + Conner 420R @@ -5080,7 +5080,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Mark Hannon mark@seeware.DIALix.oz.au - + Conner CTMS 3200 @@ -5099,7 +5099,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Thomas S. Traylor tst@titan.cs.mci.com - + <ulink url="http://www.digital.com/info/Customer-Update/931206004.txt.html">DEC TZ87</ulink> @@ -5122,7 +5122,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: &a.wilko; - + <ulink url="http://www.Exabyte.COM:80/Products/Minicartridge/2501/Rfeatures.html">Exabyte EXB-2501</ulink> @@ -5165,7 +5165,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Bob Beaulieu ez@eztravel.com - + Exabyte EXB-8200 @@ -5193,7 +5193,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Mike Smith msmith@atrad.adelaide.edu.au - + Exabyte EXB-8500 @@ -5209,7 +5209,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Greg Lehey grog@lemis.de - + <ulink url="http://www.Exabyte.COM:80/Products/8mm/8505XL/Rfeatures.html">Exabyte EXB-8505</ulink> @@ -5230,7 +5230,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: Glen Foster gfoster@gfoster.com - + Hewlett-Packard HP C1533A @@ -5314,7 +5314,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by: &a.se; - + Hewlett-Packard HP 1534A @@ -5346,7 +5346,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speedReported by Gary Crutcher gcrutchr@nightflight.com - + Hewlett-Packard HP C1553A Autoloading DDS2 @@ -5414,7 +5414,7 @@ esac scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" - + Hewlett-Packard HP 35450A @@ -5433,7 +5433,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Reported by: mark thompson mark.a.thompson@pobox.com - + Hewlett-Packard HP 35470A @@ -5461,7 +5461,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" dawes@rf900.physics.usyd.edu.au (9 09) - + Hewlett-Packard HP 35480A @@ -5497,7 +5497,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" lost. The problem has not be analyzed or resolved at this time. - + <ulink url="http://www.sel.sony.com/SEL/ccpg/storage/tape/t5000.html">Sony SDT-5000</ulink> @@ -5531,7 +5531,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Reported by: &a.jmz; - + Tandberg TDC 3600 @@ -5556,7 +5556,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Reported by: Michael Smith msmith@atrad.adelaide.edu.au - + Tandberg TDC 3620 @@ -5580,7 +5580,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Reported by: &a.jhs; - + Tandberg TDC 4222 @@ -5608,7 +5608,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Reported by: &a.joerg; - + Wangtek 5525ES @@ -5643,7 +5643,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Andrew.Gordon@net-tel.co.uk M75D - + Wangtek 6200 @@ -5664,7 +5664,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" * Problem drives - + diff --git a/en_US.ISO_8859-1/books/handbook/install/chapter.sgml b/en_US.ISO_8859-1/books/handbook/install/chapter.sgml index 8fa4033111..6dc238ab49 100644 --- a/en_US.ISO_8859-1/books/handbook/install/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/install/chapter.sgml @@ -1,7 +1,7 @@ @@ -111,7 +111,7 @@ live in the floppies subdirectory, as is typically the case). - + If you are using a UNIX system to create the floppy images: @@ -199,7 +199,7 @@ After adjusting the kernel to match how you have your hardware configured, type Q to continue booting with the new settings. - + After FreeBSD has been installed, changes made in the configuration mode will be permanent so you do not have to reconfigure every time you boot. Even so, it is likely that you will want to build a custom kernel @@ -215,16 +215,16 @@ 386sx is not recommended). Support for generic IDE or ESDI drive configurations, various SCSI controller, network and serial cards is also provided. - + A minimum of four megabytes of RAM is required to run FreeBSD. To run the X Window System, eight megabytes of RAM is the recommended minimum. - + Following is a list of all disk controllers and Ethernet cards currently known to work with FreeBSD. Other configurations may very well work, and we have simply not received any indication of this. - + Disk Controllers @@ -232,15 +232,15 @@ WD1003 (any generic MFM/RLL) - + WD1007 (any generic IDE/ESDI) - + IDE - + ATA @@ -403,7 +403,7 @@ - + DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers are supported. The DPT @@ -415,7 +415,7 @@ SMART, SMART-2/E, Smart-2/P, SMART-2SL, Smart Array 3200, Smart Array 3100ES and Smart Array 221. - + SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI @@ -451,12 +451,12 @@ - + QLogic 1020, 1040, 1040B, 1080, 1240 and 2100 SCSI and Fibre Channel Adapters - + DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -478,21 +478,21 @@ SoundBlaster SCSI and ProAudio Spectrum SCSI (cd) - + Mitsumi (all models) proprietary interface (mcd) - + Matsushita/Panasonic (Creative) CR-562/CR-563 proprietary interface (matcd) - + Sony proprietary interface (scd) - + ATAPI IDE interface (wcd) @@ -506,15 +506,15 @@ Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). - + NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. - + UltraStor 14F, 24F and 34F SCSI controllers. - + Seagate ST01/02 SCSI controllers. @@ -522,7 +522,7 @@ Future Domain 8xx/950 series SCSI controllers. - + WD7000 SCSI controller. @@ -531,11 +531,11 @@ Adaptec 1510 series ISA SCSI controllers (not for bootable devices) - + Adaptec 152x series ISA SCSI controllers - + Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. @@ -550,22 +550,22 @@ Allied-Telesis AT1700 and RE2000 cards - + SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra and 9432TX based cards are also supported. - + DEC EtherWORKS III NICs (DE203, DE204, and DE205) - + DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) - + DEC DC21040/DC21041/DC21140 based NICs: @@ -643,75 +643,75 @@ DEC FDDI (DEFPA/DEFEA) NICs - + Fujitsu FMV-181 and FMV-182 - + Fujitsu MB86960A/MB86965A - + Intel EtherExpress - + Intel EtherExpress Pro/100B 100Mbit. - + Isolan AT 4141-0 (16 bit) - + Isolink 4110 (8 bit) - + Lucent WaveLAN wireless networking interface. - + Novell NE1000, NE2000, and NE2100 ethernet interface. - + 3Com 3C501 cards - + 3Com 3C503 Etherlink II - + 3Com 3c505 Etherlink/+ - + 3Com 3C507 Etherlink 16/TP - + 3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III - + 3Com 3C590, 3C595 Etherlink III - + 3Com 3C90x cards. - + HP PC Lan Plus (27247B and 27252A) - + Toshiba ethernet cards - + PCMCIA ethernet cards from IBM and National Semiconductor are also supported. @@ -732,71 +732,71 @@ AST 4 port serial card using shared IRQ. - + ARNET 8 port serial card using shared IRQ. - + BOCA IOAT66 6 port serial card using shared IRQ. - + BOCA 2016 16 port serial card using shared IRQ. - + Cyclades Cyclom-y Serial Board. - + STB 4 port card using shared IRQ. - + SDL Communications Riscom/8 Serial Board. - + SDL Communications RISCom/N2 and N2pci sync serial cards. - + Digiboard Sync/570i high-speed sync serial card. - + Decision-Computer Intl. “Eight-Serial” 8 port serial cards using shared IRQ. - + Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound, Gravis UltraSound MAX and Roland MPU-401 sound cards. - + Matrox Meteor video frame grabber. - + Creative Labs Video spigot frame grabber. - + Omnimedia Talisman frame grabber. - + Brooktree BT848 chip based frame grabbers. - + X-10 power controllers. - + PC joystick and speaker. @@ -947,7 +947,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent c:\freebsd — the BIN dist is only the minimal requirement. - + Before installing from QIC/SCSI Tape @@ -974,7 +974,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent installation probe may otherwise fail to find it. - + Before installing over a network @@ -989,7 +989,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent SLIP or PPP - + Parallel port @@ -997,7 +997,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent PLIP (laplink cable) - + Ethernet @@ -1062,7 +1062,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent Preparing for NFS installation - + NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution files you want onto a server somewhere and then point the NFS media selection at it. @@ -1094,7 +1094,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent Preparing for FTP Installation - + FTP installation may be done from any mirror site containing a reasonably up-to-date version of FreeBSD &rel.current;. A full menu of reasonable choices from almost anywhere in the world is provided @@ -1134,13 +1134,13 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent - + Active and passive modes are not the same as a “proxy” connection, where a proxy FTP server is listening and forwarding FTP requests! - + For a proxy FTP server, you should usually give name of the server you really want as a part of the username, after an @-sign. The proxy server then 'fakes' the real server. An example: Say you @@ -1170,14 +1170,14 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent Once you have taken note of the appropriate preinstallation steps, you should be able to install FreeBSD without any further trouble. - + Should this not be true, then you may wish to go back and re-read the relevant preparation section above for the installation media type you are trying to use, perhaps there is a helpful hint there that you missed the first time? If you are having hardware trouble, or FreeBSD refuses to boot at all, read the Hardware Guide provided on the boot floppy for a list of possible solutions. - + The FreeBSD boot floppies contain all the on-line documentation you should need to be able to navigate through an installation and if it does not then we would like to know what you found most confusing. Send @@ -1186,10 +1186,10 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent 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! - + Meanwhile, you may also find the following “typical installation sequence” to be helpful: - + Boot the kern.flp floppy and, when asked, @@ -1243,7 +1243,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent Many FreeBSD users wish to install FreeBSD on PCs inhabited by MS-DOS. Here are some commonly asked questions about installing FreeBSD on such systems. - + Help! I have no space! Do I need to delete everything first? @@ -1252,7 +1252,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent find the FIPS utility, provided in the tools directory on the FreeBSD CDROM or on the various FreeBSD ftp sites, to be quite useful. - + FIPS allows you to split an existing MS-DOS partition into two pieces, preserving the original partition and allowing you to install onto the second free piece. You first defragment your MS-DOS partition, @@ -1262,24 +1262,24 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent See the Distributions menu for an estimation of how much free space you will need for the kind of installation you want. - + Can I use compressed MS-DOS filesystems from FreeBSD? - + No. If you are using a utility such as Stacker(tm) or DoubleSpace(tm), FreeBSD will only be able to use whatever portion of the filesystem you leave uncompressed. The rest of the filesystem will show up as one large file (the stacked/dblspaced file!). Do not remove that file! You will probably regret it greatly! - + It is probably better to create another uncompressed MS-DOS primary partition and use this for communications between MS-DOS and FreeBSD. - + Can I mount my MS-DOS extended partitions? - + Yes. DOS extended partitions are mapped in at the end of the other “slices” in FreeBSD, e.g. your D: drive might be /dev/da0s5, your @@ -1289,7 +1289,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent da appropriately. You otherwise mount extended partitions exactly like you would mount any other DOS drive, e.g.: - + &prompt.root; mount -t msdos /dev/da0s5 /dos_d diff --git a/en_US.ISO_8859-1/books/handbook/internals/chapter.sgml b/en_US.ISO_8859-1/books/handbook/internals/chapter.sgml index aadcbc519e..0942b7c0d5 100644 --- a/en_US.ISO_8859-1/books/handbook/internals/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/internals/chapter.sgml @@ -1,7 +1,7 @@ @@ -12,11 +12,11 @@ Contributed by &a.phk;. v1.1, April 26th. - + Booting FreeBSD is essentially a three step process: load the kernel, determine the root filesystem and initialize user-land things. This leads to some interesting possibilities shown below. - + Loading a kernel @@ -36,7 +36,7 @@ Biosboot can load a kernel from a FreeBSD filesystem. - + Dosboot @@ -53,7 +53,7 @@ for its case. - + Netboot @@ -64,7 +64,7 @@ - + Determine the root filesystem @@ -95,7 +95,7 @@ “UNIXisms”. - + MFS @@ -106,7 +106,7 @@ function. - + CD9660 @@ -114,7 +114,7 @@ This is for using a CD-ROM as root filesystem. - + NFS @@ -125,7 +125,7 @@ - + Initialize user-land things @@ -187,7 +187,7 @@ disk... - + B — Using NFS @@ -200,7 +200,7 @@ control the NFS server... - + C — Start an X-server @@ -222,7 +222,7 @@ ago... - + E — Acts as a firewall/web-server/what do I know... @@ -239,25 +239,25 @@ PC Memory Utilization - + Contributed by &a.joerg;. 16 Apr 1995. - + A short description of how FreeBSD uses memory on the i386 platform - + The boot sector will be loaded at 0:0x7c00, and relocates itself immediately to 0x7c0:0. (This is nothing magic, just an adjustment for the %cs selector, done by an ljmp.) - + It then loads the first 15 sectors at 0x10000 (segment BOOTSEG in the biosboot Makefile), and sets up the stack to work below 0x1fff0. After this, it jumps to the entry of boot2 within that code. I.e., it jumps over itself and the (dummy) partition table, and it is going to adjust the %cs selector—we are still in 16-bit mode there. - + boot2 asks for the boot file, and examines the a.out header. It masks the file entry point (usually 0xf0100000) by @@ -265,7 +265,7 @@ usual load point is 1 MB (0x00100000). During load, the boot code toggles back and forth between real and protected mode, to use the BIOS in real mode. - + The boot code itself uses segment selectors 0x18 and 0x20 for %cs and %ds/%es in protected mode, and @@ -273,16 +273,16 @@ finally started with %cs 0x08 and %ds/%es/%ss 0x10, which refer to dummy descriptors covering the entire address space. - + The kernel will be started at its load point. Since it has been linked for another (high) address, it will have to execute PIC until the page table and page directory stuff is setup properly, at which point paging will be enabled and the kernel will finally run at the address for which it was linked. - + Contributed by &a.dg;. 16 Apr 1995. - + The physical pages immediately following the kernel BSS contain proc0's page directory, page tables, and upages. Some time later when the VM system is initialized, the physical memory between @@ -297,43 +297,43 @@ Copyright © 1995,1997 &a.uhclem;, All Rights Reserved. 10 December 1996. Last Update 8 October 1997. - + Direct Memory Access (DMA) is a method of allowing data to be moved from one location to another in a computer without intervention from the central processor (CPU). - + The way that the DMA function is implemented varies between computer architectures, so this discussion will limit itself to the implementation and workings of the DMA subsystem on the IBM Personal Computer (PC), the IBM PC/AT and all of its successors and clones. - + The PC DMA subsystem is based on the Intel 8237 DMA controller. The 8237 contains four DMA channels that can be programmed independently and any one of the channels may be active at any moment. These channels are numbered 0, 1, 2 and 3. Starting with the PC/AT, IBM added a second 8237 chip, and numbered those channels 4, 5, 6 and 7. - + The original DMA controller (0, 1, 2 and 3) moves one byte in each transfer. The second DMA controller (4, 5, 6, and 7) moves 16-bits from two adjacent memory locations in each transfer, with the first byte always coming from an even-numbered address. The two controllers are identical components and the difference in transfer size is caused by the way the second controller is wired into the system. - + The 8237 has two electrical signals for each channel, named DRQ and -DACK. There are additional signals with the names HRQ (Hold Request), HLDA (Hold Acknowledge), -EOP (End of Process), and the bus control signals -MEMR (Memory Read), -MEMW (Memory Write), -IOR (I/O Read), and -IOW (I/O Write). - + 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 a memory address, but not between two I/O ports or two memory locations. - + The 8237 does allow two channels to be connected together to allow memory-to-memory DMA operations in a non-“fly-by” mode, @@ -341,11 +341,11 @@ it is faster to move data between memory locations using the CPU. - + In the PC architecture, each DMA channel is normally activated only when the hardware that uses a given DMA channel requests a transfer by asserting the DRQ line for that channel. - + A Sample DMA transfer @@ -514,7 +514,7 @@ 32 bit address space, without the use of bounce buffers. - + DMA Operational Modes and Settings @@ -536,7 +536,7 @@ only has a one-byte buffer, so it uses this mode. - + Block/Demand @@ -562,7 +562,7 @@ locations used in the transfer were above the 16Meg mark. - + Cascade @@ -644,7 +644,7 @@ other high-performance peripheral controllers. - + Autoinitialize @@ -669,7 +669,7 @@ - + Programming the DMA @@ -701,7 +701,7 @@ system, which describes where the DMA and Page Register ports are located. A complete port map table is located below. - + DMA Port Map @@ -817,9 +817,9 @@ - + DMA Command Registers - + @@ -927,9 +927,9 @@ 0xc0–0xdf DMA Controller #2 (Channels 4, 5, 6 and 7) - + DMA Address and Count Registers - + @@ -1031,9 +1031,9 @@ - + DMA Command Registers - + @@ -1141,7 +1141,7 @@ 0x80–0x9f DMA Page Registers - + @@ -1199,7 +1199,7 @@ 0x400–0x4ff 82374 Enhanced DMA Registers - + The Intel 82374 EISA System Component (ESC) was introduced in early 1996 and includes a DMA controller that provides a superset of 8237 functionality as well as other PC-compatible core peripheral @@ -1216,7 +1216,7 @@ Writing to a traditional 8237 register forces the contents of some of the 82374 enhanced registers to zero to provide backward software compatibility. - + @@ -1624,7 +1624,7 @@ Except for the wired state, the page is typically placed in a doubly link list queue representing the state that it is in. Wired pages are not placed on any queue. - + FreeBSD implements a more involved paging queue for cached and free pages in order to implement page coloring. Each of these states involves multiple queues arranged according to the size of the @@ -1632,12 +1632,12 @@ FreeBSD attempts to obtain one that is reasonably well aligned from the point of view of the L1 and L2 caches relative to the VM object the page is being allocated for. - + Additionally, a page may be held with a reference count or locked with a busy count. The VM system also implements an “ultimate locked” state for a page using the PG_BUSY bit in the page's flags. - + In general terms, each of the paging queues operates in a LRU fashion. A page is typically placed in a wired or active state initially. When wired, the page is usually associated with a page @@ -1649,14 +1649,14 @@ the number of pages in the free queue, but a certain minimum number of truly free pages must be maintained in order to accommodate page allocation at interrupt time. - + If a process attempts to access a page that does not exist in its page table but does exist in one of the paging queues ( such as the inactive or cache queues), a relatively inexpensive page reactivation fault occurs which causes the page to be reactivated. If the page does not exist in system memory at all, the process must block while the page is brought in from disk. - + FreeBSD dynamically tunes its paging queues and attempts to maintain reasonable ratios of pages in the various queues as well as attempts to maintain a reasonable breakdown of clean vs dirty pages. @@ -1682,14 +1682,14 @@ file-backed storage. Since the filesystem uses the same VM objects to manage in-core data relating to files, the result is a unified buffer cache. - + VM objects can be shadowed. That is, they can be stacked on top of each other. For example, you might have a swap-backed VM object stacked on top of a file-backed VM object in order to implement a MAP_PRIVATE mmap()ing. This stacking is also used to implement various sharing properties, including, copy-on-write, for forked address spaces. - + It should be noted that a vm_page_t can only be associated with one VM object at a time. The VM object shadowing implements the perceived sharing of the same page across multiple @@ -1707,7 +1707,7 @@ its backing s tore. Additionally, filesystems need to be able to map portions of a file or file metadata into KVM in order to operate on it. - + The entities used to manage this are known as filesystem buffers, struct buf's, and also known as bp's. When a filesystem needs to operate on a @@ -1719,7 +1719,7 @@ duration of the I/O. Filesystem buffers also have their own notion of being busy, which is useful to filesystem driver code which would rather operate on filesystem buffers instead of hard VM pages. - + FreeBSD reserves a limited amount of KVM to hold mappings from struct bufs, but it should be made clear that this KVM is used solely to hold mappings and does not limit the ability to cache data. @@ -1739,7 +1739,7 @@ fly and are usually considered throwaway. Special page tables such as those managing KVM are typically permanently preallocated. These page tables are not throwaway. - + FreeBSD associates portions of vm_objects with address ranges in virtual memory through vm_map_t and vm_entry_t structures. Page tables are directly @@ -1763,14 +1763,14 @@ FreeBSD uses KVM to hold various kernel structures. The single largest entity held in KVM is the filesystem buffer cache. That is, mappings relating to struct buf entities. - + Unlike Linux, FreeBSD does NOT map all of physical memory into KVM. This means that FreeBSD can handle memory configurations up to 4G on 32 bit platforms. In fact, if the mmu were capable of it, FreeBSD could theoretically handle memory configurations up to 8TB on a 32 bit platform. However, since most 32 bit platforms are only capable of mapping 4GB of ram, this is a moot point. - + KVM is managed through several mechanisms. The main mechanism used to manage KVM is the zone allocator. The zone allocator takes a chunk of KVM and splits it up into @@ -1790,7 +1790,7 @@ /usr/src/sys/i386/conf/CONFIG_FILE. A description of all available kernel configuration options can be found in /usr/src/sys/i386/conf/LINT. - + In a large system configuration you may wish to increase maxusers. Values typically range from 10 to 128. Note that raising maxusers too high can cause the @@ -1798,11 +1798,11 @@ It is better to leave maxusers at some reasonable number and add other options, such as NMBCLUSTERS, to increase specific resources. - + If your system is going to use the network heavily, you may want to increase NMBCLUSTERS. Typical values range from 1024 to 4096. - + The NBUF parameter is also traditionally used to scale the system. This parameter determines the amount of KVA the system can use to map filesystem buffers for I/O. Note that this @@ -1823,16 +1823,16 @@ makeoptions DEBUG="-g" makeoptions COPTFLAGS="-O2 -pipe" - + Sysctl provides a way to tune kernel parameters at run-time. You typically do not need to mess with any of the sysctl variables, especially the VM related ones. - + Run time VM and system tuning is relatively straightforward. First, use softupdates on your UFS/FFS filesystems whenever possible. /usr/src/contrib/sys/softupdates/README contains instructions (and restrictions) on how to configure it up. - + Second, configure sufficient swap. You should have a swap partition configured on each physical disk, up to four, even on your “work” disks. You should have at least 2x the swap space @@ -1843,7 +1843,7 @@ makeoptions COPTFLAGS="-O2 -pipe" able to accommodate a crash dump, your first swap partition must be at least as large as main memory and /var/crash must have sufficient free space to hold the dump. - + NFS-based swap is perfectly acceptable on -4.x or later systems, but you must be aware that the NFS server will take the brunt of the paging load. diff --git a/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml b/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml index b2e28e9bf1..8a2df78d1d 100644 --- a/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml @@ -1,7 +1,7 @@ @@ -27,7 +27,7 @@ architecture. FreeBSD provides you with many advanced features previously available only on much more expensive systems. These features include: - + Preemptive multitasking with @@ -139,7 +139,7 @@ the commercial giants struggle to field PC operating systems with such features, performance and reliability, FreeBSD can offer them now! - + The applications to which FreeBSD can be put are truly limited only by your own imagination. From software development to factory automation, inventory control to azimuth correction of remote satellite @@ -149,7 +149,7 @@ applications developed by research centers and universities around the world, often available at little to no cost. Commercial applications are also available and appearing in greater numbers every day. - + Because the source code for FreeBSD itself is generally available, the system can also be customized to an almost unheard of degree for special applications or projects, and in ways not generally possible @@ -188,7 +188,7 @@ And more... - + With FreeBSD, you can easily start out small with an inexpensive 386 class PC and upgrade all the way up to a quad-processor Xeon with RAID storage as your enterprise @@ -271,7 +271,7 @@ 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. - + It did not take us long to decide that the goal remained worthwhile, even without Bill's support, and so we adopted the name “FreeBSD”, coined by David Greenman. Our initial objectives @@ -285,14 +285,14 @@ Walnut Creek CDROM's almost unprecedented degree of faith in what was, at the time, a completely unknown project, it is quite unlikely that FreeBSD would have gotten as far, as fast, as it has today. - + 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 (“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 1994. - + Around this time, some rather unexpected storm clouds formed on 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 @@ -306,7 +306,7 @@ 1994 to stop shipping its own Net/2 based product. Under the terms of that agreement, the project was allowed one last release before the deadline, that release being FreeBSD 1.1.5.1. - + 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 “Lite” releases were light in part because @@ -319,7 +319,7 @@ rough around the edges, the release was a significant success and was followed by the more robust and easier to install FreeBSD 2.0.5 release in June of 1995. - + We released FreeBSD 2.1.5 in August of 1996, and it appeared to be popular enough among the ISP and commercial communities that another release along the 2.1-stable branch was merited. This was FreeBSD @@ -327,7 +327,7 @@ development on 2.1-stable. Now in maintenance mode, only security enhancements and other critical bug fixes will be done on this branch (RELENG_2_1_0). - + FreeBSD 2.2 was branched from the development mainline (“-current”) in November 1996 as the RELENG_2_2 branch, and the first full release (2.2.1) was released in April, 1997. Further @@ -362,7 +362,7 @@ provides the widest possible benefit. This is, I believe, one of the most fundamental goals of Free Software and one that we enthusiastically support. - + That code in our source tree which falls under the GNU General Public License (GPL) or Library General Public License (LGPL) comes with slightly more strings attached, though at least on the side of enforced access @@ -389,10 +389,10 @@ to distribute their own patches or work-in-progress sources. The &a.announce; is also available to those wishing to make other FreeBSD users aware of major areas of work. - + Useful things to know about the FreeBSD project and its development process, whether working independently or in close cooperation: - + The CVS repository The FreeBSD core team - + The FreeBSD core team would be equivalent to the board of directors if the FreeBSD Project @@ -468,7 +468,7 @@ Outside contributors - + Last, but definitely not least, the largest group of developers are the users themselves who provide feedback and @@ -515,7 +515,7 @@ Alpha based computer systems. It is based primarily on software from U.C. Berkeley's CSRG group, with some enhancements from NetBSD, OpenBSD, 386BSD, and the Free Software Foundation. - + Since our release of FreeBSD 2.0 in late 94, the performance, feature set, and stability of FreeBSD has improved dramatically. The largest change is a revamped virtual memory system with a merged VM/file @@ -526,12 +526,12 @@ an improved SCSI subsystem, ISDN support, support for ATM, FDDI, Fast and Gigabit Ethernet (1000Mbit) adapters, improved support for the latest Adaptec controllers and many hundreds of bug fixes. - + We have also taken the comments and suggestions of many of our users to heart and have attempted to provide what we hope is a more sane and easily understood installation process. Your feedback on this (constantly evolving) process is especially welcome! - + In addition to the base distributions, FreeBSD offers a new ported software collection with hundreds of commonly sought-after programs. By mid-September 1999, there were more than 2600 ports! The list of @@ -550,7 +550,7 @@ 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. - + A number of additional documents which you may find very helpful in the process of installing and using FreeBSD may now also be found in the /usr/share/doc directory on any machine running @@ -569,7 +569,7 @@ The FreeBSD FAQ - + file:/usr/share/doc/FAQ/FAQ.html @@ -589,7 +589,7 @@ outside the U.S.) exportable European distribution of DES for our non-U.S. users also exists and is described in the FreeBSD FAQ. - + If password security for FreeBSD is all you need, and you have no requirement for copying encrypted passwords from different hosts (Suns, DEC machines, etc) into FreeBSD password entries, then FreeBSD's MD5 diff --git a/en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml b/en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml index ebc543fdf4..014292ce36 100644 --- a/en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml @@ -1,7 +1,7 @@ @@ -68,7 +68,7 @@ while everything outside the i386 directory is common to all platforms which FreeBSD could potentially be ported to. - + If there is not a /usr/src/sys directory on your system, then the @@ -90,7 +90,7 @@ maintaining multiple FreeBSD machines with different hardware, it is a good idea to name it after your machine's hostname. We will call it MYKERNEL for the purpose of this example. - + You must execute these and all of the following commands under the root account or you will get permission denied @@ -107,7 +107,7 @@ comment lines at the top to reflect your configuration or the changes you have made to differentiate it from GENERIC. - + If you have build a kernel under SunOS or some other BSD operating system, much of this file will be very familiar to you. If you are coming from some other operating system such as DOS, on the other hand, @@ -169,14 +169,14 @@ directory as GENERIC. If you are in doubt as to the purpose or necessity of a line, check first in LINT. - + The kernel is currently being moved to a better organization of the option handling. Traditionally, each option in the config file was simply converted into a switch for the CFLAGS line of the kernel Makefile. Naturally, this caused a creeping optionism, with nobody really knowing which option has been referenced in what files. - + In the new scheme, every #ifdef that is intended to be dependent upon an option gets this option out of an opt_foo.h declaration @@ -226,7 +226,7 @@ alpha. - + cpu "cpu_type" @@ -277,7 +277,7 @@ cpu_type. - + ident machine_name @@ -302,7 +302,7 @@ vax. - + maxusers number @@ -344,7 +344,7 @@ - + config kernel_name root on @@ -393,7 +393,7 @@ - + options "COMPAT_43" @@ -402,7 +402,7 @@ will act strangely if you comment this out. - + options UCONSOLE @@ -414,7 +414,7 @@ as any console messages sent by the kernel. - + options SYSVSHM @@ -427,7 +427,7 @@ definitely want to include this. - + options SYSVSEM @@ -436,7 +436,7 @@ only adds a few hundred bytes to the kernel. - + options SYSVMSG @@ -476,7 +476,7 @@ from the hard disk. - + options NFS @@ -486,7 +486,7 @@ out. - + options MSDOSFS @@ -501,7 +501,7 @@ all). - + options "CD9660" @@ -512,7 +512,7 @@ data CD). Audio CD's do not need this filesystem. - + options PROCFS @@ -523,7 +523,7 @@ what processes are running. - + options MFS @@ -557,7 +557,7 @@ - + options "EXT2FS" @@ -568,7 +568,7 @@ the two systems. - + options QUOTA @@ -600,7 +600,7 @@ run FreeBSD at this time. - + controller eisa0 @@ -609,7 +609,7 @@ EISA bus. - + controller pci0 @@ -619,7 +619,7 @@ ISA bus. - + controller fdc0 @@ -638,7 +638,7 @@ - + controller wdc0 @@ -652,7 +652,7 @@ all six lines, for example). - + device acd0 @@ -665,7 +665,7 @@ line options ATAPI. - + device npx0 at isa? port "IO_NPX" irq 13 vector npxintr @@ -677,7 +677,7 @@ optional. - + device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr @@ -686,7 +686,7 @@ Wangtek and Archive QIC-02/QIC-36 tape drive support - + Proprietary CD-ROM support @@ -848,7 +848,7 @@ - + options SCSI_DELAY=15000 @@ -861,7 +861,7 @@ your SCSI devices, you will have to raise it back up. - + controller scbus0 @@ -871,7 +871,7 @@ and the following three lines, out. - + device da0 @@ -879,7 +879,7 @@ Support for SCSI hard drives. - + device sa0 @@ -887,7 +887,7 @@ Support for SCSI tape drives. - + device cd0 @@ -895,7 +895,7 @@ Support for SCSI CD-ROM drives. - + device ch0 @@ -904,7 +904,7 @@ as tape libraries. - + device pass0 @@ -1056,7 +1056,7 @@ - + device mse0 at isa? port 0x23c tty irq 5 vector ms @@ -1073,7 +1073,7 @@ - + device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr @@ -1122,7 +1122,7 @@ used. - + controller ppbus0 @@ -1130,7 +1130,7 @@ Provides support for the parallel port bus. - + device ppc0 at isa? port? tty irq 7 @@ -1138,7 +1138,7 @@ ISA-bus parallel port interface. - + device lpt0 at ppbus? @@ -1173,7 +1173,7 @@ your PC) so this is essentially mandatory. - + Ethernet cards @@ -1362,7 +1362,7 @@ back at you through this pseudo-device. Mandatory. - + pseudo-device ether @@ -1372,7 +1372,7 @@ code. - + pseudo-device sl number @@ -1389,7 +1389,7 @@ linkend="slips">server. - + pseudo-device ppp number @@ -1407,7 +1407,7 @@ simultaneous PPP connections to support. - + pseudo-device tun number @@ -1422,7 +1422,7 @@ for more information. - + pseudo-device bpfilter number @@ -1463,7 +1463,7 @@ pcm. - + device pas0 at isa? port 0x388 irq 10 drq 6 vector pasintr @@ -1472,7 +1472,7 @@ ProAudioSpectrum digital audio and MIDI. - + device sb0 at isa? port 0x220 irq 7 conflicts drq 1 vector sbintr @@ -1488,7 +1488,7 @@ - + device sbxvi0 at isa? drq 5 @@ -1502,7 +1502,7 @@ - + device sbmidi0 at isa? port 0x330 @@ -1512,7 +1512,7 @@ compile. - + device gus0 at isa? port 0x220 irq 10 drq 1 vector gusintr @@ -1521,7 +1521,7 @@ Gravis Ultrasound. - + device mss0 at isa? port 0x530 irq 10 drq 1 vector adintr @@ -1530,7 +1530,7 @@ Microsoft Sound System. - + device opl0 at isa? port 0x388 conflicts @@ -1542,7 +1542,7 @@ (in the ports collection). - + device mpu0 at isa? port 0x330 irq 6 drq 0 @@ -1551,7 +1551,7 @@ Roland MPU-401 stand-alone card. - + device uart0 at isa? port 0x330 irq 5 vector "m6850intr" @@ -1560,7 +1560,7 @@ Stand-alone 6850 UART for MIDI. - + device pca0 at isa? port "IO_TIMER1" tty @@ -1619,7 +1619,7 @@ - + pseudo-device log @@ -1628,7 +1628,7 @@ messages. Mandatory. - + pseudo-device pty number - + pseudo-device snp number @@ -1660,7 +1660,7 @@ of simultaneous snoop sessions. Optional. - + pseudo-device vn @@ -1672,7 +1672,7 @@ Optional. - + pseudo-device ccd number @@ -1707,7 +1707,7 @@ PC joystick device. - + pseudo-device speaker @@ -1745,7 +1745,7 @@ of them, so when you add support for a new device, it pays to make sure that the appropriate entries are in this directory, and if not, add them. Here is a simple example: - + Suppose you add the IDE CD-ROM support to the kernel. The line to add is: @@ -1764,7 +1764,7 @@ device acd0 When this script finishes, you will find that there are now acd0c and racd0c entries in /dev so you know that it executed correctly. - + For sound cards, the command: &prompt.root; sh MAKEDEV snd0 @@ -1833,7 +1833,7 @@ device acd0 Kernel will not boot - + If your new kernel does not boot, or fails to recognize your devices, do not panic! Fortunately, BSD has an excellent mechanism @@ -1881,7 +1881,7 @@ device acd0 Kernel works, but ps does not work any more! - + If you have installed a different version of the kernel from the one that the system utilities have been built with, for diff --git a/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml b/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml index 1ebf9d9620..ce7b253523 100644 --- a/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml @@ -1,7 +1,7 @@ @@ -55,7 +55,7 @@ some programs will drastically increase, and since the whole kernel is loaded entirely at boot time and cannot be swapped out later, several megabytes of physical memory will be wasted. - + If you are testing a new kernel, for example by typing the new kernel's name at the boot prompt, but need to boot a different one in order to get your system up and running again, boot it only into single @@ -186,7 +186,7 @@ line 20: - + This is the location of function trap() in the stack trace. @@ -195,7 +195,7 @@ line 36: - + Force usage of a new stack frame; this is no longer necessary now. The stack frames are supposed to point to the right @@ -210,7 +210,7 @@ line 52: - + The pointer looks suspicious, but happens to be a valid address. @@ -219,7 +219,7 @@ line 56: - + However, it obviously points to garbage, so we have found our error! (For those unfamiliar with that particular piece of code: @@ -251,7 +251,7 @@ What do you do if a kernel dumped core but you did not expect it, and it is therefore not compiled using config -g? Not everything is lost here. Do not panic! - + Of course, you still need to enable crash dumps. See above on the options you have to specify in order to do this. @@ -271,14 +271,14 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols - + Go and examine the dump as described above. The debugging symbols might be incomplete for some places, as can be seen in the stack trace in the example above where some functions are displayed without line numbers and argument lists. If you need more debugging symbols, remove the appropriate object files and repeat the kgdb session until you know enough. - + All this is not guaranteed to work, but it will do it fine in most cases. @@ -290,14 +290,14 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols - + If you need to do low-level debugging on your kernel, there is an on-line debugger available called DDB. It allows to setting breakpoints, single-stepping kernel functions, examining and changing kernel variables, etc. However, it cannot access kernel source files, and only has access to the global and static symbols, not to the full debug information like kgdb. - + To configure your kernel to include DDB, add the option line @@ -318,7 +318,7 @@ options DDB right at the boot prompt. The kernel will start up in debug mode and enter DDB prior to any device probing. Hence you can even debug the device probe/attach functions. - + The second scenario is a hot-key on the keyboard, usually Ctrl-Alt-ESC. For syscons, this can be remapped; some of the distributed maps do this, so watch out. There is an option available @@ -327,11 +327,11 @@ options DDB in the kernel config file). It is not the default since there are a lot of crappy serial adapters around that gratuitously generate a BREAK condition, for example when pulling the cable. - + The third way is that any panic condition will branch to DDB if the kernel is configured to use it. For this reason, it is not wise to configure a kernel with DDB for a machine running unattended. - + The DDB commands roughly resemble some gdb commands. The first thing you probably need to do is to set a breakpoint: @@ -344,7 +344,7 @@ options DDB a-f need to be preceded with 0x (this is optional for other numbers). Simple expressions are allowed, for example: function-name + 0x103. - + To continue the operation of an interrupted kernel, simply type: @@ -419,11 +419,11 @@ options DDB specifies the size of the data to be written, the first following expression is the address to write to and the remainder is interpreted as data to write to successive memory locations. - + If you need to know the current registers, use: show reg - + Alternatively, you can display a single register value by e.g. p $eax @@ -468,7 +468,7 @@ options DDB is the final way out of disaster and almost the same as hitting the Big Red Button. - + If you need a short command summary, simply type: help @@ -493,7 +493,7 @@ options DDB with all the symbols in it, and the other one is the target machine that simply runs a similar copy of the very same kernel (but stripped of the debugging information). - + You should configure the kernel in question with config -g, include into the configuration, and compile it as usual. This gives a large blurb of a binary, due to the @@ -573,7 +573,7 @@ text_addr = 0xf5109020? (y or n) y Debugging a Console Driver - + Since you need a console driver to run DDB on, things are more complicated if the console driver itself is failing. You might remember the use of a serial console (either with modified boot blocks, or by diff --git a/en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml b/en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml index de1012a5e7..b133e948f2 100644 --- a/en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml @@ -1,7 +1,7 @@ @@ -41,39 +41,39 @@ #ifndef THIS_OPTION #define THIS_OPTION (some_default_value) #endif /* THIS_OPTION */ - + This way, an administrator mentioning another value for the option in his config file will take the default out of effect, and replace it with his new value. Clearly, the new value will be substituted into the source code during the preprocessor run, so it must be a valid C expression in whatever context the default value would have been used. - + It is also possible to create value-less options that simply enable or disable a particular piece of code by embracing it in - + #ifdef THAT_OPTION [your code here] #endif - + Simply mentioning THAT_OPTION in the config file (with or without any value) will then turn on the corresponding piece of code. - + People familiar with the C language will immediately recognize that everything could be counted as a “config option” where there is at least a single #ifdef referencing it... However, it's unlikely that many people would put - + options notyet,notdef - + in their config file, and then wonder why the kernel compilation falls over. :-) - + Clearly, using arbitrary names for the options makes it very hard to track their usage throughout the kernel source tree. That is the rationale behind the new-style option scheme, where @@ -83,7 +83,7 @@ options notyet,notdef the usual Makefile dependencies could be applied, and make can determine what needs to be recompiled once an option has been changed. - + The old-style option mechanism still has one advantage for local options or maybe experimental options that have a short anticipated lifetime: since it is easy to add a new #ifdef to the @@ -104,7 +104,7 @@ options notyet,notdef e. g. sys/i386/conf/options.i386), and select an opt_foo.h file where your new option would best go into. - + If there is already something that comes close to the purpose of the new option, pick this. For example, options modifying the overall behaviour of the SCSI subsystem can go into @@ -113,7 +113,7 @@ options notyet,notdef implies its value will go into the corresponding file opt_foo.h. This can be overridden on the right-hand side of a rule by specifying another filename. - + If there is no opt_foo.h already available for the intended new option, invent a new name. Make it @@ -122,12 +122,12 @@ options notyet,notdef file. &man.config.8; will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves.. - + Packing too many options into a single opt_foo.h will cause too many kernel files to be rebuilt when one of the options has been changed in the config file. - + Finally, find out which kernel files depend on the new option. Unless you have just invented your option, and it does not exist anywhere yet, &prompt.user; find /usr/src/sys -name @@ -139,7 +139,7 @@ options notyet,notdef the regular include files, if the defaults are of the form #ifndef NEW_OPTION #define NEW_OPTION (something) #endif in the regular header. - + Adding an option that overrides something in a system header file (i.e., a file sitting in /usr/include/sys/) is almost always a mistake. diff --git a/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml b/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml index da83fe2442..a520480abf 100644 --- a/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml @@ -1,7 +1,7 @@ @@ -30,7 +30,7 @@ options "SC_MOUSE_CHAR=0x03" to move character codes used for mouse cursor off KOI8-R pseudographics range. - + Russian console entry in /etc/rc.conf should looks like: @@ -59,7 +59,7 @@ font8x8=cp866-8x8 Shift+CapsLock. CapsLock LED will indicate RUS mode, not CapsLock mode. - + For each ttyv? entry in /etc/ttys change terminal type from @@ -83,7 +83,7 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure LANG for POSIX &man.setlocale.3; family functions; - + MM_CHARSET for applications MIME character set. @@ -97,17 +97,17 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure Login Class Method - + First of all check your /etc/login.conf have russian login class, this entry may looks like: - + russian:Russian Users Accounts:\ :charset=KOI8-R:\ :lang=ru_RU.KOI8-R:\ :tc=default: - + How to do it with &man.vipw.8; @@ -118,7 +118,7 @@ russian:Russian Users Accounts:\ user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh - + How to do it with &man.adduser.8; @@ -153,7 +153,7 @@ defaultclass = russian - + How to do it with &man.pw.8; @@ -166,12 +166,12 @@ defaultclass = russian Shell Startup Files Method - + If you don't want to use login class method for some reasons, just set this two environment variables in the following shell startup files: - + /etc/profile: @@ -189,7 +189,7 @@ setenv LANG ru_RU.KOI8-R setenv MM_CHARSET KOI8-R - + Alternatively you can add this instructions to @@ -259,7 +259,7 @@ lp|Russian local line printer:\ less than 3.3 first). - + Go to /usr/ports/russian/X.language directory and say @@ -281,7 +281,7 @@ FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/100dpi" If you use high resolution video mode, swap 75 dpi and 100 dpi lines. - + To activate Russian keyboard add diff --git a/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml b/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml index 6078b29aa4..a95f3724d0 100644 --- a/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml @@ -1,7 +1,7 @@ @@ -19,16 +19,16 @@ &rel.current;-RELEASE is vastly more capable and runs all these as well as Oracle8, WordPerfect, StarOffice, Acrobat, Quake, Abuse, IDL, and netrek for Linux and a whole host of other programs. - + There are some Linux-specific operating system features that are not supported on FreeBSD. Linux binaries will not work on FreeBSD if they overly use the Linux /proc filesystem (which is different from the optional FreeBSD /proc filesystem) or i386-specific calls, such as enabling virtual 8086 mode. - + Depending on which version of FreeBSD you are running, how you get Linux mode up will vary somewhat: - + Installing Linux Mode in 3.0-RELEASE and later @@ -210,7 +210,7 @@ linux Installing using the linux_base port - + Most Linux applications use shared libraries, so you are still not done until you install the shared libraries. It is possible to do this by hand, however, it is vastly simpler to just grab the @@ -231,7 +231,7 @@ linux Installing libraries manually - + 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. @@ -262,7 +262,7 @@ linux How to install additional shared libraries - + What if you install the linux_base port and your application still complains about missing shared libraries? How do you know which shared libraries Linux binaries need, and where to @@ -281,7 +281,7 @@ linux libXt.so.3 (DLL Jump 3.1) => /usr/X11/lib/libXt.so.3.1.0 libX11.so.3 (DLL Jump 3.1) => /usr/X11/lib/libX11.so.3.1.0 libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 - + You would need to get all the files from the last column, and put them under /compat/linux, with the names in the first column as symbolic links pointing to them. This means you @@ -321,7 +321,7 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 /compat/linux/lib/libc.so.4.6.29 /compat/linux/lib/libc.so.4 -> libc.so.4.6.29 - + The symbolic link mechanism is only needed for Linux binaries. The FreeBSD runtime linker takes care @@ -333,7 +333,7 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 Configuring the <filename>ld.so</filename> — for FreeBSD 2.2-RELEASE and later - + This section applies only to FreeBSD 2.2-RELEASE and later. Those running 2.1-STABLE should skip this section. @@ -350,7 +350,7 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 extra files you need from various ftp sites. Information on where to look for the various files is appended below. For now, let us assume you know where to get the files. - + Retrieve the following files (all from the same ftp site to avoid any version mismatches), and install them under /compat/linux (i.e. @@ -402,7 +402,7 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 the names of all the shared libraries and should be rerun to recreate this file whenever you install additional shared libraries. - + On 2.1-STABLE do not install /compat/linux/etc/ld.so.cache or run ldconfig; in 2.1-STABLE the syscalls are @@ -471,10 +471,10 @@ Abort Configuring the host name resolver If DNS does not work or you get the messages - + resolv+: "bind" is an invalid keyword resolv+: "hosts" is an invalid keyword - + then you need to configure a /compat/linux/etc/host.conf file containing: @@ -526,7 +526,7 @@ multi on sunsite.unc.edu:/pub/Linux/distributions - + tsx-11.mit.edu:/pub/linux/distributions @@ -538,11 +538,11 @@ multi on ftp.luth.se:/pub/linux/distributions - + ftp.demon.co.uk:/pub/unix/linux - + src.doc.ic.ac.uk:/packages/linux/distributions @@ -666,15 +666,15 @@ multi on slakware/a2/ldso.tgz - + slakware/a2/shlibs.tgz - + slakware/x6/oldlibs.tgz - + slakware/x9/xf_lib.tgz @@ -705,7 +705,7 @@ multi on DOS the cost of upgrading to the Linux version at the time this was written, March 1996, was $45.00. It can be ordered directly from Wolfram at (217) 398-6500 and paid for by credit card. - + Unpacking the Mathematica distribution diff --git a/en_US.ISO_8859-1/books/handbook/mail/chapter.sgml b/en_US.ISO_8859-1/books/handbook/mail/chapter.sgml index ddf08a6149..1b96df4f34 100644 --- a/en_US.ISO_8859-1/books/handbook/mail/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/mail/chapter.sgml @@ -1,7 +1,7 @@ @@ -25,7 +25,7 @@ These are the major programs involved in an E-Mail exchange. A “mailhost” is a server that is responsible for delivering and receiving all email for your host, and possibly your network. - + User program @@ -94,7 +94,7 @@ This handbook section has a complete reference on the Ports system. - + Modify /etc/inetd.conf to load the POP server. @@ -123,7 +123,7 @@ your own domain smallminingco.com - + Get mail delivered to the current DNS name for your host. Ie: dorm6.ahouse.school.edu diff --git a/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml b/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml index c1e4a2467b..8a1103abb4 100644 --- a/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml @@ -1,7 +1,7 @@ @@ -98,7 +98,7 @@ Australia - + In case of problems, please contact the hostmaster hostmaster@au.FreeBSD.org for this domain. @@ -129,7 +129,7 @@ Brazil - + In case of problems, please contact the hostmaster hostmaster@br.FreeBSD.org for this domain. @@ -175,7 +175,7 @@ Canada - + In case of problems, please contact the hostmaster hostmaster@ca.FreeBSD.org for this domain. @@ -211,7 +211,7 @@ In case of problems, please contact the hostmaster hostmaster@cz.FreeBSD.org for this domain. - + Denmark - + In case of problems, please contact the hostmaster hostmaster@dk.FreeBSD.org for this domain. @@ -243,7 +243,7 @@ Estonia - + In case of problems, please contact the hostmaster hostmaster@ee.FreeBSD.org for this domain. @@ -259,7 +259,7 @@ Finland - + In case of problems, please contact the hostmaster hostmaster@fi.FreeBSD.org for this domain. @@ -275,7 +275,7 @@ France - + In case of problems, please contact the hostmaster hostmaster@fr.FreeBSD.org for this domain. @@ -305,7 +305,7 @@ Germany - + In case of problems, please contact the mirrors admins de-bsd-hubs@de.freebsd.org for this domain. @@ -351,7 +351,7 @@ Hong Kong - + @@ -365,7 +365,7 @@ Ireland - + In case of problems, please contact the hostmaster hostmaster@ie.FreeBSD.org for this domain. @@ -381,7 +381,7 @@ Israel - + In case of problems, please contact the hostmaster hostmaster@il.FreeBSD.org for this domain. @@ -402,7 +402,7 @@ Japan - + In case of problems, please contact the hostmaster hostmaster@jp.FreeBSD.org for this domain. @@ -443,7 +443,7 @@ Korea - + In case of problems, please contact the hostmaster hostmaster@kr.FreeBSD.org for this domain. @@ -481,7 +481,7 @@ Netherlands - + In case of problems, please contact the hostmaster hostmaster@nl.FreeBSD.org for this domain. @@ -497,7 +497,7 @@ New Zealand - + In case of problems, please contact the hostmaster hostmaster@nz.FreeBSD.org for this domain. @@ -512,7 +512,7 @@ Poland - + In case of problems, please contact the hostmaster hostmaster@pl.FreeBSD.org for this domain. @@ -528,7 +528,7 @@ Portugal - + In case of problems, please contact the hostmaster hostmaster@pt.FreeBSD.org for this domain. @@ -549,7 +549,7 @@ Russia - + In case of problems, please contact the hostmaster hostmaster@ru.FreeBSD.org for this domain. @@ -595,7 +595,7 @@ South Africa - + In case of problems, please contact the hostmaster hostmaster@za.FreeBSD.org for this domain. @@ -621,7 +621,7 @@ Slovak Republic - + In case of problems, please contact the hostmaster hostmaster@sk.FreeBSD.org for this domain. @@ -635,7 +635,7 @@ Slovenia - + In case of problems, please contact the hostmaster hostmaster@si.FreeBSD.org for this domain. @@ -651,7 +651,7 @@ Spain - + In case of problems, please contact the hostmaster hostmaster@es.FreeBSD.org for this domain. @@ -666,7 +666,7 @@ Sweden - + In case of problems, please contact the hostmaster hostmaster@se.FreeBSD.org for this domain. @@ -723,7 +723,7 @@ Thailand - + @@ -736,7 +736,7 @@ Ukraine - + @@ -749,7 +749,7 @@ UK - + In case of problems, please contact the hostmaster hostmaster@uk.FreeBSD.org for this domain. @@ -780,7 +780,7 @@ USA - + In case of problems, please contact the hostmaster hostmaster@FreeBSD.org for this domain. @@ -829,7 +829,7 @@ South Africa - + Hostmaster hostmaster@internat.FreeBSD.org for this domain. @@ -850,7 +850,7 @@ Brazil - + Hostmaster hostmaster@br.FreeBSD.org for this domain. @@ -866,7 +866,7 @@ Finland - + @@ -885,7 +885,7 @@ CTM/FreeBSD is available via anonymous FTP from the following mirror sites. If you choose to obtain CTM via anonymous FTP, please try to use a site near you. - + In case of problems, please contact &a.phk;. @@ -904,7 +904,7 @@ Germany, Trier - + @@ -917,7 +917,7 @@ South Africa, backup server for old deltas - + @@ -930,7 +930,7 @@ Taiwan/R.O.C, Chiayi - + @@ -982,7 +982,7 @@ Australia - + @@ -995,7 +995,7 @@ Brazil - + @@ -1057,7 +1057,7 @@ Denmark - + @@ -1083,7 +1083,7 @@ Finland - + @@ -1114,7 +1114,7 @@ Germany - + @@ -1137,7 +1137,7 @@ Iceland - + @@ -1150,7 +1150,7 @@ Japan - + @@ -1184,7 +1184,7 @@ Korea - + @@ -1198,7 +1198,7 @@ Netherlands - + @@ -1216,7 +1216,7 @@ Norway - + @@ -1229,7 +1229,7 @@ Poland - + @@ -1242,7 +1242,7 @@ Russia - + @@ -1260,7 +1260,7 @@ Slovak Republic - + @@ -1291,7 +1291,7 @@ South Africa - + @@ -1322,7 +1322,7 @@ Sweden - + @@ -1335,7 +1335,7 @@ Taiwan - + @@ -1359,7 +1359,7 @@ Ukraine - + @@ -1373,7 +1373,7 @@ United Kingdom - + @@ -1391,7 +1391,7 @@ USA - + @@ -1453,7 +1453,7 @@ - + The following CVSup site is especially designed for CTM users. Unlike the other CVSup mirrors, it is kept up-to-date by CTM. @@ -1508,7 +1508,7 @@ Sweden - + The path to the files are: /afs/stacken.kth.se/ftp/pub/FreeBSD/ diff --git a/en_US.ISO_8859-1/books/handbook/pgpkeys/chapter.sgml b/en_US.ISO_8859-1/books/handbook/pgpkeys/chapter.sgml index 66ca51dce0..9f97eb14ff 100644 --- a/en_US.ISO_8859-1/books/handbook/pgpkeys/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/pgpkeys/chapter.sgml @@ -1,7 +1,7 @@ @@ -317,7 +317,7 @@ Sb97WRLEYDi686osaGfsuKNA87Rm+q5F+jxeUV4w4szoqp60gGvCbD0KCB2hWraP =QoiM -----END PGP PUBLIC KEY BLOCK----- - + &a.jdp; diff --git a/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml b/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml index a161306857..084c8f7c50 100644 --- a/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml @@ -1,7 +1,7 @@ @@ -20,27 +20,27 @@ If a particular portion of the FreeBSD distribution is being maintained by a person or group of persons, they can communicate this fact to the world by adding a - + MAINTAINER= email-addresses - + line to the Makefiles covering this portion of the source tree. - + The semantics of this are as follows: The maintainer owns and is responsible for that code. This means that he is responsible for fixing bugs and answer problem reports pertaining to that piece of the code, and in the case of contributed software, for tracking new versions, as appropriate. - + Changes to directories which have a maintainer defined shall be sent to the maintainer for review before being committed. Only if the maintainer does not respond for an unacceptable period of time, to several emails, will it be acceptable to commit changes without review by the maintainer. However, it is suggested that you try and have the changes reviewed by someone else if at all possible. - + It is of course not acceptable to add a person or group as maintainer unless they agree to assume this duty. On the other hand it doesn't have to be a committer and it can easily be a group of @@ -58,11 +58,11 @@ MAINTAINER= email-addresses actively being maintained outside the FreeBSD project. For historical reasons, we call this contributed software. Some examples are perl, gcc and patch. - + Over the last couple of years, various methods have been used in dealing with this type of software and all have some number of advantages and drawbacks. No clear winner has emerged. - + Since this is the case, after some debate one of these methods has been selected as the “official” method and will be required for future imports of software of this kind. Furthermore, it is @@ -72,7 +72,7 @@ MAINTAINER= email-addresses “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. - + Ultimately, however, it comes down to the people actually doing the work. If using this model is particularly unsuited to the package being dealt with, exceptions to these rules may be granted only with the @@ -93,28 +93,28 @@ MAINTAINER= email-addresses The Tcl embedded programming language will be used as example of how this model works: - + src/contrib/tcl contains the source as distributed by the maintainers of this package. Parts that are entirely not applicable for FreeBSD can be removed. In the case of Tcl, the mac, win and compat subdirectories were eliminated before the import - + src/lib/libtcl contains only a "bmake style" Makefile that uses the standard bsd.lib.mk makefile rules to produce the library and install the documentation. - + src/usr.bin/tclsh contains only a bmake style Makefile which will produce and install the tclsh program and its associated man-pages using the standard bsd.prog.mk rules. - + src/tools/tools/tcl_bmake contains a couple of shell-scripts that can be of help when the tcl software needs updating. These are not part of the built or installed software. - + The important thing here is that the src/contrib/tcl directory is created according to the rules: It is supposed to contain the sources as distributed (on a @@ -133,7 +133,7 @@ MAINTAINER= email-addresses be patched into the FreeBSD checked out version and "committed", as this destroys the vendor branch coherency and makes importing future versions rather difficult as there will be conflicts. - + Since many packages contain files that are meant for compatibility with other architectures and environments that FreeBSD, it is permissible to remove parts of the distribution tree that are of no @@ -148,7 +148,7 @@ MAINTAINER= email-addresses check in such utilities (as necessary) in the src/tools directory along with the port itself so that it is available to future maintainers. - + In the src/contrib/tcl level directory, a file called FREEBSD-upgrade should be added and it should states things like: @@ -177,7 +177,7 @@ MAINTAINER= email-addresses with the contributed source. Rather you should cvs add FREEBSD-upgrade ; cvs ci after the initial import. Example wording from src/contrib/cpio is below: - + This directory contains virgin sources of the original distribution files on a "vendor" branch. Do not, under any circumstances, attempt to upgrade @@ -316,12 +316,12 @@ obrien@FreeBSD.org - 30 March 1997 Contributed by &a.asami;, &a.peter;, and &a.obrien; 9 December 1996. - + If you are adding shared library support to a port or other piece of software that doesn't have one, the version numbers should follow these rules. Generally, the resulting numbers will have nothing to do with the release version of the software. - + The three principles of shared library building are: diff --git a/en_US.ISO_8859-1/books/handbook/ppp-and-slip/chapter.sgml b/en_US.ISO_8859-1/books/handbook/ppp-and-slip/chapter.sgml index 9e35438dd1..1ff8c615df 100644 --- a/en_US.ISO_8859-1/books/handbook/ppp-and-slip/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/ppp-and-slip/chapter.sgml @@ -1,7 +1,7 @@ @@ -36,13 +36,13 @@ ppp program can be run as and when desired. No PPP interface needs to be compiled into the kernel, as the program can use the generic tunnel device to get data into and out of the kernel. - + From here on out, user ppp will be referred to simply as ppp unless a distinction needs to be made between it and any other PPP client/server software such as pppd. Unless otherwise stated, all commands in this section should be executed as root. - + There are a large number of enhancements in version 2 of ppp. You can discover what version you have by running ppp with no arguments and typing show version at the prompt. It is a simple @@ -66,13 +66,13 @@ Your ISPs phone number(s). - + Your login name and password. This can be either a regular unix style login/password pair, or a PPP PAP or CHAP login/password pair. - + The IP addresses of one or more nameservers. Normally, you will be given two IP numbers. You must have @@ -100,7 +100,7 @@ This IP number is referred to as HISADDR by ppp. - + Your ISP's netmask. If your ISP hasn't given you this information, you can safely use a netmask of mtu 1500 Edit the <filename>/etc/host.conf</filename> file - + This file should contain the following two lines (in this order): @@ -247,7 +247,7 @@ bind Edit the <filename>/etc/hosts</filename>(5) file - + This file should contain the IP addresses and names of machines on your network. At a bare minimum it should contain entries for the machine which will be running ppp. Assuming that your machine @@ -258,7 +258,7 @@ bind 127.0.0.1 localhost 10.0.0.1 foo.bar.com foo - + The first line defines the alias localhost as a synonym for the current machine. Regardless of your own IP address, the IP address for this line should always be Edit the <filename>/etc/resolv.conf</filename> file - + /etc/resolv.conf tells the resolver how to behave. If you are running your own DNS, you may leave this file empty. Normally, you will need to enter the following @@ -294,7 +294,7 @@ domain bar.com and is probably unnecessary. Refer to the resolv.conf manual page for details of other possible entries in this file. - + If you are running PPP version 2 or greater, the enable dns command will tell PPP to request that your ISP confirms the nameserver values. If your ISP supplies different @@ -322,17 +322,17 @@ domain bar.com PPP and Static IP addresses - + You will need to create a configuration file called /etc/ppp/ppp.conf. It should look similar to the example below. - + Lines that end in a : start in the first column, all other lines should be indented as shown using spaces or tabs. - + 1 default: 2 set device /dev/cuaa0 @@ -498,21 +498,21 @@ protocol: ppp - + It is not necessary to add an entry to ppp.linkup when you have a static IP address as your routing table entries are already correct before you connect. You may however wish to create an entry to invoke programs after connection. This is explained later with the sendmail example. - + Example configuration files can be found in the /etc/ppp directory. PPP and Dynamic IP addresses - + If your service provider does not assign static IP numbers, ppp can be configured to negotiate the local and remote addresses. This is done by “guessing” an IP @@ -549,7 +549,7 @@ protocol: ppp - + If you are running version 1.x of PPP, you will also need to create an entry in /etc/ppp/ppp.linkup. ppp.linkup is used after a connection has been @@ -599,7 +599,7 @@ protocol: ppp - + See the pmdemand entry in the files /etc/ppp/ppp.conf.sample and /etc/ppp/ppp.linkup.sample for a detailed @@ -619,7 +619,7 @@ protocol: ppp This section describes setting up ppp in a server role. - + When you configure ppp to receive incoming calls on a machine connected to a LAN, you must decide if you wish to forward packets to the LAN. If you do, you should allocate the @@ -661,7 +661,7 @@ gateway=YES AutoPPP for more information on mgetty. - + PPP permissions @@ -683,7 +683,7 @@ allow users fred mary If this command is used in the default section, it gives the specified users access to everything. - + Setting up a PPP shell for dynamic-IP users @@ -729,7 +729,7 @@ pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup/etc/motd from being displayed. - + Setting up a PPP shell for static-IP users @@ -751,7 +751,7 @@ pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialupmary's shell should be /etc/ppp/ppp-mary). - + Setting up ppp.conf for dynamic-IP users @@ -782,7 +782,7 @@ ttyd1: unique IP address from your pool of IP addresses for dynamic users. - + Setting up <filename>ppp.conf</filename> for static-IP users @@ -820,7 +820,7 @@ sam: mary: add 203.14.103.0 netmask 255.255.255.0 HISADDR - + More on <command>mgetty</command>, AutoPPP, and MS extensions @@ -921,7 +921,7 @@ set nbns 203.14.100.5 PAP and CHAP authentication - + Some ISPs set their system up so that the authentication part of your connection is done using either of the PAP or CHAP authentication mechanisms. If this is the case, your ISP will not @@ -996,7 +996,7 @@ set nbns 203.14.100.5 Changing your <command>ppp</command> configuration on the fly - + It is possible to talk to the ppp program while it is running in the background, but only if a suitable diagnostic port has been set up. To do this, add the following line @@ -1004,7 +1004,7 @@ set nbns 203.14.100.5 set server /var/run/ppp-tun%d DiagnosticPassword 0177 - + This will tell PPP to listen to the specified unix-domain socket, asking clients for the specified password before allowing access. The %d in the name is replaced with the @@ -1123,29 +1123,29 @@ sendmail_flags="-bd" Ensure that the tun device is built into your kernel. - + Ensure that the tunX device file is available in the /dev directory. - + Create an entry in /etc/ppp/ppp.conf. The pmdemand example should suffice for most ISPs. - + If you have a dynamic IP address, create an entry in /etc/ppp/ppp.linkup. - + Update your /etc/rc.conf (or sysconfig) file. - + Create a start_if.tun0 script if you require demand dialing. @@ -1159,34 +1159,34 @@ sendmail_flags="-bd" Ensure that the tun device is built into your kernel. - + Ensure that the tunX device file is available in the /dev directory. - + Create an entry in /etc/passwd (using the &man.vipw.8; program). - + Create a profile in this users home directory that runs ppp -direct direct-server or similar. - + Create an entry in /etc/ppp/ppp.conf. The direct-server example should suffice. - + Create an entry in /etc/ppp/ppp.linkup. - + Update your /etc/rc.conf (or sysconfig) file. @@ -1219,9 +1219,9 @@ sendmail_flags="-bd" Before you start setting up PPP on your machine make sure that pppd is located in /usr/sbin and directory /etc/ppp exists. - + pppd can work in two modes: - + as a “client”, i.e. you want to connect your machine @@ -1237,10 +1237,10 @@ sendmail_flags="-bd" In both cases you will need to set up an options file (/etc/ppp/options or ~/.ppprc if you have more then one user on your machine that uses PPP). - + You also will need some modem/serial software (preferably kermit) so you can dial and establish connection with remote host. - + Working as a PPP client @@ -1272,11 +1272,11 @@ defaultroute # put this if you want that PPP server will be your enter your user name and password (or whatever is needed to enable PPP on the remote host) - + Exit kermit (without hanging up the line). - + enter: @@ -1654,12 +1654,12 @@ exit 1 Setting up a SLIP Client Contributed by &a.asami; 8 Aug 1995. - + The following is one way to set up a FreeBSD machine for SLIP on a static host network. For dynamic hostname assignments (i.e., your address changes each time you dial up), you probably need to do something much fancier. - + First, determine which serial port your modem is connected to. I have a symbolic link to /dev/modem from /dev/cuaa1, and only use the modem name in my @@ -1681,7 +1681,7 @@ pseudo-device sl 1 in your kernel's config file. It is included in the GENERIC kernel, so this will not be a problem unless you deleted it. - + Things you have to do only once @@ -1707,7 +1707,7 @@ pseudo-device sl 1 in your /etc/host.conf. Otherwise, funny things may happen. - + Edit the file /etc/rc.conf. Note that you should edit the file /etc/sysconfig @@ -1757,7 +1757,7 @@ defaultrouter=slip-gateway - + Make a file /etc/resolv.conf which contains: @@ -1821,7 +1821,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a am just too lazy. - + Leave the kermit there (you can suspend it by z) and as root, type: @@ -1835,7 +1835,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a - + How to shutdown the connection @@ -1869,12 +1869,12 @@ output ***\x0d, echo \x0aCONNECTED\x0a slattach (I have no idea why this can be fatal, but adding this flag solved the problem for at least one person) - + Using instead of (might be hard to see the difference on some fonts). - + Try ifconfig sl0 to see your interface status. I get: @@ -1925,7 +1925,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438 not answer all of your questions, and the author cannot be responsible if you damage your system or lose data due to attempting to follow the suggestions here. - + This guide was originally written for SLIP Server services on a FreeBSD 1.x system. It has been modified to reflect changes in the pathnames and the removal of the SLIP interface compression flags in @@ -1933,7 +1933,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438 between FreeBSD versions. If you do encounter mistakes in this document, please email the author with enough information to help correct the problem. - + Prerequisites @@ -1981,7 +1981,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438 An Example of a SLIP Server Login - + For example, if a SLIP user ID were Shelmerg, Shelmerg's entry in /etc/master.passwd would look something like @@ -2107,10 +2107,10 @@ pseudo-device sl 2 <filename>slip.hosts</filename> Configuration - + /etc/sliphome/slip.hosts contains lines which have at least four items, separated by whitespace: - + SLIP user's login ID @@ -2129,7 +2129,7 @@ pseudo-device sl 2 Network mask - + The local and remote addresses may be host names (resolved to IP addresses by /etc/hosts or by the domain name service, depending on your specifications in @@ -2147,7 +2147,7 @@ pseudo-device sl 2 Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp At the end of the line is one or more of the options. - + — no header compression @@ -2168,7 +2168,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp - + Note that sliplogin under early releases of FreeBSD 2 ignored the options that FreeBSD 1.x recognized, so the options , , @@ -2208,7 +2208,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp <filename>slip.login</filename> Configuration - + The typical /etc/sliphome/slip.login file looks like this: @@ -2288,7 +2288,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp <filename>slip.logout</filename> Configuration - + /etc/sliphome/slip.logout is not strictly needed (unless you are implementing “proxy ARP”), but if you decide to create it, this is an example of a basic @@ -2351,7 +2351,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp Static Routes - + Adding static routes to your nearest default routers can be troublesome (or impossible, if you do not have authority to do so...). If you have a multiple-router network in your organization, @@ -2364,7 +2364,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp Running <command>gated</command> - + An alternative to the headaches of static routes is to install gated on your FreeBSD SLIP server and configure it to use the appropriate routing protocols (RIP/OSPF/BGP/EGP) to @@ -2462,7 +2462,7 @@ import proto rip interface ed { - + Piero Serini diff --git a/en_US.ISO_8859-1/books/handbook/printing/chapter.sgml b/en_US.ISO_8859-1/books/handbook/printing/chapter.sgml index 22ac77e354..172951b3c8 100644 --- a/en_US.ISO_8859-1/books/handbook/printing/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/printing/chapter.sgml @@ -1,7 +1,7 @@ @@ -23,10 +23,10 @@ What the Spooler Does - + LPD controls everything about a host's printers. It is responsible for a number of things: - + It controls access to attached printers and printers attached to @@ -155,13 +155,13 @@ accept data to print instead of a serial or parallel interface, see Printers With Networked Data Stream Interaces. - + 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 get the printer working. - + Hardware Setup @@ -177,7 +177,7 @@ Ports and Cables - + Nearly all printers you can get for a PC today support one or both of the following interfaces: @@ -251,7 +251,7 @@ Parallel Ports - + To hook up a printer using a parallel interface, connect the Centronics cable between the printer and the computer. The instructions that came with the printer, the computer, or both @@ -264,12 +264,12 @@ Serial Ports - + To hook up a printer using a serial interface, connect the proper serial cable between the printer and the computer. The instructions that came with the printer, the computer, or both should give you complete guidance. - + If you are unsure what the “proper serial cable” is, you may wish to try one of the following alternatives: @@ -339,7 +339,7 @@ Communications gives some suggestions on how to do this. - + Set up LPD for the printer by modifying the file /etc/printcap. Section Kernel Configuration - + The operating system kernel is compiled to work with a specific set of devices. The serial or parallel interface for your printer is a part of that set. Therefore, it might be necessary to add @@ -365,22 +365,22 @@ Where N is the number of the serial port, starting from zero. If you see output similar to the following: - + sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A then the kernel supports the port. - + To find out if the kernel supports a parallel interface, type: - + &prompt.root; dmesg | grep lptN Where N is the number of the parallel port, starting from zero. If you see output similar to the following lpt0 at 0x378-0x37f on isa then the kernel supports the port. - + You might have to reconfigure your kernel in order for the operating system to recognize and use the parallel or serial port you are using for the printer. @@ -436,7 +436,7 @@ sio2: type 16550A - + Setting the Communication Mode for the Parallel Port @@ -535,7 +535,7 @@ device lpt0 at isa? port? tty vector lptintr your system boots. See &man.lptcontrol.8; for more information. - + Checking Printer Communications @@ -722,7 +722,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none Enabling the Spooler: The <filename>/etc/printcap</filename> File - + At this point, your printer should be hooked up, your kernel configured to communicate with it (if necessary), and you have been able to send some simple data to the printer. Now, we are ready to @@ -743,7 +743,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none The simple spooler configuration consists of the following steps: - + Pick a name (and a few convenient aliases) for the printer, @@ -792,7 +792,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none linkend="printing-troubleshooting">Troubleshooting. - + Language-based printers, such as PostScript printers, cannot directly print plain text. The simple setup outlined above and @@ -800,7 +800,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none installing such a printer you will print only files that the printer can understand. - + Users often expect that they can print plain text to any of the printers installed on your system. Programs that interface to LPD to do their printing usually make the same assumption. If you are @@ -861,7 +861,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4: S, panasonic, and Panasonic KX-P4455 PostScript v51.4. - + Suppressing Header Pages @@ -893,7 +893,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ single TAB. Every line in an entry except the last ends in a backslash character. - + Making the Spooling Directory @@ -1108,7 +1108,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ :sh:sd=/var/spool/lpd/bamboo:\ :lp=/dev/ttyd5:fs#0x82000c1:xs#0x820: - + Installing the Text Filter @@ -1174,7 +1174,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ :lp=/dev/ttyd5:fs#0x82000e1:xs#0x820:\ :if=/usr/local/libexec/if-simple: - + Trying It Out @@ -1224,7 +1224,7 @@ $%&'()*+,-./01234567 If the printer did not work, see the next section, Troubleshooting. - + Troubleshooting @@ -1533,7 +1533,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\ This section tells you how to use printers you have setup with FreeBSD. Here is an overview of the user-level commands: - + &man.lpr.1; @@ -1545,7 +1545,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\ &man.lpq.1; - + Check printer queues @@ -1553,7 +1553,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\ &man.lprm.1; - + Remove jobs from a printer's queue @@ -1597,7 +1597,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\ To select a specific printer, type: &prompt.user; lpr -P printer-name filename ... - + This example prints a long listing of the current directory to the printer named rattan: @@ -1676,7 +1676,7 @@ kelly: 2nd [job 010rose] mary: 3rd [job 011rose] /home/orchid/mary/research/venus/alpha-regio/mapping 78519 bytes - + Removing Jobs @@ -1707,7 +1707,7 @@ mary: 3rd [job 011rose] you. - + lprm user @@ -1717,7 +1717,7 @@ mary: 3rd [job 011rose] users' jobs; you can remove only your own jobs. - + lprm @@ -1771,7 +1771,7 @@ cfA013rose dequeued Formatting and Conversion Options - + The following &man.lpr.1; options control formatting of the files in the job. Use these options if the job does not contain plain text or if you want plain text formatted through the @@ -1796,7 +1796,7 @@ cfA013rose dequeued linkend="printing-advanced-convfilters">Conversion Filters gives details. - + @@ -1919,7 +1919,7 @@ cfA013rose dequeued Job Handling Options - + The following options to &man.lpr.1; tell LPD to handle the job specially: @@ -1999,7 +1999,7 @@ cfA013rose dequeued Header Page Options - + These options to &man.lpr.1; adjust the text that normally appears on a job's header page. If header pages are suppressed for the destination printer, these options have no effect. See section @@ -2059,11 +2059,11 @@ cfA013rose dequeued Start and stop the printers - + Enable and disable their queues - + Rearrange the order of the jobs in each queue. @@ -2102,7 +2102,7 @@ cfA013rose dequeued still submit jobs if the queue's enabled. - + clean printer-name @@ -2116,7 +2116,7 @@ cfA013rose dequeued removes them. - + disable printer-name @@ -2134,7 +2134,7 @@ cfA013rose dequeued enable command. - + down printer-name message @@ -2148,7 +2148,7 @@ cfA013rose dequeued status. - + enable printer-name @@ -2158,7 +2158,7 @@ cfA013rose dequeued the printer will not print anything until it is started. - + help command-name @@ -2170,7 +2170,7 @@ cfA013rose dequeued commands available. - + restart printer-name @@ -2185,7 +2185,7 @@ cfA013rose dequeued start. - + start printer-name @@ -2195,7 +2195,7 @@ cfA013rose dequeued queue. - + stop printer-name @@ -2207,7 +2207,7 @@ cfA013rose dequeued queue. - + topq printer-name job-or-username @@ -2222,7 +2222,7 @@ cfA013rose dequeued printer-name. - + up printer-name @@ -2249,7 +2249,7 @@ cfA013rose dequeued This section describes filters for printing specially formatted files, header pages, printing across networks, and restricting and accounting for printer usage. - + Filters @@ -2301,7 +2301,7 @@ cfA013rose dequeued should do to overcome this problem. I recommend reading this section if you have a PostScript printer. - + PostScript is a popular output format for many programs. Even some people (myself included) write PostScript code directly. But @@ -2333,7 +2333,7 @@ cfA013rose dequeued linkend="printing-advanced-header-pages">Header Pages), you can probably skip that section altogether. - + Section lpf: a Text Filter describes lpf, a fairly @@ -2348,7 +2348,7 @@ cfA013rose dequeued How Filters Work - + As mentioned before, a filter is an executable program started by LPD to handle the device-dependent part of communicating with the printer. @@ -2370,10 +2370,10 @@ cfA013rose dequeued if filter (this is mostly true: see Output Filters for details). - + There are three kinds of filters you can specify in /etc/printcap: - + The text filter, confusingly called the @@ -2514,7 +2514,7 @@ cfA013rose dequeued arguments. - + Filters should also exit with the following exit status: @@ -2546,13 +2546,13 @@ cfA013rose dequeued - + The text filter that comes with the FreeBSD release, /usr/libexec/lpr/lpf, takes advantage of the page width and length arguments to determine when to send a form feed and how to account for printer usage. It uses the login, host, and accounting file arguments to make the accounting entries. - + If you are shopping for filters, see if they are LPD-compatible. If they are, they must support the argument lists described above. If you plan on writing filters for general use, then have them @@ -2561,7 +2561,7 @@ cfA013rose dequeued Accommodating Plain Text Jobs on PostScript Printers - + If you are the only user of your computer and PostScript (or other language-based) printer, and you promise to never send plain text to your printer and to never use features of various programs @@ -2579,7 +2579,7 @@ cfA013rose dequeued will convert the text into PostScript and print the result. How do we do this? - + If you have got a serial printer, a great way to do it is to install lprps. lprps is a PostScript printer filter which performs two-way communication with @@ -2649,7 +2649,7 @@ fi Simulating PostScript on Non-PostScript Printers - + PostScript is the de facto standard for high quality typesetting and printing. PostScript is, however, an expensive standard. Thankfully, Alladin @@ -2737,7 +2737,7 @@ exit 2 Conversion Filters - + After completing the simple setup described in Simple Printer Setup, the first thing you will probably want to do is install conversion filters for @@ -2777,7 +2777,7 @@ exit 2 text, the filter converts the file into a format the printer can understand. - + Which Conversions Filters Should I Install? @@ -2869,7 +2869,7 @@ exit 2 lpr -g mean “print Printerleaf files.” - + Installing Conversion Filters @@ -3129,7 +3129,7 @@ dvilj2p -M1 -q -e- dfhp$$.dvi cleanup exit 0 - + Automated Conversion: An Alternative To Conversion Filters @@ -3161,7 +3161,7 @@ exit 0 Output Filters - + The LPD spooling system supports one other type of filter that we have not yet explored: an output filter. An output filter is intended for printing plain text only, like the text filter, but @@ -3197,7 +3197,7 @@ exit 0 question. - + Do not be seduced by an output filter's simplicity. If you would like each file in a job to start on a different page an output filter will not work. Use a text filter (also @@ -3244,7 +3244,7 @@ exit 0 <command>lpf</command>: a Text Filter - + The program /usr/libexec/lpr/lpf that comes with FreeBSD binary distribution is a text filter (input filter) that can indent output (job submitted with lpr @@ -3298,15 +3298,15 @@ exit 0 Enabling Header Pages - + In the Simple Printer Setup, we turned off header pages by specifying sh (meaning “suppress header”) in the /etc/printcap file. To enable header pages for a printer, just remove the sh capability. - + Sounds too easy, right? - + You are right. You might have to provide an output filter to send initialization strings to the printer. Here is an example output filter for Hewlett Packard PCL-compatible @@ -3357,7 +3357,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ Controlling Header Pages - + By enabling header pages, LPD will produce a long header, a full page of large letters identifying the user, host, and job. Here is an example (kelly printed the job @@ -3424,7 +3424,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995 - + Also by default, LPD prints the header page first, then the job. To reverse that, specify hl (header last) in /etc/printcap. @@ -3432,13 +3432,13 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995 Accounting for Header Pages - + Using LPD's built-in header pages enforces a particular paradigm when it comes to printer accounting: header pages must be free of charge. Why? - + Because the output filter is the only external program that will have control when the header page is printed that could do accounting, and it is not provided with any user or @@ -3458,9 +3458,9 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995 header pages with lpr -h, they will still get them and be charged for them since LPD does not pass any knowledge of the option to any of the filters. - + So, what are your options? - + You can: @@ -3501,7 +3501,7 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995 Header Pages on PostScript Printers - + As described above, LPD can generate a plain text header page suitable for many printers. Of course, PostScript cannot directly print plain text, so the header page feature of LPD is @@ -3684,7 +3684,7 @@ done linkend="printing-advanced-network-rm">Printers Installed on Remote Hosts tells how to do this. - + Accessing a printer attached directly to a network. The printer has a network interface in addition (or in place of) a @@ -3716,7 +3716,7 @@ done Printers Installed on Remote Hosts - + The LPD spooling system has built-in support for sending jobs to other hosts also running LPD (or are compatible with LPD). This feature enables you to install a printer on one host and make it @@ -3745,7 +3745,7 @@ done Then, on the other hosts you want to have access to the printer, make an entry in their /etc/printcap files with the following: - + Name the entry anything you want. For simplicity, though, @@ -3779,7 +3779,7 @@ done That is it. You do not need to list conversion filters, page dimensions, or anything else in the /etc/printcap file. - + Here is an example. The host rose has two printers, bamboo and rattan. We will enable users on the host orchid to print to those printers. @@ -3789,7 +3789,7 @@ done Pages). It already had the entry for the printer teak; we have added entries for the two printers on the host rose: - + # # /etc/printcap for host orchid - added (remote) printers on rose @@ -3840,7 +3840,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ Printers with Networked Data Stream Interfaces - + Often, when you buy a network interface card for a printer, you can get two versions: one which emulates a spooler (the more expensive version), or one which just lets you send data to it as if @@ -3920,7 +3920,7 @@ exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100 Restricting Multiple Copies - + The LPD system makes it easy for users to print multiple copies of a file. Users can print jobs with lpr -#5 (for example) and get five copies of each file in the job. Whether @@ -3933,8 +3933,8 @@ exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100-# option, they will see: lpr: multiple copies are not allowed - - + + Note that if you have set up access to a printer remotely (see section Printers Installed on Remote Hosts), you need the @@ -3971,7 +3971,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ /etc/printcap (and while we are at it, let us disable multiple copies for the printer teak): - + # # /etc/printcap for host orchid - no multiple copies for local @@ -4002,7 +4002,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ Restricting Access To Printers - + You can control who can print to what printers by using the UNIX group mechanism and the rg capability in /etc/printcap. Just place the users you want @@ -4014,7 +4014,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ lpr: Not a member of the restricted group if they try to print to the controlled printer. - + As with the sc (suppress multiple copies) capability, you need to specify rg on remote hosts that also have access to your printers, if you feel it is @@ -4058,7 +4058,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ Controlling Sizes of Jobs Submitted - + If you have many users accessing the printers, you probably need to put an upper limit on the sizes of the files users can submit to print. After all, there is only so much free space on the @@ -4076,7 +4076,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ The limit applies to files in a job, and not the total job size. - + LPD will not refuse a file that is larger than the limit you place on a printer. Instead, it will queue as much of the file up to the limit, which will then get printed. The rest will be @@ -4128,7 +4128,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ Restricting Jobs from Remote Printers - + The LPD spooling system provides several ways to restrict print jobs submitted from remote hosts: @@ -4296,7 +4296,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ Quick and Dirty Printer Accounting - + FreeBSD comes with two programs that can get you set up with simple periodic accounting right away. They are the text filter lpf, described in section af capability in /etc/printcap, and if not specified as an absolute path, is relative to the spooling directory. - + LPD starts lpf with page width and length arguments (from the pw and pl capabilities). lpf uses these arguments to @@ -4353,7 +4353,7 @@ rose:root 26.00 12 $ 0.52 total 337.00 154 $ 6.74 These are the arguments &man.pac.8; expects: - + @@ -4427,7 +4427,7 @@ total 337.00 154 $ 6.74 - + In the default summary that &man.pac.8; produces, you see the number of pages printed by each user from various hosts. If, at your site, host does not matter (because users can use any host), @@ -4458,7 +4458,7 @@ total 337.00 154 $ 6.74 makes each page cost one dollar and fifty cents. You can really rake in the profits by using this option. - + Finally, running pac -s will save the summary information in a summary accounting file, which is named the same as the printer's accounting file, but with _sum @@ -4470,7 +4470,7 @@ total 337.00 154 $ 6.74 How Can You Count Pages Printed? - + In order to perform even remotely accurate accounting, you need to be able to determine how much paper a job uses. This is the essential problem of printer accounting. @@ -4488,20 +4488,20 @@ total 337.00 154 $ 6.74 to examine lpf's source code. How do you handle other file formats, though? - + Well, for DVI-to-LaserJet or DVI-to-PostScript conversion, you can have your filter parse the diagnostic output of dvilj or dvips and look to see how many pages were converted. You might be able to do similar things with other file formats and conversion programs. - + But these methods suffer from the fact that the printer may not actually print all those pages. For example, it could jam, run out of toner, or explode—and the user would still get charged. So, what can you do? - + There is only one sure way to do accurate accounting. Get a printer that can tell you how much paper it uses, and attach it via a serial line or @@ -4528,15 +4528,15 @@ total 337.00 154 $ 6.74 many of its shortcomings, which naturally leads to the question: “What other spooling systems are out there (and work with FreeBSD)?” - + Unfortunately, I have located only two alternatives—and they are almost identical to each other! They are: - + PLP, the Portable Line Printer Spooler System - + PLP was based on software developed by Patrick Powell and then maintained by an Internet-wide group of developers. The main site @@ -4579,7 +4579,7 @@ total 337.00 154 $ 6.74 LPRng - + LPRng, which purportedly means “LPR: the Next Generation” is a complete rewrite of PLP. Patrick Powell @@ -4596,12 +4596,12 @@ total 337.00 154 $ 6.74 I would like to thank the following people who have assisted in the development of this document: - + Daniel Eischen deischen@iworks.interworks.org - + For providing a plethora of HP filter programs for perusal. @@ -4610,7 +4610,7 @@ total 337.00 154 $ 6.74 &a.jehamby; - + For the Ghostscript-to-HP filter. @@ -4618,7 +4618,7 @@ total 337.00 154 $ 6.74 &a.jfieber; - + For debugging why printing from Windows 95 to a FreeBSD system simulating a PostScript printer with Ghostscript didn't @@ -4641,7 +4641,7 @@ total 337.00 154 $ 6.74 My wife, Mary Kelly urquhart@argyre.colorado.edu - + For allowing me to spend more time with FreeBSD than with her. diff --git a/en_US.ISO_8859-1/books/handbook/quotas/chapter.sgml b/en_US.ISO_8859-1/books/handbook/quotas/chapter.sgml index 3c7c097d8c..170c8af567 100644 --- a/en_US.ISO_8859-1/books/handbook/quotas/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/quotas/chapter.sgml @@ -1,7 +1,7 @@ @@ -33,14 +33,14 @@ options QUOTA custom kernel in order to use disk quotas. Please refer to the Configuring the FreeBSD Kernel section for more information on kernel configuration. - + Next you will need to enable disk quotas in /etc/rc.conf. This is done by adding the line: enable_quotas=YES - + For finer control over your quota startup, there is an additional configuration variable available. Normally on bootup, the quota integrity of each file system is checked by the quotacheck @@ -65,7 +65,7 @@ check_quotas=YES enable disk quotas on a per-file system basis. This is where you can either enable user or group quotas or both for all of your file systems. - + To enable per-user quotas on a file system, add the userquota option to the options field in the /etc/fstab entry for the file system you want to to @@ -73,7 +73,7 @@ check_quotas=YES /dev/da1s2g /home ufs rw,userquota 1 2 - + Similarly, to enable group quotas, use the groupquota option instead of the userquota keyword. To enable both user and group @@ -81,7 +81,7 @@ check_quotas=YES /dev/da1s2g /home ufs rw,userquota,groupquota 1 2 - + By default the quota files are stored in the root directory of the file system with the names quota.user and quota.group for user and group quotas respectively. @@ -89,13 +89,13 @@ check_quotas=YES man page says that you can specify an alternate location for the quota files, this is not recommended since all of the various quota utilities do not seem to handle this properly. - + At this point you should reboot your system with your new kernel. /etc/rc will automatically run the appropriate commands to create the initial quota files for all of the quotas you enabled in /etc/fstab, so there is no need to manually create any zero length quota files. - + In the normal course of operations you should not be required to run the quotacheck, quotaon, or quotaoff commands manually. However, you may want to @@ -112,31 +112,31 @@ check_quotas=YES You should see a one line summary of disk usage and current quota limits for each file system that quotas are enabled on. - + You are now ready to start assigning quota limits with the edquota command. - + You have several options on how to enforce limits on the amount of disk space a user or group may allocate, and how many files they may create. You may limit allocations based on disk space (block quotas) or number of files (inode quotas) or a combination of both. Each of these limits are further broken down into two categories: hard and soft limits. - + A hard limit may not be exceeded. Once a user reaches their hard limit they may not make any further allocations on the file system in question. For example, if the user has a hard limit of 500 blocks on a file system and is currently using 490 blocks, the user can only allocate an additional 10 blocks. Attempting to allocate an additional 11 blocks will fail. - + Soft limits on the other hand can be exceeded for a limited amount of time. This period of time is known as the grace period, which is one week by default. If a user stays over his or her soft limit longer than their grace period, the soft limit will turn into a hard limit and no further allocations will be allowed. When the user drops back below the soft limit, the grace period will be reset. - + The following is an example of what you might see when you run then edquota command. When the edquota command is invoked, you are placed into the @@ -164,7 +164,7 @@ Quotas for user test: The new quota limits will be in place when you exit the editor. - + Sometimes it is desirable to set quota limits on a range of uids. This can be done by use of the option on the edquota command. First, assign the desired quota @@ -179,7 +179,7 @@ Quotas for user test: The ability to specify uid ranges was added to the system after 2.1 was released. If you need this feature on a 2.1 system, you will need to obtain a newer copy of edquota. - + See man edquota for more detailed information. @@ -195,12 +195,12 @@ Quotas for user test: are not a member of. The repquota command can be used to get a summary of all quotas and disk usage for file systems with quotas enabled. - + The following is some sample output from the quota -v command for a user that has quota limits on two file systems. - - + + Disk quotas for user test (uid 1002): Filesystem blocks quota limit grace files quota limit grace @@ -212,7 +212,7 @@ Disk quotas for user test (uid 1002): has 5 days of their grace period left. Note the asterisk * which indicates that the user is currently over their quota limit. - + Normally file systems that the user is not using any disk space on will not show up in the output from the quota command, even if they have a quota limit assigned for that file system. diff --git a/en_US.ISO_8859-1/books/handbook/security/chapter.sgml b/en_US.ISO_8859-1/books/handbook/security/chapter.sgml index 8aba1b63ad..579dbfe39c 100644 --- a/en_US.ISO_8859-1/books/handbook/security/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/security/chapter.sgml @@ -1,7 +1,7 @@ @@ -12,7 +12,7 @@ Contributed by &a.wollman; 24 September 1995. - + In order to protect the security of passwords on UN*X systems from being easily exposed, passwords have traditionally been scrambled in some way. Starting with Bell Labs' Seventh Edition Unix, passwords were @@ -27,7 +27,7 @@ available, because national governments in many places like to place restrictions on cross-border transport of DES and other encryption software. - + So, the FreeBSD team was faced with a dilemma: how could we provide compatibility with all those UNIX systems out there while still not running afoul of the law? We decided to take a dual-track approach: we @@ -43,7 +43,7 @@ Because neither of these functions involve encryption, they are believed to be exportable from the US and importable into many other countries. - + Meanwhile, work was also underway on the DES-based password hash function. First, a version of the crypt function which was written outside the US was imported, thus synchronizing the US @@ -128,7 +128,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -> libdescrypt_p.a - + 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 “UNIX password”. The @@ -140,14 +140,14 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -> libdescrypt_p.akeyinit program) which it uses to generate one-time passwords; we will call it a “secret password” or just unqualified “password”. - + The secret password does not necessarily have anything to do with your UNIX password (while they can be the same, this is not recommended). While UNIX passwords are limited to eight characters in length, your S/Key secret password can be as long as you like; I use seven-word phrases. In general, the S/Key system operates completely independently of the UNIX password system. - + There are in addition two other sorts of data involved in the S/Key system; one is called the “seed” or (confusingly) “key”, and consists of two letters and five digits, and the @@ -165,7 +165,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -> libdescrypt_p.a - + There are four programs involved in the S/Key system which we will discuss below. The key program accepts an iteration count, a seed, and a secret password, and generates a one-time password. @@ -180,7 +180,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -> libdescrypt_p.alogin program is also capable of disallowing the use of UNIX passwords on connections coming from specified addresses. - + There are four different sorts of operations we will cover. The first is using the keyinit program over a secure connection to set up S/Key for the first time, or to change your @@ -193,7 +193,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -> libdescrypt_p.a - + Secure connection initialization @@ -294,7 +294,7 @@ s/key 92 hi52030 annotation (s/key required), indicating that only S/Key one-time passwords will be accepted. - + Generating a single one-time password @@ -415,16 +415,16 @@ permit port ttyd0 Services such as remote login, remote copy, secure inter-system file copying and other high-risk tasks are made considerably safer and more controllable. - + The following instructions can be used as a guide on how to set up Kerberos as distributed for FreeBSD. However, you should refer to the relevant manual pages for a complete description. - + In FreeBSD, the Kerberos is not that from the original 4.4BSD-Lite, distribution, but eBones, which had been previously ported to FreeBSD 1.1.5.1, and was sourced from outside the USA/Canada, and is thus available to system owners outside those countries. - + For those needing to get a legal foreign distribution of this software, please do not get it from a USA or Canada site. You will get that site in big trouble! A @@ -594,7 +594,7 @@ Principal's new key version = 1 Edit O.K. Principal name: <---- null entry here will cause an exit - + Creating the server file @@ -668,7 +668,7 @@ Principal's new key version = 1 Edit O.K. Principal name: <---- null entry here will cause an exit - + Testing it all out @@ -729,7 +729,7 @@ Verifying password New Password for jane: Password changed. - + Adding <command>su</command> privileges @@ -798,7 +798,7 @@ Principal: jane.root@GRONDAR.ZA Issued Expires Principal May 2 20:43:12 May 3 04:43:12 krbtgt.GRONDAR.ZA@GRONDAR.ZA - + Using other commands @@ -861,15 +861,15 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 Firewalls - + Contributed by &a.gpalmer; and &a.alex;. - + Firewalls are an area of increasing interest for people who are connected to the Internet, and are even finding applications on private networks to provide enhanced security. This section will hopefully explain what firewalls are, how to use them, and how to use the facilities provided in the FreeBSD kernel to implement them. - + People often think that having a firewall between your companies internal network and the “Big Bad Internet” will solve all @@ -883,7 +883,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 firewall to be impenetrable, you have just made the crackers job that bit easier. - + What is a firewall? @@ -912,7 +912,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 Packet filtering routers - + A router is a machine which forwards packets between two or more networks. A packet filtering router has an extra piece of code in its kernel, which compares each packet to a list of rules before @@ -968,7 +968,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 depends largely on what proxy software you choose. - + What does IPFW allow me to do? @@ -993,7 +993,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 IPFW, and the same commands and techniques should be used in this situation. - + Enabling IPFW on FreeBSD @@ -1027,7 +1027,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 happen. - + options IPFIREWALL_VERBOSE_LIMIT=10 @@ -1055,7 +1055,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 the firewall code automatically includes accounting facilities. - + Configuring IPFW @@ -1075,7 +1075,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 Altering the IPFW rules - + The syntax for this form of the command is: ipfw @@ -1088,10 +1088,10 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 addresses options - + There is one valid flag when using this form of the command: - + -N @@ -1101,7 +1101,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 - + The command given can be shortened to the shortest unique form. The valid commands are: @@ -1124,7 +1124,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 - + Previous versions of IPFW used separate firewall and accounting entries. The present version provides packet accounting with each firewall entry. @@ -1181,7 +1181,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 - + Each action will be recognized by the shortest unambiguous prefix. @@ -1221,9 +1221,9 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 - + The address specification is: - + from address/maskport @@ -1256,7 +1256,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 address:mask-pattern - + A valid hostname may be specified in place of the IP address. is a decimal number representing how many bits in the address mask should be set. @@ -1284,7 +1284,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 with a list, but the range must always be specified first. The options available are: - + frag @@ -1382,7 +1382,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 Listing the IPFW rules - + The syntax for this form of the command is: ipfw @@ -1391,7 +1391,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 -N l - + There are three valid flags when using this form of the command: @@ -1428,13 +1428,13 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 Flushing the IPFW rules - + The syntax for flushing the chain is: ipfw flush - + This causes all entries in the firewall chain to be removed except the fixed default policy enforced by the kernel (index 65535). Use caution when flushing rules, the default deny policy @@ -1444,21 +1444,21 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 Clearing the IPFW packet counters - + The syntax for clearing one or more packet counters is: ipfw zero index - + When used without an index argument, all packet counters are cleared. If an index is supplied, the clearing operation only affects a specific chain entry. - + Example commands for ipfw @@ -1554,7 +1554,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 where most of the security sensitive services are, like finger, SMTP (mail) and telnet. - + Block all incoming UDP traffic. There are very few useful services that travel over UDP, and what useful diff --git a/en_US.ISO_8859-1/books/handbook/serialcomms/chapter.sgml b/en_US.ISO_8859-1/books/handbook/serialcomms/chapter.sgml index 63d630b4d7..7e45aa5283 100644 --- a/en_US.ISO_8859-1/books/handbook/serialcomms/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/serialcomms/chapter.sgml @@ -1,7 +1,7 @@ @@ -15,7 +15,7 @@ This section should give you some general information about serial ports. If you do not find what you want here, check into the Terminal and Dialup sections of the handbook. - + The ttydX (or cuaaX) device is the regular device you will want to open for your applications. When a @@ -38,17 +38,17 @@ Now, an application will have these settings by default when it opens ttyd5. It can still change these settings to its liking, though. - + You can also prevent certain settings from being changed by an application by making adjustments to the “lock state” device. For example, to lock the speed of ttyd5 to 57600 bps, do &prompt.root; stty -f /dev/ttyld5 57600 - + Now, an application that opens ttyd5 and tries to change the speed of the port will be stuck with 57600 bps. - + Naturally, you should make the initial state and lock state devices writable only by root. The MAKEDEV script does not do @@ -59,12 +59,12 @@ Terminals Contributed by &a.kelly; 28 July 1996 - + Terminals provide a convenient and low-cost way to access the power of your FreeBSD system when you are not at the computer's console or on a connected network. This section describes how to use terminals with FreeBSD. - + Uses and Types of Terminals @@ -95,11 +95,11 @@ Dumb terminals - + PCs acting as terminals - + X terminals @@ -109,7 +109,7 @@ Dumb Terminals - + Dumb terminals are specialized pieces of hardware that let you connect to computers over serial lines. They are called “dumb” because they have only enough computational power @@ -132,7 +132,7 @@ PCs Acting As Terminals - + If a dumb terminal has just enough ability to display, send, and receive text, then certainly any spare personal computer can be a dumb terminal. All you need is @@ -147,7 +147,7 @@ X Terminals - + X terminals are the most sophisticated kind of terminal available. Instead of connecting to a serial port, they usually connect to a network like Ethernet. Instead of being relegated to @@ -170,7 +170,7 @@ Cables - + Because terminals use serial ports, you need to use serial—also known as RS-232C—cables to connect the terminal to the FreeBSD system. @@ -195,7 +195,7 @@ linkend="term-std">standard cable. - + Also, the serial port on both the terminal and your FreeBSD system must have connectors that will fit the cable you are using. @@ -299,7 +299,7 @@ hood. - + Standard RS-232C Cables @@ -314,12 +314,12 @@ Ports - + Serial ports are the devices through which data is transferred between the FreeBSD host computer and the terminal. This section describes the kinds of ports that exist and how they are addressed in FreeBSD. - + Kinds of Ports @@ -336,7 +336,7 @@ specifications on the kind of port in use. A visual inspection of the port often works, too. - + Port Names @@ -406,18 +406,18 @@ the /dev directory for the serial port if it is not already there. - + Specify that /usr/libexec/getty be run on the port, and specify the appropriate getty type from the /etc/gettytab file. - + Specify the default terminal type. - + Set the port to “on.” @@ -426,7 +426,7 @@ Specify whether the port should be “secure.” - + Force init to reread the /etc/ttys file. @@ -453,11 +453,11 @@ Adding an Entry to <filename>/etc/ttys</filename> - + First, you need to add an entry to the /etc/ttys file, unless one is already there. - + The /etc/ttys file lists all of the ports on your FreeBSD system where you want to allow logins. For example, the first virtual console ttyv0 has an entry in @@ -486,7 +486,7 @@ ttyd5 Specifying the <replaceable>getty</replaceable> Type - + Next, we need to specify what program will be run to handle the logins on a terminal. For FreeBSD, the standard program to do that is /usr/libexec/getty. It is what provides the @@ -529,7 +529,7 @@ ttyd5 "/usr/libexec/getty std.19200" Specifying the Default Terminal Type - + The third field in the /etc/ttys file lists the default terminal type for the port. For dialup ports, you typically put unknown or @@ -537,18 +537,18 @@ ttyd5 "/usr/libexec/getty std.19200" with practically any kind of terminal or software. For hardwired terminals, the terminal type does not change, so you can put a real terminal type in this field. - + Users will usually use the tset program in their .login or .profile files to check the terminal type and prompt for one if necessary. By setting a terminal type in the /etc/ttys file, users can forego such prompting. - + To find out what terminal types FreeBSD supports, see the file /usr/share/misc/termcap. It lists about 600 terminal types. You can add more if you wish. See the &man.termcap.5; manual page for information. - + In our example, the Wyse-50 is a Wyse-50 type of terminal (although it can emulate others, we will leave it in Wyse-50 mode). The 286 PC is running Procomm which will be set to emulate a VT-100. @@ -562,7 +562,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 Enabling the Port - + The next field in /etc/ttys, the fourth field, tells whether to enable the port. Putting on here will have the init @@ -582,7 +582,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on Specifying Secure Ports - + We have arrived at the last field (well, almost: there is an optional window specifier, but we will ignore that). The last field tells whether the port is secure. @@ -592,9 +592,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on 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 root to login. - + How do you use secure and insecure ports? - + By marking a port as insecure, the terminal to which it is connected will not allow root to login. People who know the root password to your FreeBSD system will first have to login using a @@ -613,7 +613,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on command records. Which should you use? - + Just use “insecure.” Use “insecure” even for terminals not in public user areas or behind locked doors. It is quite easy to login @@ -632,7 +632,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom Force <command>init</command> to Reread <filename>/etc/ttys</filename> - + When you boot FreeBSD, the first process, init, will read the /etc/ttys file and start the programs listed @@ -704,7 +704,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroomkill -HUP 1. - + Garbage appears instead of a login prompt @@ -716,7 +716,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom. - + Characters appear doubled; the password appears when typed @@ -744,7 +744,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom - + Prerequisites @@ -757,7 +757,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom FreeBSD Version - + First, it is assumed that you are using FreeBSD version 1.1 or higher (including versions 2.x). FreeBSD version 1.0 included two different serial drivers, which complicates the situation. Also, @@ -769,9 +769,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom Terminology - + A quick rundown of terminology: - + bps @@ -807,12 +807,12 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom - + If you need more information about these terms and data communications in general, the author remembers reading that The RS-232 Bible (anybody have an ISBN?) is a good reference. - + When talking about communications data rates, the author does not use the term “baud”. Baud refers to the number of electrical state transitions that may be made in a period of time, @@ -823,7 +823,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom External vs. Internal Modems - + External modems seem to be more convenient for dialup, because external modems often can be semi-permanently configured via parameters stored in non-volatile RAM and they usually provide @@ -842,7 +842,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroomModems and Cables A background knowledge of these items is assumed - + You know how to connect your modem to your computer so that @@ -861,7 +861,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom - + The first, connecting your modem, is usually simple — most straight-through serial cables work without any problems. You need to have a cable with appropriate connectors (DB-25 or DB-9, male or @@ -901,7 +901,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroomSignal Ground (SG) - + FreeBSD needs the RTS and CTS signals for flow-control at speeds above 2400bps, the CD signal to detect when a call has @@ -930,7 +930,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom Serial Interface Considerations - + FreeBSD supports NS8250-, NS16450-, NS16550-, and NS16550A-based EIA RS-232C (CCITT V.24) communications interfaces. The 8250 and 16450 devices have single-character buffers. The 16550 device @@ -1074,7 +1074,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr &man.config.8; manual page to prepare a kernel building directory, then build, install, and test the new kernel. - + Device Special Files @@ -1103,7 +1103,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr Making Device Special Files - + A shell script called MAKEDEV in the /dev directory manages the device special files. (The manual page for &man.MAKEDEV.8; on FreeBSD 1.1.5 is @@ -1195,12 +1195,12 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01 <filename>/etc/gettytab</filename> - + /etc/gettytab is a &man.termcap.5;-style file of configuration information for &man.getty.8;. Please see the &man.gettytab.5; manual page for complete information on the format of the file and the list of capabilities. - + Locked-Speed Config @@ -1208,7 +1208,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01 particular speed, you probably will not need to make any changes to /etc/gettytab. - + Matching-Speed Config @@ -1297,7 +1297,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ <filename>/etc/ttys</filename> - + /etc/ttys is the list of ttys for init to monitor. /etc/ttys also provides security information to @@ -1350,7 +1350,7 @@ ttyd0 "/usr/libexec/getty xxx" dialup on first time setting up the system, though, you may want to wait until your modem(s) are properly configured and connected before signaling init. - + Locked-Speed Config @@ -1370,7 +1370,7 @@ ttyd0 "/usr/libexec/getty std.19200" dialup on /etc/gettytab for your modem's data rate. - + Matching-Speed Config @@ -1391,7 +1391,7 @@ ttyd0 "/usr/libexec/getty V19200" dialup on <filename>/etc/rc.serial</filename> or <filename>/etc/rc.local</filename> - + High-speed modems, like V.32, V.32bis, and V.34 modems, need to use hardware (RTS/CTS) flow control. You can add stty commands to @@ -1447,28 +1447,28 @@ stty -f /dev/ttyd3 crtscts CD asserted when connected - + DTR asserted for operation; dropping DTR hangs up line & resets modem - + CTS transmitted data flow control - + Disable XON/XOFF flow control - + RTS received data flow control - + Quiet mode (no result codes) - + No command echo @@ -1497,32 +1497,32 @@ AT&C1&D2&H1&I0&R2&W Switch 1: UP — DTR Normal - + Switch 2: Do not care (Verbal Result Codes/Numeric Result Codes) - + Switch 3: UP — Suppress Result Codes - + Switch 4: DOWN — No echo, offline commands - + Switch 5: UP — Auto Answer - + Switch 6: UP — Carrier Detect Normal - + Switch 7: UP — Load NVRAM Defaults - + Switch 8: Do not care (Smart Mode/Dumb Mode) @@ -1537,7 +1537,7 @@ AT&C1&D2&H1&I0&R2&W Locked-speed Config - + For a locked-speed configuration, you will need to configure the modem to maintain a constant modem-to-computer data rate independent of the communications rate. On a USR Sportster 14,400 external @@ -1551,7 +1551,7 @@ AT&B1&W Matching-speed Config - + For a variable-speed configuration, you will need to configure your modem to adjust its serial port data rate to match the incoming call rate. On a USR Sportster 14,400 external modem, these commands @@ -1566,7 +1566,7 @@ AT&B2&W Checking the Modem's Configuration - + Most high-speed modems provide commands to view the modem's current operating parameters in a somewhat human-readable fashion. On the USR Sportster 14,400 external modems, the command @@ -1589,7 +1589,7 @@ AT&B2&W Checking out the FreeBSD system - + Hook up your modem to your FreeBSD system, boot the system, and, if your modem has status indication lights, watch to see whether the modem's DTR indicator lights when the @@ -1603,7 +1603,7 @@ AT&B2&W ax to see if FreeBSD is trying to run a getty process on the correct port. You should see a lines like this among the processes displayed: - + 114 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd0 115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd1 @@ -1635,7 +1635,7 @@ AT&B2&W Try Dialing In - + Try dialing into the system; be sure to use 8 bits, no parity, 1 stop bit on the remote system. If you do not get a prompt right away, or get garbage, try pressing <Enter> @@ -1649,7 +1649,7 @@ AT&B2&W If you still cannot get a login: prompt, check /etc/gettytab again and double-check that - + The initial capability name specified in @@ -1667,7 +1667,7 @@ AT&B2&W gettytab capability name - + If you dial but the modem on the FreeBSD system will not answer, make sure that the modem is configured to answer the phone when DTR is asserted. If the modem seems to be @@ -1715,7 +1715,7 @@ AT&B2&W the Internet if you have problems with PPP. If you need to ftp something and PPP is broken, use the terminal session to ftp it. Then use zmodem to transfer it to your machine. - + Why cannot I run <command>tip</command> or <command>cu</command>? @@ -2044,7 +2044,7 @@ raisechar=^^ cable and a null-modem adapter. See for a discussion on serial cables. - + Unplug your keyboard. @@ -2085,7 +2085,7 @@ raisechar=^^ not much good without the keyboard anyway. - + Plug a dumb terminal into COM1: (sio0). @@ -2175,7 +2175,7 @@ device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 If the flags were not set, you need to run UserConfig (on a different console) or recompile the kernel. - + Create boot.config in the root directory of the a partition on the boot drive. @@ -2259,7 +2259,7 @@ device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 serial port as the console only during the boot block; the boot loader will use the internal video display as the console. - + Boot the machine. @@ -2363,9 +2363,9 @@ boot: Case 1: You set the flags to 0x10 for sio0 - + device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 - + @@ -2426,7 +2426,7 @@ boot: Case 2: You set the flags to 0x30 for sio0 - + device sio0 at isa? port "IO_COM1" tty flags 0x30 irq 4 @@ -2493,13 +2493,13 @@ boot: Setting A Faster Serial Port Speed - + By default the serial port settings are set to 9600 baud, 8 bits, no parity, 1 stop bit. If you wish to change the speed, you need to recompile at least the boot blocks. Add the following line to /etc/make.conf and compile new boot blocks: - + BOOT_COMCONSOLE_SPEED=19200 If the serial console is configured in some other way than by @@ -2514,7 +2514,7 @@ boot: Using Serial Port Other Than <devicename>sio0</devicename> For The Console - + Using a port other than sio0 as the console requires some recompiling. If you want to use another serial port for whatever reasons, recompile the boot blocks, the @@ -2581,7 +2581,7 @@ boot: Entering the DDB Debugger from the Serial Line - + If you wish to drop into the kernel debugger from the serial console (useful for remote diagnostics, but also dangerous if you generate a spurious BREAK on the serial port!) then you should @@ -2593,7 +2593,7 @@ options DDB Getting a Login Prompt on the Serial Console - + While this is not required, you may wish to get a login prompt over the serial line, now that you can see boot messages and can enter the kernel debugging session @@ -2636,7 +2636,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure Setting Up the Serial Console - + You can easily specify the boot loader and the kernel to use the serial console by writing just one line in /boot/loader.rc: @@ -2651,7 +2651,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure the serial console as early as possible. Likewise, you can specify the internal console as: - + set console=vidconsole If you do not set the boot loader environment variable @@ -2674,11 +2674,11 @@ start console=comconsole or - + console=vidconsole See &man.loader.conf.5; for more information. - + At the moment, the boot loader has no option equivalent to the option in the boot block, and there is no @@ -2690,7 +2690,7 @@ start Using Serial Port Other than <devicename>sio0</devicename> for the Console - + You need to recompile the boot loader to use a serial port other than sio0 for the serial console. Follow the procedure described in . diff --git a/en_US.ISO_8859-1/books/handbook/staff/chapter.sgml b/en_US.ISO_8859-1/books/handbook/staff/chapter.sgml index 959beb8ba0..8894b17db9 100644 --- a/en_US.ISO_8859-1/books/handbook/staff/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/staff/chapter.sgml @@ -1,7 +1,7 @@