From owner-svn-doc-projects@FreeBSD.ORG Sun May 12 18:54:31 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 32E004F8; Sun, 12 May 2013 18:54:31 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 2440C97F; Sun, 12 May 2013 18:54:31 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4CIsT6E030456; Sun, 12 May 2013 18:54:29 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4CIsT9K030455; Sun, 12 May 2013 18:54:29 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201305121854.r4CIsT9K030455@svn.freebsd.org> From: Dru Lavigne Date: Sun, 12 May 2013 18:54:29 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41615 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 May 2013 18:54:31 -0000 Author: dru Date: Sun May 12 18:54:29 2013 New Revision: 41615 URL: http://svnweb.freebsd.org/changeset/doc/41615 Log: White space fix only. Translators can ignore. Approved by: bcr (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml Sun May 12 17:59:38 2013 (r41614) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml Sun May 12 18:54:29 2013 (r41615) @@ -68,13 +68,12 @@ - How to use the various configuration files in - /etc. + How to use the various configuration files in /etc. - How to tune &os; using &man.sysctl.8; - variables. + How to tune &os; using &man.sysctl.8; variables. @@ -120,8 +119,8 @@ When laying out file systems with &man.bsdlabel.8; or &man.sysinstall.8;, remember that hard drives transfer data - faster from the outer tracks to the inner. Thus, smaller and - heavier-accessed file systems should be closer to the + faster from the outer tracks to the inner. Thus, smaller + and heavier-accessed file systems should be closer to the outside of the drive, while larger partitions like /usr should be placed toward the inner parts of the disk. It is a good idea to @@ -133,26 +132,25 @@ The size of the /var partition reflects the intended machine's usage. This partition - is used to hold - mailboxes, log files, and printer spools. Mailboxes and log - files can grow to unexpected sizes depending on the number of - users and how long log files are kept. On average, most users - rarely need more than about a gigabyte of free disk space in - /var. + is used to hold mailboxes, log files, and printer spools. + Mailboxes and log files can grow to unexpected sizes + depending on the number of users and how long log files + are kept. On average, most users rarely need more than + about a gigabyte of free disk space in /var. - Sometimes, a lot of disk space is - required in - /var/tmp. When new - software is installed with &man.pkg.add.1;, the packaging - tools extract a temporary copy of the packages under - /var/tmp. Large - software packages, like + Sometimes, a lot of disk space is required in + /var/tmp. When + new software is installed with &man.pkg.add.1;, the + packaging tools extract a temporary copy of the packages + under /var/tmp. + Large software packages, like Firefox, OpenOffice or LibreOffice may be tricky to - install if there is not enough disk space under - /var/tmp. + install if there is not enough disk space under /var/tmp. The /usr @@ -162,17 +160,14 @@ partition. When selecting partition sizes, keep the space - requirements in mind. Running out of space in - one partition while barely using another can be a - hassle. + requirements in mind. Running out of space in one partition + while barely using another can be a hassle. - The - Auto-defaults partition sizer used by - &man.sysinstall.8; will - sometimes select smaller than adequate - /var and - / partitions. + The Auto-defaults partition sizer + used by &man.sysinstall.8; will sometimes select smaller + than adequate /var + and / partitions. Partition wisely and generously. @@ -185,30 +180,27 @@ As a rule of thumb, the swap partition should be about double the size of physical memory (RAM) - as the kernel's - virtual memory (VM) paging algorithms - are tuned to perform - best when the swap partition is at least two times - the size of main memory. Systems with minimal - RAM may - perform better with more swap. Configuring too little swap - can lead to inefficiencies in the VM - page scanning code and - might create issues later if more memory is added. + as the kernel's virtual memory (VM) + paging algorithms are tuned to perform best when the swap + partition is at least two times the size of main memory. + Systems with minimal RAM may perform + better with more swap. Configuring too little swap can + lead to inefficiencies in the VM page + scanning code and might create issues later if more memory + is added. On larger systems with multiple SCSI - disks or multiple - IDE disks operating on different - controllers, it is - recommended that swap be configured on each drive, up to - four drives. The swap partitions should be approximately - the same size. The kernel can handle arbitrary sizes but - internal data structures scale to 4 times the largest swap - partition. Keeping the swap partitions near the same size - will allow the kernel to optimally stripe swap space across - disks. Large swap sizes are fine, even if swap is not used - much. It might be easier to recover from a runaway program - before being forced to reboot. + disks or multiple IDE disks operating + on different controllers, it is recommended that swap be + configured on each drive, up to four drives. The swap + partitions should be approximately the same size. The + kernel can handle arbitrary sizes but internal data + structures scale to 4 times the largest swap partition. + Keeping the swap partitions near the same size will allow + the kernel to optimally stripe swap space across disks. + Large swap sizes are fine, even if swap is not used much. + It might be easier to recover from a runaway program before + being forced to reboot. @@ -218,24 +210,24 @@ fine, but there are several reasons why this is a bad idea. First, each partition has different operational characteristics and separating them allows the file system - to tune accordingly. For example, the root and - /usr partitions are + to tune accordingly. For example, the root and /usr partitions are read-mostly, with few writes, while a lot of reads and - writes could occur in - /var and - /var/tmp. + writes could occur in /var and /var/tmp. By properly partitioning a system, fragmentation introduced in the smaller write heavy partitions will not bleed over into the mostly read partitions. Keeping the write loaded partitions closer to the disk's edge will increase I/O performance in the partitions where it occurs - the most. While I/O performance in the larger - partitions may be needed, shifting them more toward the edge - of the disk will not lead to a significant performance - improvement over moving - /var to the edge. - Finally, there are safety concerns. A smaller, neater root + the most. While I/O performance in the larger partitions + may be needed, shifting them more toward the edge of the + disk will not lead to a significant performance + improvement over moving /var to the edge. Finally, + there are safety concerns. A smaller, neater root partition which is mostly read-only has a greater chance of surviving a bad crash. @@ -251,8 +243,8 @@ The principal location for system configuration information - is /etc/rc.conf. This file contains - a wide range of configuration information and it is read at + is /etc/rc.conf. This file contains a + wide range of configuration information and it is read at system startup to configure the system. It provides the configuration information for the rc* files. @@ -269,8 +261,7 @@ system-specific configuration in order to keep administration overhead down. The recommended approach is to place system-specific configuration into - /etc/rc.conf.local. For - example: + /etc/rc.conf.local. For example: @@ -291,10 +282,10 @@ ifconfig_fxp0="inet 10.1.1.1/8" - Distribute /etc/rc.conf - to every system using rsync or a - similar program, while /etc/rc.conf.local - remains unique. + Distribute /etc/rc.conf to every + system using rsync or a similar program, + while /etc/rc.conf.local remains + unique. Upgrading the system using &man.sysinstall.8; or make world will not overwrite @@ -320,18 +311,17 @@ ifconfig_fxp0="inet 10.1.1.1/8"/usr/local/etc - Typically, these files are installed in - /usr/local/etc. In the - case where an application has a large number of configuration + Typically, these files are installed in /usr/local/etc. In the case + where an application has a large number of configuration files, a subdirectory will be created to hold them. Normally, when a port or package is installed, sample configuration files are also installed. These are usually identified with a suffix such as .sample. - If - there are no existing configuration files for the application, - they can be created by copying the - sample files. + If there are no existing configuration files for the + application, they can be created by copying the sample + files. For example, consider the contents of the directory - The file sizes show that only - srm.conf has been changed. A later - update of the Apache port would not - overwrite this changed file. + The file sizes show that only srm.conf + has been changed. A later update of the + Apache port would not overwrite + this changed file. @@ -371,10 +361,10 @@ ifconfig_fxp0="inet 10.1.1.1/8"Many users install third party software on &os; from the Ports Collection and require the installed services to be - started upon system initialization. Services, - such as mail/postfix or - www/apache22 are just two of - the many software packages which may be started during system + started upon system initialization. Services, such as + mail/postfix or + www/apache22 are just two + of the many software packages which may be started during system initialization. This section explains the procedures available for starting third party software. @@ -386,13 +376,12 @@ ifconfig_fxp0="inet 10.1.1.1/8"Now that &os; includes rc.d, configuration of application startup is easier and provides - more features. Using the key words discussed in - , - applications can be set to start after certain other services - and extra flags can be passed through - /etc/rc.conf in place of hard coded flags - in the start up script. A basic script may look similar to - the following: + more features. Using the key words discussed in , applications can be set to + start after certain other services and extra flags can be + passed through /etc/rc.conf in place of + hard coded flags in the start up script. A basic script may + look similar to the following: #!/bin/sh # @@ -429,34 +418,32 @@ run_rc_command "$1" utility_enable="YES" - This method allows for easier manipulation of - command line arguments, inclusion of the default functions - provided in /etc/rc.subr, compatibility - with &man.rcorder.8;, and provides for easier - configuration via rc.conf. + This method allows for easier manipulation of command + line arguments, inclusion of the default functions provided + in /etc/rc.subr, compatibility with + &man.rcorder.8;, and provides for easier configuration via + rc.conf. Using Services to Start Services - Other services can be started using - &man.inetd.8;. Working - with &man.inetd.8; and its configuration is + Other services can be started using &man.inetd.8;. + Working with &man.inetd.8; and its configuration is described in depth in . In some cases, it may make more sense to use &man.cron.8; to start system services. This approach - has a number of advantages as &man.cron.8; - runs these processes as the owner of the &man.crontab.5;. - This allows regular users to start and maintain their own + has a number of advantages as &man.cron.8; runs these + processes as the owner of the &man.crontab.5;. This allows + regular users to start and maintain their own applications. The @reboot feature of &man.cron.8;, - may be used in - place of the time specification. This causes the job to - run when &man.cron.8; is started, normally during system - initialization. + may be used in place of the time specification. This causes + the job to run when &man.cron.8; is started, normally during + system initialization. @@ -479,20 +466,18 @@ run_rc_command "$1" One of the most useful utilities in &os; is &man.cron.8;. This utility runs in the background and regularly checks /etc/crontab for tasks to execute and - searches - /var/cron/tabs for custom - &man.crontab.5; files. These files store - information about specific functions which - &man.cron.8; is supposed to perform at certain - times. + searches /var/cron/tabs + for custom &man.crontab.5; files. These files store + information about specific functions which &man.cron.8; is + supposed to perform at certain times. Two different types of configuration files are used by - &man.cron.8;: the system crontab and user crontabs. - These formats only differ in the sixth field and later. In the - system crontab, &man.cron.8; runs the command as - the user specified in the sixth field. In a user crontab, all - commands run as the user who created the crontab, so the sixth - field is the last field; this is an important security feature. + &man.cron.8;: the system crontab and user crontabs. These + formats only differ in the sixth field and later. In the + system crontab, &man.cron.8; runs the command as the user + specified in the sixth field. In a user crontab, all commands + run as the user who created the crontab, so the sixth field + is the last field; this is an important security feature. The final field is always the command to run. @@ -505,14 +490,13 @@ run_rc_command "$1" just like any other user. The root user crontab is separate from the system crontab, /etc/crontab. - Because the system crontab - invokes the specified commands as root, - there is usually no - need to create a user crontab for - root. + Because the system crontab invokes the specified commands as + root, there is usually no need to create + a user crontab for root. - Here is a sample entry from /etc/crontab: + Here is a sample entry from + /etc/crontab: # /etc/crontab - root's crontab for FreeBSD # @@ -538,15 +522,13 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin - The equals - (=) character is used to define any - environment settings. In this example, it is used to define - the SHELL and PATH. - If the SHELL is omitted, - &man.cron.8; will use the default of - &man.sh.1;. If the PATH - is omitted, no default will be used and file locations will - need to be absolute. + The equals (=) character is used to + define any environment settings. In this example, it is + used to define the SHELL and + PATH. If the SHELL is + omitted, &man.cron.8; will use the default of &man.sh.1;. + If the PATH is omitted, no default will be + used and file locations will need to be absolute. @@ -557,20 +539,18 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin who, and command. These are almost all self explanatory. minute is the time in minutes when the - specified command - will be run. hour is the hour when - the specified command will be run. + specified command will be run. hour is + the hour when the specified command will be run. mday stands for day of the month and - month - designates the month. The wday option - stands for day of the week. These fields must be - numeric values, representing the twenty-four hour clock, - or a *, representing all values for that - field. The + month designates the month. The + wday option stands for day of the week. + These fields must be numeric values, representing the + twenty-four hour clock, or a *, + representing all values for that field. The who field only exists in the system - crontab. This field specifies - which user the command should be run as. The last field is - the command to be executed. + crontab. This field specifies which user the command + should be run as. The last field is the command to be + executed. @@ -580,9 +560,8 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin * characters mean first-last, and can be interpreted as every time. In this example, - &man.atrun.8; is invoked by - root every five minutes, regardless of - the day or month. + &man.atrun.8; is invoked by root + every five minutes, regardless of the day or month. Commands can have any number of flags passed to them; however, commands which extend to multiple lines need to be @@ -591,11 +570,10 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin - This is the basic setup for every - &man.crontab.5;. However, field number six, which specifies - the username, only exists in the system - &man.crontab.5;. This field should be omitted for - individual user &man.crontab.5; files. + This is the basic setup for every &man.crontab.5;. + However, field number six, which specifies the username, only + exists in the system &man.crontab.5;. This field should be + omitted for individual user &man.crontab.5; files. Installing a Crontab @@ -604,17 +582,16 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin Do not use the procedure described here to edit and install the system crontab, /etc/crontab. Instead, use an - editor and &man.cron.8; will notice that the file - has changed and immediately begin using the updated version. + editor and &man.cron.8; will notice that the file has + changed and immediately begin using the updated version. See this FAQ entry for more information. - To install a freshly written user - &man.crontab.5;, use an editor to create - and save a file in the proper format. Then, specify the file - name with &man.crontab.1;: + To install a freshly written user &man.crontab.5;, use + an editor to create and save a file in the proper format. + Then, specify the file name with &man.crontab.1;: &prompt.user; crontab crontab-file @@ -627,13 +604,12 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin Users who wish to begin their own crontab file from scratch, without the use of a template, can use - crontab -e. This will - invoke the default editor with an empty file. When the file - is saved, it will be automatically installed by - &man.crontab.1;. + crontab -e. This will invoke the default + editor with an empty file. When the file is saved, it will + be automatically installed by &man.crontab.1;. - In order to remove a user &man.crontab.5; - completely, use crontab -r. + In order to remove a user &man.crontab.5; completely, + use crontab -r. @@ -651,46 +627,41 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin Using &man.rc.8; Under &os; - In 2002, &os; integrated the NetBSD &man.rc.8; - system for system initialization. The files - listed in /etc/rc.d - provide basic services which can - be controlled with the , + In 2002, &os; integrated the NetBSD &man.rc.8; system for + system initialization. The files listed in /etc/rc.d provide basic services + which can be controlled with the , , and options - to &man.service.8;. - For instance, &man.sshd.8; can be restarted with the following - command: + to &man.service.8;. For instance, &man.sshd.8; can be restarted + with the following command: &prompt.root; service sshd restart This procedure can be used to start services on a running - system. - Services will be started automatically at boot time as - specified in &man.rc.conf.5;. For example, to enable &man.natd.8; - at system startup, add the - following line to /etc/rc.conf: + system. Services will be started automatically at boot time + as specified in &man.rc.conf.5;. For example, to enable + &man.natd.8; at system startup, add the following line to + /etc/rc.conf: natd_enable="YES" If a line is already present, change the NO to YES. The &man.rc.8; scripts will - automatically load - any dependent services during the next boot, as - described below. - - Since the &man.rc.8; system is primarily - intended to start and stop services at system startup and - shutdown time, - the , and + automatically load any dependent services during the next boot, + as described below. + + Since the &man.rc.8; system is primarily intended to start + and stop services at system startup and shutdown time, the + , and options will only perform their action if the appropriate /etc/rc.conf variable is set. For instance, sshd restart will only work if sshd_enable is set to in /etc/rc.conf. To , or - a service regardless of the settings in - /etc/rc.conf, these commands should be + a service regardless of the settings + in /etc/rc.conf, these commands should be prefixed with one. For instance, to restart &man.sshd.8; regardless of the current /etc/rc.conf setting, execute the following @@ -700,9 +671,8 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin To check if a service is enabled in /etc/rc.conf, run the appropriate - &man.rc.8; script with - . This example checks to see if - &man.sshd.8; is enabled in + &man.rc.8; script with . This example + checks to see if &man.sshd.8; is enabled in /etc/rc.conf: &prompt.root; service sshd rcvar @@ -711,9 +681,7 @@ $sshd_enable=YES The # sshd line is output from the - above command, - not a - root console. + above command, not a root console. To determine whether or not a service is running, use @@ -723,40 +691,38 @@ $sshd_enable=YES &prompt.root; service sshd status sshd is running as pid 433. - In some cases, it is also possible to - a service. This attempts to send a signal to an individual - service, forcing the service to reload its configuration files. - In most cases, this means sending the service a - SIGHUP signal. Support for this feature is - not included for every service. - - The &man.rc.8; system is used for - network services and it also contributes to most of the system - initialization. For instance, when the + In some cases, it is also possible to + a service. This attempts to send a + signal to an individual service, forcing the service to reload + its configuration files. In most cases, this means sending + the service a SIGHUP signal. Support for + this feature is not included for every service. + + The &man.rc.8; system is used for network services and it + also contributes to most of the system initialization. For + instance, when the /etc/rc.d/bgfsck script is executed, it - prints - out the following message: + prints out the following message: Starting background file system checks in 60 seconds. - This script is used for background file system - checks, which occur only during system initialization. + This script is used for background file system checks, + which occur only during system initialization. Many system services depend on other services to function properly. For example, &man.yp.8; and other - RPC-based services may - fail to start until after the &man.rpcbind.8; - service has started. To resolve this issue, - information about dependencies and other meta-data is included - in the comments at the top of each startup script. The - &man.rcorder.8; program is used to parse these comments + RPC-based services may fail to start until + after the &man.rpcbind.8; service has started. To resolve this + issue, information about dependencies and other meta-data is + included in the comments at the top of each startup script. + The &man.rcorder.8; program is used to parse these comments during system initialization to determine the order in which system services should be invoked to satisfy the dependencies. - The following key word must be included in all startup scripts - as it is required by &man.rc.subr.8; to enable - the startup script: + The following key word must be included in all startup + scripts as it is required by &man.rc.subr.8; to + enable the startup script: @@ -773,15 +739,15 @@ sshd is running as pid 433. REQUIRE: Lists services which are required for this service. The script containing this key - word will run - after the specified services. + word will run after the specified + services. BEFORE: Lists services which depend on this service. The script containing this key word will - run - before the specified services. + run before the specified + services. @@ -791,9 +757,9 @@ sshd is running as pid 433. runlevels used by some &unix; operating systems. - Additional information - can be found in &man.rc.8; and &man.rc.subr.8;. Refer to - this article for + Additional information can be found in &man.rc.8; and + &man.rc.subr.8;. Refer to this article for instructions on how to create custom &man.rc.8; scripts. @@ -818,8 +784,8 @@ sshd is running as pid 433. Adding and configuring a network interface card - (NIC) is a common task for - any &os; administrator. + (NIC) is a common task for any &os; + administrator. Locating the Correct Driver @@ -832,14 +798,12 @@ sshd is running as pid 433. First, determine the model of the NIC and the chip it uses. &os; supports a wide variety of NICs. Check the Hardware Compatibility - List for - the &os; release to see if the NIC is - supported. + List for the &os; release to see if the NIC + is supported. If the NIC is supported, determine - the name of the &os; - driver for the NIC. Refer to - /usr/src/sys/conf/NOTES and + the name of the &os; driver for the NIC. + Refer to /usr/src/sys/conf/NOTES and /usr/src/sys/arch/conf/NOTES for the list of NIC drivers with some information about the supported chipsets. When in doubt, read @@ -848,12 +812,10 @@ sshd is running as pid 433. limitations of the driver. The drivers for common NICs are - already present - in the GENERIC kernel, meaning the - NIC - should show up during boot. In this example, two - NICs using - the &man.dc.4; driver are present on the system: + already present in the GENERIC kernel, + meaning the NIC should show up during boot. + In this example, two NICs using the + &man.dc.4; driver are present on the system: dc0: <82c169 PNIC 10/100BaseTX> port 0xa000-0xa0ff mem 0xd3800000-0xd38 000ff irq 15 at device 11.0 on pci0 @@ -871,36 +833,33 @@ dc1: Ethernet address: 00:a0:cc:da:da:db dc1: [ITHREAD] If the driver for the NIC is not - present in - GENERIC, but a driver is available, the - driver will need to be loaded before the - NIC can be - configured and used. This may be accomplished in one of two - ways: + present in GENERIC, but a driver is + available, the driver will need to be loaded before the + NIC can be configured and used. This may + be accomplished in one of two ways: The easiest way is to load a kernel module for the NIC using &man.kldload.8;. To also - automatically - load the driver at boot time, add the appropriate line to + automatically load the driver at boot time, add the + appropriate line to /boot/loader.conf. Not all - NIC - drivers are available as modules. + NIC drivers are available as + modules. Alternatively, statically compile support for the - NIC - into a custom kernel. Refer to + NIC into a custom kernel. Refer to /usr/src/sys/conf/NOTES, /usr/src/sys/arch/conf/NOTES and the manual page of the driver to determine which line to add to the custom kernel configuration file. For more - information about recompiling the kernel, refer to - . If the - NIC was detected - at boot, the kernel does not need to be recompiled. + information about recompiling the kernel, refer to . If the + NIC was detected at boot, the kernel + does not need to be recompiled. @@ -914,7 +873,8 @@ dc1: [ITHREAD] device drivers - KLD (kernel loadable object) + KLD (kernel loadable + object) community because they regard such information as trade secrets. Consequently, the developers of &os; and other operating systems are left with two choices: develop the - drivers - by a long and pain-staking process of reverse engineering or - using the existing driver binaries available for - µsoft.windows; platforms. - - &os; provides - native support for the Network Driver - Interface Specification (NDIS). It - includes - &man.ndisgen.8; which can be used to - convert a &windowsxp; driver - into a format that can be used on &os;. - Because the &man.ndis.4; driver uses a - &windowsxp; binary, it only runs on &i386; and amd64 systems. - PCI, CardBus, PCMCIA, - and USB devices are - supported. + drivers by a long and pain-staking process of reverse + engineering or using the existing driver binaries available + for µsoft.windows; platforms. + + &os; provides native support for the + Network Driver Interface Specification + (NDIS). It includes &man.ndisgen.8; + which can be used to convert a &windowsxp; driver into a + format that can be used on &os;. Because the &man.ndis.4; + driver uses a &windowsxp; binary, it only runs on &i386; + and amd64 systems. PCI, CardBus, + PCMCIA, and USB + devices are supported. To use &man.ndisgen.8;, three things are needed: @@ -963,11 +919,9 @@ linuxemu/chapter.xml --> Download the .SYS and .INF files for the specific - NIC. - Generally, - these can be found on the driver CD or at the vendor's - website. The following examples use - W32DRIVER.SYS and + NIC. Generally, these can be found on + the driver CD or at the vendor's website. The following + examples use W32DRIVER.SYS and W32DRIVER.INF. The driver bit width must match the version of &os;. @@ -982,9 +936,8 @@ linuxemu/chapter.xml --> This command is interactive and prompts for any extra information it requires. A new kernel module will be - generated in - the current directory. Use &man.kldload.8; to load the new - module: + generated in the current directory. Use &man.kldload.8; + to load the new module: &prompt.root; kldload ./W32DRIVER_SYS.ko @@ -998,13 +951,12 @@ linuxemu/chapter.xml --> &prompt.root; kldload ndis &prompt.root; kldload if_ndis - The first command loads the &man.ndis.4; - miniport driver - wrapper and the second loads the generated NIC - driver. + The first command loads the &man.ndis.4; miniport driver + wrapper and the second loads the generated + NIC driver. - Check &man.dmesg.8; to see if there were any load errors. - If all went well, the output should be similar to + Check &man.dmesg.8; to see if there were any load + errors. If all went well, the output should be similar to the following: ndis0: <Wireless-G PCI Adapter> mem 0xf4100000-0xf4101fff irq 3 at device 8.0 on pci1 @@ -1013,15 +965,14 @@ ndis0: Ethernet address: 0a:b1:2c:d3:4e: ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 36Mbps 48Mbps 54Mbps - From here, - ndis0 can be configured like any other - NIC. + From here, ndis0 can be + configured like any other NIC. - To configure the system to load the &man.ndis.4; modules at - boot time, copy the generated module, + To configure the system to load the &man.ndis.4; modules + at boot time, copy the generated module, W32DRIVER_SYS.ko, to /boot/modules. Then, - add the following line to + class="directory">/boot/modules. Then, add the + following line to /boot/loader.conf: W32DRIVER_SYS_load="YES" @@ -1037,8 +988,7 @@ ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18M Once the right driver is loaded for the - NIC, the - card needs to be configured. It + NIC, the card needs to be configured. It may have been configured at installation time by &man.sysinstall.8;. @@ -1088,13 +1038,12 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M &os; uses the driver name followed by the order in which the card is detected at boot to name the NIC. For example, - sis2 is - the third NIC on the system using the - &man.sis.4; + sis2 is the third + NIC on the system using the &man.sis.4; driver. - In this example, dc0 - is up and running. The key indicators are: + In this example, dc0 is up and + running. The key indicators are: @@ -1104,26 +1053,26 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M The card has an Internet (inet) - address, - 192.168.1.3. + address, 192.168.1.3. It has a valid subnet mask - (netmask), where - 0xffffff00 is the same as + (netmask), where 0xffffff00 is the same as 255.255.255.0. - It has a valid broadcast address, - 192.168.1.255. + It has a valid broadcast address, 192.168.1.255. The MAC address of the card - (ether) - is 00:a0:cc:da:da:da. + (ether) is 00:a0:cc:da:da:da. @@ -1157,14 +1106,12 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M it would indicate the card has not been configured. - The card must be configured as - root. The NIC - configuration can be performed from the command line with - &man.ifconfig.8; but will not persist after a reboot unless - the configuration is also added to - /etc/rc.conf. Add a - line for each NIC present on the system, - as seen in + The card must be configured as root. + The NIC configuration can be performed + from the command line with &man.ifconfig.8; but will not + persist after a reboot unless the configuration is also added + to /etc/rc.conf. Add a line for each + NIC present on the system, as seen in this example: ifconfig_dc0="inet 192.168.1.3 netmask 255.255.255.0" @@ -1172,31 +1119,27 @@ ifconfig_dc1="inet 10.0.0.1 netmask 255. Replace dc0 and dc1 and the IP - address information - with the correct values for the system. *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***