From owner-svn-doc-projects@FreeBSD.ORG Sun May 12 13:19:04 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C47F3B21; Sun, 12 May 2013 13:19:04 +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 B5E07B0F; Sun, 12 May 2013 13:19:04 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4CDJ462011244; Sun, 12 May 2013 13:19:04 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4CDJ4Z0011243; Sun, 12 May 2013 13:19:04 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201305121319.r4CDJ4Z0011243@svn.freebsd.org> From: Dru Lavigne Date: Sun, 12 May 2013 13:19:04 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41607 - 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 13:19:04 -0000 Author: dru Date: Sun May 12 13:19:04 2013 New Revision: 41607 URL: http://svnweb.freebsd.org/changeset/doc/41607 Log: This patch addresses the following: - you - missing acronym tags - replace command/app tags with entities - fix links - update some sample files - move sysctl.conf section until after sysctl to improve the flow of a topic not yet introduced A subsequent patch will fix white space. 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 10:42:44 2013 (r41606) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml Sun May 12 13:19:04 2013 (r41607) @@ -73,7 +73,7 @@ - How to tune &os; using sysctl + How to tune &os; using &man.sysctl.8; variables. @@ -120,30 +120,31 @@ 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 + 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 - create partitions in an order similar to: root, swap, - /var, + create partitions in an order similar to: /, swap, + /var, and /usr. The size of the /var partition reflects the intended machine's usage. This partition - /var is used to hold + is used to hold mailboxes, log files, and printer spools. Mailboxes and log - files can grow to unexpected sizes depending on how many - users exist and how long log files are kept. Most users + 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. - There are a few times that a lot of disk space is + Sometimes, a lot of disk space is required in /var/tmp. When new - software is installed with &man.pkg.add.1; the packaging + 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 @@ -166,8 +167,9 @@ hassle. - Some users have found that &man.sysinstall.8;'s - Auto-defaults partition sizer will + The + Auto-defaults partition sizer used by + &man.sysinstall.8; will sometimes select smaller than adequate /var and / partitions. @@ -182,18 +184,24 @@ swap partition 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 + 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 + 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 + 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 + 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 @@ -219,10 +227,10 @@ 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 + 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. Now while I/O performance in the larger + 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 @@ -283,21 +291,20 @@ ifconfig_fxp0="inet 10.1.1.1/8" - rc.conf can then be - distributed to every system using rsync or a - similar program, while rc.conf.local + 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 - rc.conf, so system configuration + /etc/rc.conf, so system configuration information will not be lost. - The /etc/rc.conf configuration file + The configuration in /etc/rc.conf is parsed by &man.sh.1;. This allows system operators to - add a certain amount of logic to this file, which may help to - create very complex configuration scenarios. Refer to + create complex configuration scenarios. Refer to &man.rc.conf.5; for further information on this topic. @@ -320,10 +327,11 @@ ifconfig_fxp0="inet 10.1.1.1/8"Normally, when a port or package is installed, sample configuration files are also installed. These are usually - identified with a .default suffix. If + identified with a suffix such as .sample. + If there are no existing configuration files for the application, - they will be created by copying the - .default files. + they can be created by copying the + sample files. For example, consider the contents of the directory Now that &os; includes rc.d, configuration of application startup is easier and provides - more features. Using the key words discussed in the - rc.d section, + 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 @@ -411,47 +419,43 @@ pidfile=${utility_pidfile-"/var/run/util run_rc_command "$1" This script will ensure that the provided - utility will be started after the + utility will be started after the DAEMON pseudo-service. It also provides a - method for setting and tracking the PID, or - process ID file. + method for setting and tracking the process ID + (PID). This application could then have the following line placed in /etc/rc.conf: utility_enable="YES" - This method also allows for easier manipulation of the + This method allows for easier manipulation of command line arguments, inclusion of the default functions provided in /etc/rc.subr, compatibility - with the &man.rcorder.8; utility and provides for easier + with &man.rcorder.8;, and provides for easier configuration via rc.conf. Using Services to Start Services - Other services, such as the POP3 server - daemons or IMAP, could be started using - &man.inetd.8;. This involves installing the service utility - from the Ports Collection with a configuration line added to - /etc/inetd.conf, or by - uncommenting one of the current configuration lines. Working - with inetd and its configuration is - described in depth in the - inetd section. - - In some cases it may make more sense to use the - &man.cron.8; daemon to start system services. This approach - has a number of advantages because cron - runs these processes as the crontab's - file owner. This allows regular users to start and maintain - some applications. - - The cron utility provides a unique - feature, @reboot, which may be used in - place of the time specification. This will cause the job to - be run when &man.cron.8; is started, normally during system + 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 + 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. @@ -467,7 +471,7 @@ run_rc_command "$1" - Configuring the <command>cron</command> Utility + Configuring &man.cron.8; cron configuration @@ -477,15 +481,15 @@ run_rc_command "$1" /etc/crontab for tasks to execute and searches /var/cron/tabs for custom - crontab files. These files store + &man.crontab.5; files. These files store information about specific functions which - cron is supposed to perform at certain + &man.cron.8; is supposed to perform at certain times. - The cron utility uses two different types - of configuration files, the system crontab and user crontabs. + 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, cron will run the command as + 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. @@ -499,29 +503,27 @@ run_rc_command "$1" The root user can have a user crontab just like any other user. The root user - crontab is separate from /etc/crontab - (the system crontab). Because the system crontab effectively - invokes the specified commands as root there is usually no + 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. - Let us take a look at /etc/crontab, - the system crontab: + Here is a sample entry from /etc/crontab: - # /etc/crontab - root's crontab for &os; + # /etc/crontab - root's crontab for FreeBSD # -# $&os;: src/etc/crontab,v 1.32 2002/11/22 16:13:39 tom Exp $ +# $FreeBSD$ # # SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin -HOME=/var/log -# # #minute hour mday month wday who command # -# */5 * * * * root /usr/libexec/atrun @@ -536,52 +538,51 @@ HOME=/var/log - First, the environment must be defined. The equals + The equals (=) character is used to define any - environment settings, as with this example where it is used - for the SHELL, PATH, and - HOME options. If the shell line is omitted, - cron will use the default, which is - sh. If the PATH variable + 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. If HOME is omitted, - cron will use the invoking users home - directory. + need to be absolute. - This line defines a total of seven fields. Listed here - are the values minute, + This line defines a total of seven fields: + minute, hour, mday, month, wday, who, and command. These are almost all self explanatory. - minute is the time in minutes the command - will be run. hour is similar to the - minute option, just in hours. - mday stands for day of the month. - month is similar to - hour and minute, as it + minute is the time in minutes when the + 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. All these fields must be - numeric values, and follow the twenty-four hour clock. The - who field is special, and only exists in - /etc/crontab. This field specifies + 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. - This last line will define the values discussed above. + This last line defines the values discussed above. This example has a */5 listing,followed by several more * characters. These * characters mean first-last, and can be interpreted as every time. In this example, - atrun is invoked by - root every five minutes regardless of - the day or month. For more information on - atrun, refer to &man.atrun.8;. + &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 +592,10 @@ HOME=/var/log This is the basic setup for every - crontab, although there is one thing - different about this one. Field number six, which specifies + &man.crontab.5;. However, field number six, which specifies the username, only exists in the system - crontab. This field should be omitted for - individual user crontab files. + &man.crontab.5;. This field should be omitted for + individual user &man.crontab.5; files. Installing a Crontab @@ -604,7 +604,7 @@ HOME=/var/log Do not use the procedure described here to edit and install the system crontab, /etc/crontab. Instead, use an - editor: cron will notice that the file + editor and &man.cron.8; will notice that the file has changed and immediately begin using the updated version. See @@ -612,27 +612,27 @@ HOME=/var/log To install a freshly written user - crontab, first use an editor to create + &man.crontab.5;, use an editor to create and save a file in the proper format. Then, specify the file - name with crontab: + name with &man.crontab.1;: &prompt.user; crontab crontab-file In this example, crontab-file is the - filename of a crontab that was previously + filename of a &man.crontab.5; that was previously created. - To list installed crontab files, pass - to crontab. + To list installed &man.crontab.5; files, pass + to &man.crontab.1;. - For users who wish to begin their own crontab file from - scratch, without the use of a template, the - crontab -e option is available. This will - invoke the selected editor with an empty file. When the file + 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 - crontab. + &man.crontab.1;. - In order to remove a user crontab + In order to remove a user &man.crontab.5; completely, use crontab -r. @@ -651,105 +651,112 @@ HOME=/var/log Using &man.rc.8; Under &os; - In 2002 &os; integrated the NetBSD rc.d - system for system initialization. Users should notice the files - listed in the /etc/rc.d - directory. Many of these files are for basic services which can + 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. + , and options + to &man.service.8;. For instance, &man.sshd.8; can be restarted with the following command: &prompt.root; service sshd restart - This procedure is similar for other services. Of course, - services are usually started automatically at boot time as - specified in &man.rc.conf.5;. For example, enabling the Network - Address Translation daemon at startup is as simple as adding the + 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: natd_enable="YES" If a line is already - present, then simply change the to - . The rc scripts will automatically load - any other dependent services during the next reboot, as + 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 rc.d system is primarily - intended to start/stop services at system startup/shutdown time, - the standard , and + 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 variables - are set. For instance, sshd restart will + 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, the commands should be + /etc/rc.conf, these commands should be prefixed with one. For instance, to restart - sshd regardless of the current + &man.sshd.8; regardless of the current /etc/rc.conf setting, execute the following command: &prompt.root; service sshd onerestart - It is easy to check if a service is enabled in - /etc/rc.conf by running the appropriate - rc.d script with the option - . Thus, an administrator can check that - sshd is in fact enabled in - /etc/rc.conf by running: + 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 + /etc/rc.conf: &prompt.root; service sshd rcvar # sshd $sshd_enable=YES - The second line (# sshd) is the output - from sshd, not a + The # sshd line is output from the + above command, + not a root console. To determine whether or not a service is running, use . For instance, to verify that - sshd is running: + &man.sshd.8; is running: &prompt.root; service sshd status sshd is running as pid 433. - In some cases it is also possible to - a service. This will attempt to send a signal to an individual + 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 + In most cases, this means sending the service a SIGHUP signal. Support for this feature is not included for every service. - The rc.d system is not only used for - network services, it also contributes to most of the system + The &man.rc.8; system is used for + network services and it also contributes to most of the system initialization. For instance, when the - bgfsck script is executed, it will print + /etc/rc.d/bgfsck script is executed, it + prints out the following message: Starting background file system checks in 60 seconds. - Therefore this file is used for background file system - checks, which are done 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, NIS and other RPC-based services may - fail to start until after the rpcbind - (portmapper) service has started. To resolve this issue, + 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 then used to parse these comments + &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 words must be included in all startup scripts - (they are 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: @@ -758,34 +765,36 @@ sshd is running as pid 433. - The following words may be included at the top of each - startup file. They are not strictly necessary, but they are + The following key words may be included at the top of each + startup script. They are not strictly necessary, but are useful as hints to &man.rcorder.8;: REQUIRE: Lists services which are - required for this service. This file will run + required for this service. The script containing this key + word will run after the specified services. BEFORE: Lists services which depend - on this service. This file will run + on this service. The script containing this key word will + run before the specified services. By carefully setting these keywords for each startup script, - an administrator has a very fine-grained level of control of the - startup order of the scripts, without the hassle of - runlevels like some other &unix; operating + an administrator has a fine-grained level of control of the + startup order of the scripts, without the need for + runlevels used by some &unix; operating systems. - Additional information about the rc.d - system can be found in &man.rc.8; and &man.rc.subr.8;. Refer to + 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 rc.d + instructions on how to create custom &man.rc.8; scripts. @@ -808,7 +817,8 @@ sshd is running as pid 433. configuration - Adding and configuring a network card is a common task for + Adding and configuring a network interface card + (NIC) is a common task for any &os; administrator. @@ -819,24 +829,31 @@ sshd is running as pid 433. driver - First, determine the model of the network interface card - and the chip it uses. &os; supports a wide variety of network - interface cards. Check the Hardware Compatibility List for - the &os; release to see if the card is supported. - - If the card is supported, determine the name of the &os; - driver for the card. Refer to + 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. + + If the NIC is supported, determine + 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 network interface drivers with some + for the list of NIC drivers with some information about the supported chipsets. When in doubt, read the manual page of the driver as it will provide more information about the supported hardware and any known limitations of the driver. - The drivers for common network cards are already present - in the GENERIC kernel, meaning the card - should show up during boot, as in this example: + 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: dc0: <82c169 PNIC 10/100BaseTX> port 0xa000-0xa0ff mem 0xd3800000-0xd38 000ff irq 15 at device 11.0 on pci0 @@ -853,52 +870,51 @@ bmtphy1: 10baseT, 10baseT-FDX, 100baseT dc1: Ethernet address: 00:a0:cc:da:da:db dc1: [ITHREAD] - In this example, two cards using the &man.dc.4; driver are - present on the system. - - If the driver for the interface is not present in + 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 interface can be + 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 - network card with &man.kldload.8;. To also automatically + NIC using &man.kldload.8;. To also + automatically load the driver at boot time, add the appropriate line to - /boot/loader.conf. Not all NIC - drivers are available as modules; notable examples of - devices for which modules do not exist are ISA - cards. + /boot/loader.conf. Not all + NIC + drivers are available as modules. - Alternatively, statically compile support for the card + Alternatively, statically compile support for the + 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 card was detected + . If the + NIC was detected at boot, the kernel does not need to be recompiled. - Using &windows; NDIS Drivers + Using &windows; <acronym>NDIS</acronym> Drivers - NDIS + NDIS NDISulator &windows; drivers - Microsoft Windows - - Microsoft Windows - device drivers + µsoft.windows; + device drivers - KLD (kernel loadable object) + KLD (kernel loadable object) provide schematics for their drivers to the open source community because they regard such information as trade secrets. Consequently, the developers of &os; and other - operating systems are left two choices: develop the drivers + 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 the - µsoft.windows; platforms. Most developers, including - those involved with &os;, have taken the latter - approach. - - Thanks to the contributions of Bill Paul (wpaul) there - is native support for the Network Driver - Interface Specification (NDIS). The &os; NDISulator - (otherwise known as Project Evil) takes a &windows; driver - binary and basically tricks it into thinking it is running - on &windows;. Because the &man.ndis.4; driver is using a - &windows; binary, it only runs on &i386; and amd64 systems. - PCI, CardBus, PCMCIA (PC-Card), and USB devices are + 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 the NDISulator, three things are needed: + To use &man.ndisgen.8;, three things are needed: - Kernel sources + &os; kernel sources. - &windowsxp; driver binary - (.SYS extension) + A &windowsxp; driver binary with a + .SYS extension. - &windowsxp; driver configuration file - (.INF extension) + A &windowsxp; driver configuration file with a + .INF extension. - Locate the files for the specific card. Generally, - they can be found on the included CDs or at the vendor's + 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 W32DRIVER.INF. @@ -959,8 +980,9 @@ linuxemu/chapter.xml --> &prompt.root; ndisgen /path/to/W32DRIVER.INF /path/to/W32DRIVER.SYS - &man.ndisgen.8; is interactive and prompts for any extra - information it requires. A new kernel module is written in + 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: @@ -976,12 +998,13 @@ linuxemu/chapter.xml --> &prompt.root; kldload ndis &prompt.root; kldload if_ndis - The first command loads the NDIS miniport driver - wrapper, the second loads the actual network - interface. + The first command loads the &man.ndis.4; + miniport driver + wrapper and the second loads the generated NIC + driver. - Now, check &man.dmesg.8; to see if there were any errors - loading. 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 @@ -990,14 +1013,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 you can treat the - ndis0 device like any other network - interface (e.g., dc0). + From here, + ndis0 can be configured like any other + NIC. - To configure the system to load the NDIS modules at + To configure the system to load the &man.ndis.4; modules at boot time, copy the generated module, - W32DRIVER_SYS.ko, to the /boot/modules directory. Then, + W32DRIVER_SYS.ko, to /boot/modules. Then, add the following line to /boot/loader.conf: @@ -1013,12 +1036,13 @@ ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18M configuration - Once the right driver is loaded for the network card, the - card needs to be configured. As with many other things, the - network card may have been configured at installation time by - sysinstall. + Once the right driver is loaded for the + NIC, the + card needs to be configured. It + may have been configured at installation time by + &man.sysinstall.8;. - To display the configuration for the network interfaces, + To display the NIC configuration, enter the following command: &prompt.user; ifconfig @@ -1047,27 +1071,29 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M dc0: The first Ethernet - interface + interface. dc1: The second Ethernet - interface + interface. lo0: The loopback - device + device. &os; uses the driver name followed by the order in which - one the card is detected at the kernel boot to name the - network card. For example sis2 would - be the third network card on the system using the &man.sis.4; + 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; driver. - In this example, the dc0 device + In this example, dc0 is up and running. The key indicators are: @@ -1078,32 +1104,33 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M The card has an Internet (inet) - address (in this case - 192.168.1.3). + address, + 192.168.1.3. It has a valid subnet mask - (netmask; + (netmask), where 0xffffff00 is the same as - 255.255.255.0). + 255.255.255.0. - It has a valid broadcast address (in this case, - 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 + The MAC address of the card + (ether) + is 00:a0:cc:da:da:da. The physical media selection is on autoselection mode (media: Ethernet autoselect (100baseTX <full-duplex>)). In this example, - dc1 was configured to run with + dc1 is configured to run with 10baseT/UTP media. For more information on available media types for a driver, refer to its manual page. @@ -1130,39 +1157,44 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M it would indicate the card has not been configured. - To configure the card, you will need - root privileges. The network card + The card must be configured as + root. The NIC *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-projects@FreeBSD.ORG Sun May 12 15:15:21 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 A408F7B1; Sun, 12 May 2013 15:15:21 +0000 (UTC) (envelope-from gjb@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 96E29F4F; Sun, 12 May 2013 15:15:21 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4CFFLes052393; Sun, 12 May 2013 15:15:21 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4CFFLiM052392; Sun, 12 May 2013 15:15:21 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201305121515.r4CFFLiM052392@svn.freebsd.org> From: Glen Barber Date: Sun, 12 May 2013 15:15:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41608 - 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 15:15:21 -0000 Author: gjb Date: Sun May 12 15:15:20 2013 New Revision: 41608 URL: http://svnweb.freebsd.org/changeset/doc/41608 Log: Fix index generation (I think...). 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 13:19:04 2013 (r41607) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml Sun May 12 15:15:20 2013 (r41608) @@ -910,8 +910,8 @@ dc1: [ITHREAD] NDIS NDISulator &windows; drivers - µsoft.windows; - device drivers + µsoft.windows; + device drivers KLD (kernel loadable object) From owner-svn-doc-projects@FreeBSD.ORG Sun May 12 15:28:17 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 E8E5FBAE; Sun, 12 May 2013 15:28:17 +0000 (UTC) (envelope-from gjb@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 DB5F6FB9; Sun, 12 May 2013 15:28:17 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4CFSHVe056341; Sun, 12 May 2013 15:28:17 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4CFSHl0056340; Sun, 12 May 2013 15:28:17 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201305121528.r4CFSHl0056340@svn.freebsd.org> From: Glen Barber Date: Sun, 12 May 2013 15:28:17 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41609 - 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 15:28:18 -0000 Author: gjb Date: Sun May 12 15:28:17 2013 New Revision: 41609 URL: http://svnweb.freebsd.org/changeset/doc/41609 Log: Fix whitespace nit from previous commit. 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 15:15:20 2013 (r41608) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml Sun May 12 15:28:17 2013 (r41609) @@ -911,7 +911,7 @@ dc1: [ITHREAD] NDISulator &windows; drivers µsoft.windows; - device drivers + device drivers KLD (kernel loadable object) From owner-svn-doc-projects@FreeBSD.ORG Sun May 12 17:36:00 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CA6D24C7; Sun, 12 May 2013 17:36:00 +0000 (UTC) (envelope-from gabor@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 BD0235EA; Sun, 12 May 2013 17:36:00 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4CHa0LR003164; Sun, 12 May 2013 17:36:00 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4CHa0Kc003163; Sun, 12 May 2013 17:36:00 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305121736.r4CHa0Kc003163@svn.freebsd.org> From: Gabor Kovesdan Date: Sun, 12 May 2013 17:36:00 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41610 - projects/xml-tools/share/misc 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 17:36:00 -0000 Author: gabor Date: Sun May 12 17:36:00 2013 New Revision: 41610 URL: http://svnweb.freebsd.org/changeset/doc/41610 Log: - Readjust styling for some recent changes Modified: projects/xml-tools/share/misc/docbook.css Modified: projects/xml-tools/share/misc/docbook.css ============================================================================== --- projects/xml-tools/share/misc/docbook.css Sun May 12 15:28:17 2013 (r41609) +++ projects/xml-tools/share/misc/docbook.css Sun May 12 17:36:00 2013 (r41610) @@ -145,12 +145,15 @@ div.procedure p b { } h1.title, h2.title, h3.title, h4.title, h5.title, h6.title, -h3.author, .corpauthor, .abstract p.title, -div.toc p:first-child, -div.list-of-figures p:first-child, -div.list-of-tables p:first-child, -div.list-of-examples p:first-child { +h3.author, .corpauthor, +div.abstract div.abstract-title, +div.toc div.toc-title, +div.list-of-figures div.toc-title, +div.list-of-tables div.toc-title, +div.list-of-examples div.toc-title { + font-weight: bold; line-height: 1.3; + margin-top: 1em; margin-left: 0; color: #990000; } From owner-svn-doc-projects@FreeBSD.ORG Sun May 12 17:36:38 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 92947506; Sun, 12 May 2013 17:36:38 +0000 (UTC) (envelope-from gabor@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 848E25ED; Sun, 12 May 2013 17:36:38 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4CHacr7003316; Sun, 12 May 2013 17:36:38 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4CHaccw003315; Sun, 12 May 2013 17:36:38 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305121736.r4CHaccw003315@svn.freebsd.org> From: Gabor Kovesdan Date: Sun, 12 May 2013 17:36:38 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41611 - projects/xml-tools/share/xml 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 17:36:38 -0000 Author: gabor Date: Sun May 12 17:36:38 2013 New Revision: 41611 URL: http://svnweb.freebsd.org/changeset/doc/41611 Log: - Add title to legalnotices, which changes the link name pointing to them Modified: projects/xml-tools/share/xml/trademarks.ent Modified: projects/xml-tools/share/xml/trademarks.ent ============================================================================== --- projects/xml-tools/share/xml/trademarks.ent Sun May 12 17:36:00 2013 (r41610) +++ projects/xml-tools/share/xml/trademarks.ent Sun May 12 17:36:38 2013 (r41611) @@ -426,6 +426,8 @@ Coverity, Inc."> + Copyright + Redistribution and use in source (XML DocBook) and 'compiled' forms (XML, HTML, PDF, PostScript, RTF and so forth) with or without modification, are permitted provided that the following conditions are @@ -466,6 +468,7 @@ Coverity, Inc."> + Legal Notice FreeBSD is a registered trademark of The FreeBSD Foundation. From owner-svn-doc-projects@FreeBSD.ORG Sun May 12 17:37:11 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6AC7B544; Sun, 12 May 2013 17:37:11 +0000 (UTC) (envelope-from gabor@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 5DA415F0; Sun, 12 May 2013 17:37:11 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4CHbBd2003450; Sun, 12 May 2013 17:37:11 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4CHbBYR003449; Sun, 12 May 2013 17:37:11 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305121737.r4CHbBYR003449@svn.freebsd.org> From: Gabor Kovesdan Date: Sun, 12 May 2013 17:37:11 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41612 - projects/xml-tools/share/xsl 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 17:37:11 -0000 Author: gabor Date: Sun May 12 17:37:10 2013 New Revision: 41612 URL: http://svnweb.freebsd.org/changeset/doc/41612 Log: - Do not render userinput with bold Modified: projects/xml-tools/share/xsl/freebsd-common.xsl Modified: projects/xml-tools/share/xsl/freebsd-common.xsl ============================================================================== --- projects/xml-tools/share/xsl/freebsd-common.xsl Sun May 12 17:36:38 2013 (r41611) +++ projects/xml-tools/share/xsl/freebsd-common.xsl Sun May 12 17:37:10 2013 (r41612) @@ -12,6 +12,10 @@ + + + + From owner-svn-doc-projects@FreeBSD.ORG Sun May 12 17:37:58 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9C99B593; Sun, 12 May 2013 17:37:58 +0000 (UTC) (envelope-from gabor@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 75D8D5FB; Sun, 12 May 2013 17:37:58 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4CHbwab003607; Sun, 12 May 2013 17:37:58 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4CHbwYf003606; Sun, 12 May 2013 17:37:58 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305121737.r4CHbwYf003606@svn.freebsd.org> From: Gabor Kovesdan Date: Sun, 12 May 2013 17:37:58 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41613 - projects/xml-tools/share/xsl 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 17:37:58 -0000 Author: gabor Date: Sun May 12 17:37:57 2013 New Revision: 41613 URL: http://svnweb.freebsd.org/changeset/doc/41613 Log: - Add a doc format navigation at the end of the titlepage as we used to have Modified: projects/xml-tools/share/xsl/freebsd-xhtml-common.xsl Modified: projects/xml-tools/share/xsl/freebsd-xhtml-common.xsl ============================================================================== --- projects/xml-tools/share/xsl/freebsd-xhtml-common.xsl Sun May 12 17:37:10 2013 (r41612) +++ projects/xml-tools/share/xsl/freebsd-xhtml-common.xsl Sun May 12 17:37:57 2013 (r41613) @@ -10,10 +10,10 @@ exclude-result-prefixes="#default"> - + - + @@ -49,6 +49,20 @@ For questions about this documentation, e-mail <doc@FreeBSD.org>.

+ + + + book.html + article.html + + + +
+ [ Split HTML / + Single HTML ] +
+
+ @@ -284,4 +298,11 @@ . + + + + + +
+
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 *** From owner-svn-doc-projects@FreeBSD.ORG Mon May 13 16:51:51 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B7783435; Mon, 13 May 2013 16:51:51 +0000 (UTC) (envelope-from gabor@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 A9B66894; Mon, 13 May 2013 16:51:51 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4DGpp0V099678; Mon, 13 May 2013 16:51:51 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4DGpp30099677; Mon, 13 May 2013 16:51:51 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305131651.r4DGpp30099677@svn.freebsd.org> From: Gabor Kovesdan Date: Mon, 13 May 2013 16:51:51 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41626 - projects/xml-tools/share/misc 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: Mon, 13 May 2013 16:51:51 -0000 Author: gabor Date: Mon May 13 16:51:51 2013 New Revision: 41626 URL: http://svnweb.freebsd.org/changeset/doc/41626 Log: - Add a boxed formatting for procedure descriptions Modified: projects/xml-tools/share/misc/docbook.css Modified: projects/xml-tools/share/misc/docbook.css ============================================================================== --- projects/xml-tools/share/misc/docbook.css Mon May 13 14:56:33 2013 (r41625) +++ projects/xml-tools/share/misc/docbook.css Mon May 13 16:51:51 2013 (r41626) @@ -259,14 +259,14 @@ div.programlisting { text-align: left; } -.note, .tip, .important, .warning, .caution, .example { +.note, .tip, .important, .warning, .caution, .example, div.procedure { border-radius: 6px; padding: 2ex 2ex; margin: .75em 3em .75em 3em; line-height: 1.3; } -.note { +.note, div.procedure { color: #222; background: #eee; border: 1px solid #ccc; @@ -314,6 +314,12 @@ div.programlisting { margin-right: 0; } +.procedure-title { + font-weight: bold; + line-height: 1; + margin-right: 0; +} + .note p, .tip p, .important p, .warning p, .caution p, .example p { display: inline; } @@ -331,6 +337,10 @@ div.programlisting { font-weight: bold; } +.userinput { + font-weight: normal; +} + pre.screen strong { font-weight: normal; } From owner-svn-doc-projects@FreeBSD.ORG Mon May 13 16:52:32 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 D125D48C; Mon, 13 May 2013 16:52:32 +0000 (UTC) (envelope-from gabor@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 C36528A3; Mon, 13 May 2013 16:52:32 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4DGqWrX099838; Mon, 13 May 2013 16:52:32 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4DGqWn4099837; Mon, 13 May 2013 16:52:32 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305131652.r4DGqWn4099837@svn.freebsd.org> From: Gabor Kovesdan Date: Mon, 13 May 2013 16:52:32 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41627 - projects/xml-tools/share/xsl 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: Mon, 13 May 2013 16:52:32 -0000 Author: gabor Date: Mon May 13 16:52:32 2013 New Revision: 41627 URL: http://svnweb.freebsd.org/changeset/doc/41627 Log: - Do not render commands in bold - Merge two patterns Modified: projects/xml-tools/share/xsl/freebsd-common.xsl Modified: projects/xml-tools/share/xsl/freebsd-common.xsl ============================================================================== --- projects/xml-tools/share/xsl/freebsd-common.xsl Mon May 13 16:51:51 2013 (r41626) +++ projects/xml-tools/share/xsl/freebsd-common.xsl Mon May 13 16:52:32 2013 (r41627) @@ -8,11 +8,7 @@ - - - - - + From owner-svn-doc-projects@FreeBSD.ORG Wed May 15 13:40:07 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 705AD285; Wed, 15 May 2013 13:40:07 +0000 (UTC) (envelope-from gabor@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 62A6EE68; Wed, 15 May 2013 13:40:07 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4FDe7oR043551; Wed, 15 May 2013 13:40:07 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4FDe71j043550; Wed, 15 May 2013 13:40:07 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305151340.r4FDe71j043550@svn.freebsd.org> From: Gabor Kovesdan Date: Wed, 15 May 2013 13:40:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41629 - projects/xml-tools/share/mk 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: Wed, 15 May 2013 13:40:07 -0000 Author: gabor Date: Wed May 15 13:40:06 2013 New Revision: 41629 URL: http://svnweb.freebsd.org/changeset/doc/41629 Log: - The old LANGCODE detection was bogus and did not work properly with release notes. Use a different approach that works. Modified: projects/xml-tools/share/mk/doc.common.mk Modified: projects/xml-tools/share/mk/doc.common.mk ============================================================================== --- projects/xml-tools/share/mk/doc.common.mk Tue May 14 14:06:32 2013 (r41628) +++ projects/xml-tools/share/mk/doc.common.mk Wed May 15 13:40:06 2013 (r41629) @@ -20,20 +20,8 @@ DOC_PREFIX_NAME?= head .endif .if (!defined(LANGCODE) || empty(LANGCODE)) -# Calculate _LANGCODE. -_LANGCODE:= ${.CURDIR} -. for _ in 1 2 3 4 5 6 7 8 9 10 -. if !(${_LANGCODE:H:T} == ${DOC_PREFIX_NAME}) -_LANGCODE:= ${_LANGCODE:H} -. endif -. endfor -_LANGCODE:= ${_LANGCODE:T} -.else # (!defined(LANGCODE) || empty(LANGCODE)) -# when LANGCODE is defined, use the value. -_LANGCODE?= ${LANGCODE} -.endif # (!defined(LANGCODE) || empty(LANGCODE)) - -LANGCODE?= ${_LANGCODE} +LANGCODE!= echo ${.CURDIR} | grep -o '[a-z]*_[A-Z]*\.[-A-Za-z0-9]*' || true +.endif # normalize DOC_PREFIX DOC_PREFIX!= ${REALPATH} ${DOC_PREFIX} From owner-svn-doc-projects@FreeBSD.ORG Wed May 15 13:40:52 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 13A50314; Wed, 15 May 2013 13:40:52 +0000 (UTC) (envelope-from gabor@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 06F9FE7E; Wed, 15 May 2013 13:40:52 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4FDepmX045126; Wed, 15 May 2013 13:40:51 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4FDepMN045125; Wed, 15 May 2013 13:40:51 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305151340.r4FDepMN045125@svn.freebsd.org> From: Gabor Kovesdan Date: Wed, 15 May 2013 13:40:51 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41630 - projects/xml-tools/share/mk 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: Wed, 15 May 2013 13:40:52 -0000 Author: gabor Date: Wed May 15 13:40:51 2013 New Revision: 41630 URL: http://svnweb.freebsd.org/changeset/doc/41630 Log: - Properly support EXTRA_CATALOGS (they are now XML catalogs) Modified: projects/xml-tools/share/mk/doc.xml.mk Modified: projects/xml-tools/share/mk/doc.xml.mk ============================================================================== --- projects/xml-tools/share/mk/doc.xml.mk Wed May 15 13:40:06 2013 (r41629) +++ projects/xml-tools/share/mk/doc.xml.mk Wed May 15 13:40:51 2013 (r41630) @@ -6,6 +6,9 @@ XML_CATALOG_FILES= file://${.OBJDIR}/cat file://${DOC_PREFIX}/share/xml/catalog.xml \ file://${DOC_PREFIX}/share/xml/catalog-common.xml \ file://${LOCALBASE}/share/xml/catalog +.if defined(EXTRA_CATALOGS) +XML_CATALOG_FILES+= ${EXTRA_CATALOGS} +.endif .if exists(${DOC_PREFIX}/share/xml/catalog-cwd.xml) XML_CATALOG_CWD= ${DOC_PREFIX}/share/xml/catalog-cwd.xml From owner-svn-doc-projects@FreeBSD.ORG Wed May 15 13:42:25 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 CDC4D4AC; Wed, 15 May 2013 13:42:25 +0000 (UTC) (envelope-from gabor@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 C15EAE9A; Wed, 15 May 2013 13:42:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4FDgP4O045574; Wed, 15 May 2013 13:42:25 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4FDgP9T045572; Wed, 15 May 2013 13:42:25 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305151342.r4FDgP9T045572@svn.freebsd.org> From: Gabor Kovesdan Date: Wed, 15 May 2013 13:42:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41631 - projects/xml-tools/share/xml 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: Wed, 15 May 2013 13:42:25 -0000 Author: gabor Date: Wed May 15 13:42:25 2013 New Revision: 41631 URL: http://svnweb.freebsd.org/changeset/doc/41631 Log: - Add a releasetype profiling attribute that will be used in the release notes to avoid the ugly workaround of that parameter entities can only be used in DTD subset now. Modified: projects/xml-tools/share/xml/freebsd45.dtd Modified: projects/xml-tools/share/xml/freebsd45.dtd ============================================================================== --- projects/xml-tools/share/xml/freebsd45.dtd Wed May 15 13:40:51 2013 (r41630) +++ projects/xml-tools/share/xml/freebsd45.dtd Wed May 15 13:42:25 2013 (r41631) @@ -32,7 +32,11 @@ - + + + From owner-svn-doc-projects@FreeBSD.ORG Wed May 15 14:07:05 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 1398FCCF; Wed, 15 May 2013 14:07:05 +0000 (UTC) (envelope-from gabor@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 038DEAC; Wed, 15 May 2013 14:07:05 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4FE74ch053784; Wed, 15 May 2013 14:07:04 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4FE72ec053763; Wed, 15 May 2013 14:07:02 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305151407.r4FE72ec053763@svn.freebsd.org> From: Gabor Kovesdan Date: Wed, 15 May 2013 14:07:02 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41632 - in projects/xml-tools: de_DE.ISO8859-1/htdocs/docs de_DE.ISO8859-1/share/xml en_US.ISO8859-1/articles/contributors en_US.ISO8859-1/articles/mailing-list-faq en_US.ISO8859-1/art... 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: Wed, 15 May 2013 14:07:05 -0000 Author: gabor Date: Wed May 15 14:07:01 2013 New Revision: 41632 URL: http://svnweb.freebsd.org/changeset/doc/41632 Log: - MFH Added: projects/xml-tools/en_US.ISO8859-1/htdocs/news/status/report-2013-01-2013-03.xml - copied unchanged from r41631, head/en_US.ISO8859-1/htdocs/news/status/report-2013-01-2013-03.xml Deleted: projects/xml-tools/en_US.ISO8859-1/htdocs/docproj/sgml.xml projects/xml-tools/ja_JP.eucJP/htdocs/docproj/sgml.xml Modified: projects/xml-tools/de_DE.ISO8859-1/htdocs/docs/books.xml projects/xml-tools/de_DE.ISO8859-1/share/xml/news.xml projects/xml-tools/en_US.ISO8859-1/articles/contributors/contrib.additional.xml projects/xml-tools/en_US.ISO8859-1/articles/mailing-list-faq/article.xml projects/xml-tools/en_US.ISO8859-1/articles/new-users/article.xml projects/xml-tools/en_US.ISO8859-1/books/faq/book.xml projects/xml-tools/en_US.ISO8859-1/htdocs/community/irc.xml projects/xml-tools/en_US.ISO8859-1/htdocs/community/webresources.xml projects/xml-tools/en_US.ISO8859-1/htdocs/docproj/Makefile projects/xml-tools/en_US.ISO8859-1/htdocs/docproj/docproj.xml projects/xml-tools/en_US.ISO8859-1/htdocs/features.xml projects/xml-tools/en_US.ISO8859-1/htdocs/news/status/Makefile projects/xml-tools/en_US.ISO8859-1/htdocs/news/status/status.xml projects/xml-tools/en_US.ISO8859-1/htdocs/releases/8.4R/schedule.xml projects/xml-tools/en_US.ISO8859-1/htdocs/releases/index.xml projects/xml-tools/en_US.ISO8859-1/htdocs/releng/index.xml projects/xml-tools/en_US.ISO8859-1/htdocs/security/security.xml projects/xml-tools/ja_JP.eucJP/books/handbook/users/chapter.xml projects/xml-tools/ja_JP.eucJP/htdocs/community/webresources.xml projects/xml-tools/ja_JP.eucJP/htdocs/docproj/Makefile projects/xml-tools/ja_JP.eucJP/htdocs/docproj/docproj.xml projects/xml-tools/ja_JP.eucJP/htdocs/java/index.xml projects/xml-tools/ja_JP.eucJP/htdocs/java/news.xml projects/xml-tools/ja_JP.eucJP/htdocs/releases/index.xml projects/xml-tools/ja_JP.eucJP/htdocs/security/security.xml projects/xml-tools/ja_JP.eucJP/share/xml/news.xml projects/xml-tools/nl_NL.ISO8859-1/articles/Makefile projects/xml-tools/nl_NL.ISO8859-1/books/handbook/book.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/jails/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/mirrors/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/pgpkeys/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/security/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/books/handbook/x11/chapter.xml projects/xml-tools/nl_NL.ISO8859-1/htdocs/administration.xml projects/xml-tools/nl_NL.ISO8859-1/htdocs/features.xml projects/xml-tools/nl_NL.ISO8859-1/htdocs/where.xml projects/xml-tools/nl_NL.ISO8859-1/share/xml/mailing-lists.ent projects/xml-tools/nl_NL.ISO8859-1/share/xml/navibar.l10n.ent projects/xml-tools/ru_RU.KOI8-R/articles/mailing-list-faq/Makefile projects/xml-tools/ru_RU.KOI8-R/articles/mailing-list-faq/article.xml projects/xml-tools/ru_RU.KOI8-R/articles/new-users/Makefile projects/xml-tools/ru_RU.KOI8-R/articles/new-users/article.xml projects/xml-tools/share/xml/commercial.isp.xml projects/xml-tools/share/xml/mirrors.xml projects/xml-tools/share/xml/news.xml projects/xml-tools/share/xml/release.ent Directory Properties: projects/xml-tools/ (props changed) projects/xml-tools/de_DE.ISO8859-1/ (props changed) projects/xml-tools/en_US.ISO8859-1/ (props changed) projects/xml-tools/ja_JP.eucJP/ (props changed) projects/xml-tools/nl_NL.ISO8859-1/ (props changed) projects/xml-tools/ru_RU.KOI8-R/ (props changed) projects/xml-tools/share/ (props changed) Modified: projects/xml-tools/de_DE.ISO8859-1/htdocs/docs/books.xml ============================================================================== --- projects/xml-tools/de_DE.ISO8859-1/htdocs/docs/books.xml Wed May 15 13:42:25 2013 (r41631) +++ projects/xml-tools/de_DE.ISO8859-1/htdocs/docs/books.xml Wed May 15 14:07:01 2013 (r41632) @@ -161,10 +161,6 @@ CVSROOT-Infrastruktur wie der des FreeBSD Projects einrichtet.

-

CVSup - Advanced Points (cvsup-advanced)
- Ein Artikel, der die Feinheiten von CVSup beschreibt.

-

Hintergrundwissen zu BSD (explaining-bsd)
Eine Antwort auf die Frage: "Was ist BSD?"

@@ -192,7 +188,7 @@ Tipps und Tricks, wie man am besten die gewünschten Informationen von der Mailingliste -questions erhält.

-

Build +

Build Your Own FreeBSD Update Server (freebsd-update-server)
Der Einsatz eines FreeBSD Update-Servers erlaubt es Systemadministratoren, Updates für mehrere Maschinen Modified: projects/xml-tools/de_DE.ISO8859-1/share/xml/news.xml ============================================================================== --- projects/xml-tools/de_DE.ISO8859-1/share/xml/news.xml Wed May 15 13:42:25 2013 (r41631) +++ projects/xml-tools/de_DE.ISO8859-1/share/xml/news.xml Wed May 15 14:07:01 2013 (r41632) @@ -4,7 +4,7 @@ + + + January-March + + 2013 + + +

+ Introduction + +

This report covers &os;-related projects between January and + March 2013. This is the first of four reports planned for 2013.

+ +

Highlights from this status report include the busy preparations + of 8.4-RELEASE, restoration of binary package building, steady + progress of several porting efforts, like work on the &os; ports + of xorg, GNOME, KDE, and Xfce, bringing &os; to Cubieboard and + Hackberry boards, development of ARM and AMD GPU support, + improving performance of UFS/FFS and callouts, and introducing a + multipath TCP implementation for the network stack.

+ +

Thanks to all the reporters for the excellent work! This report + contains 31 entries and we hope you enjoy reading it.

+ +

The deadline for submissions covering the period between April + and June 2013 is July 7th, 2013.

+
+ + + proj + + Projects + + + + team + + &os; Team Reports + + + + kern + + Kernel + + + + docs + + Documentation + + + + arch + + Architectures + + + + ports + + Ports + + + + misc + + Miscellaneous + + + + &os; Core Team + + + + + Core Team + + core@FreeBSD.org + + + + + + +

At the end of 2012, the Core Team approved using Google + Analytics on the Project web site to enable the Documentation + Engineering Team to collect statistics on its usage for better + profiling. In the first quarter of 2013, the Core Team worked + with the Documentation Engineering Team to finalize the + associated policies.

+ +

Due to some debates around the political correctness of quotes + added for the fortune(6) utility, the corresponding data file + has been removed from the base system in -CURRENT.

+ +

In light of the security incident, the liaison role between the + Core Team and the Security Team has been restored, with Gavin + Atkinson assuming this role. The Core Team work hard on + resolving the current situation of the binary package building + cluster and the associated security problems in tight + cooperation with the Ports Management Team, Cluster + Administators, and the &os; Foundation Board. The compromise page + is kept updated on the results.

+ +

The &os; Project submitted an application for Google Summer of + Code this year again.

+ +

There was access granted for 2 new committers and 1 commit bit + was taken for safekeeping in this quarter.

+ +
+ + + &os; Port Managers + + + + + Thomas + Abthorpe + + portmgr-secretary@FreeBSD.org + + + + + Port + Management Team + + portmgr@FreeBSD.org + + + + + + + + + + + + + + +

The ports tree contains approximately 24,300 ports, while the + PR count still is close to 1600.

+ +

In the first quarter we added 4 new committers, took in 1 + commit bit for safe keeping, and re-instated 1 commit bit.

+ +

In February, Mark Linimon (linimon) stepped down from his + duties in the team. Mark had been the longest serving member of + the team. Mark had spent many long hours refactoring and + documenting the portbuild software to ensure that pointyhat + services could be restored.

+ +

After a security review, redports.org was turned back on, + restoring Tinderbox services to contributors, along with post + commit QATs. In addition, pointyhat infrastructure had also + undergone a review and work begain on restoring the package + build system.

+ +

Erwin Lansing (erwin) and Martin Wilke (miwi) took on the + principle roles of getting the portbuild software installed and + running on pointyhat. As a result of all their hard work, + portmgr@ was finally able to resume doing -exp runs, preparing + packages for the upcoming 8.4 release, as well as getting a set + of 9.1 packages retroactively prepared.

+ +

After many long years of being the defacto standard for the + Project, CVS support for the ports tree officially ended on + February 28.

+ +

The ports tree was tagged with RELEASE_7_EOL, to + coincide with the end of life for &os; 7.X.

+ +

Beat Gaetzi (beat) stepped down from his duties on portmgr@ in + March. Among his notable contributions, was the task of migrating + the Ports Tree from the old CVS repo to Subversion.

+ +

Bryan Drewery (bdrewery) joined the Ports Management team in + March, bringing with him his wealth of knowledge and skill from + maintaining portupgrade, portmaster, assisting with pkgng, as + well as co-developing poudriere.

+ + + + Most ports PRs are assigned, we now need to focus on + testing, committing and closing. + +
+ + + The &os; Japanese Documentation Project + + + + + Hiroki + Sato + + hrs@FreeBSD.org + + + + + Ryusuke + Suzuki + + ryusuke@FreeBSD.org + + + + + Japanese &os; Web Page + The &os; Japanese Documentation Project Web Page + + + +

Web page (htdocs): Newsflash and some other updates in + the English version have been translated to keep them up-to-date. + Specifically, the release related contents were updated in this + period.

+ +

Books: &os; Handbook has constantly been updated since the last + report; particularly, "ports", "desktop" section were largely + updated. Some progress has been made in the + "advanced-networking" section, contributed by a new + translator.

+ +

Writing &os; Problem Reports article is now in sync with + the English version.

+ + + + Further translation work of outdated documents in + ja_JP.eucJP subtree. + +
+ + + &os; on Cubieboard + + + + + Ganbold + Tsagaankhuu + + ganbold@FreeBSD.org + + + + + Oleksandr + Tymoshenko + + gonzo@FreeBSD.org + + + + + + +

Initial support of Allwinner A10 SoC is committed to -CURRENT. + &os; is now running on boards such as Cubieboard, Hackberry and + it supports following peripherals:

+ +
    +
  • USB EHCI
  • +
  • GPIO
  • +
+ + + + Get EMAC Ethernet driver working. Need more help from + network driver experts. + Implement more drivers. + +
+ + + Multipath TCP (MPTCP) for &os; + + + + + Nigel + Williams + + njwilliams@swin.edu.au + + + + + Lawrence + Stewart + + lastewart@swin.edu.au + + + + + Grenville + Armitage + + garmitage@swin.edu.au + + + + + + + + + + + +

We have been working to create a BSD-licensed implementation of + Multipath TCP — a set of TCP extensions that allow for + transparent multipath operation with multiple IP addresses as + specified in experimental RFC6824.

+ +

We made our first v0.1 public release on 2013-03-11 and + recently released v0.3 on 2013-04-16. The code is currently + considered to be of alpha quality. We are working towards + pushing the code into a &os; Subversion repository project + branch to continue the on-going development effort in a more + publicly accessible location. As part of this move, we hope to + begin releasing regular snapshot installer ISOs of the MPTCP + project branch courtesy of Hiroki Sato and the allbsd.org daily + snapshot infrastructure.

+ +

We are about to release a CAIA technical report 130424A + entitled Design Overview of Multipath TCP version 0.3 for + &os; 10 on 2013-04-24 which provides a high-level + design and architecture overview of the v0.3 code release.

+ +

Going forward, we expect to continue development and release + additional technical reports and academic papers covering topics + such as performance analysis and multipath congestion + control/scheduling.

+ + + + The code is currently of alpha quality so we welcome all + testing feedback, but please familiarize yourself with the README + file and "Known Limitations" section in particular before + jumping in. + +
+ + + TCP-AO Authentication Option + + + + + André + Oppermann + + andre@FreeBSD.org + + + + + SVN branch + + + +

Work is under way to implement TCP-AO (TCP Authentication + Option) according to RFC5925 and RFC5926. TCP-AO is an + extension to TCP-MD5 signatures commonly used in routers to + secure BGP routing protocol sessions against spoofing attacks. + The work is under contract and sponsored by Juniper + Networks.

+ +
+ + + Atomic "close-on-exec" + + + + + Jilles + Tjoelker + + jilles@FreeBSD.org + + + + + + + + +

If threads or signal handlers call fork() and + exec(), file descriptors may be passed undesirably to + child processes, which may lead to hangs (if a pipe is not + closed), exceeding the file descriptor limit and security + problems (if the child process has lower privilege). One + solution is various new APIs that set the close-on-exec + flag atomically with allocating a file descriptor. Some + existing software will use the new features if present or will + even refuse to compile without them.

+ +

Various parts have been present for some time.

+ +

In first quarter of 2013, extensions to recvmsg(), + socket(), socketpair() and + posix_openpt() have been added.

+ +
+ + + BXR.SU — Super User's BSD Cross Reference + + + + + Constantine A. + Murenin + + cnst++@FreeBSD.org + + + + + BXR.SU — Super User's BSD Cross Reference + + + + +

Super User's BSD Cross Reference (BXR.SU) is a new source-code + search engine that covers the complete kernel and non-GNU + userland source trees of &os;, NetBSD, OpenBSD, and DragonFly + BSD.

+ +

BXR.SU is optimised to be very fast, has daily updates of all + the trees, and also acts as a deterministic URL shortener.

+ +

BXR.SU is based on an OpenGrok fork, but it is more than just + OpenGrok. We have fixed a number of annoyances, eliminated + features that just never worked right from the outright, and + provided integration with tools like CVSweb (including great + mirrors like allbsd.org), &os;'s ViewVC (SVN), as well as GitHub + and Gitweb from git.freebsd.your.org, plus a tad of + other improvements, including a complete rewrite of an mdoc + parser. Last, but definitely not least, is an extensive set of + nginx rewrite rules that makes it a breeze to use BXR.SU as a + deterministic URL compactor for referencing BSD source code. + For example, the http://bxr.su/f/kern/sched_ule.c URL + will automatically redirect to + http://bxr.su/FreeBSD/sys/kern/sched_ule.c through + nginx.

+ +

Note that according to the release schedule of BXR.SU, there is + no IPv4 glue until 2013-04-24; otherwise, the service is available + via both IPv4 and IPv6. See the 2013-04-01 announcement on the + freebsd-hackers mailing list for more details.

+ + + + Find up-to-date git repositories (served with Gitweb) of + NetBSD and OpenBSD. + Find a Gitweb mirror of &os; that is faster than GitHub and + Gitorious. + +
+ + + &os; Postmaster Team + + + + + David + Wolfskill + + postmaster@FreeBSD.org + + + + + + +

In the first quarter of 2013, the &os; Postmaster Team has + implemented the following items that may be interest of the + general public:

+ +
    +
  • Changes in configuration of Mailman-managed lists: allow to + accept the application/pkcs7-signature MIME type (in + addition to the application/x-pkcs7-signature MIME + type), thus permitting S/MIME signatures on list mail.
  • + +
  • New lists: freebsd-ops-announce — + announcements of infrastructure issues, and freebsd-pkg + — discussion of binary package management and package + tools.
  • +
+ +
+ + + &os; Bugmeister Team + + + + + Eitan + Adler + + eadler@FreeBSD.org + + + + + Gavin + Atkinson + + gavin@FreeBSD.org + + + + + Oleksandr + Tymoshenko + + gonzo@FreeBSD.org + + + + + + +

The &os; Bugmeister Team are continuing to evaluate options for + alternate bug trackers and have narrowed their choices to two + possibilities: Bugzilla and roundup.

+ +

The number of non-ports PRs have remained relatively static over + the last three months, with as many coming in as being closed. + The number of ports PRs have increased recently, largely due to + the ports freeze for the upcoming 8.4-RELEASE.

+ +

The Bugmeister team continue work on trying to make the contents + of the GNATS PR database cleaner, more accessible and easier for + committers to find and resolve PRs, by tagging PRs to indicate + the areas involved, and by ensuring that there is sufficient + info within each PR to resolve each issue.

+ +

As always, anybody interested in helping out with the PR queue is + welcome to join us in #freebsd-bugbusters on EFnet. We + are always looking for additional help, whether your interests + lie in triaging incoming PRs, generating patches to resolve + existing problems, or simply helping with the database + housekeeping (identifying duplicate PRs, ones that have already + been resolved, etc). This is a great way of getting more + involved with &os;!

+ + + + Finalize the decision of which new bug tracker to + use. + + Get more users involved with triaging PRs as they come + in. + + Assist committers with closing PRs. + +
+ + + callout(9) Improvements + + + + + Davide + Italiano + + davide@FreeBSD.org + + + + + Alexander + Motin + + mav@FreeBSD.org + + + + + + + + + + +

In &os;, timers are provided by the callout facility, which + allows to register a function with an argument to be called at + specified future time. The subsystem suffered of some problems, + such as the impossibility of handling high-resolution events or + its inherent periodic structure, which may lead to spurious + wakeups and higher power consumption. Some consumers, such as + high-speed networking, VoIP and other real-time applications + need a better precision than the one currently allowed. Also, + especially with the ubiquity of laptops in the last years, the *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-projects@FreeBSD.ORG Fri May 17 16:02:27 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 677F74A6; Fri, 17 May 2013 16:02:27 +0000 (UTC) (envelope-from trhodes@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 497C78DD; Fri, 17 May 2013 16:02:27 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4HG2Q3u014101; Fri, 17 May 2013 16:02:26 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4HG2Qn7014100; Fri, 17 May 2013 16:02:26 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305171602.r4HG2Qn7014100@svn.freebsd.org> From: Tom Rhodes Date: Fri, 17 May 2013 16:02:26 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41639 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac 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: Fri, 17 May 2013 16:02:27 -0000 Author: trhodes Date: Fri May 17 16:02:26 2013 New Revision: 41639 URL: http://svnweb.freebsd.org/changeset/doc/41639 Log: Fix bad titles ( tags) by replacing them with a bullet list containing the procedure items. Done to shut up: bcr Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac/chapter.xml Fri May 17 14:11:38 2013 (r41638) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac/chapter.xml Fri May 17 16:02:26 2013 (r41639) @@ -1807,14 +1807,11 @@ setpmac biba/10\(10-10\) /usr/local/etc/ This section discusses common configuration issues. - - <option>multilabel</option> cannot be enabled on - <filename>/</filename> - - The flag does not stay + + + The flag does not stay enabled on my root (/) partition! - The following steps may resolve this transient error: @@ -1853,12 +1850,9 @@ setpmac biba/10\(10-10\) /usr/local/etc/ root file system. - - - - Xorg Server Will Not Start After - <acronym>MAC</acronym> + + After establishing a secure environment with MAC, I am no longer able to start Xorg! @@ -1892,15 +1886,14 @@ setpmac biba/10\(10-10\) /usr/local/etc/ the &a.questions; mailing list. - + - - Error: &man..secure.path.3; cannot stat - <filename>.login_conf</filename> + + The error: _secure_path: unable to stat .login_conf shows up. When a user attempts to switch from the root user to another user in the system, - the error message _secure_path: unable to state + the error message _secure_path: unable to stat .login_conf appears. This message is usually shown when the user has a higher @@ -1915,10 +1908,11 @@ setpmac biba/10\(10-10\) /usr/local/etc/ the Biba integrity model will not permit root to view objects set at a lower integrity level. - + - - The <username>root</username> username is broken! + + The system no longer recognizes the + root user. In normal or even single user mode, the root is not recognized, @@ -1942,6 +1936,7 @@ setpmac biba/10\(10-10\) /usr/local/etc/ system and access would be blocked as the file has inherited the new label. Disable the policy using &man.sysctl.8; and everything should return to normal. - + + From owner-svn-doc-projects@FreeBSD.ORG Fri May 17 17:26:21 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 5CD19256; Fri, 17 May 2013 17:26:21 +0000 (UTC) (envelope-from trhodes@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 4F4ECCD3; Fri, 17 May 2013 17:26:21 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4HHQLJI042958; Fri, 17 May 2013 17:26:21 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4HHQLwc042957; Fri, 17 May 2013 17:26:21 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305171726.r4HHQLwc042957@svn.freebsd.org> From: Tom Rhodes Date: Fri, 17 May 2013 17:26:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41640 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac 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: Fri, 17 May 2013 17:26:21 -0000 Author: trhodes Date: Fri May 17 17:26:20 2013 New Revision: 41640 URL: http://svnweb.freebsd.org/changeset/doc/41640 Log: Whitespace love after previous commit. Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac/chapter.xml Fri May 17 16:02:26 2013 (r41639) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac/chapter.xml Fri May 17 17:26:20 2013 (r41640) @@ -1809,134 +1809,135 @@ setpmac biba/10\(10-10\) /usr/local/etc/ - The flag does not stay - enabled on my root (/) partition! + The flag does not stay + enabled on my root (/) partition! - The following steps may resolve this transient - error: + The following steps may resolve this transient + error: - - - Edit /etc/fstab and set the root - partition to for read-only. - - - - Reboot into single user mode. - + + + Edit /etc/fstab and set the root + partition to for read-only. + + + + Reboot into single user mode. + - - Run tunefs + - - Reboot the system. - - - - Run mount - / and change the - back to in - /etc/fstab and reboot the system - again. - - - - Double-check the output from - mount to ensure that - has been properly set on the - root file system. - - - - - - After establishing a secure environment with - MAC, I am no longer able to start - Xorg! - - This could be caused by the MAC - partition policy or by a mislabeling in - one of the MAC labeling policies. To - debug, try the following: - - - - Check the error message; if the user is in the - insecure class, the - partition policy may be the culprit. - Try setting the user's class back to the - default class and rebuild the database - with cap_mkdb. If this does not - alleviate the problem, go to step two. - - - - Double-check the label policies. Ensure that the - policies are set correctly for the user, the Xorg - application, and the /dev entries. - - - - If neither of these resolve the problem, send the - error message and a description of the environment to - the &a.questions; mailing list. - - - - - - The error: _secure_path: unable to stat .login_conf shows up. - - When a user attempts to switch from the - root user to another user in the system, - the error message _secure_path: unable to stat + + Reboot the system. + + + + Run mount + / and change the + back to in + /etc/fstab and reboot the system + again. + + + + Double-check the output from + mount to ensure that + has been properly set on the + root file system. + + + + + + After establishing a secure environment with + MAC, I am no longer able to start + Xorg! + + This could be caused by the MAC + partition policy or by a mislabeling in + one of the MAC labeling policies. To + debug, try the following: + + + + Check the error message; if the user is in the + insecure class, the + partition policy may be the culprit. + Try setting the user's class back to the + default class and rebuild the database + with cap_mkdb. If this does not + alleviate the problem, go to step two. + + + + Double-check the label policies. Ensure that the + policies are set correctly for the user, the Xorg + application, and the /dev entries. + + + + If neither of these resolve the problem, send the + error message and a description of the environment to + the &a.questions; mailing list. + + + + + + The error: _secure_path: unable to stat + .login_conf shows up. + + When a user attempts to switch from the + root user to another user in the system, + the error message _secure_path: unable to stat .login_conf appears. - This message is usually shown when the user has a higher - label setting than that of the user they are attempting to - become. For instance, joe has a default - label of . The - root user, who has a label of - , cannot view - joe's home directory. This will happen - whether or not root has used - su to become joe as - the Biba integrity model will not permit - root to view objects set at a lower - integrity level. - - - - The system no longer recognizes the - root user. - - In normal or even single user mode, the - root is not recognized, - whoami returns 0 (zero), and - su returns who are + This message is usually shown when the user has a higher + label setting than that of the user they are attempting to + become. For instance, joe has a default + label of . The + root user, who has a label of + , cannot view + joe's home directory. This will happen + whether or not root has used + su to become joe as + the Biba integrity model will not permit + root to view objects set at a lower + integrity level. + + + + The system no longer recognizes the + root user. + + In normal or even single user mode, the + root is not recognized, + whoami returns 0 (zero), and + su returns who are you?. - This can happen if a labeling policy has been disabled, - either by a &man.sysctl.8; or the policy module was unloaded. - If the policy is disabled, the login capabilities database - needs to be reconfigured with removed. - Double check login.conf to ensure that - all options have been removed and - rebuild the database with cap_mkdb. - - This may also happen if a policy restricts access to - master.passwd. This is usually caused by - an administrator altering the file under a label which - conflicts with the general policy being used by the system. - In these cases, the user information would be read by the - system and access would be blocked as the file has inherited - the new label. Disable the policy using &man.sysctl.8; and - everything should return to normal. - - + This can happen if a labeling policy has been disabled, + either by a &man.sysctl.8; or the policy module was unloaded. + If the policy is disabled, the login capabilities database + needs to be reconfigured with removed. + Double check login.conf to ensure that + all options have been removed and + rebuild the database with cap_mkdb. + + This may also happen if a policy restricts access to + master.passwd. This is usually caused by + an administrator altering the file under a label which + conflicts with the general policy being used by the system. + In these cases, the user information would be read by the + system and access would be blocked as the file has inherited + the new label. Disable the policy using &man.sysctl.8; and + everything should return to normal. + + From owner-svn-doc-projects@FreeBSD.ORG Fri May 17 17:27:34 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 12BD729C; Fri, 17 May 2013 17:27:34 +0000 (UTC) (envelope-from trhodes@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 0595FCDB; Fri, 17 May 2013 17:27:34 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4HHRXuB043191; Fri, 17 May 2013 17:27:33 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4HHRXB7043190; Fri, 17 May 2013 17:27:33 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305171727.r4HHRXB7043190@svn.freebsd.org> From: Tom Rhodes Date: Fri, 17 May 2013 17:27:33 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41641 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/security 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: Fri, 17 May 2013 17:27:34 -0000 Author: trhodes Date: Fri May 17 17:27:33 2013 New Revision: 41641 URL: http://svnweb.freebsd.org/changeset/doc/41641 Log: Add a section on rctl(8). Requested by: someone (bcr? dru?) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/security/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/security/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/security/chapter.xml Fri May 17 17:26:20 2013 (r41640) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/security/chapter.xml Fri May 17 17:27:33 2013 (r41641) @@ -89,6 +89,11 @@ What Process Accounting is and how to enable it on &os;. + + + Understand the resource limits database and + how to utilize it to control user resources. + Before reading this chapter, you should: @@ -3691,4 +3696,119 @@ VII. References + + + + + + Tom + Rhodes + Contributed by + + + + + Resource Limits + + + Resource limits + + + For years, &os; has used a resource limits + database controlled through a flat file, + /etc/login.conf. While it has + been discussed previously and is still supported, it + is not the most optimal method of controlling resources. + The flat file requires users to be divided into various + group labels known as classes, which require changes not + only to this flat file but also the password database. + Potentially a single, more constrained user would require + an additional label added, the resource database needs to be + built using cap_mkdb, edits made to + the /etc/master.passwd file. In + addition, the password database must be rebuilt using + pwd_mkdb. This multi-step process could be + very time consuming depending on how many users must be + singled out. + + A new command in &os;, &man.rctl.8;, allows for a more + fine grained method of controlling resources limits for + users. This command will support much more than users, + it will also set resource constraints on processes, jails, + and the original login class. These advanced features + provide administrators and users with methods to control + resources through the command line and set rules on + system initialization using a configuration + file. + + To enable this feature, add these lines to + GENERIC, or the custom kernel + configuration file, and rebuild.: + + options RACCT +options RCTL + + The entire system will need rebuilt. See , which will provide instructions for + the process. Once this is complete, the rctl + may be used to set rules for the system. + + Rule syntax is simple, controlled through the use of + a subject, a subject-id, + resource, and action. + Take the following example rule: + + user:trhodes:maxproc:deny=10/user + + This rule shows a basic premise of a rule, here the + subject is user and the subject-id + is trhodes. The maxproc is, of course, + max number of processes, which is considered the action. + The action here is set to deny, which blocks + any new processes from being created. In the previous example, + the user, trhodes will be constrained + to 10 (ten) processes and no greater. + Other actions are available and could be log to the console, + pass a notification to &man.devd.8;, or + send a sigterm to the process. + + Some care must be taken while adding rules. The one above + will unfortunately block my user from doing the most simple tasks + after I have logged in and executed a screen + session. When a resource limit has been hit, an error will + be printed, as in this example: + + &prompt.user; man test + /usr/bin/man: Cannot fork: Resource temporarily unavailable +eval: Cannot fork: Resource temporarily unavailable + + For another example, &man.rctl.8; can be used to prevent + a jail from exceeding a memory limit. This rule could be + written as: + + &prompt.root; rctl -a jail:httpd:memoryuse:deny=2G/jail + + Rules may also persist across reboots if they have been + added to /etc/rctl.conf file. The + format is a rule, without the preceding command. For example, + the previous rule could be added like the following: + + # Block jail from using more than 2G memory: +jail:httpd:memoryuse:deny=2G/jail + + To remove a rule, just ask rctl to + remove it from the list: + + &prompt.root; rctl -r user:trhodes:maxproc:deny=10/user + + The manual page shows a method for removing all rules; + however, if removing all rules for a single user is required, + this command may be issued: + + &prompt.root; rctl -r user:trhodes + + Many other resources exist which can be used to excert + additional control over various subjects. + See &man.rctl.8; to learn about them. + From owner-svn-doc-projects@FreeBSD.ORG Fri May 17 18:05:44 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 DFB38CA5; Fri, 17 May 2013 18:05:44 +0000 (UTC) (envelope-from gabor@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 D148CE2F; Fri, 17 May 2013 18:05:44 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4HI5iPF056943; Fri, 17 May 2013 18:05:44 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4HI5i1b056936; Fri, 17 May 2013 18:05:44 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305171805.r4HI5i1b056936@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 17 May 2013 18:05:44 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41643 - in projects/xml-tools: en_US.ISO8859-1/books/faq en_US.ISO8859-1/books/fdp-primer/writing-style en_US.ISO8859-1/htdocs/news/status share/pgpkeys share/xml 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: Fri, 17 May 2013 18:05:44 -0000 Author: gabor Date: Fri May 17 18:05:43 2013 New Revision: 41643 URL: http://svnweb.freebsd.org/changeset/doc/41643 Log: - MFH Modified: projects/xml-tools/en_US.ISO8859-1/books/faq/book.xml projects/xml-tools/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.xml projects/xml-tools/en_US.ISO8859-1/htdocs/news/status/report-2013-01-2013-03.xml projects/xml-tools/share/pgpkeys/philip.key projects/xml-tools/share/xml/header.ent projects/xml-tools/share/xml/navibar.ent Directory Properties: projects/xml-tools/ (props changed) projects/xml-tools/en_US.ISO8859-1/ (props changed) projects/xml-tools/share/ (props changed) Modified: projects/xml-tools/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- projects/xml-tools/en_US.ISO8859-1/books/faq/book.xml Fri May 17 17:57:13 2013 (r41642) +++ projects/xml-tools/en_US.ISO8859-1/books/faq/book.xml Fri May 17 18:05:43 2013 (r41643) @@ -1732,8 +1732,7 @@ - &os; supports SCSI and QIC-36 (with a QIC-02 - interface). + &os; supports all standard SCSI tape interfaces. Modified: projects/xml-tools/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.xml ============================================================================== --- projects/xml-tools/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.xml Fri May 17 17:57:13 2013 (r41642) +++ projects/xml-tools/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.xml Fri May 17 18:05:43 2013 (r41643) @@ -479,6 +479,10 @@ GB. Hardware compression … + read-only + + + web server Modified: projects/xml-tools/en_US.ISO8859-1/htdocs/news/status/report-2013-01-2013-03.xml ============================================================================== --- projects/xml-tools/en_US.ISO8859-1/htdocs/news/status/report-2013-01-2013-03.xml Fri May 17 17:57:13 2013 (r41642) +++ projects/xml-tools/en_US.ISO8859-1/htdocs/news/status/report-2013-01-2013-03.xml Fri May 17 18:05:43 2013 (r41643) @@ -620,7 +620,7 @@ - Evaluating if it is worth to migrate any of the other + Evaluating if it is worthwhile to migrate any of the other callout(9) consumers to the new interface. Move callout consumers still using the legacy timeout()/untimeout() interface to callout_*() in order to get @@ -1096,7 +1096,7 @@

The project progressed well since February:

    -
  • Konstantin committed is TTM port to 10-CURRENT.
  • +
  • Konstantin committed his TTM port to 10-CURRENT.
  • With the help of John Baldwin (jhb) and Andriy Gapon (avg), the Video BIOS situation greatly improved: the @@ -1121,17 +1121,17 @@ the VM folks.
-

Yakaz lended +

Yakaz loaned Jean-Sébastien a computer which allows him to test a RV630-based discrete card and, in the future, other PCIe cards. Several users already kindly tested the driver. Big thanks to all those contributors!

-

In its current state, the driver allows to have a simple X +

In its current state, the driver allows a simple X session (no OpenGL), run common applications, watch movies, change the resolution and enable additional monitors with xrandr(1). The most blocking issue now is the OpenGL - deadlock which prevents to run modern compositors/desktop + deadlock which prevents running modern compositors/desktop environment, games and WebGL demos. We are not ready for a "Call For Testers" yet.

Modified: projects/xml-tools/share/pgpkeys/philip.key ============================================================================== --- projects/xml-tools/share/pgpkeys/philip.key Fri May 17 17:57:13 2013 (r41642) +++ projects/xml-tools/share/pgpkeys/philip.key Fri May 17 18:05:43 2013 (r41643) @@ -10,8 +10,8 @@ uid Philip Paeps uid Philip Paeps uid Philip Paeps -sub 1024D/035EFC58 2006-10-22 [expires: 2010-10-13] -sub 2048g/6E5FD7D6 2006-10-22 [expires: 2010-10-14] +sub 1024D/035EFC58 2006-10-22 +sub 2048g/6E5FD7D6 2006-10-22 ]]>
Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D3E7AA7C; Fri, 17 May 2013 19:23:19 +0000 (UTC) (envelope-from trhodes@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 B65C6176; Fri, 17 May 2013 19:23:19 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4HJNJIs085909; Fri, 17 May 2013 19:23:19 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4HJNJH8085908; Fri, 17 May 2013 19:23:19 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305171923.r4HJNJH8085908@svn.freebsd.org> From: Tom Rhodes Date: Fri, 17 May 2013 19:23:19 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41647 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia 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: Fri, 17 May 2013 19:23:19 -0000 Author: trhodes Date: Fri May 17 19:23:19 2013 New Revision: 41647 URL: http://svnweb.freebsd.org/changeset/doc/41647 Log: Axe the mythtv depends section and migrate it into the introduction area. Slight wording tweaks for grammar. Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Fri May 17 18:54:21 2013 (r41646) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Fri May 17 19:23:19 2013 (r41647) @@ -1437,6 +1437,26 @@ bktr0: Pinnacle/Miro TV, Philips SECAM t url="http://www.mythtv.org/wiki/">MythTV wiki for more information on how to use MythTV.
+ MythTV requires a frontend and a backend; however, + it allows the user to have the frontend and backend on + different machines. + + For the frontend, multimedia/mythtv-frontend is + required, as well as an X server, which can be found in + x11/xorg. Ideally, the + frontend computer also has a video card that supports XvMC and, + optionally, a LIRC-compatible remote. + + For the backend, multimedia/mythtv is required, + along with the &mysql; database server. Optionally a tuner + and storage for any recorded data. The &mysql; package should + be automatically installed as a dependency when installing + multimedia/mythtv. + Hardware @@ -1469,29 +1489,6 @@ bktr0: Pinnacle/Miro TV, Philips SECAM t - Dependencies - - Being flexible and modular, MythTV allows the user to - have the frontend and backend on different machines. - - For the frontend, multimedia/mythtv-frontend is - required, as well as an X server, which can be found in - x11/xorg. Ideally, the - frontend computer also has a video card that supports XvMC and, - optionally, a LIRC-compatible remote. - - For the backend, multimedia/mythtv is required, - as well as a &mysql; database, and optionally a tuner and - storage for recordings. The &mysql; package should be - automatically installed as a dependency when installing - multimedia/mythtv. - - - Setting up MythTV To install the MythTV port: From owner-svn-doc-projects@FreeBSD.ORG Fri May 17 20:08:12 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 14E53EDA; Fri, 17 May 2013 20:08:12 +0000 (UTC) (envelope-from trhodes@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 E19F0325; Fri, 17 May 2013 20:08:11 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4HK8BAe001540; Fri, 17 May 2013 20:08:11 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4HK8BDu001539; Fri, 17 May 2013 20:08:11 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305172008.r4HK8BDu001539@svn.freebsd.org> From: Tom Rhodes Date: Fri, 17 May 2013 20:08:11 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41650 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/disks 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: Fri, 17 May 2013 20:08:12 -0000 Author: trhodes Date: Fri May 17 20:08:11 2013 New Revision: 41650 URL: http://svnweb.freebsd.org/changeset/doc/41650 Log: Axe the "why encrypt swap" mini-section and migrate the useful stuff into the section introduction. Re-word some sentences and a section name. Reviewed by: bcr (quick look) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/disks/chapter.xml Fri May 17 19:56:43 2013 (r41649) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/disks/chapter.xml Fri May 17 20:08:11 2013 (r41650) @@ -3830,27 +3830,22 @@ geli_da2_flags="-p -k /root/da2.key"encrypting - Swap encryption in &os; is easy to configure. Depending on - which version of &os; is being used, different options are - available and configuration can vary slightly. The &man.gbde.8; - or &man.geli.8; encryption systems can be used for swap - encryption. Both systems use the encswap + Like the encryption of disk partitions, encryption of swap + space is used to protect sensitive information. Consider an + application that deals with passwords. As long as these + passwords stay in physical memory, these passwords will not + be written to disk and be cleared after a reboot. If &os; + starts swapping out memory pages to free + space for other applications, the passwords may be written to + the disk platters unencrypted. Encrypting swap space can be a + solution for this scenario. + + The &man.gbde.8; or &man.geli.8; encryption systems may be + used for swap encryption. Both systems use the + encswap rc.d script. - Why Should Swap be Encrypted? - - Like the encryption of disk partitions, encryption of swap - space is used to protect sensitive information. Consider an - application that deals with passwords. As long as these - passwords stay in physical memory, all is well. However, if - the operating system starts swapping out memory pages to free - space for other applications, the passwords may be written to - the disk platters unencrypted. Encrypting swap space can be a - solution for this scenario. - - - Preparation @@ -3907,7 +3902,7 @@ geli_da2_flags="-p -k /root/da2.key" - Verifying That it Works + Encrypted Swap Verification Once the system has rebooted, proper operation of the encrypted swap can be verified using From owner-svn-doc-projects@FreeBSD.ORG Fri May 17 20:21:58 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 75C893ED; Fri, 17 May 2013 20:21:58 +0000 (UTC) (envelope-from trhodes@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 4F4F438A; Fri, 17 May 2013 20:21:58 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4HKLvLD007798; Fri, 17 May 2013 20:21:57 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4HKLvhD007797; Fri, 17 May 2013 20:21:57 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305172021.r4HKLvhD007797@svn.freebsd.org> From: Tom Rhodes Date: Fri, 17 May 2013 20:21:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41652 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/disks 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: Fri, 17 May 2013 20:21:58 -0000 Author: trhodes Date: Fri May 17 20:21:57 2013 New Revision: 41652 URL: http://svnweb.freebsd.org/changeset/doc/41652 Log: Migrate the encypted swap preparation section into the introduction and do some wording tweaks to remove redundancy. Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/disks/chapter.xml Fri May 17 20:12:00 2013 (r41651) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/disks/chapter.xml Fri May 17 20:21:57 2013 (r41652) @@ -3845,22 +3845,18 @@ geli_da2_flags="-p -k /root/da2.key"encswap rc.d script. - - Preparation - - - For the remainder of this section, - ad0s1b will be the swap - partition. - - - By default, swap is unencrypted. It is possible that it - contains passwords or other sensitive data in cleartext. To - rectify this, the data on the swap partition should be - overwritten with random garbage: + + For the remainder of this section, + ad0s1b will be the swap + partition. + + + Swap partitions are not encrypted by default and should + be cleared of any sensitive data before continuing. To + overwrite the current swap parition with random garbage, + execute the following command: - &prompt.root; dd if=/dev/random of=/dev/ad0s1b bs=1m - + &prompt.root; dd if=/dev/random of=/dev/ad0s1b bs=1m Swap Encryption with &man.gbde.8; From owner-svn-doc-projects@FreeBSD.ORG Fri May 17 21:00:40 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4D071C4F; Fri, 17 May 2013 21:00:40 +0000 (UTC) (envelope-from trhodes@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 25AEC6DD; Fri, 17 May 2013 21:00:40 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4HL0dna021286; Fri, 17 May 2013 21:00:39 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4HL0dUQ021285; Fri, 17 May 2013 21:00:39 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305172100.r4HL0dUQ021285@svn.freebsd.org> From: Tom Rhodes Date: Fri, 17 May 2013 21:00:39 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41655 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia 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: Fri, 17 May 2013 21:00:40 -0000 Author: trhodes Date: Fri May 17 21:00:39 2013 New Revision: 41655 URL: http://svnweb.freebsd.org/changeset/doc/41655 Log: Refactor a bit so we don't jump from a right into a with no introduction text. Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Fri May 17 20:55:56 2013 (r41654) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Fri May 17 21:00:39 2013 (r41655) @@ -1529,24 +1529,20 @@ bktr0: Pinnacle/Miro TV, Philips SECAM t image scanners - - Introduction - - In &os;, access to image scanners is provided by the - SANE (Scanner Access Now Easy) - API available through the &os; Ports - Collection. SANE will also use - some &os; device drivers to provide access to the scanner - hardware. - - &os; supports both SCSI and USB scanners. Be sure the - scanner is supported by SANE prior - to performing any configuration. Refer to the supported - devices list for more information about supported - scanners. - + In &os;, access to image scanners is provided by the + SANE (Scanner Access Now Easy) + API available through the &os; Ports + Collection. SANE will also use + some &os; device drivers to provide access to the scanner + hardware. + + &os; supports both SCSI and USB scanners. Be sure the + scanner is supported by SANE prior + to performing any configuration. Refer to the + supported devices list for more information about supported + scanners. Kernel Configuration From owner-svn-doc-projects@FreeBSD.ORG Fri May 17 21:01:18 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D1665CA8; Fri, 17 May 2013 21:01:18 +0000 (UTC) (envelope-from trhodes@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 C3CB26EC; Fri, 17 May 2013 21:01:18 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4HL1I3h021483; Fri, 17 May 2013 21:01:18 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4HL1I4M021482; Fri, 17 May 2013 21:01:18 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305172101.r4HL1I4M021482@svn.freebsd.org> From: Tom Rhodes Date: Fri, 17 May 2013 21:01:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41656 - 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: Fri, 17 May 2013 21:01:18 -0000 Author: trhodes Date: Fri May 17 21:01:18 2013 New Revision: 41656 URL: http://svnweb.freebsd.org/changeset/doc/41656 Log: Mark up "crontab" in . 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 Fri May 17 21:00:39 2013 (r41655) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml Fri May 17 21:01:18 2013 (r41656) @@ -472,11 +472,13 @@ run_rc_command "$1" 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 + &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. @@ -486,13 +488,15 @@ run_rc_command "$1" Commands in a user's crontab run with the permissions of the user who owns the crontab. - The root user can have a user crontab - 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 + The root user can have a user + crontab 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. + a user crontab for + root. Here is a sample entry from @@ -580,7 +584,7 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin Do not use the procedure described here to edit and - install the system crontab, + 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. @@ -602,11 +606,12 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin To list installed &man.crontab.5; files, pass to &man.crontab.1;. - 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;. + 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 this + 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. From owner-svn-doc-projects@FreeBSD.ORG Fri May 17 21:24:42 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 0D3A3E69; Fri, 17 May 2013 21:24:42 +0000 (UTC) (envelope-from trhodes@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 F3F868CB; Fri, 17 May 2013 21:24:41 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4HLOf8b029392; Fri, 17 May 2013 21:24:41 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4HLOfEt029391; Fri, 17 May 2013 21:24:41 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305172124.r4HLOfEt029391@svn.freebsd.org> From: Tom Rhodes Date: Fri, 17 May 2013 21:24:41 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41658 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/basics 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: Fri, 17 May 2013 21:24:42 -0000 Author: trhodes Date: Fri May 17 21:24:41 2013 New Revision: 41658 URL: http://svnweb.freebsd.org/changeset/doc/41658 Log: Add a note about fs acls PR: 160445 Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/basics/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/basics/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/basics/chapter.xml Fri May 17 21:24:10 2013 (r41657) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/basics/chapter.xml Fri May 17 21:24:41 2013 (r41658) @@ -310,6 +310,13 @@ console none belongs to, and one for everyone else. This numerical representation works like this: + + This section will discuss the traditional &unix; + permissions. For finer grained file system access + control, see the File System + Access Control Lists section. + + permissions file permissions From owner-svn-doc-projects@FreeBSD.ORG Sat May 18 17:29: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 33C1FE3A; Sat, 18 May 2013 17:29:31 +0000 (UTC) (envelope-from trhodes@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 0AE05A7C; Sat, 18 May 2013 17:29: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 r4IHTUiw048361; Sat, 18 May 2013 17:29:30 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4IHTUcI048360; Sat, 18 May 2013 17:29:30 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305181729.r4IHTUcI048360@svn.freebsd.org> From: Tom Rhodes Date: Sat, 18 May 2013 17:29:30 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41661 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports 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: Sat, 18 May 2013 17:29:31 -0000 Author: trhodes Date: Sat May 18 17:29:30 2013 New Revision: 41661 URL: http://svnweb.freebsd.org/changeset/doc/41661 Log: Remove a one line section, fix up the introduction a bit. Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Sat May 18 01:56:17 2013 (r41660) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Sat May 18 17:29:30 2013 (r41661) @@ -337,22 +337,19 @@ Info: Lists information about open fil Using Binary Packages - There are several different tools used to manage packages on - &os;: - - - - The sysinstall utility can be invoked - on a running system to install, delete, and list available - and installed packages. For more information, see - . - - - - The package management command line tools, which are - the subject of the rest of this section. - - + At the present time, &os; is transitioning toward a new + method of package management. Users of the latest releases + may wish to investigate the benefits of using + PKGng to manage third + party software on &os;. For those not yet migrated to the + pkgng tool, the tools discussed + here may be used for managing the package database. For + simplicity, the sysinstall utility is + also available post-install for package management. + + All package installation files are stored in the + package database directory, + /var/db/pkg. Installing a Package @@ -569,14 +566,6 @@ docbook = in this case, all packages whose names start with xchat will be deleted. - - - Miscellaneous - - All package information, including the file list and - descriptions of each installed package is stored within the - /var/db/pkg directory. - From owner-svn-doc-projects@FreeBSD.ORG Sat May 18 18:09:00 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AF08AAEB; Sat, 18 May 2013 18:09:00 +0000 (UTC) (envelope-from trhodes@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 912FEBEC; Sat, 18 May 2013 18:09:00 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4II90Hl062396; Sat, 18 May 2013 18:09:00 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4II90dV062395; Sat, 18 May 2013 18:09:00 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305181809.r4II90dV062395@svn.freebsd.org> From: Tom Rhodes Date: Sat, 18 May 2013 18:09:00 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41662 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports 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: Sat, 18 May 2013 18:09:00 -0000 Author: trhodes Date: Sat May 18 18:09:00 2013 New Revision: 41662 URL: http://svnweb.freebsd.org/changeset/doc/41662 Log: Alter the title name here, it's bad (though I doubt my re-word is much of an improvement). Add information on where documentation is actually installed rather than just recommend a user read it. Add some tags. More coming. Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Sat May 18 17:29:30 2013 (r41661) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Sat May 18 18:09:00 2013 (r41662) @@ -1778,17 +1778,25 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ - Post-installation Activities + Working With Installed Ports - After installing a new application you will normally want to - read any documentation it may have included, edit any - required configuration files, and ensure that the - application's service starts at boot time. - - The exact steps you need to take to configure each - application will obviously be different. However, if you have - just installed a new application and are wondering - What now? these tips might help: + Most third party applications will need some level of + configuration after they were installed. This may be a simple + configuration file alteration, or perhaps the application will + just generate a configuration file. Most applications will + have documentation installed into + /usr/local/share/doc and + manual pages. This documentation should be consulted before + continuing. Some applications run services which must be added + to the /etc/rc.conf file before + starting. + + The following list contains useful information for + post-install port management. In several cases, finding + the location of binaries if they were installed outside + of the PATH. Users of &man.csh.1; should run + the rehash to rebuild the known binary + list in the shells PATH. @@ -1796,7 +1804,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ installed, and where. For example, if you have just installed FooPackage version 1.0.0, then this command - &prompt.root; pkg_info -L foopackage-1.0.0 | less + &prompt.root; pkg_info -L foopackage-1.0.0 | less will show all the files installed by the package. Pay special attention to files located in From owner-svn-doc-projects@FreeBSD.ORG Sat May 18 18:24:12 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 0EE42D47; Sat, 18 May 2013 18:24:12 +0000 (UTC) (envelope-from trhodes@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 E4123CC6; Sat, 18 May 2013 18:24:11 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4IIOBSp068567; Sat, 18 May 2013 18:24:11 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4IIOBcm068566; Sat, 18 May 2013 18:24:11 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305181824.r4IIOBcm068566@svn.freebsd.org> From: Tom Rhodes Date: Sat, 18 May 2013 18:24:11 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41663 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports 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: Sat, 18 May 2013 18:24:12 -0000 Author: trhodes Date: Sat May 18 18:24:11 2013 New Revision: 41663 URL: http://svnweb.freebsd.org/changeset/doc/41663 Log: Reword to avoid "you" in the ports after install section (which is where I performed work in the previous commit). Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Sat May 18 18:09:00 2013 (r41662) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Sat May 18 18:24:11 2013 (r41663) @@ -1800,18 +1800,18 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ - Use &man.pkg.info.1; to find out which files were - installed, and where. For example, if you have just - installed FooPackage version 1.0.0, then this command + The &man.pkg.info.1; will print all installed + files and their location. For example, if the FooPackage + version 1.0.0 was just installed, then the following + command will show all the files installed with the + package. &prompt.root; pkg_info -L foopackage-1.0.0 | less - will show all the files installed by the package. Pay - special attention to files located in - man/, which will be manual pages, - etc/, which will be configuration - files, and doc/, which will be more - comprehensive documentation. + Configuration files are always installed in the + /usr/local/etc + and should definitely be consulted before attempting + to use the new application. To determine which version of the application was installed: @@ -1825,17 +1825,18 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ - Once you have identified where the application's manual - pages have been installed, review them using &man.man.1;. - Review the sample configuration files and any additional - documentation that may have been provided. + These commands will also show the names of any manual + pages installed with the application. This additional + documentation will now be available to the &man.man.1; + command. - If the application has a web site, check it for - additional documentation, frequently asked questions, and so - forth. If you are not sure of the web site address it may - be listed in the output from + If the application has a web site, consult it for + additional documentation, frequently asked questions, or + a forum. If the website is unknown, the following command + will be useful to print out this information if it's + available. &prompt.root; pkg_info foopackage-1.0.0 From owner-svn-doc-projects@FreeBSD.ORG Sat May 18 19:56:00 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 B1F808DF; Sat, 18 May 2013 19:56:00 +0000 (UTC) (envelope-from trhodes@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 944EB9D; Sat, 18 May 2013 19:56:00 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4IJu0Xi001538; Sat, 18 May 2013 19:56:00 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4IJu0kK001534; Sat, 18 May 2013 19:56:00 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305181956.r4IJu0kK001534@svn.freebsd.org> From: Tom Rhodes Date: Sat, 18 May 2013 19:56:00 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41664 - in projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook: config network-servers 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: Sat, 18 May 2013 19:56:00 -0000 Author: trhodes Date: Sat May 18 19:55:59 2013 New Revision: 41664 URL: http://svnweb.freebsd.org/changeset/doc/41664 Log: Mark up syslogd and newsyslogd in tags in the section titles. Add an introduction to the tuning disks chapter. 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/network-servers/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 Sat May 18 18:24:11 2013 (r41663) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/config/chapter.xml Sat May 18 19:55:59 2013 (r41664) @@ -1362,7 +1362,7 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 n Configuring the System Logger, - &man.syslogd.8; + syslogd system logging syslog @@ -1383,7 +1383,7 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 n linkend="network-syslogd"/>. - Using &man.syslogd.8; + Using <command>syslogd</command> In the default &os; configuration, &man.syslogd.8; is started at boot. This is controlled by the variable @@ -1401,7 +1401,7 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 n - Configuring &man.syslogd.8; + Configuring <command>syslogd</command> syslog.conf @@ -1541,7 +1541,7 @@ cron.* Log Management and Rotation with - &man.newsyslog.8; + newsyslog newsyslog newsyslog.conf @@ -1563,7 +1563,7 @@ cron.* Configuring - &man.newsyslog.8; + newsyslog To know which actions to take, &man.newsyslog.8; reads its configuration file, by default @@ -1959,6 +1959,19 @@ device_probe_and_attach: cbb0 attach ret Tuning Disks + The following section will discuss various tuning + mechanisms and options which may be applied to disk + devices. In many cases, disks with mechanical parts, + such as SCSI drives, will be the bottle + neck driving down the overall system performance. While + a solution is to install a drive without mechanical parts, + such as a solid state drive, mechanical drives are not + going away anytime in the near future. When tuning disks, + it is advisable to utilize the features of the &man.iostat.8; + command to test various changes to the system. This + command will allow the user to obtain valuable information + on system IO. + Sysctl Variables Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Sat May 18 18:24:11 2013 (r41663) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Sat May 18 19:55:59 2013 (r41664) @@ -5682,7 +5682,7 @@ driftfile /var/db/ntp.driftCentralized logging to a specific logging host can reduce some of the administrative burden of log file administration. - Log file aggregation, merging and rotation can be configured in + Log file aggregation, merging and rotation may be configured in one location, using the native tools of &os;, such as &man.syslogd.8; and &man.newsyslog.8;. In the following example configuration, host A, named - syslogd has been configured to accept remote messages - from client machines; + syslogd has been configured to + accept remote messages from client machines; - The syslogd server and all client machines must have - valid entries for both forward and reverse - DNS, or be properly configured in - /etc/hosts. + The syslogd server and all client + machines must have valid entries for both forward and + reverse DNS, or be properly configured + in /etc/hosts. @@ -5770,13 +5770,14 @@ syslogd_flags="-a logclient.example.com does not matter, but &man.touch.1; works great for situations such as this: - &prompt.root; touch /var/log/logclient.log + &prompt.root; touch + /var/log/logclient.log At this point, the syslogd daemon should be restarted and verified: - &prompt.root; service syslogd restart -&prompt.root; pgrep syslog + &prompt.root; service syslogd restart +&prompt.root; pgrep syslog If a PID is returned, the server has been restarted successfully, and client configuration may @@ -5851,13 +5852,14 @@ syslogd_flags="-s -v -v"Once added, syslogd must be restarted for the changes to take effect: - &prompt.root; service syslogd restart + &prompt.root; service syslogd restart To test that log messages are being sent across the network, use &man.logger.1; on the client to send a message to syslogd: - &prompt.root; logger "Test message from logclient" + &prompt.root; logger + "Test message from logclient" This message should now exist both in /var/log/messages on the client, and @@ -5888,7 +5890,7 @@ syslogd_flags="-s -v -v"syslogd_flags="-d -a logclien.example.com -v -v" - &prompt.root; service syslogd restart + &prompt.root; service syslogd restart Debugging data similar to the following will flash on the screen immediately after the restart: @@ -5913,7 +5915,7 @@ rejected in rule 0 due to name mismatch. logclien. After the proper alterations are made, a restart is issued with expected results: - &prompt.root; service syslogd restart + &prompt.root; service syslogd restart logmsg: pri 56, flags 4, from logserv.example.com, msg syslogd: restart syslogd: restarted logmsg: pri 6, flags 4, from logserv.example.com, msg syslogd: kernel boot file is /boot/kernel/kernel