diff options
Diffstat (limited to 'share/man/man4')
34 files changed, 252 insertions, 154 deletions
diff --git a/share/man/man4/ath.4 b/share/man/man4/ath.4 index e416110..9d53b89 100644 --- a/share/man/man4/ath.4 +++ b/share/man/man4/ath.4 @@ -58,8 +58,8 @@ if_ath_load="YES" The .Nm driver provides support for wireless network adapters based on -the Atheros AR5210, AR5211, and AR5212 programming api's. -These api's are used by a wide variety of chips; all chips with +the Atheros AR5210, AR5211, and AR5212 programming APIs. +These APIs are used by a wide variety of chips; all chips with a PCI and/or CardBus interface are supported. Chip-specific support is provided by the Atheros Hardware Access Layer (HAL), that is packaged separately. @@ -213,7 +213,6 @@ Create a host-based wireless bridge to fxp0: .Bd -literal -offset indent ifconfig ath0 inet up ssid my_ap media DS/11Mbps mediaopt hostap sysctl net.inet.ip.check_interface=0 -kldload if_bridge.ko ifconfig bridge0 create ifconfig bridge0 addm ath0 addm fxp0 .Ed diff --git a/share/man/man4/bpf.4 b/share/man/man4/bpf.4 index 2839dad..9911a63 100644 --- a/share/man/man4/bpf.4 +++ b/share/man/man4/bpf.4 @@ -22,7 +22,7 @@ .\" .\" $FreeBSD$ .\" -.Dd January 16, 1996 +.Dd August 23, 2005 .Dt BPF 4 .Os .Sh NAME @@ -258,8 +258,13 @@ for an explanation of the filter language. .It Dv BIOCSETWF .Pq Li "struct bpf_program" Sets the write filter program used by the kernel to control what type of -packets can be written to the interface. See the BIOCSETF command for more -information on the bpf filter program. +packets can be written to the interface. +See the +.Dv BIOCSETF +command for more +information on the +.Nm +filter program. .It Dv BIOCVERSION .Pq Li "struct bpf_version" Returns the major and minor version numbers of the filter language currently @@ -307,7 +312,10 @@ Set to one to see packets originating locally and remotely on the interface. This flag is initialized to one by default. .It Dv BIOCLOCK -Set the locked flag on the bpf descriptor. This prevents the execution of +Set the locked flag on the +.Nm +descriptor. +This prevents the execution of ioctl commands which could change the underlying operating parameters of the device. .El diff --git a/share/man/man4/cardbus.4 b/share/man/man4/cardbus.4 index 04b3e23..1c3600a 100644 --- a/share/man/man4/cardbus.4 +++ b/share/man/man4/cardbus.4 @@ -41,7 +41,7 @@ The driver supports all cardbus bridges in the system. .Sh TUNABLES The driver supports the following tunable parameters, which may be -added to +added to .Pa /boot/loader.conf or set via the .Xr sysctl 8 diff --git a/share/man/man4/dcons.4 b/share/man/man4/dcons.4 index 694a253..a0dfa1b 100644 --- a/share/man/man4/dcons.4 +++ b/share/man/man4/dcons.4 @@ -31,7 +31,7 @@ .Nm dcons .Nd dumb console device driver .Sh SYNOPSIS -To compile support for the driver into your kernel, +To compile this driver into the kernel, place the following lines in your kernel configuration file: .Bd -ragged -offset indent .Cd "options GDB" @@ -39,7 +39,7 @@ place the following lines in your kernel configuration file: .Cd "device dcons" .Ed .Pp -Alternatively, to load the driver at boot time, +Alternatively, to load the driver as a module at boot time, place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "options GDB" diff --git a/share/man/man4/de.4 b/share/man/man4/de.4 index 2179c50..16b20ab 100644 --- a/share/man/man4/de.4 +++ b/share/man/man4/de.4 @@ -33,7 +33,7 @@ .Nd "DEC DC21x4x Ethernet device driver" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device de" diff --git a/share/man/man4/ed.4 b/share/man/man4/ed.4 index f3322f2..b600678 100644 --- a/share/man/man4/ed.4 +++ b/share/man/man4/ed.4 @@ -399,6 +399,6 @@ As a result, it may throw out some good packets which have been received but not yet transferred from the card to main memory. .Pp The -.Nm -PC Card attachment supports the D-Link DMF650TX Lan/Modem card's ethernet +.Nm +PC Card attachment supports the D-Link DMF650TX LAN/Modem card's Ethernet port only at this time. diff --git a/share/man/man4/em.4 b/share/man/man4/em.4 index 7b1e8f1..cd57228 100644 --- a/share/man/man4/em.4 +++ b/share/man/man4/em.4 @@ -39,7 +39,7 @@ .Nd "Intel(R) PRO/1000 Gigabit Ethernet adapter driver" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device em" @@ -175,7 +175,7 @@ Intel PRO/1000 XT Server Adapter (82544) Tunables can be set at the .Xr loader 8 prompt before booting the kernel or stored in -.Pa /boot/loader.conf . +.Xr loader.conf 5 . .Bl -tag -width indent .It Va hw.em.rxd Number of receive descriptors allocated by the driver. diff --git a/share/man/man4/fwip.4 b/share/man/man4/fwip.4 index 4de3942..c2c9f05 100644 --- a/share/man/man4/fwip.4 +++ b/share/man/man4/fwip.4 @@ -41,7 +41,7 @@ kernel configuration file: .Ed .Pp Alternatively, to load the driver as a -module at boot time, place the following line in +module at boot time, place the following lines in .Xr loader.conf 5 : .Bd -literal -offset indent firewire_load="YES" diff --git a/share/man/man4/geom.4 b/share/man/man4/geom.4 index 78c5584b..7ea24eb 100644 --- a/share/man/man4/geom.4 +++ b/share/man/man4/geom.4 @@ -39,22 +39,31 @@ .Dt GEOM 4 .Sh NAME .Nm GEOM -.Nd modular disk I/O request transformation framework. +.Nd "modular disk I/O request transformation framework" .Sh DESCRIPTION -The GEOM framework provides an infrastructure in which "classes" +The +.Nm +framework provides an infrastructure in which +.Dq classes can perform transformations on disk I/O requests on their path from the upper kernel to the device drivers and back. .Pp -Transformations in a GEOM context range from the simple geometric +Transformations in a +.Nm +context range from the simple geometric displacement performed in typical disk partitioning modules over RAID algorithms and device multipath resolution to full blown cryptographic protection of the stored data. .Pp -Compared to traditional "volume management", GEOM differs from most +Compared to traditional +.Dq "volume management" , +.Nm +differs from most and in some cases all previous implementations in the following ways: .Bl -bullet .It -GEOM is extensible. +.Nm +is extensible. It is trivially simple to write a new class of transformation and it will not be given stepchild treatment. If @@ -62,10 +71,11 @@ someone for some reason wanted to mount IBM MVS diskpacks, a class recognizing and configuring their VTOC information would be a trivial matter. .It -GEOM is topologically agnostic. +.Nm +is topologically agnostic. Most volume management implementations have very strict notions of how classes can fit together, very often -one fixed hierarchy is provided for instance subdisk - plex - +one fixed hierarchy is provided, for instance, subdisk - plex - volume. .El .Pp @@ -74,34 +84,56 @@ than existing transformations. .Pp Fixed hierarchies are bad because they make it impossible to express the intent efficiently. -In the fixed hierarchy above it is not possible to mirror two +In the fixed hierarchy above, it is not possible to mirror two physical disks and then partition the mirror into subdisks, instead one is forced to make subdisks on the physical volumes and to mirror -these two and two resulting in a much more complex configuration. -GEOM on the other hand does not care in which order things are done, +these two and two, resulting in a much more complex configuration. +.Nm +on the other hand does not care in which order things are done, the only restriction is that cycles in the graph will not be allowed. -.Pp -.Sh "TERMINOLOGY and TOPOLOGY" -GEOM is quite object oriented and consequently the terminology +.Sh "TERMINOLOGY AND TOPOLOGY" +.Nm +is quite object oriented and consequently the terminology borrows a lot of context and semantics from the OO vocabulary: .Pp -A "class", represented by the data structure g_class implements one +A +.Dq class , +represented by the data structure +.Vt g_class +implements one particular kind of transformation. Typical examples are MBR disk partition, BSD disklabel, and RAID5 classes. .Pp -An instance of a class is called a "geom" and represented by the -data structure "g_geom". -In a typical i386 FreeBSD system, there +An instance of a class is called a +.Dq geom +and represented by the data structure +.Vt g_geom . +In a typical i386 +.Fx +system, there will be one geom of class MBR for each disk. .Pp -A "provider", represented by the data structure "g_provider", is -the front gate at which a geom offers service. -A provider is "a disk-like thing which appears in /dev" - a logical +A +.Dq provider , +represented by the data structure +.Vt g_provider , +is the front gate at which a geom offers service. +A provider is +.Do +a disk-like thing which appears in +.Pa /dev +.Dc - a logical disk in other words. -All providers have three main properties: name, sectorsize and size. -.Pp -A "consumer" is the backdoor through which a geom connects to another +All providers have three main properties: +.Dq name , +.Dq sectorsize +and +.Dq size . +.Pp +A +.Dq consumer +is the backdoor through which a geom connects to another geom provider and through which I/O requests are sent. .Pp The topological relationship between these entities are as follows: @@ -126,7 +158,7 @@ This rank number is assigned as follows: .Bl -enum .It -A geom with no attached consumers has rank=1 +A geom with no attached consumers has rank=1. .It A geom with attached consumers has a rank one higher than the highest rank of the geoms of the providers its consumers are @@ -137,46 +169,52 @@ In addition to the straightforward attach, which attaches a consumer to a provider, and detach, which breaks the bond, a number of special topological maneuvers exists to facilitate configuration and to improve the overall flexibility. -.Pp -.Em TASTING +.Bl -inset +.It Em TASTING is a process that happens whenever a new class or new provider -is created and it provides the class a chance to automatically configure an -instance on providers, which it recognize as its own. +is created, and it provides the class a chance to automatically configure an +instance on providers, which it recognizes as its own. A typical example is the MBR disk-partition class which will look for -the MBR table in the first sector and if found and validated it will +the MBR table in the first sector and, if found and validated, will instantiate a geom to multiplex according to the contents of the MBR. .Pp A new class will be offered to all existing providers in turn and a new provider will be offered to all classes in turn. .Pp Exactly what a class does to recognize if it should accept the offered -provider is not defined by GEOM, but the sensible set of options are: +provider is not defined by +.Nm , +but the sensible set of options are: .Bl -bullet .It Examine specific data structures on the disk. .It -Examine properties like sectorsize or mediasize for the provider. +Examine properties like +.Dq sectorsize +or +.Dq mediasize +for the provider. .It Examine the rank number of the provider's geom. .It Examine the method name of the provider's geom. .El -.Pp -.Em ORPHANIZATION +.It Em ORPHANIZATION is the process by which a provider is removed while it potentially is still being used. .Pp When a geom orphans a provider, all future I/O requests will -"bounce" on the provider with an error code set by the geom. +.Dq bounce +on the provider with an error code set by the geom. Any consumers attached to the provider will receive notification about the orphanization when the eventloop gets around to it, and they can take appropriate action at that time. .Pp A geom which came into being as a result of a normal taste operation -should selfdestruct unless it has a way to keep functioning lacking +should self-destruct unless it has a way to keep functioning lacking the orphaned provider. -Geoms like diskslicers should therefore selfdestruct whereas +Geoms like diskslicers should therefore self-destruct whereas RAID5 or mirror geoms will be able to continue, as long as they do not loose quorum. .Pp @@ -185,7 +223,8 @@ immediate change in the topology: any attached consumers are still attached, any opened paths are still open, any outstanding I/O requests are still outstanding. .Pp -The typical scenario is +The typical scenario is: +.Pp .Bl -bullet -offset indent -compact .It A device driver detects a disk has departed and orphans the provider for it. @@ -200,11 +239,13 @@ relevant pieces of the tree has heard the bad news. Eventually the buck stops when it reaches geom_dev at the top of the stack. .It -Geom_dev will call destroy_dev(9) to stop any more request from +Geom_dev will call +.Xr destroy_dev 9 +to stop any more request from coming in. It will sleep until all (if any) outstanding I/O requests have been returned. -It will explicitly close (ie: zero the access counts), a change +It will explicitly close (i.e.: zero the access counts), a change which will propagate all the way down through the mesh. It will then detach and destroy its geom. .It @@ -221,26 +262,41 @@ flexibility and robustness in handling disappearing devices. The one absolutely crucial detail to be aware is that if the device driver does not return all I/O requests, the tree will not unravel. -.Pp -.Em SPOILING +.It Em SPOILING is a special case of orphanization used to protect against stale metadata. It is probably easiest to understand spoiling by going through an example. .Pp -Imagine a disk, "da0" on top of which a MBR geom provides -"da0s1" and "da0s2" and on top of "da0s1" a BSD geom provides -"da0s1a" through "da0s1e", both the MBR and BSD geoms have +Imagine a disk, +.Pa da0 +on top of which an MBR geom provides +.Pa da0s1 +and +.Pa da0s2 , +and on top of +.Pa da0s1 +a BSD geom provides +.Pa da0s1a +through +.Pa da0s1e , +both the MBR and BSD geoms have autoconfigured based on data structures on the disk media. -Now imagine the case where "da0" is opened for writing and those -data structures are modified or overwritten: Now the geoms would +Now imagine the case where +.Pa da0 +is opened for writing and those +data structures are modified or overwritten: now the geoms would be operating on stale metadata unless some notification system can inform them otherwise. .Pp -To avoid this situation, when the open of "da0" for write happens, +To avoid this situation, when the open of +.Pa da0 +for write happens, all attached consumers are told about this, and geoms like -MBR and BSD will selfdestruct as a result. -When "da0" is closed again, it will be offered for tasting again +MBR and BSD will self-destruct as a result. +When +.Pa da0 +is closed again, it will be offered for tasting again and if the data structures for MBR and BSD are still there, new geoms will instantiate themselves anew. .Pp @@ -248,9 +304,13 @@ Now for the fine print: .Pp If any of the paths through the MBR or BSD module were open, they would have opened downwards with an exclusive bit rendering it -impossible to open "da0" for writing in that case and conversely +impossible to open +.Pa da0 +for writing in that case and conversely the requested exclusive bit would render it impossible to open a -path through the MBR geom while "da0" is open for writing. +path through the MBR geom while +.Pa da0 +is open for writing. .Pp From this it also follows that changing the size of open geoms can only be done with their cooperation. @@ -258,8 +318,7 @@ only be done with their cooperation. Finally: the spoiling only happens when the write count goes from zero to non-zero and the retasting only when the write count goes from non-zero to zero. -.Pp -.Em INSERT/DELETE +.It Em INSERT/DELETE are a very special operation which allows a new geom to be instantiated between a consumer and a provider attached to each other and to remove it again. @@ -277,8 +336,7 @@ We have now in essence moved a mounted file system from one disk to another while it was being used. At this point the mirror geom can be deleted from the path again, it has served its purpose. -.Pp -.Em CONFIGURE +.It Em CONFIGURE is the process where the administrator issues instructions for a particular class to instantiate itself. There are multiple @@ -287,24 +345,33 @@ specified with a level of override forcing for instance a BSD disklabel module to attach to a provider which was not found palatable during the TASTE operation. .Pp -Finally IO is the reason we even do this: it concerns itself with +Finally I/O is the reason we even do this: it concerns itself with sending I/O requests through the graph. -.Pp -.Em "I/O REQUESTS -represented by struct bio, originate at a consumer, +.It Em "I/O REQUESTS" +represented by +.Vt "struct bio" , +originate at a consumer, are scheduled on its attached provider, and when processed, returned to the consumer. -It is important to realize that the struct bio which -enters through the provider of a particular geom does not "come -out on the other side". +It is important to realize that the +.Vt "struct bio" +which enters through the provider of a particular geom does not +.Do +come out on the other side +.Dc . Even simple transformations like MBR and BSD will clone the -struct bio, modify the clone, and schedule the clone on their +.Vt "struct bio" , +modify the clone, and schedule the clone on their own consumer. -Note that cloning the struct bio does not involve cloning the -actual data area specified in the IO request. +Note that cloning the +.Vt "struct bio" +does not involve cloning the +actual data area specified in the I/O request. .Pp -In total four different IO requests exist in GEOM: read, write, -delete, and get attribute. +In total, four different I/O requests exist in +.Nm : +read, write, delete, and +.Dq "get attribute". .Pp Read and write are self explanatory. .Pp @@ -320,24 +387,32 @@ It is important to recognize that a delete indication is not a request and consequently there is no guarantee that the data actually will be erased or made unavailable unless guaranteed by specific geoms in the graph. -If "secure delete" semantics are required, a +If +.Dq "secure delete" +semantics are required, a geom should be pushed which converts delete indications into (a sequence of) write requests. .Pp -Get attribute supports inspection and manipulation +.Dq "Get attribute" +supports inspection and manipulation of out-of-band attributes on a particular provider or path. -Attributes are named by ascii strings and they will be discussed in +Attributes are named by +.Tn ASCII +strings and they will be discussed in a separate section below. +.El .Pp -(stay tuned while the author rests his brain and fingers: more to come.) +(Stay tuned while the author rests his brain and fingers: more to come.) .Sh DIAGNOSTICS -Several flags are provided for tracing GEOM operations and unlocking +Several flags are provided for tracing +.Nm +operations and unlocking protection mechanisms via the .Va kern.geom.debugflags sysctl. All of these flags are off by default, and great care should be taken in turning them on. -.Bl -tag -width FAIL +.Bl -tag -width indent .It 0x01 Pq Dv G_T_TOPOLOGY Provide tracing of topology change events. .It 0x02 Pq Dv G_T_BIO @@ -358,14 +433,23 @@ This appears to be unused at this time. Dump contents of gctl requests. .El .Sh HISTORY -This software was developed for the FreeBSD Project by Poul-Henning Kamp +This software was developed for the +.Fx +Project by +.An Poul-Henning Kamp and NAI Labs, the Security Research Division of Network Associates, Inc.\& -under DARPA/SPAWAR contract N66001-01-C-8035 ("CBOSS"), as part of the +under DARPA/SPAWAR contract N66001-01-C-8035 +.Pq Dq CBOSS , +as part of the DARPA CHATS research program. .Pp -The first precursor for GEOM was a gruesome hack to Minix 1.2 and was +The first precursor for +.Nm +was a gruesome hack to Minix 1.2 and was never distributed. An earlier attempt to implement a less general scheme -in FreeBSD never succeeded. +in +.Fx +never succeeded. .Sh AUTHORS .An "Poul-Henning Kamp" Aq phk@FreeBSD.org diff --git a/share/man/man4/hwpmc.4 b/share/man/man4/hwpmc.4 index 67dc923..ab54f31 100644 --- a/share/man/man4/hwpmc.4 +++ b/share/man/man4/hwpmc.4 @@ -35,7 +35,7 @@ .Cd "device hwpmc" .Pp Additionally, for i386 systems: -.Cd device apic +.Cd "device apic" .Sh DESCRIPTION The .Nm @@ -503,7 +503,7 @@ between the currently executing kernel and the module being loaded. .It "hwpmc: this kernel has not been compiled with 'options HWPMC_HOOKS'." The module loading process failed because the currently executing kernel was not configured with the required configuration option -.Cd HWPMC_HOOKS . +.Dv HWPMC_HOOKS . .It "hwpmc: tunable hashsize=%d must be greater than zero." A negative value was supplied for tunable .Va kern.hwpmc.hashsize . diff --git a/share/man/man4/icmp.4 b/share/man/man4/icmp.4 index 3d60787..73600d1 100644 --- a/share/man/man4/icmp.4 +++ b/share/man/man4/icmp.4 @@ -141,8 +141,8 @@ By default continue with normal source selection. .Pq Vt boolean Use the IP address of the interface the packet came through in for responses to packets which are not directly addressed to us. -If enabled this rule is processed before all others. -By default continue with normal source selection. +If enabled, this rule is processed before all others. +By default, continue with normal source selection. Enabling this option is particularly useful on routers because it makes external traceroutes show the actual path a packet has taken instead of the possibly different return path. diff --git a/share/man/man4/if_bridge.4 b/share/man/man4/if_bridge.4 index 545e514..0dc4b05 100644 --- a/share/man/man4/if_bridge.4 +++ b/share/man/man4/if_bridge.4 @@ -174,10 +174,10 @@ ifconfig bridge0 \e up .Ed .Sh SEE ALSO -.Xr ifconfig 8 , -.Xr ipfw 4 , .Xr ipf 4 , -.Xr pf 4 +.Xr ipfw 4 , +.Xr pf 4 , +.Xr ifconfig 8 .Sh HISTORY The .Nm diff --git a/share/man/man4/ip.4 b/share/man/man4/ip.4 index d5da6e1..e8bea4e 100644 --- a/share/man/man4/ip.4 +++ b/share/man/man4/ip.4 @@ -117,7 +117,7 @@ setsockopt(s, IPPROTO_IP, IP_TTL, &ttl, sizeof(ttl)); may be used to set the minimum acceptable TTL a packet must have when received on a socket. All packets with a lower TTL are silently dropped. -This option is only really useful when set to 255 preventing packets +This option is only really useful when set to 255, preventing packets from outside the directly connected networks reaching local listeners on sockets. .Pp @@ -125,15 +125,19 @@ on sockets. may be used to set the Don't Fragment flag on IP packets. Currently this option is respected only on .Xr udp 4 -and Raw +and raw .Xr ip 4 -sockets, unless the IP_HDRINCL option has been set. +sockets, unless the +.Dv IP_HDRINCL +option has been set. On .Xr tcp 4 -sockets the Don't Fragment flag is controlled by the Path +sockets, the Don't Fragment flag is controlled by the Path MTU Discovery option. Sending a packet larger than the MTU size of the egress interface, -determined by the destination address, returns an EMSGSIZE error. +determined by the destination address, returns an +.Er EMSGSIZE +error. .Pp If the .Dv IP_RECVDSTADDR diff --git a/share/man/man4/ipw.4 b/share/man/man4/ipw.4 index 82bde9a..ae19cc8 100644 --- a/share/man/man4/ipw.4 +++ b/share/man/man4/ipw.4 @@ -42,7 +42,7 @@ kernel configuration file: .Ed .Pp Alternatively, to load the driver as a -module at boot time, place the following line in +module at boot time, place the following lines in .Xr loader.conf 5 : .Bd -literal -offset indent if_ipw_load="YES" diff --git a/share/man/man4/mac_seeotheruids.4 b/share/man/man4/mac_seeotheruids.4 index dc0d30e..4eeb7bb 100644 --- a/share/man/man4/mac_seeotheruids.4 +++ b/share/man/man4/mac_seeotheruids.4 @@ -30,7 +30,7 @@ .\" .\" $FreeBSD$ .\" -.Dd October 06, 2005 +.Dd October 6, 2005 .Os .Dt MAC_SEEOTHERUIDS 4 .Sh NAME diff --git a/share/man/man4/man4.i386/acpi_ibm.4 b/share/man/man4/man4.i386/acpi_ibm.4 index d2ef59c..2912a63 100644 --- a/share/man/man4/man4.i386/acpi_ibm.4 +++ b/share/man/man4/man4.i386/acpi_ibm.4 @@ -135,7 +135,7 @@ Access IBM Button .Ss Xr led 4 Ss Interface The .Nm -driver provides an +driver provides a .Xr led 4 interface for the Thinklight. The Thinklight can be made to blink by writing @@ -307,6 +307,13 @@ UltraBay battery .Pp Defaults for these sysctls can be set in .Xr sysctl.conf 5 . +.Sh FILES +.Bl -tag -width ".Pa /dev/led/thinklight" +.It Pa /dev/led/thinklight +Thinklight +.Xr led 4 +device node +.El .Sh EXAMPLES The following can be added to .Xr devd.conf 5 @@ -396,13 +403,6 @@ then fi exit 0 .Ed -.Sh FILES -.Bl -tag -width ".Pa /dev/led/thinklight" -.It Pa /dev/led/thinklight -Thinklight -.Xr led 4 -device node -.El .Sh SEE ALSO .Xr acpi 4 , .Xr sysctl.conf 5 , diff --git a/share/man/man4/man4.i386/arl.4 b/share/man/man4/man4.i386/arl.4 index 57a19bc..d908c8a 100644 --- a/share/man/man4/man4.i386/arl.4 +++ b/share/man/man4/man4.i386/arl.4 @@ -38,7 +38,7 @@ .Nd "Aironet Arlan 655 wireless network adapter driver" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device arl" diff --git a/share/man/man4/man4.i386/cp.4 b/share/man/man4/man4.i386/cp.4 index 894adfa..049bb08 100644 --- a/share/man/man4/man4.i386/cp.4 +++ b/share/man/man4/man4.i386/cp.4 @@ -21,7 +21,7 @@ .Nd "driver for synchronous Cronyx Tau-PCI WAN adapters" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device cp" diff --git a/share/man/man4/man4.i386/cs.4 b/share/man/man4/man4.i386/cs.4 index a09904c..77551e8 100644 --- a/share/man/man4/man4.i386/cs.4 +++ b/share/man/man4/man4.i386/cs.4 @@ -33,7 +33,7 @@ .Nd "Ethernet device driver" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device cs" diff --git a/share/man/man4/man4.i386/cx.4 b/share/man/man4/man4.i386/cx.4 index 4dcab79..00df603 100644 --- a/share/man/man4/man4.i386/cx.4 +++ b/share/man/man4/man4.i386/cx.4 @@ -21,12 +21,12 @@ .Nd "driver for synchronous/asynchronous Cronyx Sigma WAN adapters" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device cx" .Ed -Pp +.Pp Alternatively, to load the driver as a module at boot time, place the following line in .Xr loader.conf 5 : diff --git a/share/man/man4/man4.i386/ep.4 b/share/man/man4/man4.i386/ep.4 index 0ff55d6..62e1b72 100644 --- a/share/man/man4/man4.i386/ep.4 +++ b/share/man/man4/man4.i386/ep.4 @@ -37,7 +37,7 @@ .Nd "Ethernet driver for 3Com Etherlink III (3c5x9) interfaces" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device ep" @@ -154,50 +154,50 @@ They are supported by the driver. .Sh DIAGNOSTICS .Bl -diag -.It ep0: reset (status: %x) +.It "ep0: reset (status: %x)" The driver has encountered a FIFO underrun or overrun. The driver will reset the card and the packet will be lost. This is not fatal. -.It ep0: eeprom failed to come ready +.It "ep0: eeprom failed to come ready" The eeprom failed to come ready. This probably means the card is wedged. -.It ep0: 3c509 in test mode. Erase pencil mark! +.It "ep0: 3c509 in test mode. Erase pencil mark!" This means that someone has scribbled with pencil in the test area on the card. Erase the pencil mark and reboot. (This is not a joke). -.It ep0: No I/O space?! +.It "ep0: No I/O space?!" The driver was unable to allocate the I/O space that it thinks should be there. Look for conflicts with other devices. -.It ep0: No irq?! +.It "ep0: No irq?!" The driver couldn't allocate the interrupt it wanted. Look for conflicts, although sharing interrupts for PC Card is normal. -.It ep0: No connectors! +.It "ep0: No connectors!" The driver queried the hardware for what ethernet attachment were present, but the hardware reported none that the driver recognized. -.It ep0: Unable to get Ethernet address! +.It "ep0: Unable to get Ethernet address!" The driver was unable to read the ethernet address from the EEPROM. This is likely the result of the card being wedged. -.It ep0: if_alloc() failed +.It "ep0: if_alloc() failed" The driver was unable to allocate a ifnet structure. This may happen in extremely low memory conditions. -.It ep0: strange connector type in EEPROM: assuming AUI +.It "ep0: strange connector type in EEPROM: assuming AUI" The driver does not know what to do with the information the EEPROM has about connectors, so it is assuming the worst. -.It ep0: unknown ID 0xXXXXXXXX +.It "ep0: unknown ID 0xXXXXXXXX" The driver has found an ID that it believes it supports, but doesn't have a specific identification string to present to the user. -.It ep0: <%s> at port 0x%03x in EISA mode +.It "ep0: <%s> at port 0x%03x in EISA mode" The 3C509 ISA card is in EISA mode. -This message appears to be purely informational. -.It ep0: <%s> at x0%03x in PnP mode +This message appears to be purely informational. +.It "ep0: <%s> at x0%03x in PnP mode" This card appears to be in Plug and Play mode. It should be probed as part of the plug and play phase of the ISA probes. -.It ep0: Invalid EEPROM checksum! +.It "ep0: Invalid EEPROM checksum!" The EEPROM has a bad checksum, so the driver is ignoring the card. -.It ep0: bus_setup_intr() failed! +.It "ep0: bus_setup_intr() failed!" The driver was unable to setup the interrupt handler. This should never happen. .El diff --git a/share/man/man4/man4.i386/ex.4 b/share/man/man4/man4.i386/ex.4 index 469b456..3ffb3fc 100644 --- a/share/man/man4/man4.i386/ex.4 +++ b/share/man/man4/man4.i386/ex.4 @@ -33,7 +33,7 @@ .Nd "Ethernet device driver for the Intel EtherExpress Pro/10 and Pro/10+" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device ex" @@ -104,7 +104,7 @@ The .Nm device driver was written by .An Javier Mart\('in Rueda . -The PC Card attachment was written by +The PC Card attachment was written by .An Mitsuru ISAWAKI and .An Warner Losh . diff --git a/share/man/man4/man4.i386/fe.4 b/share/man/man4/man4.i386/fe.4 index 0c99ad7..ff395e9 100644 --- a/share/man/man4/man4.i386/fe.4 +++ b/share/man/man4/man4.i386/fe.4 @@ -30,7 +30,7 @@ .Nd "Fujitsu MB86960A/MB86965A based Ethernet adapters" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device fe" diff --git a/share/man/man4/man4.i386/ie.4 b/share/man/man4/man4.i386/ie.4 index ceb7b61..17d24d2 100644 --- a/share/man/man4/man4.i386/ie.4 +++ b/share/man/man4/man4.i386/ie.4 @@ -33,7 +33,7 @@ .Nd "Ethernet device driver" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device ie" diff --git a/share/man/man4/man4.i386/linux.4 b/share/man/man4/man4.i386/linux.4 index 62107ac..649027b 100644 --- a/share/man/man4/man4.i386/linux.4 +++ b/share/man/man4/man4.i386/linux.4 @@ -108,10 +108,14 @@ regardless of whether the .Nm module is statically linked into the kernel or loaded as a module. -.Ed .Pp -Some linux scripts want to execute /lib/ld-linux.so.2. In order to do this, -you should turn the kern.elf32.can_exec_dyn sysctl(8) variable to 1. +Some Linux scripts want to execute +.Pa /lib/ld-linux.so.2 . +In order to do this, +you should turn the +.Va kern.elf32.can_exec_dyn +.Xr sysctl 8 +variable to 1. .Sh FILES .Bl -tag -width /compat/linux/proc -compact .It Pa /compat/linux diff --git a/share/man/man4/man4.i386/lnc.4 b/share/man/man4/man4.i386/lnc.4 index a6ce332..4b04d71 100644 --- a/share/man/man4/man4.i386/lnc.4 +++ b/share/man/man4/man4.i386/lnc.4 @@ -33,7 +33,7 @@ .Nd "AMD Lance/PCnet Ethernet device driver" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device lnc" diff --git a/share/man/man4/man4.i386/ray.4 b/share/man/man4/man4.i386/ray.4 index a079d72..23eb168 100644 --- a/share/man/man4/man4.i386/ray.4 +++ b/share/man/man4/man4.i386/ray.4 @@ -38,7 +38,7 @@ .Nd "Raytheon Raylink/Webgear Aviator PCCard driver" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device ray" diff --git a/share/man/man4/man4.i386/vx.4 b/share/man/man4/man4.i386/vx.4 index 30dae91..99d89e9 100644 --- a/share/man/man4/man4.i386/vx.4 +++ b/share/man/man4/man4.i386/vx.4 @@ -38,7 +38,7 @@ .Nd "3Com EtherLink III / Fast EtherLink III (3c59x) Ethernet driver" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device vx" diff --git a/share/man/man4/ng_iface.4 b/share/man/man4/ng_iface.4 index 809e9e2..90563b8 100644 --- a/share/man/man4/ng_iface.4 +++ b/share/man/man4/ng_iface.4 @@ -149,11 +149,11 @@ However, is a special case, since it is not a physical interface with limited bandwidth. One should not turn ALTQ on .Nm -if the latter corresponds to some tunneled connection, e.g. PPPoE or PPTP. -In this case ALTQ should be configured on the interface, that is used to +if the latter corresponds to some tunneled connection, e.g.\& PPPoE or PPTP. +In this case, ALTQ should be configured on the interface that is used to transmit the encapsulated packets. In case when your graph ends up with some kind of serial line, either -synchronous or modem, then +synchronous or modem, the .Nm is the right place to turn ALTQ on. .Sh SEE ALSO diff --git a/share/man/man4/pccard.4 b/share/man/man4/pccard.4 index 1fb6ce0..f955804 100644 --- a/share/man/man4/pccard.4 +++ b/share/man/man4/pccard.4 @@ -41,7 +41,7 @@ The driver supports all PC Card bridges in the system. .Sh TUNABLES The driver supports the following tunable parameters, which may be -added to +added to .Pa /boot/loader.conf or set via the .Xr sysctl 8 diff --git a/share/man/man4/pccbb.4 b/share/man/man4/pccbb.4 index f39546a..27ef584 100644 --- a/share/man/man4/pccbb.4 +++ b/share/man/man4/pccbb.4 @@ -166,7 +166,7 @@ Toshiba ToPIC100 .El .Sh TUNABLES The driver supports the following tunable parameters, which may be -added to +added to .Pa /boot/loader.conf or set via the .Xr sysctl 8 diff --git a/share/man/man4/txp.4 b/share/man/man4/txp.4 index a674452..64a19e8 100644 --- a/share/man/man4/txp.4 +++ b/share/man/man4/txp.4 @@ -34,7 +34,7 @@ .Nd "3Com 3XP Typhoon/Sidewinder (3CR990) Ethernet interface" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device txp" diff --git a/share/man/man4/wi.4 b/share/man/man4/wi.4 index c1004e0..4070040 100644 --- a/share/man/man4/wi.4 +++ b/share/man/man4/wi.4 @@ -327,7 +327,6 @@ Create a host-based wireless bridge to fxp0 (Prism only): .Bd -literal -offset indent ifconfig wi0 inet up ssid my_ap media DS/11Mbps mediaopt hostap sysctl net.inet.ip.check_interface=0 -kldload if_bridge.ko ifconfig bridge0 create ifconfig bridge0 addm wi0 addm fxp0 .Ed diff --git a/share/man/man4/xe.4 b/share/man/man4/xe.4 index 2ad179b..0935884 100644 --- a/share/man/man4/xe.4 +++ b/share/man/man4/xe.4 @@ -33,7 +33,7 @@ .Nd "Xircom PCMCIA Ethernet device driver" .Sh SYNOPSIS To compile this driver into the kernel, -place the following lines in your +place the following line in your kernel configuration file: .Bd -ragged -offset indent .Cd "device xe" |