diff --git a/en/handbook/README b/en/handbook/README index 416416e761..c0810586d3 100644 --- a/en/handbook/README +++ b/en/handbook/README @@ -293,3 +293,23 @@ for example, Convert the first lot to ... + 24. Fixed manual page references to use the right markup, which is + + + page_name + number + + + Did this with a regexp search for + + \([a-z-_\.]+\)(\([1-9]\)) + + and replacing with + + \1\2 + + Since most of the page references had , , or + elements wrapped around them, you then have to sweep through the + file looking for ">write access to the CVS tree, and are thus authorized to make modifications to the FreeBSD source (the term committer comes from the - cvs(1) commit command, which is used to + cvs1 commit command, which is used to bring new changes into the CVS repository). The best way of making submissions for review by the committers list is to - use the send-pr(1) command, though if something appears to be jammed in the system then you may also reach them by sending mail to committers@freebsd.org. + use the send-pr1 command, though if something appears to be jammed in the system then you may also reach them by sending mail to committers@freebsd.org. @@ -1997,11 +1996,9 @@ command chmod. References to a particular section of the on-line manual are traditionally placed in - parenthesis in written documentation, so chmod(1) refers to the + parenthesis in written documentation, so chmod1 refers to the chmod - user command and chmod(2) refers to the + user command and chmod2 refers to the system call. This is fine if you know the name of the command and simply wish @@ -2041,7 +2038,7 @@ info command or, if you installed emacs, the info mode of emacs. - To use the info(1) command, simply type: + To use the info1 command, simply type: % info For a brief introduction, type Create a link tree to it using the - lndir(1) command that comes with the + lndir1 command that comes with the XFree86 distribution. Find a location with some free space, create a directory there and then cd to it. Then - invoke the lndir(1) command with the full + invoke the lndir1 command with the full pathname of the ports directory on the CDROM as the first argument and . (the current directory) as the second. This might be, for example, something like: lndir @@ -2599,7 +2596,7 @@ directory, though check your local mirror first, please! These are more likely to work (on the whole) than trying to compile from source and a lot faster besides! Use - the pkg_add(1) program to install a + the pkg_add1 program to install a package file on your system. @@ -3251,7 +3248,7 @@ If you are trying to upgrade your kernel from an older version of FreeBSD, you will probably have to get a new version of - config(8) from the same place you got the new + config8 from the same place you got the new kernel sources. It is located in /usr/src/usr.sbin, so you will need to download those sources as well. Re-build and install it before @@ -3561,7 +3558,7 @@ hundred bytes to the kernel. - The ipcs(1) command will tell + The ipcs1 command will tell will list any processes using each of these System V facilities. @@ -3635,7 +3632,7 @@ Process filesystem. This is a pretend filesystem mounted on /proc which allows - programs like ps(1) to give you more + programs like ps1 to give you more information on what processes are running. @@ -3742,7 +3739,7 @@ QIC-80 tape support requires a separate filter - program called ft(8), see the manual + program called ft8, see the manual page for details. @@ -4121,8 +4118,8 @@ serial port at COM2 you will have to change the IRQ of the modem to 2 (for obscure technical reasons IRQ 2 = IRQ 9) in order to access it from FreeBSD. If you have a - multiport serial card, check the manual page for sio(4) for more information on the + multiport serial card, check the manual page for + sio4 for more information on the proper values for these lines. Some video cards (notably those based on S3 chips) use IO addresses of the form 0x*2e8, and since many cheap serial @@ -4408,7 +4405,7 @@ network interfaces to be placed in promiscuous mode, capturing every packet on a broadcast network (e.g. an ethernet). These packets can be captured to disk and/or - examined with the tcpdump(1) program. + examined with the tcpdump1 program. Note that implementation of this capability can seriously compromise your overall network security. The number after bpfilter is the number @@ -4607,7 +4604,7 @@ Snoop device. This pseudo-device allows one terminal session to watch another using the - watch(8) command. Note that + watch8 command. Note that implementation of this capability has important security and privacy implications. The number after snp is the total number of simultaneous snoop @@ -4619,7 +4616,7 @@ Vnode driver. Allows a file to be treated as a device - after being set up with the vnconfig(8) + after being set up with the vnconfig8 command. This driver can be useful for manipulating floppy disk images and using a file as a swap device (e.g. an MS Windows swap file). Optional. @@ -4635,8 +4632,8 @@ meta-disk. The number after ccd is the total number of concatenated disks (not total number of disks that can be concatenated) that can be - created. (See ccd(4) and - ccdconfig(8) man pages for more + created. (See ccd4 and + ccdconfig8 man pages for more details.) Optional. @@ -4801,7 +4798,7 @@ resource is the /var/log/messages file which records, among other things, all of the kernel messages from every successful boot. Also, the - dmesg(8) command will print the kernel + dmesg8 command will print the kernel messages from the current boot. @@ -4814,7 +4811,7 @@ with the last installed kernel which may be non-functional. Also, as soon as possible, move the working kernel to the proper kernel location or - commands such as ps(1) will not work + commands such as ps1 will not work properly. The proper command to unlock the kernel file that make installs (in order to move another kernel back permanently) is: @@ -4839,7 +4836,7 @@ from the one that the system utilities have been built with, for example, an experimental 2.2.0 kernel on a 2.1.0-RELEASE system, many system-status commands like - ps(1) and vmstat(8) + ps1 and vmstat8 will not work any more. You must recompile the libkvm library as well as these utilities. This is one reason it is not normally a good @@ -5862,7 +5859,7 @@ IPFW, the software supplied with FreeBSD, is a packet filtering and accounting system which resides in the kernel, and has a user-land control utility, - ipfw(8). Together, they allow you to define and + ipfw8. Together, they allow you to define and query the rules currently used by the kernel in its routing decisions. @@ -5909,7 +5906,7 @@ Enables code to allow logging of packets through - syslogd(8). Without this option, even + syslogd8. Without this option, even if you specify that packets should be logged in the filter rules, nothing will happen. @@ -5919,7 +5916,7 @@ Limits the number of packets logged through - syslogd(8) on a per entry basis. You + syslogd8 on a per entry basis. You may wish to use this option in hostile environments in which you want to log firewall activity, but do not want to be open to a denial of service attack via syslog @@ -5928,7 +5925,7 @@ When a chain entry reaches the packet limit specified, logging is turned off for that particular entry. To resume logging, you will need to reset the associated - counter using the ipfw(8) + counter using the ipfw8 utility: @@ -5955,7 +5952,7 @@ Configuring IPFW The configuration of the IPFW software is - done through the ipfw(8) utility. The syntax + done through the ipfw8 utility. The syntax for this command looks quite complicated, but it is relatively simple once you understand its structure. @@ -6256,7 +6253,7 @@ remap=bf>8 echo request (ping request), and 11 time exceeded (used to indicate TTL expiration as with - traceroute(8)). + traceroute8). @@ -6290,7 +6287,7 @@ Display the last match times for each chain entry. The time listing is incompatible with the input syntax - used by the ipfw(8) utility. + used by the ipfw8 utility. @@ -7163,8 +7160,7 @@ You could put these commands in your /etc/rc.local file to set the mode each - time your system boots. See lptcontrol(8) for more information. + time your system boots. See lptcontrol8 for more information. @@ -7405,7 +7401,7 @@ file take immediate effect. The format of the printcap file is straightforward. Use your favorite text editor to make changes to /etc/printcap. The format is identical to other capability files like /usr/share/misc/termcap and /etc/remote. For complete information about the format, see the cgetent(3). + URL="http://www.freebsd.org/cgi/man.cgi?printcap">printcap file is straightforward. Use your favorite text editor to make changes to /etc/printcap. The format is identical to other capability files like /usr/share/misc/termcap and /etc/remote. For complete information about the format, see the cgetent3. The simple spooler configuration consists of the following steps: @@ -8596,8 +8592,7 @@ Format plain text with pr - before printing. See pr(1) for more information. + before printing. See pr1 for more information. @@ -10665,8 +10660,7 @@ The format of these files is simple: one host name per line. Note that the file /etc/hosts.equiv is also used by - the ruserok(3) protocol, and affects programs like rsh and rcp, so be careful. + the ruserok3 protocol, and affects programs like rsh and rcp, so be careful. For example, here is the /etc/hosts.lpd file on the host @@ -13055,8 +13049,7 @@ The sio driver provides support for NS8250-, NS16450-, NS16550 and NS16550A-based EIA RS-232C (CCITT V.24) communications interfaces. Several - multiport cards are supported as well. See the sio(4) manual page for detailed technical + multiport cards are supported as well. See the sio4 manual page for detailed technical documentation. @@ -13151,8 +13144,7 @@ xxx lines are, you will need to add 16 more devices. Only the last device includes the interrupt vector for the - board. (See the sio(4) manual page for detail as + board. (See the sio4 manual page for detail as to why.) The following example is for a Boca Board with an interrupt of 3, and a base IO address 100h. The IO address for Each port is +8 hexadecimal from the @@ -14822,7 +14814,7 @@ address of the device that is failing, and the desired debug level in /sys/scsi/scsidebug.h. If it probes but just does not work, you can use the - scsi(8) command to dynamically set a + scsi8 command to dynamically set a debug level to it in a running kernel (if SCSIDEBUG is defined). This will give you COPIOUS debugging output with which to confuse the gurus. see man 4 @@ -15129,11 +15121,11 @@ General tape access commands - mt(1) provides generic access to the tape + mt1 provides generic access to the tape drives. Some of the more common commands are rewind, erase, and status. See the mt(1) + remap=tt>status. See the mt1 manual page for a detailed description. @@ -15153,12 +15145,12 @@ SCSI drives - The st(4) driver provides + The st4 driver provides support for 8mm (Exabyte), 4mm (DAT: Digital Audio Tape), QIC (Quarter-Inch Cartridge), DLT (Digital Linear Tape), QIC Minicartridge and 9-track (remember the big reels that you see spinning in Hollywood computer rooms) tape drives. See the - st(4) manual page for a detailed + st4 manual page for a detailed description. The drives listed below are currently being used by members @@ -15306,7 +15298,7 @@ and QIC-525 (DC6525) tapes as well. Data transfer rate is 350kB/s using - dump(8). Rates of 530kB/s have been + dump8. Rates of 530kB/s have been reported when using @@ -15413,8 +15405,7 @@ (250MB) tapes. This drives quirks are known and pre-compiled into the - scsi tape device driver (st(4)). + scsi tape device driver (st4). Under FreeBSD 2.2-current, use mt blocksize 512 to set the blocksize. (The @@ -15920,8 +15911,7 @@ Native capacity is 150/250MB. This drive has quirks which are known and work around code - is present in the scsi tape device driver (st(4)). Upgrading the firmware to XXX + is present in the scsi tape device driver (st4). Upgrading the firmware to XXX version will fix the quirks and provide SCSI 2 capabilities. @@ -15964,7 +15954,7 @@ supported for the 2.5 GB cartridges. This drives quirks are known and pre-compiled into the - scsi tape device driver (st(4)) + scsi tape device driver (st4) beginning with FreeBSD 2.2-current. For previous versions of FreeBSD, use mt to read one block from the tape, rewind the tape, and then execute the @@ -16004,8 +15994,7 @@ erased. This drives quirks are known and pre-compiled into the - scsi tape device driver (st(4)). + scsi tape device driver (st4). Other firmware revisions that are known to work are: M75D @@ -16268,10 +16257,10 @@ Use the front panel button to eject the tape. - Re-insert the tape and dump(8) data to + Re-insert the tape and dump8 data to the tape. - dump(8) will report dump8 will report DUMP: End of tape detected and the console will show: HARDWARE FAILURE info:280 asc:80,96 @@ -16286,42 +16275,42 @@ Backup Programs - The three major programs are dump(8), - tar(1), and - cpio(1). + The three major programs are dump8, + tar1, and + cpio1. Dump and Restore - dump(8) and - restore(8) are the traditional Unix backup + dump8 and + restore8 are the traditional Unix backup programs. They operate on the drive as a collection of disk blocks, below the abstractions of files, links and directories that are created by the filesystems. - dump(8) backs up devices, entire + dump8 backs up devices, entire filesystems, not parts of a filesystem and not directory trees that span more than one filesystem, using either soft links - ln(1) or mounting one filesystem onto - another. dump(8) does not write files and + ln1 or mounting one filesystem onto + another. dump8 does not write files and directories to tape, but rather writes the data blocks that are the building blocks of files and directories. - dump(8) has quirks that remain from its + dump8 has quirks that remain from its early days in Version 6 of ATT Unix (circa 1975). The default parameters are suitable for 9-track tapes (6250 bpi), not the high-density media available today (up to 62,182 ftpi). These defaults must be overridden on the command line to utilize the capacity of current tape drives. - rdump(8) and - rrestore(8) backup data across the network + rdump8 and + rrestore8 backup data across the network to a tape drive attached to another computer. Both programs - rely upon rcmd(3) and - ruserok(3) to access the remote tape + rely upon rcmd3 and + ruserok3 to access the remote tape drive. Therefore, the user performing the backup must have rhosts access to the remote - computer. The arguments to rdump(8) and - rrestore(8) must suitable to use on the + computer. The arguments to rdump8 and + rrestore8 must suitable to use on the remote computer. (e.g. When rdump'ing from a FreeBSD computer to an Exabyte tape drive connected to a Sun called komodo, use: /sbin/rdump 0dsbfu 54000 13000 126 @@ -16335,24 +16324,24 @@ Tar - tar(1) also dates back to Version 6 of - ATT Unix (circa 1975). tar(1) operates in - cooperation with the filesystem; tar(1) + tar1 also dates back to Version 6 of + ATT Unix (circa 1975). tar1 operates in + cooperation with the filesystem; tar1 writes files and directories to tape. - tar(1) does not support the full range of - options that are available from cpio(1), - but tar(1) does not require the unusual - command pipeline that cpio(1) uses. + tar1 does not support the full range of + options that are available from cpio1, + but tar1 does not require the unusual + command pipeline that cpio1 uses. - Most versions of tar(1) do not support + Most versions of tar1 do not support backups across the network. The GNU version of - tar(1), which FreeBSD utilizes, supports - remote devices using the same syntax as rdump. To tar(1) to + tar1, which FreeBSD utilizes, supports + remote devices using the same syntax as rdump. To tar1 to an Exabyte tape drive connected to a Sun called komodo, use: /usr/bin/tar cf komodo:/dev/nrst8 . 2>&1. For versions without remote device - support, you can use a pipeline and rsh(1) + support, you can use a pipeline and rsh1 to send the data to a remote tape drive. (XXX add an example command) @@ -16361,19 +16350,19 @@ Cpio - cpio(1) is the original Unix file + cpio1 is the original Unix file interchange tape program for magnetic media. - cpio(1) has options (among many others) to + cpio1 has options (among many others) to perform byte-swapping, write a number of different archives format, and pipe the data to other programs. This last feature - makes cpio(1) and excellent choice for - installation media. cpio(1) does not know + makes cpio1 and excellent choice for + installation media. cpio1 does not know how to walk the directory tree and a list of files must be provided thru STDIN. - cpio(1) does not support backups across + cpio1 does not support backups across the network. You can use a pipeline and - rsh(1) to send the data to a remote tape + rsh1 to send the data to a remote tape drive. (XXX add an example command) @@ -16381,7 +16370,7 @@ Pax - pax(1) is IEEE/POSIX's answer to + pax1 is IEEE/POSIX's answer to tar and cpio. Over the years the various versions of tar and cpio have gotten slightly incompatible. So rather than fight it out to fully standardize them, POSIX @@ -16448,11 +16437,11 @@ Which Backup Program is Best? - dump(8) Period. + dump8 Period. Elizabeth D. Zwicky torture tested all the backup programs discussed here. The clear choice for preserving all your data and all the peculiarities of Unix filesystems is - dump(8). Elizabeth created filesystems + dump8. Elizabeth created filesystems containing a large variety of unusual conditions (and some not so unusual ones) and tested each program by do a backup and restore of that filesystems. The peculiarities included: @@ -16490,11 +16479,11 @@ Otherwise, you have to create two custom bootable floppies which has a kernel that can mount your all of your disks and access your tape drive. These floppies must contain: - fdisk(8), disklabel(8), - newfs(8), mount(8), and + fdisk8, disklabel8, + newfs8, mount8, and whichever backup program you use. These programs must be - statically linked. If you use dump(8), the - floppy must contain restore(8). + statically linked. If you use dump8, the + floppy must contain restore8. Third, create backup tapes regularly. Any changes that you make after your last backup may be irretrievably lost. @@ -16609,11 +16598,10 @@ Recover each filesystem separately. - Try to mount(8) (e.g. mount /dev/sd0a - /mnt) the root partition of your first disk. If - the disklabel was damaged, use disklabel(8) + Try to mount8 (e.g. mount /dev/sd0a /mnt) the root partition of your first disk. If + the disklabel was damaged, use disklabel8 to re-partition and label the disk to match the label that - your printed and saved. Use newfs(8) to + your printed and saved. Use newfs8 to re-create the filesystems. Re-mount the root partition of the floppy read-write (mount -u -o rw /mnt). Use your backup program and backup tapes to recover the data @@ -16701,8 +16689,7 @@ This tuning means KOI8-R keyboard with Alternative screen font mapped to KOI8-R encoding to preserve pseudographics, Gray Delete - key remapped to match Russian termcap(5) entry for FreeBSD + key remapped to match Russian termcap5 entry for FreeBSD console. RUS/LAT switch will be LANG for POSIX - setlocale(3) family functions; + setlocale3 family functions; @@ -16750,8 +16737,8 @@ The best way is using /etc/login.conf russian user's login class in - passwd(5) entry login class - position. See login.conf(5) for + passwd5 entry login class + position. See login.conf5 for details. @@ -16768,9 +16755,9 @@ - How to do it with vipw(8) + How to do it with <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry> - If you use vipw(8) for adding new + If you use vipw8 for adding new users, /etc/master.passwd entry should looks like: user:password:1111:11:russian:0:0:User @@ -16780,9 +16767,9 @@ - How to do it with adduser(8) + How to do it with <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry> - If you use adduser(8) for adding new + If you use adduser8 for adding new users: @@ -16801,7 +16788,7 @@ remap=tt>russian each time when you see Enter login class: default []: prompt from - adduser(8); + adduser8; @@ -16817,9 +16804,9 @@ - How to do it with pw(8) + How to do it with <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry> - If you use pw(8) for adding new users, + If you use pw8 for adding new users, call it in this form: # pw useradd user_name -L russian @@ -16891,7 +16878,7 @@ printer /etc/printcap entry should looks like: lp|Russian local line printer:\ :sh:of=/usr/libexec/lpr/ru/koi2alt:\ - :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: see printcap(5) for detailed description. + :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: see printcap5 for detailed description. @@ -16899,11 +16886,10 @@ id="russian-msdosfs"> MSDOS FS and Russian file names - Look at following example fstab(5) entry to enable support for Russian + Look at following example fstab5 entry to enable support for Russian file names in MSDOS FS: /dev/sd0s1 /dos/c msdos rw,-W=koi2dos,-L=ru_RU.KOI8-R 0 0 see - mount_msdos(8) for detailed description of + mount_msdos8for detailed description of and options. @@ -17330,7 +17316,7 @@ - See the sio(4) manual page for more information. + See the sio4 manual page for more information. If you have connected a terminal to the first serial port (COM1 in DOS parlance), then you want to use @@ -17408,7 +17394,7 @@ As an optional step, you may wish to create a custom getty type for use in step 2 by making an entry in /etc/gettytab. This document does not explain how to do so; you are encouraged to see the - gettytab(5) and the getty(8) manual pages for more + gettytab5 and the getty8 manual pages for more information. The remaining sections detail how to do these steps. We will @@ -17420,7 +17406,7 @@ port on a multiport serial card). For more information on the /etc/ttys - file, see the ttys(5) manual page. + file, see the ttys5 manual page. std entry for each bps rate from 110 to 115200. Of course, you can add your own entries to this file. - The manual page gettytab(5) provides more information. + The manual page gettytab5 provides more information. When setting the getty type in the /etc/ttys file, make sure that the @@ -17528,7 +17514,7 @@ To find out what terminal types FreeBSD supports, see the file /usr/share/misc/termcap. It lists about 600 terminal types. You can add more if you wish. See - the termcap(5) manual page for information. + the termcap5 manual page for information. In our example, the Wyse-50 is a Wyse-50 type of terminal (although it can emulate others, we will leave it in Wyse-50 @@ -18011,8 +17997,7 @@ COM3:, and COM4:. FreeBSD can presently also handle dumb multiport serial interface cards, such as the Boca Board - 1008 and 2016 (please see the manual page sio(4) for kernel configuration information + 1008 and 2016 (please see the manual page sio4 for kernel configuration information if you have a multiport serial card). The default kernel only looks for the standard COM ports, though. @@ -18075,8 +18060,7 @@ You can comment-out or completely remove lines for devices you do not have. If you have a multiport serial board, such as the - Boca Board BB2016, please see the sio(4) man page for complete information on + Boca Board BB2016, please see the sio4 man page for complete information on how to write configuration lines for multiport boards. Be careful if you are using a configuration file that was previously used for a different version of FreeBSD because the device flags have @@ -18100,7 +18084,7 @@ When you are finished adjusting the kernel configuration file, use the program config as documented in Building Berkeley Kernels with Config and the - config(8) manual page to prepare a kernel + config8 manual page to prepare a kernel building directory, then build, install, and test the new kernel. @@ -18125,8 +18109,7 @@ modems which use CTS/RTS signaling for flow control. The locking devices are used to lock flags on ports to prevent users or programs changing certain parameters; see the - manual pages termios(4), sio(4), and stty(1) for + manual pages termios4, sio4, and stty1 for information on the terminal settings, locking & initializing devices, and setting terminal options, respectively. @@ -18136,7 +18119,7 @@ A shell script called MAKEDEV in the /dev directory manages the device special - files. (The manual page for MAKEDEV(8) on + files. (The manual page for MAKEDEV8 on FreeBSD 1.1.5 is fairly bogus in its discussion of COM ports, so ignore it.) To use MAKEDEV to make dialup device special files @@ -18232,10 +18215,9 @@ <filename>/etc/gettytab</filename> - /etc/gettytab is a termcap(5)-style file of configuration - information for getty(8). Please see the - gettytab(5) manual page for + /etc/gettytab is a termcap5-style file of configuration + information for getty8. Please see the + gettytab5 manual page for complete information on the format of the file and the list of capabilities. @@ -18343,7 +18325,7 @@ information to login (user root may only login on ttys marked secure). See the manual page for - ttys(5) for more + ttys5 for more information. You will need to either modify existing lines in @@ -19259,8 +19241,8 @@ If you have a kernel without the tun device, and you can not rebuild it for some reason, all is not lost. You should be able - to dynamically load the code. Refer to the appropriate modload(8) - and lkm(4) pages for further details. + to dynamically load the code. Refer to the appropriate modload8 + and lkm4 pages for further details. You may also wish to take this opportunity to configure a firewall. Details can be found in the The dial string. User ppp uses an expect-send - syntax similar to the chat(8) + syntax similar to the chat8 program. Refer to the manual page for information on the features of this language. @@ -20171,7 +20153,7 @@ details. Once a socket has been set up, the - pppctl(8) program may be used in scripts that + pppctl8 program may be used in scripts that wish to manipulate the running program. @@ -20362,7 +20344,7 @@ Create an entry in /etc/passwd - (using the vipw(8) program). + (using the vipw8 program). @@ -20977,12 +20959,12 @@ otherwise, check the place where you found this document for a document named dialup.txt or something similar. You may also want to check the manual pages for - sio(4) for information on the serial - port device driver and ttys(5), - gettytab(5), - getty(8), & init(8) for + sio4 for information on the serial + port device driver and ttys5, + gettytab5, + getty8, & init8 for information relevant to configuring the system to accept logins on - modems, and perhaps stty(1) for information on + modems, and perhaps stty1 for information on setting serial port parameters [such as clocal for directly-connected serial interfaces]. @@ -21060,8 +21042,8 @@ goes wrong, sliplogin usually logs good informational messages via the daemon syslog facility, which usually goes into /var/log/messages - (see the manual pages for syslogd(8) and - syslog.conf(5), and perhaps check + (see the manual pages for syslogd8 and + syslog.conf5, and perhaps check /etc/syslog.conf to see to which files syslogd is logging). @@ -21149,7 +21131,7 @@ As mentioned earlier, there are three files in the /etc/sliphome directory that are part of the configuration for /usr/sbin/sliplogin (see - sliplogin(8) for the actual manual page for + sliplogin8 for the actual manual page for sliplogin): slip.hosts, which defines the SLIP users & their associated IP addresses; @@ -21272,7 +21254,7 @@ SLIP server's Ethernet subnet, and you will also need to adjust your /etc/sliphome/slip.login and /etc/sliphome/slip.logout scripts to use - arp(8) to manage the proxy-ARP entries in the + arp8 to manage the proxy-ARP entries in the SLIP server's ARP table. @@ -21349,8 +21331,8 @@ netstat -i must be changed to colons and leading zeros should be added to each single-digit hexadecimal number to convert the address into the form that - arp(8) desires; see the manual page on - arp(8) for complete information on + arp8 desires; see the manual page on + arp8 for complete information on usage. @@ -21849,18 +21831,18 @@ Sometimes, there is a problem with routing propagation, and some sites are unable to connect to you. Perhaps the most useful command for trying to figure out where a routing is breaking down - is the traceroute(8) command. It is equally + is the traceroute8 command. It is equally useful if you cannot seem to make a connection to a remote machine - (ie. ping(8) fails). + (ie. ping8 fails). - The traceroute(8) command is run with the + The traceroute8 command is run with the name of the remote host you are trying to connect to. It will show the gateway hosts along the path of the attempt, eventually either reaching the target host, or terminating because of a lack of connection. For more information, see the manual page for - traceroute(8). + traceroute8. @@ -23378,7 +23360,7 @@ archive, any detected changes being compressed, stamped with a sequence-number and encoded for transmission over email (printable ASCII only). Once received, these "CTM deltas" can then be handed - to the ctm_rmail(1) utility which will automatically decode, verify + to the ctm_rmail1 utility which will automatically decode, verify and apply the changes to the user's copy of the sources. This process is far more efficient than CVSup, and places less strain on our server resources since it is a push rather @@ -24181,7 +24163,7 @@ the latest versions of the files on that line of development. If you wish to receive some past version, you can do so by specifying a date with the value - field. The cvsup(1) manual page explains how to do + field. The cvsup1 manual page explains how to do that. For our example, we wish to receive FreeBSD-current. @@ -24298,7 +24280,7 @@ alone. is ... arcane. If you really want to - know about it, see the cvsup(1) manual page. Otherwise, + know about it, see the cvsup1 manual page. Otherwise, just specify it and do not worry about it. enables the use of gzip-style compression @@ -24392,7 +24374,7 @@ see the manual page. Once you are satisfied with the way updates are working, you - can arrange for regular runs of cvsup using cron(8). Obviously, + can arrange for regular runs of cvsup using cron8. Obviously, you should not let cvsup use its GUI when running it from cron. @@ -25740,12 +25722,12 @@ information about this and other mailing lists. If you find a bug or are submitting a specific change, please - report it using the send-pr(1) program or its + report it using the send-pr1program or its WEB-based equivalent. Try to fill-in each field of the bug report. Unless they exceed 65KB, include any patches directly in the report. Consider compressing them and using - uuencode(1) if they exceed 20KB. + uuencode1 if they exceed 20KB. After filing a report, you should receive confirmation along with a tracking number. Keep this tracking number so that you can @@ -25754,7 +25736,7 @@ If you do not receive confirmation in a timely fashion (3 days to a week, depending on your email connection) or are, for some - reason, unable to use the send-pr(1) command, + reason, unable to use the send-pr1 command, then you may ask someone to file it for you by sending mail to the &a.bugs;. @@ -25794,7 +25776,7 @@ Assuming that you can manage to secure fairly up-to-date sources to base your changes on, the next step is to produce a set of diffs to send to the FreeBSD maintainers. This is done with - the diff(1) command, with the `context diff' + the diff1 command, with the `context diff' form being preferred. For example: diff -c oldfile newfile @@ -25803,11 +25785,11 @@ diff -c -r olddir newdir would generate such a set of context diffs for the given source file or directory hierarchy. See the man page - for diff(1) for more details. + for diff1 for more details. Once you have a set of diffs (which you may test with the - patch(1) command), you should submit them for - inclusion with FreeBSD. Use the send-pr(1) + patch1 command), you should submit them for + inclusion with FreeBSD. Use the send-pr1 program as described in . Do not just send the diffs to @@ -25818,14 +25800,14 @@ If you feel it appropriate (e.g. you have added, deleted, or renamed files), bundle your changes into a tar file and run the - uuencode(1) program on it. Shar archives are + uuencode1 program on it. Shar archives are also welcome. If your change is of a potentially sensitive nature, e.g. you are unsure of copyright issues governing its further distribution or you are simply not ready to release it without a tighter review first, then you should send it to &a.core; directly rather than - submitting it with send-pr(1). The core + submitting it with send-pr1. The core mailing list reaches a much smaller group of people who do much of the day-to-day work on FreeBSD. Note that this group is also very busy and so you should only send mail to @@ -26258,7 +26240,7 @@ - Refer to the pkg_create(1) man page + Refer to the pkg_create1 man page for details on the packing list. @@ -26303,7 +26285,7 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/ and send mail to us using - send-pr(1) (please classify it as category + send-pr1 (please classify it as category `ports' and class `change-request'). There is no need to upload the package, we will build it by ourselves. We will take a look, get back to you if necessary, and put it in the @@ -27362,7 +27344,7 @@ diff -ruN superedit.bak superedit). Please examine the output to make sure all the changes make sense. The best way to send us the - diff is by including it to send-pr(1) + diff is by including it to send-pr1 (category `ports'). Please mention any added or deleted files in the message, as they have to be explicitly specified to CVS when doing a commit. If the diff is more than about 20KB, please @@ -27508,7 +27490,7 @@ mode the script is being run in. The PKG_PREFIX environmental variable will be set to the package installation directory. See man - pkg_add(1) for additional + pkg_add1 for additional information. @@ -27527,8 +27509,8 @@ requirements script. It will be invoked automatically at installation/deinstallation time to determine whether or not installation/deinstallation should proceed. See man - pkg_create(1) and man - pkg_add(1) for more information. + pkg_create1 and man + pkg_add1 for more information. @@ -27706,7 +27688,7 @@ (executables for superusers/managers), info (documentation for info browser) or share (architecture independent - files). See man hier(7) for + files). See man hier7 for details, the rule governing /usr pretty much applies to /usr/local too. The exception are ports dealing with USENET `news'. They may use @@ -30588,10 +30570,10 @@ the supported options in the kernel into new-style ones, so for people who correctly did a make depend in their kernel compile directory after running - config(8), the build process will automatically + config8, the build process will automatically pick up modified options, and only recompile those files where it is necessary. Wiping out the old compile directory on each run of - config(8) as it is still done now can then be + config8 as it is still done now can then be eliminated again. Basically, a kernel option is nothing else than the definition @@ -30658,7 +30640,7 @@ using such an option is responsible himself for knowing about its implications (and maybe manually forcing the recompilation of parts of his kernel). Once the transition of all supported options has - been done, config(8) will warn whenever an + been done, config8 will warn whenever an unsupported option appears in the config file, but it will nevertheless include it into the kernel Makefile. @@ -30683,7 +30665,7 @@ opt_foo.h already available for the intended new option, invent a new name. Make it meaningful, and comment the new section in the - options[.<arch>] file. config(8) will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves.. + options[.<arch>] file. config8 will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves.. Packing too many options into a single opt_foo.h will cause @@ -30748,16 +30730,16 @@ is too small to hold the dump, you can configure your kernel to use an alternate dump device (in the config kernel line), or you can specify an alternate using the - dumpon(8) command. Dumps to non-swap devices, tapes for example, + dumpon8 command. Dumps to non-swap devices, tapes for example, are currently not supported. Config your kernel using config -g. See for details on configuring the FreeBSD kernel. - Use the dumpon(8) command to tell the kernel + Use the dumpon8 command to tell the kernel where to dump to (note that this will have to be done after configuring the partition in question as swap space via - swapon(8)). This is normally arranged via + swapon8). This is normally arranged via /etc/rc.conf and /etc/rc. Alternatively, you can hard-code the dump device via the `dump' clause in the `config' line of your kernel config file. This is @@ -30793,7 +30775,7 @@ fsck -p mount -a -t ufs # so your file system for /var/crash is writable savecore -N /kernel.panicked /var/crash exit # ...to multi-user - This instructs savecore(8) to + This instructs savecore8 to use another kernel for symbol name extraction. It would otherwise default to the currently running kernel and most likely not do anything at all since the crash dump and the kernel symbols @@ -30959,7 +30941,7 @@ generated code, so you will finally get a new kernel with similar code to the faulting one but some debugging symbols. You should at least verify the old and new sizes with the - size(1) command. If there is a mismatch, you + size1 command. If there is a mismatch, you probably need to give up here. Go and examine the dump as described above. The debugging @@ -31126,7 +31108,7 @@ call func(arg1, arg2, ...) The return value will be printed. - For a ps(1) style summary of all running + For a ps1 style summary of all running processes, use ps @@ -31167,7 +31149,7 @@ help However, it is highly recommended to have a - printed copy of the ddb(4) manual page + printed copy of the ddb4 manual page ready for a debugging session. Remember that it is hard to read the on-line manual while single-stepping the kernel. @@ -31694,7 +31676,7 @@ check if it needs shared libraries, and if so, whether you have them installed in the /compat/linux tree. To do this, you run the Linux version ldd on the new program, - and watch its output. ldd (see also the manual page for ldd(1)) + and watch its output. ldd (see also the manual page for ldd1) will print a list of shared libraries that the program depends on, in the form majorname (jumpversion) => fullname. @@ -35072,7 +35054,7 @@ Bug reports This is the mailing list for reporting bugs in FreeBSD Whenever - possible, bugs should be submitted using the send-pr(1) + possible, bugs should be submitted using the send-pr1 command or the WEB interface to it. diff --git a/en_US.ISO8859-1/books/handbook/book.sgml b/en_US.ISO8859-1/books/handbook/book.sgml index e2b9ccf732..7e0b598780 100644 --- a/en_US.ISO8859-1/books/handbook/book.sgml +++ b/en_US.ISO8859-1/books/handbook/book.sgml @@ -477,11 +477,10 @@ are the people who have write access to the CVS tree, and are thus authorized to make modifications to the FreeBSD source (the term committer comes from the - cvs(1) commit command, which is used to + cvs1 commit command, which is used to bring new changes into the CVS repository). The best way of making submissions for review by the committers list is to - use the send-pr(1) command, though if something appears to be jammed in the system then you may also reach them by sending mail to committers@freebsd.org. + use the send-pr1 command, though if something appears to be jammed in the system then you may also reach them by sending mail to committers@freebsd.org. @@ -1997,11 +1996,9 @@ command chmod. References to a particular section of the on-line manual are traditionally placed in - parenthesis in written documentation, so chmod(1) refers to the + parenthesis in written documentation, so chmod1 refers to the chmod - user command and chmod(2) refers to the + user command and chmod2 refers to the system call. This is fine if you know the name of the command and simply wish @@ -2041,7 +2038,7 @@ info command or, if you installed emacs, the info mode of emacs. - To use the info(1) command, simply type: + To use the info1 command, simply type: % info For a brief introduction, type Create a link tree to it using the - lndir(1) command that comes with the + lndir1 command that comes with the XFree86 distribution. Find a location with some free space, create a directory there and then cd to it. Then - invoke the lndir(1) command with the full + invoke the lndir1 command with the full pathname of the ports directory on the CDROM as the first argument and . (the current directory) as the second. This might be, for example, something like: lndir @@ -2599,7 +2596,7 @@ directory, though check your local mirror first, please! These are more likely to work (on the whole) than trying to compile from source and a lot faster besides! Use - the pkg_add(1) program to install a + the pkg_add1 program to install a package file on your system. @@ -3251,7 +3248,7 @@ If you are trying to upgrade your kernel from an older version of FreeBSD, you will probably have to get a new version of - config(8) from the same place you got the new + config8 from the same place you got the new kernel sources. It is located in /usr/src/usr.sbin, so you will need to download those sources as well. Re-build and install it before @@ -3561,7 +3558,7 @@ hundred bytes to the kernel. - The ipcs(1) command will tell + The ipcs1 command will tell will list any processes using each of these System V facilities. @@ -3635,7 +3632,7 @@ Process filesystem. This is a pretend filesystem mounted on /proc which allows - programs like ps(1) to give you more + programs like ps1 to give you more information on what processes are running. @@ -3742,7 +3739,7 @@ QIC-80 tape support requires a separate filter - program called ft(8), see the manual + program called ft8, see the manual page for details. @@ -4121,8 +4118,8 @@ serial port at COM2 you will have to change the IRQ of the modem to 2 (for obscure technical reasons IRQ 2 = IRQ 9) in order to access it from FreeBSD. If you have a - multiport serial card, check the manual page for sio(4) for more information on the + multiport serial card, check the manual page for + sio4 for more information on the proper values for these lines. Some video cards (notably those based on S3 chips) use IO addresses of the form 0x*2e8, and since many cheap serial @@ -4408,7 +4405,7 @@ network interfaces to be placed in promiscuous mode, capturing every packet on a broadcast network (e.g. an ethernet). These packets can be captured to disk and/or - examined with the tcpdump(1) program. + examined with the tcpdump1 program. Note that implementation of this capability can seriously compromise your overall network security. The number after bpfilter is the number @@ -4607,7 +4604,7 @@ Snoop device. This pseudo-device allows one terminal session to watch another using the - watch(8) command. Note that + watch8 command. Note that implementation of this capability has important security and privacy implications. The number after snp is the total number of simultaneous snoop @@ -4619,7 +4616,7 @@ Vnode driver. Allows a file to be treated as a device - after being set up with the vnconfig(8) + after being set up with the vnconfig8 command. This driver can be useful for manipulating floppy disk images and using a file as a swap device (e.g. an MS Windows swap file). Optional. @@ -4635,8 +4632,8 @@ meta-disk. The number after ccd is the total number of concatenated disks (not total number of disks that can be concatenated) that can be - created. (See ccd(4) and - ccdconfig(8) man pages for more + created. (See ccd4 and + ccdconfig8 man pages for more details.) Optional. @@ -4801,7 +4798,7 @@ resource is the /var/log/messages file which records, among other things, all of the kernel messages from every successful boot. Also, the - dmesg(8) command will print the kernel + dmesg8 command will print the kernel messages from the current boot. @@ -4814,7 +4811,7 @@ with the last installed kernel which may be non-functional. Also, as soon as possible, move the working kernel to the proper kernel location or - commands such as ps(1) will not work + commands such as ps1 will not work properly. The proper command to unlock the kernel file that make installs (in order to move another kernel back permanently) is: @@ -4839,7 +4836,7 @@ from the one that the system utilities have been built with, for example, an experimental 2.2.0 kernel on a 2.1.0-RELEASE system, many system-status commands like - ps(1) and vmstat(8) + ps1 and vmstat8 will not work any more. You must recompile the libkvm library as well as these utilities. This is one reason it is not normally a good @@ -5862,7 +5859,7 @@ IPFW, the software supplied with FreeBSD, is a packet filtering and accounting system which resides in the kernel, and has a user-land control utility, - ipfw(8). Together, they allow you to define and + ipfw8. Together, they allow you to define and query the rules currently used by the kernel in its routing decisions. @@ -5909,7 +5906,7 @@ Enables code to allow logging of packets through - syslogd(8). Without this option, even + syslogd8. Without this option, even if you specify that packets should be logged in the filter rules, nothing will happen. @@ -5919,7 +5916,7 @@ Limits the number of packets logged through - syslogd(8) on a per entry basis. You + syslogd8 on a per entry basis. You may wish to use this option in hostile environments in which you want to log firewall activity, but do not want to be open to a denial of service attack via syslog @@ -5928,7 +5925,7 @@ When a chain entry reaches the packet limit specified, logging is turned off for that particular entry. To resume logging, you will need to reset the associated - counter using the ipfw(8) + counter using the ipfw8 utility: @@ -5955,7 +5952,7 @@ Configuring IPFW The configuration of the IPFW software is - done through the ipfw(8) utility. The syntax + done through the ipfw8 utility. The syntax for this command looks quite complicated, but it is relatively simple once you understand its structure. @@ -6256,7 +6253,7 @@ remap=bf>8 echo request (ping request), and 11 time exceeded (used to indicate TTL expiration as with - traceroute(8)). + traceroute8). @@ -6290,7 +6287,7 @@ Display the last match times for each chain entry. The time listing is incompatible with the input syntax - used by the ipfw(8) utility. + used by the ipfw8 utility. @@ -7163,8 +7160,7 @@ You could put these commands in your /etc/rc.local file to set the mode each - time your system boots. See lptcontrol(8) for more information. + time your system boots. See lptcontrol8 for more information. @@ -7405,7 +7401,7 @@ file take immediate effect. The format of the printcap file is straightforward. Use your favorite text editor to make changes to /etc/printcap. The format is identical to other capability files like /usr/share/misc/termcap and /etc/remote. For complete information about the format, see the cgetent(3). + URL="http://www.freebsd.org/cgi/man.cgi?printcap">printcap file is straightforward. Use your favorite text editor to make changes to /etc/printcap. The format is identical to other capability files like /usr/share/misc/termcap and /etc/remote. For complete information about the format, see the cgetent3. The simple spooler configuration consists of the following steps: @@ -8596,8 +8592,7 @@ Format plain text with pr - before printing. See pr(1) for more information. + before printing. See pr1 for more information. @@ -10665,8 +10660,7 @@ The format of these files is simple: one host name per line. Note that the file /etc/hosts.equiv is also used by - the ruserok(3) protocol, and affects programs like rsh and rcp, so be careful. + the ruserok3 protocol, and affects programs like rsh and rcp, so be careful. For example, here is the /etc/hosts.lpd file on the host @@ -13055,8 +13049,7 @@ The sio driver provides support for NS8250-, NS16450-, NS16550 and NS16550A-based EIA RS-232C (CCITT V.24) communications interfaces. Several - multiport cards are supported as well. See the sio(4) manual page for detailed technical + multiport cards are supported as well. See the sio4 manual page for detailed technical documentation. @@ -13151,8 +13144,7 @@ xxx lines are, you will need to add 16 more devices. Only the last device includes the interrupt vector for the - board. (See the sio(4) manual page for detail as + board. (See the sio4 manual page for detail as to why.) The following example is for a Boca Board with an interrupt of 3, and a base IO address 100h. The IO address for Each port is +8 hexadecimal from the @@ -14822,7 +14814,7 @@ address of the device that is failing, and the desired debug level in /sys/scsi/scsidebug.h. If it probes but just does not work, you can use the - scsi(8) command to dynamically set a + scsi8 command to dynamically set a debug level to it in a running kernel (if SCSIDEBUG is defined). This will give you COPIOUS debugging output with which to confuse the gurus. see man 4 @@ -15129,11 +15121,11 @@ General tape access commands - mt(1) provides generic access to the tape + mt1 provides generic access to the tape drives. Some of the more common commands are rewind, erase, and status. See the mt(1) + remap=tt>status. See the mt1 manual page for a detailed description. @@ -15153,12 +15145,12 @@ SCSI drives - The st(4) driver provides + The st4 driver provides support for 8mm (Exabyte), 4mm (DAT: Digital Audio Tape), QIC (Quarter-Inch Cartridge), DLT (Digital Linear Tape), QIC Minicartridge and 9-track (remember the big reels that you see spinning in Hollywood computer rooms) tape drives. See the - st(4) manual page for a detailed + st4 manual page for a detailed description. The drives listed below are currently being used by members @@ -15306,7 +15298,7 @@ and QIC-525 (DC6525) tapes as well. Data transfer rate is 350kB/s using - dump(8). Rates of 530kB/s have been + dump8. Rates of 530kB/s have been reported when using @@ -15413,8 +15405,7 @@ (250MB) tapes. This drives quirks are known and pre-compiled into the - scsi tape device driver (st(4)). + scsi tape device driver (st4). Under FreeBSD 2.2-current, use mt blocksize 512 to set the blocksize. (The @@ -15920,8 +15911,7 @@ Native capacity is 150/250MB. This drive has quirks which are known and work around code - is present in the scsi tape device driver (st(4)). Upgrading the firmware to XXX + is present in the scsi tape device driver (st4). Upgrading the firmware to XXX version will fix the quirks and provide SCSI 2 capabilities. @@ -15964,7 +15954,7 @@ supported for the 2.5 GB cartridges. This drives quirks are known and pre-compiled into the - scsi tape device driver (st(4)) + scsi tape device driver (st4) beginning with FreeBSD 2.2-current. For previous versions of FreeBSD, use mt to read one block from the tape, rewind the tape, and then execute the @@ -16004,8 +15994,7 @@ erased. This drives quirks are known and pre-compiled into the - scsi tape device driver (st(4)). + scsi tape device driver (st4). Other firmware revisions that are known to work are: M75D @@ -16268,10 +16257,10 @@ Use the front panel button to eject the tape. - Re-insert the tape and dump(8) data to + Re-insert the tape and dump8 data to the tape. - dump(8) will report dump8 will report DUMP: End of tape detected and the console will show: HARDWARE FAILURE info:280 asc:80,96 @@ -16286,42 +16275,42 @@ Backup Programs - The three major programs are dump(8), - tar(1), and - cpio(1). + The three major programs are dump8, + tar1, and + cpio1. Dump and Restore - dump(8) and - restore(8) are the traditional Unix backup + dump8 and + restore8 are the traditional Unix backup programs. They operate on the drive as a collection of disk blocks, below the abstractions of files, links and directories that are created by the filesystems. - dump(8) backs up devices, entire + dump8 backs up devices, entire filesystems, not parts of a filesystem and not directory trees that span more than one filesystem, using either soft links - ln(1) or mounting one filesystem onto - another. dump(8) does not write files and + ln1 or mounting one filesystem onto + another. dump8 does not write files and directories to tape, but rather writes the data blocks that are the building blocks of files and directories. - dump(8) has quirks that remain from its + dump8 has quirks that remain from its early days in Version 6 of ATT Unix (circa 1975). The default parameters are suitable for 9-track tapes (6250 bpi), not the high-density media available today (up to 62,182 ftpi). These defaults must be overridden on the command line to utilize the capacity of current tape drives. - rdump(8) and - rrestore(8) backup data across the network + rdump8 and + rrestore8 backup data across the network to a tape drive attached to another computer. Both programs - rely upon rcmd(3) and - ruserok(3) to access the remote tape + rely upon rcmd3 and + ruserok3 to access the remote tape drive. Therefore, the user performing the backup must have rhosts access to the remote - computer. The arguments to rdump(8) and - rrestore(8) must suitable to use on the + computer. The arguments to rdump8 and + rrestore8 must suitable to use on the remote computer. (e.g. When rdump'ing from a FreeBSD computer to an Exabyte tape drive connected to a Sun called komodo, use: /sbin/rdump 0dsbfu 54000 13000 126 @@ -16335,24 +16324,24 @@ Tar - tar(1) also dates back to Version 6 of - ATT Unix (circa 1975). tar(1) operates in - cooperation with the filesystem; tar(1) + tar1 also dates back to Version 6 of + ATT Unix (circa 1975). tar1 operates in + cooperation with the filesystem; tar1 writes files and directories to tape. - tar(1) does not support the full range of - options that are available from cpio(1), - but tar(1) does not require the unusual - command pipeline that cpio(1) uses. + tar1 does not support the full range of + options that are available from cpio1, + but tar1 does not require the unusual + command pipeline that cpio1 uses. - Most versions of tar(1) do not support + Most versions of tar1 do not support backups across the network. The GNU version of - tar(1), which FreeBSD utilizes, supports - remote devices using the same syntax as rdump. To tar(1) to + tar1, which FreeBSD utilizes, supports + remote devices using the same syntax as rdump. To tar1 to an Exabyte tape drive connected to a Sun called komodo, use: /usr/bin/tar cf komodo:/dev/nrst8 . 2>&1. For versions without remote device - support, you can use a pipeline and rsh(1) + support, you can use a pipeline and rsh1 to send the data to a remote tape drive. (XXX add an example command) @@ -16361,19 +16350,19 @@ Cpio - cpio(1) is the original Unix file + cpio1 is the original Unix file interchange tape program for magnetic media. - cpio(1) has options (among many others) to + cpio1 has options (among many others) to perform byte-swapping, write a number of different archives format, and pipe the data to other programs. This last feature - makes cpio(1) and excellent choice for - installation media. cpio(1) does not know + makes cpio1 and excellent choice for + installation media. cpio1 does not know how to walk the directory tree and a list of files must be provided thru STDIN. - cpio(1) does not support backups across + cpio1 does not support backups across the network. You can use a pipeline and - rsh(1) to send the data to a remote tape + rsh1 to send the data to a remote tape drive. (XXX add an example command) @@ -16381,7 +16370,7 @@ Pax - pax(1) is IEEE/POSIX's answer to + pax1 is IEEE/POSIX's answer to tar and cpio. Over the years the various versions of tar and cpio have gotten slightly incompatible. So rather than fight it out to fully standardize them, POSIX @@ -16448,11 +16437,11 @@ Which Backup Program is Best? - dump(8) Period. + dump8 Period. Elizabeth D. Zwicky torture tested all the backup programs discussed here. The clear choice for preserving all your data and all the peculiarities of Unix filesystems is - dump(8). Elizabeth created filesystems + dump8. Elizabeth created filesystems containing a large variety of unusual conditions (and some not so unusual ones) and tested each program by do a backup and restore of that filesystems. The peculiarities included: @@ -16490,11 +16479,11 @@ Otherwise, you have to create two custom bootable floppies which has a kernel that can mount your all of your disks and access your tape drive. These floppies must contain: - fdisk(8), disklabel(8), - newfs(8), mount(8), and + fdisk8, disklabel8, + newfs8, mount8, and whichever backup program you use. These programs must be - statically linked. If you use dump(8), the - floppy must contain restore(8). + statically linked. If you use dump8, the + floppy must contain restore8. Third, create backup tapes regularly. Any changes that you make after your last backup may be irretrievably lost. @@ -16609,11 +16598,10 @@ Recover each filesystem separately. - Try to mount(8) (e.g. mount /dev/sd0a - /mnt) the root partition of your first disk. If - the disklabel was damaged, use disklabel(8) + Try to mount8 (e.g. mount /dev/sd0a /mnt) the root partition of your first disk. If + the disklabel was damaged, use disklabel8 to re-partition and label the disk to match the label that - your printed and saved. Use newfs(8) to + your printed and saved. Use newfs8 to re-create the filesystems. Re-mount the root partition of the floppy read-write (mount -u -o rw /mnt). Use your backup program and backup tapes to recover the data @@ -16701,8 +16689,7 @@ This tuning means KOI8-R keyboard with Alternative screen font mapped to KOI8-R encoding to preserve pseudographics, Gray Delete - key remapped to match Russian termcap(5) entry for FreeBSD + key remapped to match Russian termcap5 entry for FreeBSD console. RUS/LAT switch will be LANG for POSIX - setlocale(3) family functions; + setlocale3 family functions; @@ -16750,8 +16737,8 @@ The best way is using /etc/login.conf russian user's login class in - passwd(5) entry login class - position. See login.conf(5) for + passwd5 entry login class + position. See login.conf5 for details. @@ -16768,9 +16755,9 @@ - How to do it with vipw(8) + How to do it with <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry> - If you use vipw(8) for adding new + If you use vipw8 for adding new users, /etc/master.passwd entry should looks like: user:password:1111:11:russian:0:0:User @@ -16780,9 +16767,9 @@ - How to do it with adduser(8) + How to do it with <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry> - If you use adduser(8) for adding new + If you use adduser8 for adding new users: @@ -16801,7 +16788,7 @@ remap=tt>russian each time when you see Enter login class: default []: prompt from - adduser(8); + adduser8; @@ -16817,9 +16804,9 @@ - How to do it with pw(8) + How to do it with <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry> - If you use pw(8) for adding new users, + If you use pw8 for adding new users, call it in this form: # pw useradd user_name -L russian @@ -16891,7 +16878,7 @@ printer /etc/printcap entry should looks like: lp|Russian local line printer:\ :sh:of=/usr/libexec/lpr/ru/koi2alt:\ - :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: see printcap(5) for detailed description. + :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: see printcap5 for detailed description. @@ -16899,11 +16886,10 @@ id="russian-msdosfs"> MSDOS FS and Russian file names - Look at following example fstab(5) entry to enable support for Russian + Look at following example fstab5 entry to enable support for Russian file names in MSDOS FS: /dev/sd0s1 /dos/c msdos rw,-W=koi2dos,-L=ru_RU.KOI8-R 0 0 see - mount_msdos(8) for detailed description of + mount_msdos8for detailed description of and options. @@ -17330,7 +17316,7 @@ - See the sio(4) manual page for more information. + See the sio4 manual page for more information. If you have connected a terminal to the first serial port (COM1 in DOS parlance), then you want to use @@ -17408,7 +17394,7 @@ As an optional step, you may wish to create a custom getty type for use in step 2 by making an entry in /etc/gettytab. This document does not explain how to do so; you are encouraged to see the - gettytab(5) and the getty(8) manual pages for more + gettytab5 and the getty8 manual pages for more information. The remaining sections detail how to do these steps. We will @@ -17420,7 +17406,7 @@ port on a multiport serial card). For more information on the /etc/ttys - file, see the ttys(5) manual page. + file, see the ttys5 manual page. std entry for each bps rate from 110 to 115200. Of course, you can add your own entries to this file. - The manual page gettytab(5) provides more information. + The manual page gettytab5 provides more information. When setting the getty type in the /etc/ttys file, make sure that the @@ -17528,7 +17514,7 @@ To find out what terminal types FreeBSD supports, see the file /usr/share/misc/termcap. It lists about 600 terminal types. You can add more if you wish. See - the termcap(5) manual page for information. + the termcap5 manual page for information. In our example, the Wyse-50 is a Wyse-50 type of terminal (although it can emulate others, we will leave it in Wyse-50 @@ -18011,8 +17997,7 @@ COM3:, and COM4:. FreeBSD can presently also handle dumb multiport serial interface cards, such as the Boca Board - 1008 and 2016 (please see the manual page sio(4) for kernel configuration information + 1008 and 2016 (please see the manual page sio4 for kernel configuration information if you have a multiport serial card). The default kernel only looks for the standard COM ports, though. @@ -18075,8 +18060,7 @@ You can comment-out or completely remove lines for devices you do not have. If you have a multiport serial board, such as the - Boca Board BB2016, please see the sio(4) man page for complete information on + Boca Board BB2016, please see the sio4 man page for complete information on how to write configuration lines for multiport boards. Be careful if you are using a configuration file that was previously used for a different version of FreeBSD because the device flags have @@ -18100,7 +18084,7 @@ When you are finished adjusting the kernel configuration file, use the program config as documented in Building Berkeley Kernels with Config and the - config(8) manual page to prepare a kernel + config8 manual page to prepare a kernel building directory, then build, install, and test the new kernel. @@ -18125,8 +18109,7 @@ modems which use CTS/RTS signaling for flow control. The locking devices are used to lock flags on ports to prevent users or programs changing certain parameters; see the - manual pages termios(4), sio(4), and stty(1) for + manual pages termios4, sio4, and stty1 for information on the terminal settings, locking & initializing devices, and setting terminal options, respectively. @@ -18136,7 +18119,7 @@ A shell script called MAKEDEV in the /dev directory manages the device special - files. (The manual page for MAKEDEV(8) on + files. (The manual page for MAKEDEV8 on FreeBSD 1.1.5 is fairly bogus in its discussion of COM ports, so ignore it.) To use MAKEDEV to make dialup device special files @@ -18232,10 +18215,9 @@ <filename>/etc/gettytab</filename> - /etc/gettytab is a termcap(5)-style file of configuration - information for getty(8). Please see the - gettytab(5) manual page for + /etc/gettytab is a termcap5-style file of configuration + information for getty8. Please see the + gettytab5 manual page for complete information on the format of the file and the list of capabilities. @@ -18343,7 +18325,7 @@ information to login (user root may only login on ttys marked secure). See the manual page for - ttys(5) for more + ttys5 for more information. You will need to either modify existing lines in @@ -19259,8 +19241,8 @@ If you have a kernel without the tun device, and you can not rebuild it for some reason, all is not lost. You should be able - to dynamically load the code. Refer to the appropriate modload(8) - and lkm(4) pages for further details. + to dynamically load the code. Refer to the appropriate modload8 + and lkm4 pages for further details. You may also wish to take this opportunity to configure a firewall. Details can be found in the The dial string. User ppp uses an expect-send - syntax similar to the chat(8) + syntax similar to the chat8 program. Refer to the manual page for information on the features of this language. @@ -20171,7 +20153,7 @@ details. Once a socket has been set up, the - pppctl(8) program may be used in scripts that + pppctl8 program may be used in scripts that wish to manipulate the running program. @@ -20362,7 +20344,7 @@ Create an entry in /etc/passwd - (using the vipw(8) program). + (using the vipw8 program). @@ -20977,12 +20959,12 @@ otherwise, check the place where you found this document for a document named dialup.txt or something similar. You may also want to check the manual pages for - sio(4) for information on the serial - port device driver and ttys(5), - gettytab(5), - getty(8), & init(8) for + sio4 for information on the serial + port device driver and ttys5, + gettytab5, + getty8, & init8 for information relevant to configuring the system to accept logins on - modems, and perhaps stty(1) for information on + modems, and perhaps stty1 for information on setting serial port parameters [such as clocal for directly-connected serial interfaces]. @@ -21060,8 +21042,8 @@ goes wrong, sliplogin usually logs good informational messages via the daemon syslog facility, which usually goes into /var/log/messages - (see the manual pages for syslogd(8) and - syslog.conf(5), and perhaps check + (see the manual pages for syslogd8 and + syslog.conf5, and perhaps check /etc/syslog.conf to see to which files syslogd is logging). @@ -21149,7 +21131,7 @@ As mentioned earlier, there are three files in the /etc/sliphome directory that are part of the configuration for /usr/sbin/sliplogin (see - sliplogin(8) for the actual manual page for + sliplogin8 for the actual manual page for sliplogin): slip.hosts, which defines the SLIP users & their associated IP addresses; @@ -21272,7 +21254,7 @@ SLIP server's Ethernet subnet, and you will also need to adjust your /etc/sliphome/slip.login and /etc/sliphome/slip.logout scripts to use - arp(8) to manage the proxy-ARP entries in the + arp8 to manage the proxy-ARP entries in the SLIP server's ARP table. @@ -21349,8 +21331,8 @@ netstat -i must be changed to colons and leading zeros should be added to each single-digit hexadecimal number to convert the address into the form that - arp(8) desires; see the manual page on - arp(8) for complete information on + arp8 desires; see the manual page on + arp8 for complete information on usage. @@ -21849,18 +21831,18 @@ Sometimes, there is a problem with routing propagation, and some sites are unable to connect to you. Perhaps the most useful command for trying to figure out where a routing is breaking down - is the traceroute(8) command. It is equally + is the traceroute8 command. It is equally useful if you cannot seem to make a connection to a remote machine - (ie. ping(8) fails). + (ie. ping8 fails). - The traceroute(8) command is run with the + The traceroute8 command is run with the name of the remote host you are trying to connect to. It will show the gateway hosts along the path of the attempt, eventually either reaching the target host, or terminating because of a lack of connection. For more information, see the manual page for - traceroute(8). + traceroute8. @@ -23378,7 +23360,7 @@ archive, any detected changes being compressed, stamped with a sequence-number and encoded for transmission over email (printable ASCII only). Once received, these "CTM deltas" can then be handed - to the ctm_rmail(1) utility which will automatically decode, verify + to the ctm_rmail1 utility which will automatically decode, verify and apply the changes to the user's copy of the sources. This process is far more efficient than CVSup, and places less strain on our server resources since it is a push rather @@ -24181,7 +24163,7 @@ the latest versions of the files on that line of development. If you wish to receive some past version, you can do so by specifying a date with the value - field. The cvsup(1) manual page explains how to do + field. The cvsup1 manual page explains how to do that. For our example, we wish to receive FreeBSD-current. @@ -24298,7 +24280,7 @@ alone. is ... arcane. If you really want to - know about it, see the cvsup(1) manual page. Otherwise, + know about it, see the cvsup1 manual page. Otherwise, just specify it and do not worry about it. enables the use of gzip-style compression @@ -24392,7 +24374,7 @@ see the manual page. Once you are satisfied with the way updates are working, you - can arrange for regular runs of cvsup using cron(8). Obviously, + can arrange for regular runs of cvsup using cron8. Obviously, you should not let cvsup use its GUI when running it from cron. @@ -25740,12 +25722,12 @@ information about this and other mailing lists. If you find a bug or are submitting a specific change, please - report it using the send-pr(1) program or its + report it using the send-pr1program or its WEB-based equivalent. Try to fill-in each field of the bug report. Unless they exceed 65KB, include any patches directly in the report. Consider compressing them and using - uuencode(1) if they exceed 20KB. + uuencode1 if they exceed 20KB. After filing a report, you should receive confirmation along with a tracking number. Keep this tracking number so that you can @@ -25754,7 +25736,7 @@ If you do not receive confirmation in a timely fashion (3 days to a week, depending on your email connection) or are, for some - reason, unable to use the send-pr(1) command, + reason, unable to use the send-pr1 command, then you may ask someone to file it for you by sending mail to the &a.bugs;. @@ -25794,7 +25776,7 @@ Assuming that you can manage to secure fairly up-to-date sources to base your changes on, the next step is to produce a set of diffs to send to the FreeBSD maintainers. This is done with - the diff(1) command, with the `context diff' + the diff1 command, with the `context diff' form being preferred. For example: diff -c oldfile newfile @@ -25803,11 +25785,11 @@ diff -c -r olddir newdir would generate such a set of context diffs for the given source file or directory hierarchy. See the man page - for diff(1) for more details. + for diff1 for more details. Once you have a set of diffs (which you may test with the - patch(1) command), you should submit them for - inclusion with FreeBSD. Use the send-pr(1) + patch1 command), you should submit them for + inclusion with FreeBSD. Use the send-pr1 program as described in . Do not just send the diffs to @@ -25818,14 +25800,14 @@ If you feel it appropriate (e.g. you have added, deleted, or renamed files), bundle your changes into a tar file and run the - uuencode(1) program on it. Shar archives are + uuencode1 program on it. Shar archives are also welcome. If your change is of a potentially sensitive nature, e.g. you are unsure of copyright issues governing its further distribution or you are simply not ready to release it without a tighter review first, then you should send it to &a.core; directly rather than - submitting it with send-pr(1). The core + submitting it with send-pr1. The core mailing list reaches a much smaller group of people who do much of the day-to-day work on FreeBSD. Note that this group is also very busy and so you should only send mail to @@ -26258,7 +26240,7 @@ - Refer to the pkg_create(1) man page + Refer to the pkg_create1 man page for details on the packing list. @@ -26303,7 +26285,7 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/ and send mail to us using - send-pr(1) (please classify it as category + send-pr1 (please classify it as category `ports' and class `change-request'). There is no need to upload the package, we will build it by ourselves. We will take a look, get back to you if necessary, and put it in the @@ -27362,7 +27344,7 @@ diff -ruN superedit.bak superedit). Please examine the output to make sure all the changes make sense. The best way to send us the - diff is by including it to send-pr(1) + diff is by including it to send-pr1 (category `ports'). Please mention any added or deleted files in the message, as they have to be explicitly specified to CVS when doing a commit. If the diff is more than about 20KB, please @@ -27508,7 +27490,7 @@ mode the script is being run in. The PKG_PREFIX environmental variable will be set to the package installation directory. See man - pkg_add(1) for additional + pkg_add1 for additional information. @@ -27527,8 +27509,8 @@ requirements script. It will be invoked automatically at installation/deinstallation time to determine whether or not installation/deinstallation should proceed. See man - pkg_create(1) and man - pkg_add(1) for more information. + pkg_create1 and man + pkg_add1 for more information. @@ -27706,7 +27688,7 @@ (executables for superusers/managers), info (documentation for info browser) or share (architecture independent - files). See man hier(7) for + files). See man hier7 for details, the rule governing /usr pretty much applies to /usr/local too. The exception are ports dealing with USENET `news'. They may use @@ -30588,10 +30570,10 @@ the supported options in the kernel into new-style ones, so for people who correctly did a make depend in their kernel compile directory after running - config(8), the build process will automatically + config8, the build process will automatically pick up modified options, and only recompile those files where it is necessary. Wiping out the old compile directory on each run of - config(8) as it is still done now can then be + config8 as it is still done now can then be eliminated again. Basically, a kernel option is nothing else than the definition @@ -30658,7 +30640,7 @@ using such an option is responsible himself for knowing about its implications (and maybe manually forcing the recompilation of parts of his kernel). Once the transition of all supported options has - been done, config(8) will warn whenever an + been done, config8 will warn whenever an unsupported option appears in the config file, but it will nevertheless include it into the kernel Makefile. @@ -30683,7 +30665,7 @@ opt_foo.h already available for the intended new option, invent a new name. Make it meaningful, and comment the new section in the - options[.<arch>] file. config(8) will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves.. + options[.<arch>] file. config8 will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves.. Packing too many options into a single opt_foo.h will cause @@ -30748,16 +30730,16 @@ is too small to hold the dump, you can configure your kernel to use an alternate dump device (in the config kernel line), or you can specify an alternate using the - dumpon(8) command. Dumps to non-swap devices, tapes for example, + dumpon8 command. Dumps to non-swap devices, tapes for example, are currently not supported. Config your kernel using config -g. See for details on configuring the FreeBSD kernel. - Use the dumpon(8) command to tell the kernel + Use the dumpon8 command to tell the kernel where to dump to (note that this will have to be done after configuring the partition in question as swap space via - swapon(8)). This is normally arranged via + swapon8). This is normally arranged via /etc/rc.conf and /etc/rc. Alternatively, you can hard-code the dump device via the `dump' clause in the `config' line of your kernel config file. This is @@ -30793,7 +30775,7 @@ fsck -p mount -a -t ufs # so your file system for /var/crash is writable savecore -N /kernel.panicked /var/crash exit # ...to multi-user - This instructs savecore(8) to + This instructs savecore8 to use another kernel for symbol name extraction. It would otherwise default to the currently running kernel and most likely not do anything at all since the crash dump and the kernel symbols @@ -30959,7 +30941,7 @@ generated code, so you will finally get a new kernel with similar code to the faulting one but some debugging symbols. You should at least verify the old and new sizes with the - size(1) command. If there is a mismatch, you + size1 command. If there is a mismatch, you probably need to give up here. Go and examine the dump as described above. The debugging @@ -31126,7 +31108,7 @@ call func(arg1, arg2, ...) The return value will be printed. - For a ps(1) style summary of all running + For a ps1 style summary of all running processes, use ps @@ -31167,7 +31149,7 @@ help However, it is highly recommended to have a - printed copy of the ddb(4) manual page + printed copy of the ddb4 manual page ready for a debugging session. Remember that it is hard to read the on-line manual while single-stepping the kernel. @@ -31694,7 +31676,7 @@ check if it needs shared libraries, and if so, whether you have them installed in the /compat/linux tree. To do this, you run the Linux version ldd on the new program, - and watch its output. ldd (see also the manual page for ldd(1)) + and watch its output. ldd (see also the manual page for ldd1) will print a list of shared libraries that the program depends on, in the form majorname (jumpversion) => fullname. @@ -35072,7 +35054,7 @@ Bug reports This is the mailing list for reporting bugs in FreeBSD Whenever - possible, bugs should be submitted using the send-pr(1) + possible, bugs should be submitted using the send-pr1 command or the WEB interface to it. diff --git a/en_US.ISO_8859-1/books/handbook/book.sgml b/en_US.ISO_8859-1/books/handbook/book.sgml index e2b9ccf732..7e0b598780 100644 --- a/en_US.ISO_8859-1/books/handbook/book.sgml +++ b/en_US.ISO_8859-1/books/handbook/book.sgml @@ -477,11 +477,10 @@ are the people who have write access to the CVS tree, and are thus authorized to make modifications to the FreeBSD source (the term committer comes from the - cvs(1) commit command, which is used to + cvs1 commit command, which is used to bring new changes into the CVS repository). The best way of making submissions for review by the committers list is to - use the send-pr(1) command, though if something appears to be jammed in the system then you may also reach them by sending mail to committers@freebsd.org. + use the send-pr1 command, though if something appears to be jammed in the system then you may also reach them by sending mail to committers@freebsd.org. @@ -1997,11 +1996,9 @@ command chmod. References to a particular section of the on-line manual are traditionally placed in - parenthesis in written documentation, so chmod(1) refers to the + parenthesis in written documentation, so chmod1 refers to the chmod - user command and chmod(2) refers to the + user command and chmod2 refers to the system call. This is fine if you know the name of the command and simply wish @@ -2041,7 +2038,7 @@ info command or, if you installed emacs, the info mode of emacs. - To use the info(1) command, simply type: + To use the info1 command, simply type: % info For a brief introduction, type Create a link tree to it using the - lndir(1) command that comes with the + lndir1 command that comes with the XFree86 distribution. Find a location with some free space, create a directory there and then cd to it. Then - invoke the lndir(1) command with the full + invoke the lndir1 command with the full pathname of the ports directory on the CDROM as the first argument and . (the current directory) as the second. This might be, for example, something like: lndir @@ -2599,7 +2596,7 @@ directory, though check your local mirror first, please! These are more likely to work (on the whole) than trying to compile from source and a lot faster besides! Use - the pkg_add(1) program to install a + the pkg_add1 program to install a package file on your system. @@ -3251,7 +3248,7 @@ If you are trying to upgrade your kernel from an older version of FreeBSD, you will probably have to get a new version of - config(8) from the same place you got the new + config8 from the same place you got the new kernel sources. It is located in /usr/src/usr.sbin, so you will need to download those sources as well. Re-build and install it before @@ -3561,7 +3558,7 @@ hundred bytes to the kernel. - The ipcs(1) command will tell + The ipcs1 command will tell will list any processes using each of these System V facilities. @@ -3635,7 +3632,7 @@ Process filesystem. This is a pretend filesystem mounted on /proc which allows - programs like ps(1) to give you more + programs like ps1 to give you more information on what processes are running. @@ -3742,7 +3739,7 @@ QIC-80 tape support requires a separate filter - program called ft(8), see the manual + program called ft8, see the manual page for details. @@ -4121,8 +4118,8 @@ serial port at COM2 you will have to change the IRQ of the modem to 2 (for obscure technical reasons IRQ 2 = IRQ 9) in order to access it from FreeBSD. If you have a - multiport serial card, check the manual page for sio(4) for more information on the + multiport serial card, check the manual page for + sio4 for more information on the proper values for these lines. Some video cards (notably those based on S3 chips) use IO addresses of the form 0x*2e8, and since many cheap serial @@ -4408,7 +4405,7 @@ network interfaces to be placed in promiscuous mode, capturing every packet on a broadcast network (e.g. an ethernet). These packets can be captured to disk and/or - examined with the tcpdump(1) program. + examined with the tcpdump1 program. Note that implementation of this capability can seriously compromise your overall network security. The number after bpfilter is the number @@ -4607,7 +4604,7 @@ Snoop device. This pseudo-device allows one terminal session to watch another using the - watch(8) command. Note that + watch8 command. Note that implementation of this capability has important security and privacy implications. The number after snp is the total number of simultaneous snoop @@ -4619,7 +4616,7 @@ Vnode driver. Allows a file to be treated as a device - after being set up with the vnconfig(8) + after being set up with the vnconfig8 command. This driver can be useful for manipulating floppy disk images and using a file as a swap device (e.g. an MS Windows swap file). Optional. @@ -4635,8 +4632,8 @@ meta-disk. The number after ccd is the total number of concatenated disks (not total number of disks that can be concatenated) that can be - created. (See ccd(4) and - ccdconfig(8) man pages for more + created. (See ccd4 and + ccdconfig8 man pages for more details.) Optional. @@ -4801,7 +4798,7 @@ resource is the /var/log/messages file which records, among other things, all of the kernel messages from every successful boot. Also, the - dmesg(8) command will print the kernel + dmesg8 command will print the kernel messages from the current boot. @@ -4814,7 +4811,7 @@ with the last installed kernel which may be non-functional. Also, as soon as possible, move the working kernel to the proper kernel location or - commands such as ps(1) will not work + commands such as ps1 will not work properly. The proper command to unlock the kernel file that make installs (in order to move another kernel back permanently) is: @@ -4839,7 +4836,7 @@ from the one that the system utilities have been built with, for example, an experimental 2.2.0 kernel on a 2.1.0-RELEASE system, many system-status commands like - ps(1) and vmstat(8) + ps1 and vmstat8 will not work any more. You must recompile the libkvm library as well as these utilities. This is one reason it is not normally a good @@ -5862,7 +5859,7 @@ IPFW, the software supplied with FreeBSD, is a packet filtering and accounting system which resides in the kernel, and has a user-land control utility, - ipfw(8). Together, they allow you to define and + ipfw8. Together, they allow you to define and query the rules currently used by the kernel in its routing decisions. @@ -5909,7 +5906,7 @@ Enables code to allow logging of packets through - syslogd(8). Without this option, even + syslogd8. Without this option, even if you specify that packets should be logged in the filter rules, nothing will happen. @@ -5919,7 +5916,7 @@ Limits the number of packets logged through - syslogd(8) on a per entry basis. You + syslogd8 on a per entry basis. You may wish to use this option in hostile environments in which you want to log firewall activity, but do not want to be open to a denial of service attack via syslog @@ -5928,7 +5925,7 @@ When a chain entry reaches the packet limit specified, logging is turned off for that particular entry. To resume logging, you will need to reset the associated - counter using the ipfw(8) + counter using the ipfw8 utility: @@ -5955,7 +5952,7 @@ Configuring IPFW The configuration of the IPFW software is - done through the ipfw(8) utility. The syntax + done through the ipfw8 utility. The syntax for this command looks quite complicated, but it is relatively simple once you understand its structure. @@ -6256,7 +6253,7 @@ remap=bf>8 echo request (ping request), and 11 time exceeded (used to indicate TTL expiration as with - traceroute(8)). + traceroute8). @@ -6290,7 +6287,7 @@ Display the last match times for each chain entry. The time listing is incompatible with the input syntax - used by the ipfw(8) utility. + used by the ipfw8 utility. @@ -7163,8 +7160,7 @@ You could put these commands in your /etc/rc.local file to set the mode each - time your system boots. See lptcontrol(8) for more information. + time your system boots. See lptcontrol8 for more information. @@ -7405,7 +7401,7 @@ file take immediate effect. The format of the printcap file is straightforward. Use your favorite text editor to make changes to /etc/printcap. The format is identical to other capability files like /usr/share/misc/termcap and /etc/remote. For complete information about the format, see the cgetent(3). + URL="http://www.freebsd.org/cgi/man.cgi?printcap">printcap file is straightforward. Use your favorite text editor to make changes to /etc/printcap. The format is identical to other capability files like /usr/share/misc/termcap and /etc/remote. For complete information about the format, see the cgetent3. The simple spooler configuration consists of the following steps: @@ -8596,8 +8592,7 @@ Format plain text with pr - before printing. See pr(1) for more information. + before printing. See pr1 for more information. @@ -10665,8 +10660,7 @@ The format of these files is simple: one host name per line. Note that the file /etc/hosts.equiv is also used by - the ruserok(3) protocol, and affects programs like rsh and rcp, so be careful. + the ruserok3 protocol, and affects programs like rsh and rcp, so be careful. For example, here is the /etc/hosts.lpd file on the host @@ -13055,8 +13049,7 @@ The sio driver provides support for NS8250-, NS16450-, NS16550 and NS16550A-based EIA RS-232C (CCITT V.24) communications interfaces. Several - multiport cards are supported as well. See the sio(4) manual page for detailed technical + multiport cards are supported as well. See the sio4 manual page for detailed technical documentation. @@ -13151,8 +13144,7 @@ xxx lines are, you will need to add 16 more devices. Only the last device includes the interrupt vector for the - board. (See the sio(4) manual page for detail as + board. (See the sio4 manual page for detail as to why.) The following example is for a Boca Board with an interrupt of 3, and a base IO address 100h. The IO address for Each port is +8 hexadecimal from the @@ -14822,7 +14814,7 @@ address of the device that is failing, and the desired debug level in /sys/scsi/scsidebug.h. If it probes but just does not work, you can use the - scsi(8) command to dynamically set a + scsi8 command to dynamically set a debug level to it in a running kernel (if SCSIDEBUG is defined). This will give you COPIOUS debugging output with which to confuse the gurus. see man 4 @@ -15129,11 +15121,11 @@ General tape access commands - mt(1) provides generic access to the tape + mt1 provides generic access to the tape drives. Some of the more common commands are rewind, erase, and status. See the mt(1) + remap=tt>status. See the mt1 manual page for a detailed description. @@ -15153,12 +15145,12 @@ SCSI drives - The st(4) driver provides + The st4 driver provides support for 8mm (Exabyte), 4mm (DAT: Digital Audio Tape), QIC (Quarter-Inch Cartridge), DLT (Digital Linear Tape), QIC Minicartridge and 9-track (remember the big reels that you see spinning in Hollywood computer rooms) tape drives. See the - st(4) manual page for a detailed + st4 manual page for a detailed description. The drives listed below are currently being used by members @@ -15306,7 +15298,7 @@ and QIC-525 (DC6525) tapes as well. Data transfer rate is 350kB/s using - dump(8). Rates of 530kB/s have been + dump8. Rates of 530kB/s have been reported when using @@ -15413,8 +15405,7 @@ (250MB) tapes. This drives quirks are known and pre-compiled into the - scsi tape device driver (st(4)). + scsi tape device driver (st4). Under FreeBSD 2.2-current, use mt blocksize 512 to set the blocksize. (The @@ -15920,8 +15911,7 @@ Native capacity is 150/250MB. This drive has quirks which are known and work around code - is present in the scsi tape device driver (st(4)). Upgrading the firmware to XXX + is present in the scsi tape device driver (st4). Upgrading the firmware to XXX version will fix the quirks and provide SCSI 2 capabilities. @@ -15964,7 +15954,7 @@ supported for the 2.5 GB cartridges. This drives quirks are known and pre-compiled into the - scsi tape device driver (st(4)) + scsi tape device driver (st4) beginning with FreeBSD 2.2-current. For previous versions of FreeBSD, use mt to read one block from the tape, rewind the tape, and then execute the @@ -16004,8 +15994,7 @@ erased. This drives quirks are known and pre-compiled into the - scsi tape device driver (st(4)). + scsi tape device driver (st4). Other firmware revisions that are known to work are: M75D @@ -16268,10 +16257,10 @@ Use the front panel button to eject the tape. - Re-insert the tape and dump(8) data to + Re-insert the tape and dump8 data to the tape. - dump(8) will report dump8 will report DUMP: End of tape detected and the console will show: HARDWARE FAILURE info:280 asc:80,96 @@ -16286,42 +16275,42 @@ Backup Programs - The three major programs are dump(8), - tar(1), and - cpio(1). + The three major programs are dump8, + tar1, and + cpio1. Dump and Restore - dump(8) and - restore(8) are the traditional Unix backup + dump8 and + restore8 are the traditional Unix backup programs. They operate on the drive as a collection of disk blocks, below the abstractions of files, links and directories that are created by the filesystems. - dump(8) backs up devices, entire + dump8 backs up devices, entire filesystems, not parts of a filesystem and not directory trees that span more than one filesystem, using either soft links - ln(1) or mounting one filesystem onto - another. dump(8) does not write files and + ln1 or mounting one filesystem onto + another. dump8 does not write files and directories to tape, but rather writes the data blocks that are the building blocks of files and directories. - dump(8) has quirks that remain from its + dump8 has quirks that remain from its early days in Version 6 of ATT Unix (circa 1975). The default parameters are suitable for 9-track tapes (6250 bpi), not the high-density media available today (up to 62,182 ftpi). These defaults must be overridden on the command line to utilize the capacity of current tape drives. - rdump(8) and - rrestore(8) backup data across the network + rdump8 and + rrestore8 backup data across the network to a tape drive attached to another computer. Both programs - rely upon rcmd(3) and - ruserok(3) to access the remote tape + rely upon rcmd3 and + ruserok3 to access the remote tape drive. Therefore, the user performing the backup must have rhosts access to the remote - computer. The arguments to rdump(8) and - rrestore(8) must suitable to use on the + computer. The arguments to rdump8 and + rrestore8 must suitable to use on the remote computer. (e.g. When rdump'ing from a FreeBSD computer to an Exabyte tape drive connected to a Sun called komodo, use: /sbin/rdump 0dsbfu 54000 13000 126 @@ -16335,24 +16324,24 @@ Tar - tar(1) also dates back to Version 6 of - ATT Unix (circa 1975). tar(1) operates in - cooperation with the filesystem; tar(1) + tar1 also dates back to Version 6 of + ATT Unix (circa 1975). tar1 operates in + cooperation with the filesystem; tar1 writes files and directories to tape. - tar(1) does not support the full range of - options that are available from cpio(1), - but tar(1) does not require the unusual - command pipeline that cpio(1) uses. + tar1 does not support the full range of + options that are available from cpio1, + but tar1 does not require the unusual + command pipeline that cpio1 uses. - Most versions of tar(1) do not support + Most versions of tar1 do not support backups across the network. The GNU version of - tar(1), which FreeBSD utilizes, supports - remote devices using the same syntax as rdump. To tar(1) to + tar1, which FreeBSD utilizes, supports + remote devices using the same syntax as rdump. To tar1 to an Exabyte tape drive connected to a Sun called komodo, use: /usr/bin/tar cf komodo:/dev/nrst8 . 2>&1. For versions without remote device - support, you can use a pipeline and rsh(1) + support, you can use a pipeline and rsh1 to send the data to a remote tape drive. (XXX add an example command) @@ -16361,19 +16350,19 @@ Cpio - cpio(1) is the original Unix file + cpio1 is the original Unix file interchange tape program for magnetic media. - cpio(1) has options (among many others) to + cpio1 has options (among many others) to perform byte-swapping, write a number of different archives format, and pipe the data to other programs. This last feature - makes cpio(1) and excellent choice for - installation media. cpio(1) does not know + makes cpio1 and excellent choice for + installation media. cpio1 does not know how to walk the directory tree and a list of files must be provided thru STDIN. - cpio(1) does not support backups across + cpio1 does not support backups across the network. You can use a pipeline and - rsh(1) to send the data to a remote tape + rsh1 to send the data to a remote tape drive. (XXX add an example command) @@ -16381,7 +16370,7 @@ Pax - pax(1) is IEEE/POSIX's answer to + pax1 is IEEE/POSIX's answer to tar and cpio. Over the years the various versions of tar and cpio have gotten slightly incompatible. So rather than fight it out to fully standardize them, POSIX @@ -16448,11 +16437,11 @@ Which Backup Program is Best? - dump(8) Period. + dump8 Period. Elizabeth D. Zwicky torture tested all the backup programs discussed here. The clear choice for preserving all your data and all the peculiarities of Unix filesystems is - dump(8). Elizabeth created filesystems + dump8. Elizabeth created filesystems containing a large variety of unusual conditions (and some not so unusual ones) and tested each program by do a backup and restore of that filesystems. The peculiarities included: @@ -16490,11 +16479,11 @@ Otherwise, you have to create two custom bootable floppies which has a kernel that can mount your all of your disks and access your tape drive. These floppies must contain: - fdisk(8), disklabel(8), - newfs(8), mount(8), and + fdisk8, disklabel8, + newfs8, mount8, and whichever backup program you use. These programs must be - statically linked. If you use dump(8), the - floppy must contain restore(8). + statically linked. If you use dump8, the + floppy must contain restore8. Third, create backup tapes regularly. Any changes that you make after your last backup may be irretrievably lost. @@ -16609,11 +16598,10 @@ Recover each filesystem separately. - Try to mount(8) (e.g. mount /dev/sd0a - /mnt) the root partition of your first disk. If - the disklabel was damaged, use disklabel(8) + Try to mount8 (e.g. mount /dev/sd0a /mnt) the root partition of your first disk. If + the disklabel was damaged, use disklabel8 to re-partition and label the disk to match the label that - your printed and saved. Use newfs(8) to + your printed and saved. Use newfs8 to re-create the filesystems. Re-mount the root partition of the floppy read-write (mount -u -o rw /mnt). Use your backup program and backup tapes to recover the data @@ -16701,8 +16689,7 @@ This tuning means KOI8-R keyboard with Alternative screen font mapped to KOI8-R encoding to preserve pseudographics, Gray Delete - key remapped to match Russian termcap(5) entry for FreeBSD + key remapped to match Russian termcap5 entry for FreeBSD console. RUS/LAT switch will be LANG for POSIX - setlocale(3) family functions; + setlocale3 family functions; @@ -16750,8 +16737,8 @@ The best way is using /etc/login.conf russian user's login class in - passwd(5) entry login class - position. See login.conf(5) for + passwd5 entry login class + position. See login.conf5 for details. @@ -16768,9 +16755,9 @@ - How to do it with vipw(8) + How to do it with <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry> - If you use vipw(8) for adding new + If you use vipw8 for adding new users, /etc/master.passwd entry should looks like: user:password:1111:11:russian:0:0:User @@ -16780,9 +16767,9 @@ - How to do it with adduser(8) + How to do it with <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry> - If you use adduser(8) for adding new + If you use adduser8 for adding new users: @@ -16801,7 +16788,7 @@ remap=tt>russian each time when you see Enter login class: default []: prompt from - adduser(8); + adduser8; @@ -16817,9 +16804,9 @@ - How to do it with pw(8) + How to do it with <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry> - If you use pw(8) for adding new users, + If you use pw8 for adding new users, call it in this form: # pw useradd user_name -L russian @@ -16891,7 +16878,7 @@ printer /etc/printcap entry should looks like: lp|Russian local line printer:\ :sh:of=/usr/libexec/lpr/ru/koi2alt:\ - :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: see printcap(5) for detailed description. + :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: see printcap5 for detailed description. @@ -16899,11 +16886,10 @@ id="russian-msdosfs"> MSDOS FS and Russian file names - Look at following example fstab(5) entry to enable support for Russian + Look at following example fstab5 entry to enable support for Russian file names in MSDOS FS: /dev/sd0s1 /dos/c msdos rw,-W=koi2dos,-L=ru_RU.KOI8-R 0 0 see - mount_msdos(8) for detailed description of + mount_msdos8for detailed description of and options. @@ -17330,7 +17316,7 @@ - See the sio(4) manual page for more information. + See the sio4 manual page for more information. If you have connected a terminal to the first serial port (COM1 in DOS parlance), then you want to use @@ -17408,7 +17394,7 @@ As an optional step, you may wish to create a custom getty type for use in step 2 by making an entry in /etc/gettytab. This document does not explain how to do so; you are encouraged to see the - gettytab(5) and the getty(8) manual pages for more + gettytab5 and the getty8 manual pages for more information. The remaining sections detail how to do these steps. We will @@ -17420,7 +17406,7 @@ port on a multiport serial card). For more information on the /etc/ttys - file, see the ttys(5) manual page. + file, see the ttys5 manual page. std entry for each bps rate from 110 to 115200. Of course, you can add your own entries to this file. - The manual page gettytab(5) provides more information. + The manual page gettytab5 provides more information. When setting the getty type in the /etc/ttys file, make sure that the @@ -17528,7 +17514,7 @@ To find out what terminal types FreeBSD supports, see the file /usr/share/misc/termcap. It lists about 600 terminal types. You can add more if you wish. See - the termcap(5) manual page for information. + the termcap5 manual page for information. In our example, the Wyse-50 is a Wyse-50 type of terminal (although it can emulate others, we will leave it in Wyse-50 @@ -18011,8 +17997,7 @@ COM3:, and COM4:. FreeBSD can presently also handle dumb multiport serial interface cards, such as the Boca Board - 1008 and 2016 (please see the manual page sio(4) for kernel configuration information + 1008 and 2016 (please see the manual page sio4 for kernel configuration information if you have a multiport serial card). The default kernel only looks for the standard COM ports, though. @@ -18075,8 +18060,7 @@ You can comment-out or completely remove lines for devices you do not have. If you have a multiport serial board, such as the - Boca Board BB2016, please see the sio(4) man page for complete information on + Boca Board BB2016, please see the sio4 man page for complete information on how to write configuration lines for multiport boards. Be careful if you are using a configuration file that was previously used for a different version of FreeBSD because the device flags have @@ -18100,7 +18084,7 @@ When you are finished adjusting the kernel configuration file, use the program config as documented in Building Berkeley Kernels with Config and the - config(8) manual page to prepare a kernel + config8 manual page to prepare a kernel building directory, then build, install, and test the new kernel. @@ -18125,8 +18109,7 @@ modems which use CTS/RTS signaling for flow control. The locking devices are used to lock flags on ports to prevent users or programs changing certain parameters; see the - manual pages termios(4), sio(4), and stty(1) for + manual pages termios4, sio4, and stty1 for information on the terminal settings, locking & initializing devices, and setting terminal options, respectively. @@ -18136,7 +18119,7 @@ A shell script called MAKEDEV in the /dev directory manages the device special - files. (The manual page for MAKEDEV(8) on + files. (The manual page for MAKEDEV8 on FreeBSD 1.1.5 is fairly bogus in its discussion of COM ports, so ignore it.) To use MAKEDEV to make dialup device special files @@ -18232,10 +18215,9 @@ <filename>/etc/gettytab</filename> - /etc/gettytab is a termcap(5)-style file of configuration - information for getty(8). Please see the - gettytab(5) manual page for + /etc/gettytab is a termcap5-style file of configuration + information for getty8. Please see the + gettytab5 manual page for complete information on the format of the file and the list of capabilities. @@ -18343,7 +18325,7 @@ information to login (user root may only login on ttys marked secure). See the manual page for - ttys(5) for more + ttys5 for more information. You will need to either modify existing lines in @@ -19259,8 +19241,8 @@ If you have a kernel without the tun device, and you can not rebuild it for some reason, all is not lost. You should be able - to dynamically load the code. Refer to the appropriate modload(8) - and lkm(4) pages for further details. + to dynamically load the code. Refer to the appropriate modload8 + and lkm4 pages for further details. You may also wish to take this opportunity to configure a firewall. Details can be found in the The dial string. User ppp uses an expect-send - syntax similar to the chat(8) + syntax similar to the chat8 program. Refer to the manual page for information on the features of this language. @@ -20171,7 +20153,7 @@ details. Once a socket has been set up, the - pppctl(8) program may be used in scripts that + pppctl8 program may be used in scripts that wish to manipulate the running program. @@ -20362,7 +20344,7 @@ Create an entry in /etc/passwd - (using the vipw(8) program). + (using the vipw8 program). @@ -20977,12 +20959,12 @@ otherwise, check the place where you found this document for a document named dialup.txt or something similar. You may also want to check the manual pages for - sio(4) for information on the serial - port device driver and ttys(5), - gettytab(5), - getty(8), & init(8) for + sio4 for information on the serial + port device driver and ttys5, + gettytab5, + getty8, & init8 for information relevant to configuring the system to accept logins on - modems, and perhaps stty(1) for information on + modems, and perhaps stty1 for information on setting serial port parameters [such as clocal for directly-connected serial interfaces]. @@ -21060,8 +21042,8 @@ goes wrong, sliplogin usually logs good informational messages via the daemon syslog facility, which usually goes into /var/log/messages - (see the manual pages for syslogd(8) and - syslog.conf(5), and perhaps check + (see the manual pages for syslogd8 and + syslog.conf5, and perhaps check /etc/syslog.conf to see to which files syslogd is logging). @@ -21149,7 +21131,7 @@ As mentioned earlier, there are three files in the /etc/sliphome directory that are part of the configuration for /usr/sbin/sliplogin (see - sliplogin(8) for the actual manual page for + sliplogin8 for the actual manual page for sliplogin): slip.hosts, which defines the SLIP users & their associated IP addresses; @@ -21272,7 +21254,7 @@ SLIP server's Ethernet subnet, and you will also need to adjust your /etc/sliphome/slip.login and /etc/sliphome/slip.logout scripts to use - arp(8) to manage the proxy-ARP entries in the + arp8 to manage the proxy-ARP entries in the SLIP server's ARP table. @@ -21349,8 +21331,8 @@ netstat -i must be changed to colons and leading zeros should be added to each single-digit hexadecimal number to convert the address into the form that - arp(8) desires; see the manual page on - arp(8) for complete information on + arp8 desires; see the manual page on + arp8 for complete information on usage. @@ -21849,18 +21831,18 @@ Sometimes, there is a problem with routing propagation, and some sites are unable to connect to you. Perhaps the most useful command for trying to figure out where a routing is breaking down - is the traceroute(8) command. It is equally + is the traceroute8 command. It is equally useful if you cannot seem to make a connection to a remote machine - (ie. ping(8) fails). + (ie. ping8 fails). - The traceroute(8) command is run with the + The traceroute8 command is run with the name of the remote host you are trying to connect to. It will show the gateway hosts along the path of the attempt, eventually either reaching the target host, or terminating because of a lack of connection. For more information, see the manual page for - traceroute(8). + traceroute8. @@ -23378,7 +23360,7 @@ archive, any detected changes being compressed, stamped with a sequence-number and encoded for transmission over email (printable ASCII only). Once received, these "CTM deltas" can then be handed - to the ctm_rmail(1) utility which will automatically decode, verify + to the ctm_rmail1 utility which will automatically decode, verify and apply the changes to the user's copy of the sources. This process is far more efficient than CVSup, and places less strain on our server resources since it is a push rather @@ -24181,7 +24163,7 @@ the latest versions of the files on that line of development. If you wish to receive some past version, you can do so by specifying a date with the value - field. The cvsup(1) manual page explains how to do + field. The cvsup1 manual page explains how to do that. For our example, we wish to receive FreeBSD-current. @@ -24298,7 +24280,7 @@ alone. is ... arcane. If you really want to - know about it, see the cvsup(1) manual page. Otherwise, + know about it, see the cvsup1 manual page. Otherwise, just specify it and do not worry about it. enables the use of gzip-style compression @@ -24392,7 +24374,7 @@ see the manual page. Once you are satisfied with the way updates are working, you - can arrange for regular runs of cvsup using cron(8). Obviously, + can arrange for regular runs of cvsup using cron8. Obviously, you should not let cvsup use its GUI when running it from cron. @@ -25740,12 +25722,12 @@ information about this and other mailing lists. If you find a bug or are submitting a specific change, please - report it using the send-pr(1) program or its + report it using the send-pr1program or its WEB-based equivalent. Try to fill-in each field of the bug report. Unless they exceed 65KB, include any patches directly in the report. Consider compressing them and using - uuencode(1) if they exceed 20KB. + uuencode1 if they exceed 20KB. After filing a report, you should receive confirmation along with a tracking number. Keep this tracking number so that you can @@ -25754,7 +25736,7 @@ If you do not receive confirmation in a timely fashion (3 days to a week, depending on your email connection) or are, for some - reason, unable to use the send-pr(1) command, + reason, unable to use the send-pr1 command, then you may ask someone to file it for you by sending mail to the &a.bugs;. @@ -25794,7 +25776,7 @@ Assuming that you can manage to secure fairly up-to-date sources to base your changes on, the next step is to produce a set of diffs to send to the FreeBSD maintainers. This is done with - the diff(1) command, with the `context diff' + the diff1 command, with the `context diff' form being preferred. For example: diff -c oldfile newfile @@ -25803,11 +25785,11 @@ diff -c -r olddir newdir would generate such a set of context diffs for the given source file or directory hierarchy. See the man page - for diff(1) for more details. + for diff1 for more details. Once you have a set of diffs (which you may test with the - patch(1) command), you should submit them for - inclusion with FreeBSD. Use the send-pr(1) + patch1 command), you should submit them for + inclusion with FreeBSD. Use the send-pr1 program as described in . Do not just send the diffs to @@ -25818,14 +25800,14 @@ If you feel it appropriate (e.g. you have added, deleted, or renamed files), bundle your changes into a tar file and run the - uuencode(1) program on it. Shar archives are + uuencode1 program on it. Shar archives are also welcome. If your change is of a potentially sensitive nature, e.g. you are unsure of copyright issues governing its further distribution or you are simply not ready to release it without a tighter review first, then you should send it to &a.core; directly rather than - submitting it with send-pr(1). The core + submitting it with send-pr1. The core mailing list reaches a much smaller group of people who do much of the day-to-day work on FreeBSD. Note that this group is also very busy and so you should only send mail to @@ -26258,7 +26240,7 @@ - Refer to the pkg_create(1) man page + Refer to the pkg_create1 man page for details on the packing list. @@ -26303,7 +26285,7 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/ and send mail to us using - send-pr(1) (please classify it as category + send-pr1 (please classify it as category `ports' and class `change-request'). There is no need to upload the package, we will build it by ourselves. We will take a look, get back to you if necessary, and put it in the @@ -27362,7 +27344,7 @@ diff -ruN superedit.bak superedit). Please examine the output to make sure all the changes make sense. The best way to send us the - diff is by including it to send-pr(1) + diff is by including it to send-pr1 (category `ports'). Please mention any added or deleted files in the message, as they have to be explicitly specified to CVS when doing a commit. If the diff is more than about 20KB, please @@ -27508,7 +27490,7 @@ mode the script is being run in. The PKG_PREFIX environmental variable will be set to the package installation directory. See man - pkg_add(1) for additional + pkg_add1 for additional information. @@ -27527,8 +27509,8 @@ requirements script. It will be invoked automatically at installation/deinstallation time to determine whether or not installation/deinstallation should proceed. See man - pkg_create(1) and man - pkg_add(1) for more information. + pkg_create1 and man + pkg_add1 for more information. @@ -27706,7 +27688,7 @@ (executables for superusers/managers), info (documentation for info browser) or share (architecture independent - files). See man hier(7) for + files). See man hier7 for details, the rule governing /usr pretty much applies to /usr/local too. The exception are ports dealing with USENET `news'. They may use @@ -30588,10 +30570,10 @@ the supported options in the kernel into new-style ones, so for people who correctly did a make depend in their kernel compile directory after running - config(8), the build process will automatically + config8, the build process will automatically pick up modified options, and only recompile those files where it is necessary. Wiping out the old compile directory on each run of - config(8) as it is still done now can then be + config8 as it is still done now can then be eliminated again. Basically, a kernel option is nothing else than the definition @@ -30658,7 +30640,7 @@ using such an option is responsible himself for knowing about its implications (and maybe manually forcing the recompilation of parts of his kernel). Once the transition of all supported options has - been done, config(8) will warn whenever an + been done, config8 will warn whenever an unsupported option appears in the config file, but it will nevertheless include it into the kernel Makefile. @@ -30683,7 +30665,7 @@ opt_foo.h already available for the intended new option, invent a new name. Make it meaningful, and comment the new section in the - options[.<arch>] file. config(8) will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves.. + options[.<arch>] file. config8 will automagically pick up the change, and create that file next time it is run. Most options should go in a header file by themselves.. Packing too many options into a single opt_foo.h will cause @@ -30748,16 +30730,16 @@ is too small to hold the dump, you can configure your kernel to use an alternate dump device (in the config kernel line), or you can specify an alternate using the - dumpon(8) command. Dumps to non-swap devices, tapes for example, + dumpon8 command. Dumps to non-swap devices, tapes for example, are currently not supported. Config your kernel using config -g. See for details on configuring the FreeBSD kernel. - Use the dumpon(8) command to tell the kernel + Use the dumpon8 command to tell the kernel where to dump to (note that this will have to be done after configuring the partition in question as swap space via - swapon(8)). This is normally arranged via + swapon8). This is normally arranged via /etc/rc.conf and /etc/rc. Alternatively, you can hard-code the dump device via the `dump' clause in the `config' line of your kernel config file. This is @@ -30793,7 +30775,7 @@ fsck -p mount -a -t ufs # so your file system for /var/crash is writable savecore -N /kernel.panicked /var/crash exit # ...to multi-user - This instructs savecore(8) to + This instructs savecore8 to use another kernel for symbol name extraction. It would otherwise default to the currently running kernel and most likely not do anything at all since the crash dump and the kernel symbols @@ -30959,7 +30941,7 @@ generated code, so you will finally get a new kernel with similar code to the faulting one but some debugging symbols. You should at least verify the old and new sizes with the - size(1) command. If there is a mismatch, you + size1 command. If there is a mismatch, you probably need to give up here. Go and examine the dump as described above. The debugging @@ -31126,7 +31108,7 @@ call func(arg1, arg2, ...) The return value will be printed. - For a ps(1) style summary of all running + For a ps1 style summary of all running processes, use ps @@ -31167,7 +31149,7 @@ help However, it is highly recommended to have a - printed copy of the ddb(4) manual page + printed copy of the ddb4 manual page ready for a debugging session. Remember that it is hard to read the on-line manual while single-stepping the kernel. @@ -31694,7 +31676,7 @@ check if it needs shared libraries, and if so, whether you have them installed in the /compat/linux tree. To do this, you run the Linux version ldd on the new program, - and watch its output. ldd (see also the manual page for ldd(1)) + and watch its output. ldd (see also the manual page for ldd1) will print a list of shared libraries that the program depends on, in the form majorname (jumpversion) => fullname. @@ -35072,7 +35054,7 @@ Bug reports This is the mailing list for reporting bugs in FreeBSD Whenever - possible, bugs should be submitted using the send-pr(1) + possible, bugs should be submitted using the send-pr1 command or the WEB interface to it.