From baf849c9b0672bbc65b05ef033e94363820ff172 Mon Sep 17 00:00:00 2001 From: John Fieber Date: Sat, 7 Oct 1995 04:32:03 +0000 Subject: [PATCH] Two new sections: * Kernel configuration, from Jake Hamby I'd like as many people as possible to give this one a good check before 2.1 goes out the door. * Routing, from Coranth Gryphon A bazillion formatting tweaks (only 13 bazillion more to go!) --- share/doc/handbook/Makefile | 7 +- share/doc/handbook/authors.sgml | 10 +- share/doc/handbook/booting.sgml | 4 +- share/doc/handbook/eresources.sgml | 7 +- share/doc/handbook/esdi.sgml | 4 +- share/doc/handbook/handbook.sgml | 28 +- share/doc/handbook/hw.sgml | 10 +- share/doc/handbook/install.sgml | 7 +- share/doc/handbook/kernelconfig.sgml | 1206 ++++++++++++++++++++++++++ share/doc/handbook/porting.sgml | 184 ++-- share/doc/handbook/relnotes.sgml | 24 +- share/doc/handbook/routing.sgml | 279 ++++++ share/doc/handbook/scsi.sgml | 6 +- share/doc/handbook/sections.sgml | 3 +- share/doc/handbook/skey.sgml | 4 +- share/doc/handbook/slipc.sgml | 8 +- share/doc/handbook/submitters.sgml | 8 +- 17 files changed, 1640 insertions(+), 159 deletions(-) create mode 100644 share/doc/handbook/kernelconfig.sgml create mode 100644 share/doc/handbook/routing.sgml diff --git a/share/doc/handbook/Makefile b/share/doc/handbook/Makefile index ec54798a5a4..86bf2102430 100644 --- a/share/doc/handbook/Makefile +++ b/share/doc/handbook/Makefile @@ -1,12 +1,13 @@ -# $Id: Makefile,v 1.3 1995/09/25 18:23:02 wollman Exp $ +# $Id: Makefile,v 1.4 1995/10/01 04:43:11 jfieber Exp $ SRCS= authors.sgml basics.sgml bibliography.sgml boothelp.sgml SRCS+= booting.sgml contrib.sgml crypt.sgml ctm.sgml current.sgml dialup.sgml SRCS+= diskless.sgml dma.sgml eresources.sgml esdi.sgml glossary.sgml SRCS+= handbook.sgml history.sgml hw.sgml install.sgml kerberos.sgml -SRCS+= kerneldebug.sgml memoryuse.sgml mirrors.sgml nfs.sgml nutshell.sgml +SRCS+= kernelconfig.sgml kerneldebug.sgml memoryuse.sgml +SRCS+= mirrors.sgml nfs.sgml nutshell.sgml SRCS+= porting.sgml ports.sgml ppp.sgml printing.sgml relnotes.sgml -SRCS+= scsi.sgml sections.sgml +SRCS+= routing.sgml scsi.sgml sections.sgml SRCS+= skey.sgml slipc.sgml slips.sgml submitters.sgml sup.sgml SRCS+= troubleshooting.sgml userppp.sgml diff --git a/share/doc/handbook/authors.sgml b/share/doc/handbook/authors.sgml index 72b0258387f..0677ad44757 100644 --- a/share/doc/handbook/authors.sgml +++ b/share/doc/handbook/authors.sgml @@ -1,4 +1,4 @@ - + + @@ -21,10 +21,7 @@ Mailing lists -

Contributed by &a.dufalt;. - 20 Jun 1995. - -Though many of the FreeBSD development members read USENET, we cannot +

Though many of the FreeBSD development members read USENET, we cannot always guarantee that we'll get to your questions in a timely fashion (or at all) if you post them only to one of the comp.unix.bsd.* groups. By addressing your questions to the appropriate mailing list diff --git a/share/doc/handbook/esdi.sgml b/share/doc/handbook/esdi.sgml index a30dc05facd..6d2c3dee5df 100644 --- a/share/doc/handbook/esdi.sgml +++ b/share/doc/handbook/esdi.sgml @@ -1,4 +1,4 @@ - + + The FreeBSD Documentation Project - September 30, 1995 + October 6, 1995 Welcome to FreeBSD! This handbook covers the installation and day to day use of FreeBSD Release @@ -34,7 +34,7 @@ This manual is a work in progress and is the work of many individuals. Many sections do not yet exist and some of those that do exist need to be updated. If you are interested in helping with this project, send -email to &a.jfieber; or to the FreeBSD Documentation +email to the FreeBSD Documentation Project mailing list . The latest version of this document is always available from @@ -65,15 +65,7 @@ Web server">. System Administration - Reconfiguring the Kernel -

This section is in progress. Please contact - Deborah Bennett for more information. - In the meantime, please refer to - Kernel Configuration section of the . - - + &kernelconfig; Users, groups and security &crypt; &skey; @@ -81,12 +73,6 @@ Web server">. * Firewalls &printing; - The X-Window System

Pending the completion of this section, please refer to documentation supplied by the . &slips; Advanced networking + + &routing; &nfs; &diskless; * Yellow Pages/NIS @@ -164,7 +152,7 @@ Web server">. &memoryuse; &dma; &contrib; - &glossary; + diff --git a/share/doc/handbook/hw.sgml b/share/doc/handbook/hw.sgml index 35b5f63fbeb..a85bfa81f67 100644 --- a/share/doc/handbook/hw.sgml +++ b/share/doc/handbook/hw.sgml @@ -1,4 +1,4 @@ - + + + + + Configuring the FreeBSD Kernel + +

Contributed by &a.jehamby;.6 October 1995. + + This large section of the handbook discusses the basics of + building your own custom kernel for FreeBSD. This section + is appropriate for both novice system administrators and + those with advanced Unix experience. + + Why build a custom kernel? + +

Building a custom kernel is one of the most important + rites of passage every Unix system administrator must + learn. This process, while time-consuming, will provide + many benefits to your FreeBSD system. Unlike the GENERIC + kernel, which must support every possible SCSI and + network card, along with tons of other rarely used + hardware support, a custom kernel only contains support + for your PC's hardware. This has a number of + benefits: + + + + It will take less time to boot because it does not + have to spend time probing for hardware which you + do not have. + + A custom kernel often uses less memory, which is + important because the kernel is the one process which + must always be present in memory, and so all of that + unused code ties up pages of RAM that your programs + would otherwise be able to use. Therefore, on a + system with limited RAM, building a custom kernel is + of critical importance. + + Finally, there are several kernel options which + you can tune to fit your needs, and device driver + support for things like sound cards which you can + include in your kernel but are not present + in the GENERIC kernel. + +

+ + Building and Installing a Custom Kernel + +

First, let us take a quick tour of the kernel build + directory. All directories mentioned will be relative to + the main /usr/src/sys directory, which is also + accessible through /sys. There are a number of + subdirectories here representing different parts of the + kernel, but the most important, for our purposes, are + i386/conf, where you will edit your custom + kernel configuration, and compile, which is the + staging area where your kernel will be built. Notice the + logical organization of the directory tree, with each + supported device, filesystem, and option in its own + subdirectory. Also, anything inside the i386 + directory deals with PC hardware only, while everything + outside the i386 directory is common to all + platforms which FreeBSD could potentially be ported to. + + not a + /usr/src/sys directory on your system, then the + kernel source has not been been installed. Follow the + instructions for installing packages to add this package + to your system. + + Next, move to the i386/conf directory and copy + the GENERIC configuration file to the name you want to + give your kernel. For example: + +# cd /usr/src/sys/i386/conf +# cp GENERIC MYKERNEL + + Traditionally, this name is in all capital letters and, + if you are maintaining multiple FreeBSD machines with + different hardware, it's a good idea to name it after + your machine's hostname. We will call it MYKERNEL for + the purpose of this example. + + + + Now, edit MYKERNEL with your favorite text editor. If + you're just starting out, the only editor available will + probably be vi, which is too complex to explain + here, but is covered well in many books in the . Feel free to change the comment + lines at the top to reflect your configuration or the + changes you've made to differentiate it from GENERIC. + + If you've build a kernel under SunOS or some other BSD + operating system, much of this file will be very familiar + to you. If you're coming from some other operating + system such as DOS, on the other hand, the GENERIC + configuration file might seem overwhelming to you, so + follow the descriptions in the + section slowly and carefully. + + When you're finished, type the following to compile and + install your kernel: + +# /usr/sbin/config MYKERNEL +# cd ../../compile/MYKERNEL +# make +# make install + + The new kernel will be copied to the root directory as + /kernel and the old kernel will be moved to + /kernel.old. Now, shutdown the system and + reboot to use your kernel. In case something goes wrong, + there are some instructions at the end of this + document. Be sure to read the section which explains how + to recover in case your new kernel . + + to your + /dev directory before you can use them. + + The Configuration File + +

The general format of a configuration file is quite + simple. Each line contains a keyword and one or more + arguments. For simplicity, most lines only contain one + argument. Anything following a # is considered + a comment and ignored. The following sections describe + each keyword, generally in the order they are listed in + GENERIC, although some related keywords have been grouped + together in a single section (such as Networking) even + though they are actually scattered throughout the GENERIC + file. An exhaustive list of options is present in the + LINT configuration file, located in the same directory as + GENERIC. + + Mandatory Keywords + +

These keywords are required in every kernel you build. + + + + machine ``i386'' + +

The first keyword is machine, which, + since FreeBSD only runs on Intel 386 and compatible + chips, is i386. + + Note: that any keyword which + contains numbers used as text must be enclosed in + quotation marks, otherwise config gets + confused and thinks you mean the actual number + 386. + + cpu ``cpu_type'' + +

The next keyword is cpu, which includes + support for each CPU supported by FreeBSD. The + possible values of cpu_type + include: + + I386_CPU + I486_CPU + I586_CPU + + and multiple instances of the cpu line may + be present with different values of + cpu_type as are present in the + GENERIC kernel. For a custom kernel, it is best to + specify only the cpu you have. If, for example, + you have an Intel Pentium, use I586_CPU + for cpu_type. + + ident machine_name + +

Next, we have ident, which is the + identification of the kernel. You should change + this from GENERIC to whatever you named your + kernel, in this example, MYKERNEL. The value you + put in ident will print when you boot up + the kernel, so it's useful to give a kernel a + different name if you want to keep it separate from + your usual kernel (if you want to build an + experimental kernel, for example). Note that, as + with machine and cpu, enclose + your kernel's name in quotation marks if it + contains any numbers. + + maxusers number + +

This file sets the size of a number of important + system tables. This number is supposed to be + roughly equal to the number of simultaneous users + you expect to have on your machine. However, under + normal circumstances, you will want to set + maxusers to at least four, especially if + you're using X Windows or compiling software. The + reason is that the most important table set by + maxusers is the maximum number of + processes, which is set to 20 + 16 * + maxusers, so if you set maxusers + to one, then you can only have 36 simultaneous + processes, including the 18 or so that the system + starts up at boot time, and the 15 or so you will + probably create when you start X Windows. Even a + simple task like reading a man page will + start up nine processes to filter, decompress, and + view it. Setting maxusers to 4 will allow + you to have up to 84 simultaneous processes, which + should be enough for anyone. If, however, you see + the dreaded ``proc table full'' error when trying + to start another program, or are running a server + with a large number of simultaneous users (like + Walnut Creek CDROM's FTP site!), you can always + increase this number and rebuild. + + maxuser does + not limit the number of users which can + log into your machine. It simply sets various + table sizes to reasonable values considering the + maximum number of users you will likely have on + your system and how many processes each of them + will be running. One keyword which + does limit the number of simultaneous + remote logins is . + + config kernel_name root on root_device + +

This line specifies the location and name of the + kernel. Traditionally the kernel is called + vmunix but in FreeBSD, it is aptly named + kernel. You should always use + kernel for kernel_name because + changing it will render numerous system utilities + inoperative. The second part of the line specifies + the disk and partition where the root filesystem + and kernel can be found. Typically this will be + wd0 for systems with non-SCSI drives, or + sd0 for systems with SCSI drives. + + + + General Options + +

These lines provide kernel support for various + filesystems and other options. + + + +

This line allows the kernel to simulate a math + coprocessor if your computer does not have one (386 + or 486SX). If you have a Pentium, a 486DX, or a + 386 or 486SX with a separate 387 or 487 chip, you + can comment this line out. + + Note: The normal math coprocessor + emulation routines that come with FreeBSD are + not very accurate. If you do not have a + math coprocessor, and you need the best accuracy, + I recommend that you change this option to + GPL_MATH_EMULATE to use the superior GNU + math support, which is not included by default + for licensing reasons. + + options ``COMPAT_43'' + +

Compatibility with BSD 4.3. Leave this in; some + programs will act strangely if you comment this + out. + + options BOUNCE_BUFFERS + +

ISA devices and EISA devices operating in an ISA + compatibilty mode can only perform DMA (Direct + Memory Access) to memory below 16 megabytes. This + option enables such devices to work in systems with + more than 16 megabytes of memory. + + options UCONSOLE + +

Allow users to grab the console, useful for X + Windows. For example, you can create a console + xterm by typing xterm -C, which will + display any `write', `talk', and other messages you + receive. + + options SYSVSHM + +

This option + provides for System V shared memory. The most + common use of this is the XSHM extension in X + Windows, which many graphics-intensive programs + (such as the movie player XAnim, and Linux DOOM) + will automatically take advantage of for extra + speed. If you use X Windows, you'll definitely + want to include this. + + options SYSVSEM + +

Support for System V + semaphores. Less commonly used but only adds a few + hundred bytes to the kernel. + + options SYSVMSG + +

Support for System V + messages. Again, only adds a few hundred bytes to + the kernel. + + ipcs(1) command will + tell will list any processes using using each of + these System V facilities. + + + + Filesystem Options + +

These options add support for various filesystems. + You must include at least one of these to support the + device you boot from; typically this will be + FFS if you boot from a hard drive, or + NFS if you are booting a diskless workstation + from Ethernet. You can include other commonly-used + filesystems in the kernel, but feel free to comment out + support for filesystems you use less often (perhaps the + MS-DOS filesystem?), since they will be dynamically + loaded from the Loadable Kernel Module directory + /lkm the first time you mount a partition of + that type. + + + + options FFS + +

The basic hard drive + filesystem; leave it in if you boot from the hard + disk. + + options NFS + +

Network Filesystem. Unless + you plan to mount partitions from a Unix file + server over Ethernet, you can comment this out. + + options MSDOSFS + +

MS-DOS Filesystem. Unless + you plan to mount a DOS formatted hard drive + partition at boot time, you can safely comment this + out. It will be automatically loaded the first + time you mount a DOS partition, as described above. + Also, the excellent mtools software (in + the ports collection) allows you to access DOS + floppies without having to mount and unmount them + (and does not require MSDOSFS at all). + + options ``CD9660'' + +

ISO 9660 filesystem for + CD-ROMs. Comment it out if you do not have a + CD-ROM drive or only mount data CD's occasionally + (since it will be dynamically loaded the first time + you mount a data CD). Audio CD's do not need this + filesystem. + + options PROCFS + +

Process filesystem. This + is a pretend filesystem mounted on /proc which + allows programs like ps(1) to give you + more information on what processes are running. + Leave it in. + + options MFS + +

Memory-mapped file system. + This is basically a RAM disk for fast storage of + temporary files, useful if you have a lot of swap + space that you want to take advantage of. A + perfect place to mount an MFS partition is on the + /tmp directory, since many programs store + temporary data here. To mount an MFS RAM disk on + /tmp, add the following line to + /etc/fstab and then reboot or type + mount /tmp: + +/dev/wd1s2b /tmp mfs rw 0 0 + + + /dev/wd1s2b + with the name of your swap partition, which will + be listed in your /etc/fstab as follows: + +/dev/wd1s2b none swap sw 0 0 + + + + /tmp device + simultaneously). As such, you may want to avoid + it for now. --> Also, the MFS filesystem + can not be dynamically loaded, so you + must compile it into your kernel if you + want to experiment with it. + + options QUOTA + +

Enable disk quotas. If you + have a public access system, and do not want users + to be able to overflow the /home + partition, you can establish disk quotas for each + user. This code is a little buggy, so do not + enable it unless you have to. View the manual page + for quota(1) to learn more about disk + quotas. + + + + Basic Controllers and Devices + +

These sections describe the basic disk, tape, and + CD-ROM controllers supported by FreeBSD. There are + separate sections for controllers and cards. + + + + controller isa0 + +

All PC's supported by + FreeBSD have one of these. If you have an IBM PS/2 + (Micro Channel Architecture), then you cannot run + FreeBSD at this time. + + controller pci0 + +

Include this if you have a + PCI motherboard. This enables auto-detection of + PCI cards and gatewaying from the PCI to the ISA + bus. + + controller fdc0 + +

Floppy drive controller: + fd0 is the ``A:'' floppy drive, and + fd1 is the ``B:'' drive. ft0 is + a QIC-80 tape drive attached to the floppy + controller. Comment out any lines corresponding to + devices you do not have. + + ft(8), see + the manual page for details. + + controller wdc0 + +

This is the primary IDE + controller. wd0 and wd1 are the + master and slave hard drive, respectively. + wdc1 is a secondary IDE controller where + you might have a third or fourth hard drive, or an + IDE CD-ROM. Comment out the lines which do not + apply (if you have a SCSI hard drive, you'll + probably want to comment out all six lines, for + example). + + controller wcd0 + +

This device + provides IDE CD-ROM support. Be sure to leave + wdc1 uncommented if your CD-ROM is on + its own controller card. To use this, you must + also include the line options ATAPI. + + device npx0 at isa? port ``IO_NPX'' irq 13 vector npxintr + +

npx0 is the interface to the + math coprocessor. If you have one then make sure + you've commented out above. If you do not have a + math coprocessor, you can comment this out. + + device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr + +

Wangtek and Archive + QIC-02/QIC-36 tape drive support + + Proprietary CD-ROM support + +

The following + drivers are for the so-called proprietary + CD-ROM drives. These drives have their own + controller card or might plug into a sound card + such as the Soundblaster 16. They are not + IDE or SCSI. Most older single-speed and + double-speed CD-ROMs use these interfaces, while + newer quad-speeds are likely to be or . + + + + device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr + +

Mitsumi CD-ROM (LU002, + LU005, FX001D). + + device scd0 at isa? port 0x230 bio + +

Sony CD-ROM (CDU31, CDU33A). + + controller matcd0 at isa? port ? bio + +

Matsushita/Panasonic CD-ROM (sold by Creative + Labs for Soundblaster). + + + + + + SCSI Device Support + +

This section describes the various SCSI controllers + and devices supported by FreeBSD. + + + + SCSI Controllers + +

The next ten or so lines include support for + different kinds of SCSI controllers. Comment out + all except for the one(s) you have: + + + + controller bt0 at isa? port ``IO_BT0'' bio irq ? vector btintr + +

Most Buslogic controllers + + controller uha0 at isa? port ``IO_UHA0'' bio irq ? drq 5 vector uhaintr + +

UltraStor 14F and 34F + + controller ahc0 + +

Adaptec 274x/284x/294x + + controller ahb0 at isa? bio irq ? vector ahbintr + +

Adaptec 174x + + controller aha0 at isa? port ``IO_AHA0'' bio irq ? drq 5 vector ahaintr + +

Adaptec 154x + + controller aic0 at isa? port 0x340 bio irq 11 vector aicintr + + +

Adaptec 152x and sound cards using Adaptec AIC-6360 (slow!) + + controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr + + +

ProAudioSpectrum cards using NCR 5380 or Trantor T130 + + controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr + +

Seagate ST01/02 8 bit controller (slow!) + + controller wds0 at isa? port 0x350 bio irq 15 drq 6 vector wdsintr + +

Western Digital WD7000 controller + + controller ncr0 + +

NCR 53C810 and 53C825 PCI SCSI controller + + + + options ``SCSI_DELAY=15'' + +

This causes the + kernel to pause 15 seconds before probing each SCSI + device in your system. If you only have IDE hard + drives, you can ignore this, otherwise you'll + probably want to lower this number, perhaps to 5 + seconds, to speed up booting. Of course if you do + this, and FreeBSD has trouble recognizing your SCSI + devices, you'll have to raise it back up. + + controller scbus0 + +

If you have any SCSI + controllers, this line provides generic SCSI + support. If you do not have SCSI, you can comment + this, and the following three lines, out. + + device sd0 + +

Support for SCSI hard + drives. + + device st0 + +

Support for SCSI tape + drives. + + device cd0 + +

Support for SCSI CD-ROM + drives. + + + + Console, Bus Mouse, and X Server Support + +

You must choose one of these two console types, and, if you plan + to use X Windows, enable the XSERVER option and optionally, a bus + mouse or PS/2 mouse device. + + + + device sc0 at isa? port ``IO_KBD' tty irq 1 vector scintr + +

sc0 is the default + console driver, which resembles an SCO console. + Since most full-screen programs access the console + through a terminal database library like + termcap, it should not matter much whether + you use this or vt0, the VT220 compatible + console driver. When you log in, set your TERM + variable to ``scoansi'' if full-screen programs + have trouble running under this console. + + device vt0 at isa? port ``IO_KBD'' tty irq 1 vector pcrint + +

This is a VT220-compatible + console driver, backwards compatible to VT100/102. + It works well on some laptops which have hardware + incompatibilities with sc0. Also, set + your TERM variable to ``vt220'' when you log in if + full-screen programs do not run correctly on this + console. + + + + options ``PCVT_FREEBSD=210'' + +

Required + with the vt0 console driver. + + options XSERVER + +

This includes code + required to run the XFree86 X Window + Server. + + + + device mse0 at isa? port 0x23c tty irq 5 vector ms + +

Use this device if you have a Logitech or + ATI InPort bus mouse card. + + port is enabled (probably + COM1). + + device psm0 at isa? port ``IO_KBD'' conflicts tty irq 12 vector psmintr + +

Use this device if your + mouse plugs into the PS/2 mouse port. + + + + Serial and Parallel Ports + +

Nearly all systems have these. If you are attaching a + printer to one of these ports, the section of the handbook is very + useful. If you are using modem, provides extensive detail on + serial port configuration for use with such devices. + + + + device sio0 at isa? port ``IO_COM1'' tty irq 4 vector siointr + +

sio0 + through sio3 are the four serial ports + referred to as COM1 through COM4 in the MS-DOS + world. Note that if you have an internal modem on + COM4 and a serial port at COM2 you will have to + change the IRQ of the modem to 2 (for obscure + technical reasons IRQ 2 = IRQ 9) in order to access + it from FreeBSD. If you have a multiport serial + card, check the manual page for sio(4) for + more information on the proper values for these + lines. + + device lpt0 at isa? port? tty irq 7 vector lptintr + +

lpt0 through lpt2 + are the three printer ports you could conceivably + have. Most people just have one, though, so feel + free to comment out the other two lines if you do + not have them. + + + + Networking + +

FreeBSD, as with Unix in general, places a + big emphasis on networking. Therefore, even + if you do not have an Ethernet card, pay attention to + the mandatory options and the dial-up networking + support. + + + + options INET + Networking support. Leave it in even if you do not plan + to be connected to a network. Most programs require at least + loopback networking (i.e. making network connections within your + PC) so this is essentially mandatory. + + Ethernet cards + +

The next lines enable support for various Ethernet + cards. If you do not have a network card, you can + comment out all of these lines. Otherwise, you'll + want to leave in support for your particular + Ethernet card(s): + + + + device de0 + +

Digital Equipment DC21040 PCI Ethernet adapter + + device cx0 at isa? port 0x240 net irq 15 drq 7 vector cxintr + +

Cronyx/Sigma multiport + sync/async (with Cisco or PPP framing) + + device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr + +

Western Digital and SMC 80xx; Novell NE1000 + and NE2000; 3Com 3C503 + + device el0 at isa? port 0x300 net irq 9 vector elintr + +

3Com 3C501 (slow!) + + device eg0 at isa? port 0x310 net irq 5 vector egintr + +

3Com 3C505 + + device ep0 at isa? port 0x300 net irq 10 vector epintr + +

3Com 3C509 (buggy) + + device fe0 at isa? port 0x240 net irq ? vector feintr + +

Fujitsu MB86960A/MB86965A Ethernet + + device fea0 at isa? net irq ? vector feaintr + +

DEC DEFEA EISA FDDI adapter + + device ie0 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr + +

AT&T StarLAN 10 and EN100; 3Com 3C507; + unknown NI5210 + + device ix0 at isa? port 0x300 net irq 10 iomem 0xd0000 iosiz 32768 vector ixintr + +

Intel EtherExpress 16 + + device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr + +

Digital Equipment EtherWorks 2 and EtherWorks + 3 (DEPCA, DE100, DE101, DE200, DE201, DE202, + DE203, DE204, DE205, DE422) + + device lnc0 at isa? port 0x300 net irq 10 drq 0 vector lncintr + +

Lance/PCnet cards (Isolan, Novell NE2100, + NE32-VL) + + device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr + +

IBM/National Semiconductor PCMCIA ethernet + controller. + + device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr + +

3Com PCMCIA Etherlink III + + + + + + pseudo-device loop + +

loop is the + generic loopback device for TCP/IP. If you telnet + or FTP to localhost + (a.k.a. 127.0.0.1) it will come back at + you through this pseudo-device. Mandatory. + + pseudo-device ether + +

ether is only + needed if you have an Ethernet card and includes + generic Ethernet protocol code. + + pseudo-device sl number + +

sl is for SLIP (Serial Line Internet + Protocol) support. This has been almost entirely + supplanted by PPP, which is easier to set up, + better suited for modem-to-modem connections, as + well as more powerful. The number after + sl specifies how many simultaneous SLIP + sessions to support. This handbook has more + information on setting up a SLIP or . + + pseudo-device ppp number + +

ppp is for kernel-mode PPP (Point-to-Point + Protocol) support for dial-up Internet connections. + There is also version of PPP implemented as a user + application that uses the tun and offers + more flexibility and features such as demand + dialing. If you still want to use this PPP driver, + read the + section of the handbook. As with the sl + device, number specifies how many + simultaneous PPP connections to support. + + pseudo-device tun number + +

tun is used by the user-mode PPP software. + This program is easy to set up and very fast. It + also has special features such as automatic + dial-on-demand. The number after tun + specifies the number of simultaneous PPP sessions + to support. See the section of the handbook for + more information. + + pseudo-device bpfilter number + +

Berkeley packet filter. This pseudo-device allows + network interfaces to be placed in promiscuous + mode, capturing every packet on a broadcast network + (e.g. an ethernet). These packets can be captured + to disk and/or examined with the + tcpdump(1) program. Note that + implementation of this capability can seriously + compromise your overall network security. + The number after bpfilter is the number of + interfaces that can be examined + simultaneously. Optional, not recommended except + for those who are fully aware of the potential + pitfalls. Not all network cards support this + capability. + + + + Sound cards + +

This is the first section containing lines that are + not in the GENERIC kernel. To include sound card + support, you'll have to copy the appropriate lines from + the LINT kernel (which contains support for + every device) as follows: + + + + controller snd0 + +

Generic sound driver code. + Required for all of the following sound cards + except pca. + + device pas0 at isa? port 0x388 irq 10 drq 6 vector pasintr + +

ProAudioSpectrum digital audio and MIDI. + + device sb0 at isa? port 0x220 irq 7 conflicts drq 1 vector sbintr + +

SoundBlaster digital audio. + + irq 7 + to, for example, irq 5 and remove the + conflicts keyword. Also, you must add + the line: options ``SBC_IRQ=5'' + + device sbxvi0 at isa? drq 5 + +

SoundBlaster 16 digital 16-bit audio. + + drq 5 keyword appropriately, and then + add the line: options + "SB16_DMA=6" + + device sbmidi0 at isa? port 0x330 + +

SoundBlaster 16 MIDI interface. If you have a + SoundBlaster 16, you must include this line, or the + kernel will not compile. + + device gus0 at isa? port 0x220 irq 10 drq 1 vector gusintr + +

Gravis Ultrasound. + + device mss0 at isa? port 0x530 irq 10 drq 1 vector adintr + +

Microsoft Sound System. + + device opl0 at isa? port 0x388 conflicts + +

AdLib FM-synthesis audio. Include this line for + AdLib, SoundBlaster, and ProAudioSpectrum users, if + you want to play MIDI songs with a program such as + playmidi (in the ports collection). + + device mpu0 at isa? port 0x330 irq 6 drq 0 + +

Roland MPU-401 stand-alone card. + + device uart0 at isa? port 0x330 irq 5 vector ``m6850intr'' + +

Stand-alone 6850 UART for MIDI. + + device pca0 at isa? port ``IO_TIMER1'' tty + +

Digital audio through PC speaker. This is going to + be very poor sound quality and quite CPU-intensive, + so you have been warned (but it does not require a + sound card)! + + + + /usr/src/sys/i386/isa/sound/sound.doc. + Also, if you add any of these devices, be sure to + create the sound . + + Pseudo-devices + +

Pseudo-device drivers are parts of the kernel that act + like device drivers but do not correspond to any actual + hardware in the machine. The + pseudo-devices are in that section, while the remainder + are here. + + + + pseudo-device gzip + +

gzip allows you to run FreeBSD programs + that have been compressed with gzip. This + is really only useful when you need to compress + FreeBSD programs to fit on a boot floppy. You will + probably never need to compress programs on your + hard drive in this fashion, so you'll probably want + to comment out this line. + pseudo-device log + +

log is used for logging of kernel error + messages. Mandatory. + + + pseudo-device pty number + +

pty is a ``pseudo-terminal'' or simulated + login port. It's used by incoming telnet + and rlogin sessions, xterm, and some other + applications such as emacs. The number + indicates the number of ptys to create. + If you need more than GENERIC default of 16 + simultaneous xterm windows and/or remote logins, be + sure to increase this number accordingly, up to a + maximum of 64. + + pseudo-device snp number + +

Snoop device. This pseudo-device allows one + terminal session to watch another using the + watch(8) command. Note that + implementation of this capability has important + security and privacy implications. The + number after snp is the total number of + simultaneous snoop sessions. Optional. + + pseudo-device vn + +

Vnode driver. Allows a file to be treated as a + device after being set up with the + vnconfig(8) command. This driver can be + useful for manipulating floppy disk images and + using a file as a swap device (e.g. an MS Windows + swap file). Optional. + + + + Joystick, PC Speaker, Miscellaneous + +

This section describes some miscellaneous hardware + devices supported by FreeBSD. Note that none of these + lines are included in the GENERIC kernel, you'll have + to copy them from this handbook or the LINT kernel + (which contains support for every device): + + + + device joy0 at isa? port ``IO_GAME'' + +

PC joystick device. + + pseudo-device speaker + +

Supports IBM BASIC-style noises through the PC + speaker. Some fun programs which use this are + /usr/sbin/spkrtest, which is a shell + script that plays some simple songs, and + /usr/games/piano which lets you play songs + using the keyboard as a simple piano (this file + only exists if you've installed the games + package). Also, the excellent text role-playing + game NetHack (in the ports collection) can be + configured to use this device to play songs when + you play musical instruments in the game. + + + + Making Device Nodes + +

Almost every device in the kernel has a corresponding + ``node'' entry in the /dev directory. These + nodes look like regular files, but are actually special + entries into the kernel which programs use to access the + device. The shell script /dev/MAKEDEV, which is + executed when you first install the operating system, + creates nearly all of the device nodes supported. + However, it does not create all 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: + +controller wcd0 + + This means that you should look for some entries that + start with wcd0 in the /dev directory, + possibly followed by a letter, such as `c', or preceded + by the letter 'r', which means a `raw' device. It turns + out that those files are not there, so I must change to + the /dev directory and type: + +# sh MAKEDEV wcd0 + + When this script finishes, you will find that there are + now wcd0c and rwcd0c entries in + /dev so you know that it executed correctly. + + For sound cards, the command: + +# sh MAKEDEV snd0 + + creates the appropriate entries. Follow this simple + procedure for any other non-GENERIC devices which do not + have entries. + + /dev entries, so you do not need to create + these. Also, network cards and SLIP/PPP pseudo-devices + do not have entries in /dev at all, so you do + not have to worry about these either. + +If Something Goes Wrong + +

There are four categories of trouble that can occur when + building a custom kernel. They are: + + + + Config command fails + +

If the config + command fails when you give it your kernel + description, you've probably made a simple error + somewhere. Fortunately, config will print + the line number that it had trouble with, so you can + quickly skip to it with vi. For example, if + you see: + +config: line 17: syntax error + + you can skip to the problem in vi by typing + ``17G'' in command mode. Make sure the keyword is + typed correctly, by comparing it to the GENERIC + kernel or another reference. + + Make command fails + +

If the make + command fails, it usually signals an error in your + kernel description, but not severe enough for + config to catch it. Again, look over your + configuration, and if you still cannot resolve the + problem, send mail to with your kernel + configuration, and it should be diagnosed very + quickly. + + 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 for recovering from incompatible kernels. + Simply type the name of the kernel you want to boot + from (i.e. ``kernel.old'') at the FreeBSD boot + prompt instead of pressing return. When + reconfiguring a kernel, it is always a good idea to + keep a kernel that is known to work on hand. + + After booting with a good kernel you can check over + your configuration file and try to build it again. + One helpful resource is the + /var/log/messages file which records, among + other things, all of the kernel messages from every + successful boot. Also, the dmesg(8) command + will print the kernel messages from the current boot. + + kernel.old + because when installing a new kernel, + kernel.old is overwritten with the last + installed kernel which may be non-functional. + Also, as soon as possible, move the working kernel + to the proper ``kernel'' location or commands such + as ps(1) will not work properly. The + proper command to ``unlock'' the kernel file that + make installs (in order to move another + kernel back permanently) is: + +# chflags noschg /kernel + + And, if you want to ``lock'' your new kernel into place, or any file + for that matter, so that it cannot be moved or tampered with: + +# chflags schg /kernel + + + + Kernel works, but ps does not work any more! + +

If you've installed a different version + of the kernel from the one that the system utilities + have been built with, for example, an experimental + ``2.2.0'' kernel on a 2.1.0-RELEASE system, many + system-status commands like ps(1) and + vmstat(8) will not work any more. You must + recompile the libkvm library as well as + these utilities. This is one reason it is not + normally a good idea to use a different version of + the kernel from the rest of the operating system. + + diff --git a/share/doc/handbook/porting.sgml b/share/doc/handbook/porting.sgml index 88597ed880f..d100ff1d73c 100644 --- a/share/doc/handbook/porting.sgml +++ b/share/doc/handbook/porting.sgml @@ -1,4 +1,4 @@ - + Porting applications @@ -120,23 +120,23 @@

The minimal Makefile would look something like this: -# New ports collection makefile for: oneko -# Version required: 1.1b -# Date created: 5 December 1994 -# Whom: asami -# -# $Id: porting.sgml,v 1.5 1995/09/27 00:46:24 jmz Exp $ -# - -DISTNAME= oneko-1.1b -CATEGORIES+= games -MASTER_SITES= ftp://ftp.cs.columbia.edu/archives/X11R5/contrib/ - -MAINTAINER= asami@FreeBSD.ORG - -USE_IMAKE= yes - -.include + # New ports collection makefile for: oneko + # Version required: 1.1b + # Date created: 5 December 1994 + # Whom: asami + # + # $Id: porting.sgml,v 1.6 1995/10/03 07:11:51 asami Exp $ + # + + DISTNAME= oneko-1.1b + CATEGORIES+= games + MASTER_SITES= ftp://ftp.cs.columbia.edu/archives/X11R5/contrib/ + + MAINTAINER= asami@FreeBSD.ORG + + USE_IMAKE= yes + + .include

See if you can figure it out. Don't worry about the contents @@ -725,11 +725,11 @@ FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2 user can set in /etc/make.conf to disable man page compression. Here's an example: -post-install: - strip ${PREFIX}/bin/xdl -.if !defined(NOMANCOMPRESS) - gzip -9nf ${PREFIX}/man/man1/xdl.1 -.endif + post-install: + strip ${PREFIX}/bin/xdl + .if !defined(NOMANCOMPRESS) + gzip -9nf ${PREFIX}/man/man1/xdl.1 + .endif

Use the file command on the installed executable @@ -874,75 +874,75 @@ lib/libtcl.so.7.3 important information is easy to locate. -[the header...just to make it easier for us to identify the ports] -# New ports collection makefile for: xdvi -# Version required: 2.2 [things like "1.5alpha" are fine here too] -# Date created: 26 May 1995 -[this is the person who did the original port to FreeBSD, in particular, the - person who wrote this Makefile] -# Whom: Satoshi Asami -# -# $Id: porting.sgml,v 1.5 1995/09/27 00:46:24 jmz Exp $ -[ ^^^^ don't worry about this...it will be automatically filled in by CVS when - it is committed to our repository] -# - -[section to describe the package itself and main ftp site - DISTNAME - is always first, followed by PKGNAME (if necessary), CATEGORIES, - KEYWORDs (if necessary) and then MASTER_SITES, and optionally - EXTRACT_SUFX or DISTFILES] -DISTNAME= xdvi -PKGNAME= xdvi-pl18 -CATEGORIES+= printing -[don't forget the trailing slash ("/")!] -MASTER_SITES= ftp://crl.dec.com/pub/X11/contrib/applications/ -[set this if the source is not in the standard ".tar.gz" form] -EXTRACT_SUFX= .tar.Z - -[section for distributed patches -- can be empty] -PATCH_SITES= ftp://ftp.sra.co.jp/pub/X11/japanese/ -PATCHFILES= xdvi-18.patch1.gz xdvi-18.patch2.gz - -[maintainer; *mandatory*! This is the person (preferably with commit - privileges) who a user can contact for questions and bug reports - this - person should be the porter or someone who can forward questions to the - original porter reasonably promptly. If you really don't want to have your - address here, set it to "ports@FreeBSD.ORG".] -MAINTAINER= asami@FreeBSD.ORG - -[dependencies -- can be empty] -RUN_DEPENDS= gs:${PORTSDIR}/print/ghostscript -LIB_DEPENDS= Xpm\\.4\\.:${PORTSDIR}/graphics/xpm - -[this section is for other standard bsd.port.mk variables that don't belong to - any of the above] -[If it extracts to a directory other than ${DISTNAME}...] -WRKSRC= ${WRKDIR}/xdvi-new -[If it asks questions during configure, build, install...] -IS_INTERACTIVE= yes -[If it requires "configure" in the distributed source directory to be run...] -HAS_CONFIGURE= yes -[If it requires GNU make, not /usr/bin/make, to build...] -USE_GMAKE= yes -[If it is an X application and requires "xmkmf -a" to be run...] -USE_IMAKE= yes -[et cetera.] - -[non-standard variables to be used in the rules below] -MY_FAVORITE_RESPONSE= "yeah, right" - -[then the special rules, in the order they are called] -pre-fetch: - i go fetch something, yeah - -post-patch: - i need to do something after patch, great - -pre-install: - and then some more stuff before installing, wow - -[and then the epilogue] -.include + [the header...just to make it easier for us to identify the ports] + # New ports collection makefile for: xdvi + # Version required: 2.2 [things like "1.5alpha" are fine here too] + # Date created: 26 May 1995 + [this is the person who did the original port to FreeBSD, in particular, the + person who wrote this Makefile] + # Whom: Satoshi Asami + # + # $Id: porting.sgml,v 1.6 1995/10/03 07:11:51 asami Exp $ + [ ^^^^ don't worry about this...it will be automatically filled in by CVS when + it is committed to our repository] + # + + [section to describe the package itself and main ftp site - DISTNAME + is always first, followed by PKGNAME (if necessary), CATEGORIES, + KEYWORDs (if necessary) and then MASTER_SITES, and optionally + EXTRACT_SUFX or DISTFILES] + DISTNAME= xdvi + PKGNAME= xdvi-pl18 + CATEGORIES+= printing + [don't forget the trailing slash ("/")!] + MASTER_SITES= ftp://crl.dec.com/pub/X11/contrib/applications/ + [set this if the source is not in the standard ".tar.gz" form] + EXTRACT_SUFX= .tar.Z + + [section for distributed patches -- can be empty] + PATCH_SITES= ftp://ftp.sra.co.jp/pub/X11/japanese/ + PATCHFILES= xdvi-18.patch1.gz xdvi-18.patch2.gz + + [maintainer; *mandatory*! This is the person (preferably with commit + privileges) who a user can contact for questions and bug reports - this + person should be the porter or someone who can forward questions to the + original porter reasonably promptly. If you really don't want to have your + address here, set it to "ports@FreeBSD.ORG".] + MAINTAINER= asami@FreeBSD.ORG + + [dependencies -- can be empty] + RUN_DEPENDS= gs:${PORTSDIR}/print/ghostscript + LIB_DEPENDS= Xpm\\.4\\.:${PORTSDIR}/graphics/xpm + + [this section is for other standard bsd.port.mk variables that don't belong to + any of the above] + [If it extracts to a directory other than ${DISTNAME}...] + WRKSRC= ${WRKDIR}/xdvi-new + [If it asks questions during configure, build, install...] + IS_INTERACTIVE= yes + [If it requires "configure" in the distributed source directory to be run...] + HAS_CONFIGURE= yes + [If it requires GNU make, not /usr/bin/make, to build...] + USE_GMAKE= yes + [If it is an X application and requires "xmkmf -a" to be run...] + USE_IMAKE= yes + [et cetera.] + + [non-standard variables to be used in the rules below] + MY_FAVORITE_RESPONSE= "yeah, right" + + [then the special rules, in the order they are called] + pre-fetch: + i go fetch something, yeah + + post-patch: + i need to do something after patch, great + + pre-install: + and then some more stuff before installing, wow + + [and then the epilogue] + .include diff --git a/share/doc/handbook/relnotes.sgml b/share/doc/handbook/relnotes.sgml index d85f2992cce..f7a581f2ee1 100644 --- a/share/doc/handbook/relnotes.sgml +++ b/share/doc/handbook/relnotes.sgml @@ -1,4 +1,4 @@ - + + + + + Gateways and routes + +

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 destination and a + gateway. The pair indicates that if you are + trying to get to this destination, send along + through this gateway. There are three types of + destinations: individual hosts, subnets, and ``default''. The + ``default route'' is used if none of the other routes + apply. We will talk a little bit more about default routes + later on. There are also three types of gateways: + individual hosts, interfaces (also called ``links''), and + ethernet hardware addresses. + + An example + +

To illustrate different aspects of routing, we will use + the following example which is the output of the command + netstat -r: + + +Destination Gateway Flags Refs Use Netif Expire + +default outside-gw UGSc 37 418 ppp0 +localhost localhost UH 0 181 lo0 +test0 0:e0:b5:36:cf:4f UHLW 5 63288 ed0 77 +10.20.30.255 link#1 UHLW 1 2421 +foobar.com link#1 UC 0 0 +host1 0:e0:a8:37:8:1e UHLW 3 4601 lo0 +host2 0:e0:a8:37:8:1e UHLW 0 5 lo0 => +host2.foobar.com link#1 UC 0 0 +224 link#1 UC 0 0 + + + The first two lines specify the default route (which we + will cover in the next section) and the localhost route. + + The interface (Netif column) that it specifies to use + for localhost is lo0, also known as the + loopback device. This says to keep all traffic for this + destination internal, rather than sending it out over the + LAN, since it will only end up back where it started + anyway. + + The next thing that stands out are the + ``0:e0:...'' addresses. These are ethernet + hardware addresses. FreeBSD will automatically identify any + hosts (test0 in the example) on the local ethernet and + add a route for that host, directly to it over the ethernet + interface, ed0. There is also a timeout + (Expire column) associated with this type of route, + which is used if we fail to hear from the host in a + specific amount of time. In this case the route will be + automatically deleted. These hosts are identified using a + mechanism known as RIP (Routing Information Protocol), + which figures out routes to local hosts based upon a + shortest path determination. + + FreeBSD will also add subnet routes for the local subnet + (10.20.30.255 is the broadcast address for the subnet + 10.20.30, and foobar.com is the domain name + associated with that subnet). The designation link#1 + refers to the first ethernet card in the machine. You'll + notice no additional interface is specified for those. + + Both of these groups (local network hosts and local + subnets) have their routes automatically configured by a + daemon called routed. If this is not run, then only + routes which are statically defined (ie. entered + explicitly) will exist. + + The host1 line refers to our host, which it knows by + ethernet address. Since we are the sending host, FreeBSD + knows to use the loopback interface (lo0) rather than + sending it out over the ethernet interface. + + The two host2 lines are an example of what happens + when we use an ifconfig alias (see the section of ethernet + for reasons why we would do this). The => + symbol after the lo0 interface says that not only are + we using the loopback (since this is address also refers to + the local host), but specifically it is an alias. Such + routes only show up on the host that supports the alias; + all other hosts on the local network will simply have a + link#1 line for such. + + The final line (destination subnet 224) deals with + MultiCasting, which will be covered in a another section. + + The other column that we should talk about are the + Flags. Each route has different attributes that are + described in the column. Below is a short table of some of + these flags and their meanings: + + + + + + + Default routes + +

When the local system needs to make a connection to + remote host, it checks the routing table to determine if + a known path exists. If the remote host falls into a + subnet that we know how to reach (Cloned routes), then + the system checks to see if it can connect along that + interface. + + If all known paths fail, the system has one last option: + the default route. This route is a special type + of gateway route (usually the only one present in the + system), and is always marked with a ``c'' in + the flags field. For hosts on a local area network, this + gateway is set to whatever machine has a direct + connection to the outside world (whether via PPP link, or + your hardware device attached to a dedicated data line). + + If you are configuring the default route for a machine + which itself is functioning as the gateway to the outside + world, then the default route will be the gateway machine + at your Internet Service Provider's (ISP) site. + + Let's look at an example of default routes. This is a + common configuration: + +[Local2] <--ether--> [Local1] <--PPP--> [ISP-Serv] <--ether--> [T1-GW] + + + The hosts Local1 and Local2 are at your + site, with the formed being your PPP connection to your + ISP's Terminal Server. Your ISP has a local network at + their site, which has, among other things, the server + where you connect and a hardware device (T1-GW) attached + to the ISP's internet feed. + + The default routes for each of your machines will be: + + +host default gateway interface +---- --------------- --------- +Local2 Local1 ethernet +Local1 T1-GW PPP + + + A common question is ``Why (or how) would we set the + T1-GW to be the default gateway for Local1, rather than + the ISP server it is connected to?''. + + Remember, since the PPP interface is using an address on + the ISP's local network for your side of the connection, + routes for any other machines on the ISP's local network + will be automatically generated. Hence, you will already + know how to reach the T1-GW machine, so there is no need + for the intermediate step of sending traffic to the ISP + server. + + As a final note, it is common to use the address ``...1'' + as the gateway address for your local network. So (using + the same example), if your local class-C address space + was 10.20.30 and your ISP was using 10.9.9 then the + default routes would be: + + +Local2 (10.20.30.2) --> Local1 (10.20.30.1) +Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1) + + + Dual homed hosts + +

There is one other type of configuration that we should + cover, and that is a host that sits on two different + networks. Technically, any machine functioning as a + gateway (in the example above, using a PPP connection) + counts as a dual-homed host. But the term is really only + used to refer to a machine that sits on two local-area + networks. + + In one case, the machine as two ethernet cards, each + having an address on the seperate subnets. Alternately, + the machine may only have one ethernet card, and be using + ifconfig aliasing. The former is used if two physically + separate ethernet networks are in use, the latter if + there is one physical network segment, but two logically + seperate subnets. + + Either way, routing tables are set up so that each subnet + knows that this machine is the defined gateway (inbound + route) to the other subnet. This configuration, with the + machine acting as a Bridge between the two subnets, is + often used when we need to implement packet filtering or + firewall security in either or both directions. + + Routing propogation + +

We have already talked about how we define our routes to + the outside world, but not about how the outside world + finds us. + + We already know that routing tables can be set up so that + all traffic for a particular address space (in our + examples, a class-C subnet) can be sent to a particular + host on that network, which will forward the packets + inbound. + + When you get an address space assigned to your site, your + service provider will set up their routing tables so that + all traffic for your subnet will be sent down your PPP + link to your site. But how do sites across the country + know to send to your ISP? + + There is a system (much like the distributed DNS + information) that keeps track of all assigned + address-spaces, and defines their point of connection to + the Internet Backbone. The ``Backbone'' are the main + trunk lines that carry internet traffic across the + country, and around the world. Each backbone machine has + a copy of a master set of tables, which direct traffic + for a particular network to a specific backbone carrier, + and from there down the chain of service providers until + it reaches your network. + + It is the task of your service provider to advertise to + the backbone sites that they are the point of connection + (and thus the path inward) for your site. This is known + as route propogation. + + + + Troubleshooting + +

Sometimes, there is a problem with routing propogation, + and some sites are unable to connect to you. Perhaps the + most useful command for trying to figure out where a + routing is breaking down is the traceroute(8) + command. It is equally useful if you cannot seem to make + a connection to a remote machine (ie. ping(8) + fails). + + The traceroute(8) command is run with the name + of the remote host you are trying to connect to. It will + show the gateway hosts along the path of the attempt, + eventually either reaching the target host, or + terminating because of a lack of connection. + + For more information, see the manual page for + traceroute(8). + diff --git a/share/doc/handbook/scsi.sgml b/share/doc/handbook/scsi.sgml index 9542f107e0e..2bdbf9afa07 100644 --- a/share/doc/handbook/scsi.sgml +++ b/share/doc/handbook/scsi.sgml @@ -1,4 +1,4 @@ - + SCSI -

© 1995, &a.wilko;.3 September 1995. +

Copyright © 1995, &a.wilko;.3 September 1995. SCSI is an acronym for Small Computer Systems Interface. It is an ANSI standard that has become one of the leading I/O buses in the @@ -163,7 +163,7 @@ 0 Volts (indeed, TTL levels) and are relative to a COMMON ground reference. A singled ended 8 bit SCSI bus has approximately 25 ground lines, who are all tied to a single - 'rail' on all devices. A standard single ended bus has a + `rail' on all devices. A standard single ended bus has a maximum length of 6 meters. If the same bus is used with fast-SCSI devices, the maximum length allowed drops to 3 meters. Fast-SCSI means that instead of 5Mbytes/sec the bus diff --git a/share/doc/handbook/sections.sgml b/share/doc/handbook/sections.sgml index 13125988fb4..33011b321e7 100644 --- a/share/doc/handbook/sections.sgml +++ b/share/doc/handbook/sections.sgml @@ -1,4 +1,4 @@ - + @@ -32,6 +32,7 @@ + diff --git a/share/doc/handbook/skey.sgml b/share/doc/handbook/skey.sgml index 4f8149e499e..865e2ca5cfe 100644 --- a/share/doc/handbook/skey.sgml +++ b/share/doc/handbook/skey.sgml @@ -1,4 +1,4 @@ - + + Setting up a SLIP client @@ -17,10 +17,10 @@ mileage may vary. --> First, determine which serial port your modem is connected to. I have -a symbolic link /dev/modem -> cuaa1, and only use the modem name in my +a symbolic link /dev/modem -> cuaa1, and only use the modem name in my configuration files. It can become quite cumbersome when you need to -fix a bunch of files in /etc and .kermrc's all over the system! (Note -that /dev/cuaa0 is COM1, cuaa1 is COM2, etc.) +fix a bunch of files in /etc and .kermrc's all over the system! (Note +that /dev/cuaa0 is COM1, cuaa1 is COM2, etc.) Make sure you have diff --git a/share/doc/handbook/submitters.sgml b/share/doc/handbook/submitters.sgml index babbea8db27..8123f0fe981 100644 --- a/share/doc/handbook/submitters.sgml +++ b/share/doc/handbook/submitters.sgml @@ -1,4 +1,4 @@ - + Contributing to FreeBSD @@ -82,11 +82,11 @@ are each, in their own way, quite significant to the project. FreeBSD maintainers. This is done with the diff(1) command, with the `context diff' form being preferred. For example: -diff -c <oldfile> <newfile> +diff -c oldfile newfile or -diff -c -r <olddir> <newdir> +diff -c -r olddir newdir would generate such a set of context diffs for the given source file or directory hierarchy. See the man page for diff(1) for more @@ -193,7 +193,7 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - $Id: submitters.sgml,v 1.6 1995/08/12 21:33:24 jkh Exp $ + $Id: submitters.sgml,v 1.7 1995/09/27 00:46:29 jmz Exp $ For your convenience, a copy of this text can be found in /usr/share/examples/etc/bsd-style-copyright.