From bd9330d762749598f98b7865a9c24eb408d9bc25 Mon Sep 17 00:00:00 2001 From: Nik Clayton Date: Thu, 18 Jun 1998 08:42:02 +0000 Subject: [PATCH] Swept through looking for explanatory notes and marking them up as 'note' elements. --- en/handbook/README | 15 + en/handbook/handbook.sgml | 1715 +++++++++++---------- en_US.ISO8859-1/books/handbook/book.sgml | 1715 +++++++++++---------- en_US.ISO_8859-1/books/handbook/book.sgml | 1715 +++++++++++---------- 4 files changed, 2745 insertions(+), 2415 deletions(-) diff --git a/en/handbook/README b/en/handbook/README index 27e2545c5b..765f8de444 100644 --- a/en/handbook/README +++ b/en/handbook/README @@ -205,3 +205,18 @@ for example, which matches elements spread over two lines. + 12. Looked for explanatory notes in the text (typically prefixed by "note", + "Note:" or "
Note:" + and marked them up as 'note' elements. + + This change involves markup changes *and* text changes. This is because + text like + + Note: The foo file is only used once, and can be deleted. + + became + + + The foo file is only used once, and can be deleted. + + diff --git a/en/handbook/handbook.sgml b/en/handbook/handbook.sgml index c769392ae5..043f28336e 100644 --- a/en/handbook/handbook.sgml +++ b/en/handbook/handbook.sgml @@ -504,15 +504,19 @@ Some core team members also have specific , meaning that they are committed to ensuring that some large - portion of the system works as advertised. Note that most - members of the core team are volunteers when it comes to - FreeBSD development and do not benefit from the project - financially, so "commitment" should also not be misconstrued - as meaning "guaranteed support." The board of directors - analogy above is not actually very accurate, and it may be - more suitable to say that these are the people who gave up - their lives in favor of FreeBSD against their better - judgement! ;) + portion of the system works as advertised. + + + Most members of the core team are volunteers when it + comes to FreeBSD development and do not benefit from the + project financially, so "commitment" should also not be + misconstrued as meaning "guaranteed support." The + board of directors analogy above is not + actually very accurate, and it may be more suitable to say + that these are the people who gave up their lives in favor + of FreeBSD against their better judgement! ;) + @@ -717,9 +721,14 @@ If you're running DOS and have the proper drivers to access your CD, run the install.bat script provided on the CD. This will attempt to boot into the FreeBSD - installation straight from DOS (note: You must - do this from actual DOS and not a Windows DOS - box). If you also want to install FreeBSD + installation straight from DOS. + + + You must do this from actual DOS and not a Windows + DOS box. + + + If you also want to install FreeBSD from your DOS partition (perhaps because your CDROM drive is completely unsupported by FreeBSD) then run the setup program first to copy the appropriate files from the CD to @@ -741,7 +750,12 @@ If you don't have a CDROM distribution then simply download the installation boot disk image file to your hard drive, being sure to tell your browser to save rather than display the file. Note: This disk image can only be used with 1.44 megabyte 3.5 inch floppy disks. + URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/&rel.current;-RELEASE/floppies/boot.flp">installation boot disk image file to your hard drive, being sure to tell your browser to save rather than display the file. + + + This disk image can only be used with 1.44 megabyte 3.5 + inch floppy disks. + @@ -942,23 +956,27 @@ Adaptec AIC-6360 based boards, which includes the - AHA-152x and SoundBlaster SCSI cards. Note: You cannot boot from the - SoundBlaster cards as they have no on-board BIOS, which is - necessary for mapping the boot device into the system BIOS - I/O vectors. They are perfectly usable for external tapes, - CDROMs, etc, however. The same goes for any other AIC-6x60 - based card without a boot ROM. Some systems DO have a boot - ROM, which is generally indicated by some sort of message - when the system is first powered up or reset. Check your - system/board documentation for more details. - + AHA-152x and SoundBlaster SCSI cards. + + + You cannot boot from the + SoundBlaster cards as they have no on-board BIOS, which is + necessary for mapping the boot device into the system BIOS + I/O vectors. They are perfectly usable for external tapes, + CDROMs, etc, however. The same goes for any other AIC-6x60 + based card without a boot ROM. Some systems DO have a boot + ROM, which is generally indicated by some sort of message + when the system is first powered up or reset. Check your + system/board documentation for more details. + - Buslogic 545S & 545c Note: that Buslogic was formerly known - as "Bustek". + Buslogic 545S & 545c + + + Buslogic was formerly known as "Bustek". + @@ -1256,12 +1274,13 @@ - - Note: FreeBSD does not currently support - PnP (plug-n-play) features present on some ethernet cards. If - your card has PnP and is giving you problems, try disabling its - PnP features. - + + + FreeBSD does not currently support + PnP (plug-n-play) features present on some ethernet cards. If + your card has PnP and is giving you problems, try disabling its + PnP features. + + can make a boot floppy with the ``makeflp.bat'' command. + + + If you are running FreeBSD 2.1-RELEASE and have an IDE + CDROM, use the inst_ide.bat or atapiflp.bat batch files + instead. + For the easiest interface of all (from DOS), type ``view''. This will bring up a DOS menu utility that leads you through all @@ -1414,16 +1437,13 @@ to first type: umount /cdrom. Do not just remove it from the drive! - -
- Special note: Before - invoking the installation, be sure that the CDROM is in the - drive so that the install probe can find it. This is also - true if you wish the CDROM to be added to the default system - configuration automatically during the install (whether or not - you actually use it as the installation media). -
- + + Before invoking the installation, be sure that the CDROM is + in the drive so that the install probe can find it. This is + also true if you wish the CDROM to be added to the default + system configuration automatically during the install (whether + or not you actually use it as the installation media). + Finally, if you would like people to be able to FTP install FreeBSD directly from the CDROM in your machine, you will find it @@ -1547,14 +1567,11 @@ should expect to require as much temporary storage as you have stuff written on tape. - -
- Note: When going to do the - installation, the tape must be in the drive - before booting from the boot floppy. The - installation probe may otherwise fail to find it. -
- + + When going to do the installation, the tape must be in the + drive before booting from the boot floppy. + The installation probe may otherwise fail to find it. + @@ -1725,14 +1742,11 @@ - -
- Note: Active and passive - modes are not the same as a `proxy' connection, where a - proxy FTP server is listening and forwarding FTP - requests! -
- + + Active and passive modes are not the same as a `proxy' + connection, where a proxy FTP server is listening and + forwarding FTP requests! + For a proxy FTP server, you should usually give name of the server you really want as a part of the username, after an @@ -3092,9 +3106,12 @@ bsd.ports.mk and bsd.ports.subdir.mk files in your makefiles - directory. (Note: readers with an aversion to - intricate shell-scripts are advised not to follow this - link...) + directory. + + + Readers with an aversion to intricate shell-scripts are + advised not to follow this link...) + @@ -3188,15 +3205,13 @@ i386 directory is common to all platforms which FreeBSD could potentially be ported to. - -
- Note: If there is - not a /usr/src/sys - directory on your system, then the kernel source has not been - been installed. Follow the instructions for installing packages - to add this package to your system. -
- + + If there is not a + /usr/src/sys directory on your system, then + the kernel source has not been been installed. Follow the + instructions for installing packages to add this package to your + system. + Next, move to the i386/conf directory and copy the GENERIC configuration file to the name @@ -3209,13 +3224,11 @@ machine's hostname. We will call it MYKERNEL for the purpose of this example. - -
- Note: You must execute these and all of - the following commands under the root account or you will get - ``permission denied'' errors. -
- + + You must execute these and all of the following commands + under the root account or you will get ``permission denied'' + errors. + Now, edit MYKERNEL with your favorite text editor. If you are just starting out, the only editor available @@ -3236,17 +3249,15 @@ linkend="kernelconfig-config" remap="Configuration File"> section slowly and carefully. - -
- Note: 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 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 - running the next commands. -
- + + 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 + 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 + running the next commands. + When you are finished, type the following to compile and install your kernel: @@ -3263,15 +3274,13 @@ your new kernel . - -
- Note: If you have added any new devices - (such as sound cards) you may have to add some to your - /dev directory before you can use - them. -
- + + If you have added any new devices (such as sound cards) you + may have to add some to your + /dev directory before you can use + them. + @@ -3326,14 +3335,12 @@ remap=tt>machine, which, since FreeBSD only runs on Intel 386 and compatible chips, is i386. - -
- Note: that any keyword which - contains numbers used as text must be enclosed in - quotation marks, otherwise config gets confused and thinks - you mean the actual number 386. -
- + + Any keyword which contains numbers used as text + must be enclosed in quotation marks, otherwise + config gets confused and thinks you + mean the actual number 386. + @@ -3429,23 +3436,19 @@ simultaneous users (like Walnut Creek CDROM's FTP site), you can always increase this number and rebuild. - -
- Note: maxuser does - not limit the number of users - which can log into your machine. It simply sets - various table sizes to reasonable values considering - the maximum number of users you will likely have on - your system and how many processes each of them will - be running. One keyword which - does limit the number of - simultaneous remote logins is + + maxuser does + not limit the number of users which + can log into your machine. It simply sets various table + sizes to reasonable values considering the maximum + number of users you will likely have on your system and + how many processes each of them will be running. One + keyword which does limit the number + of simultaneous remote logins is . -
- + @@ -3488,18 +3491,15 @@ with a separate 387 or 487 chip, you can comment this line out. - -
- Note: The normal math - co-processor emulation routines that come with FreeBSD - are not very accurate. If you do - not have a math co-processor, and you need the best - accuracy, I recommend that you change this option to - GPL_MATH_EMULATE to use the superior - GNU math support, which is not included by default for - licensing reasons. -
- + + The normal math co-processor emulation routines that + come with FreeBSD are not very + accurate. If you do not have a math co-processor, and + you need the best accuracy, I recommend that you change + this option to GPL_MATH_EMULATE to use + the superior GNU math support, which is not included by + default for licensing reasons. + @@ -3561,14 +3561,11 @@ Support for System V messages. Again, only adds a few hundred bytes to the kernel. - -
- Note: The - ipcs(1) command will tell will list - any processes using each of these System V - facilities. -
- + + The ipcs(1) command will tell + will list any processes using each of these System V + facilities. + @@ -3661,28 +3658,22 @@ - -
- Note: Replace the - /dev/wd1s2b with the name of your - swap partition, which will be listed in your - /etc/fstab as follows: - - /dev/wd1s2b none swap sw 0 0 - - -
- + + Replace the /dev/wd1s2b with + the name of your swap partition, which will be listed in + your /etc/fstab as follows: + + /dev/wd1s2b none swap sw 0 0 + + + - -
- Note: Also, the - MFS filesystem can - not be dynamically loaded, so you - must compile it into your kernel - if you want to experiment with it. -
- + + Also, the MFS filesystem can + not be dynamically loaded, so you + must compile it into your kernel if + you want to experiment with it. + @@ -3750,14 +3741,12 @@ attached to the floppy controller. Comment out any lines corresponding to devices you do not have. - -
- Note: QIC-80 tape support - requires a separate filter program called - ft(8), see the manual page for - details. + + QIC-80 tape support requires a separate filter + program called ft(8), see the manual + page for details.
- + @@ -4089,15 +4078,13 @@ Use this device if you have a Logitech or ATI InPort bus mouse card. - -
- Note: If you have a serial - mouse, ignore these two lines, and instead, make sure - the appropriate + If you have a serial mouse, ignore these two lines, + and instead, make sure the appropriate port is enabled (probably - COM1). -
- + COM1). + @@ -4335,14 +4322,11 @@ - -
- Note: With certain cards - (notably the NE2000) you will have to change the port - and/or IRQ since there is no ``standard'' location for - these cards. -
- + + With certain cards (notably the NE2000) you will + have to change the port and/or IRQ since there is no + ``standard'' location for these cards. + @@ -4474,17 +4458,14 @@ SoundBlaster digital audio. - -
- Note: If your SoundBlaster is - on a different IRQ (such as 5), change irq 7 to, for example, irq 5 and remove the conflicts keyword. Also, you - must add the line: options - ``SBC_IRQ=5'' -
- + + If your SoundBlaster is on a different IRQ (such as + 5), change irq 7 to, for + example, irq 5 and remove + the conflicts keyword. + Also, you must add the line: options + ``SBC_IRQ=5'' + @@ -4493,15 +4474,12 @@ SoundBlaster 16 digital 16-bit audio. - -
- Note: If your SB16 is on a - different 16-bit DMA channel (such as 6 or 7), change - the drq 5 keyword - appropriately, and then add the line: options - "SB16_DMA=6" -
- + + If your SB16 is on a different 16-bit DMA channel + (such as 6 or 7), change the drq + 5 keyword appropriately, and then add the + line: options "SB16_DMA=6" + @@ -4570,16 +4548,13 @@ - -
- Note: There is some additional - documentation in - /usr/src/sys/i386/isa/sound/sound.doc. - Also, if you add any of these devices, be sure to create the - sound . -
- + + There is some additional documentation in + /usr/src/sys/i386/isa/sound/sound.doc. + Also, if you add any of these devices, be sure to create the + sound . + @@ -4750,25 +4725,26 @@ For sound cards, the command: # sh MAKEDEV snd0 - creates the appropriate entries. Note: when - creating device nodes for devices such as sound cards, if other - people have access to your machine, it may be desirable to protect - the devices from outside access by adding them to the - /etc/fbtab file. See man - fbtab for more information. + creates the appropriate entries. + + + When creating device nodes for devices such as sound cards, if + other people have access to your machine, it may be desirable to + protect the devices from outside access by adding them to the + /etc/fbtab file. See man + fbtab for more information. + Follow this simple procedure for any other non-GENERIC devices which do not have entries. - -
- Note: All SCSI controllers use the same - set of /dev entries, so you do not need to - create these. Also, network cards and SLIP/PPP pseudo-devices - do not have entries in /dev at all, so you - do not have to worry about these either. -
- + + All SCSI controllers use the same set of + /dev entries, so you do not need to create + these. Also, network cards and SLIP/PPP pseudo-devices do not + have entries in /dev at all, so you do not + have to worry about these either. + @@ -4832,33 +4808,31 @@ dmesg(8) command will print the kernel messages from the current boot. - -
- Note: If you are having trouble - building a kernel, make sure to keep a GENERIC, or some - other kernel that is known to work on hand as a - different name that will not get erased on the next - build. You cannot rely on - kernel.old because when installing - a new kernel, kernel.old is - overwritten with the last installed kernel which may be - non-functional. Also, as soon as possible, move the - working kernel to the proper ``kernel'' location or - commands such as ps(1) will not work - properly. The proper command to unlock the kernel - file that make installs - (in order to move another kernel back permanently) is: + + If you are having trouble building a kernel, make sure + to keep a GENERIC, or some other kernel that is known to + work on hand as a different name that will not get erased + on the next build. You cannot rely on + kernel.old because when installing a + new kernel, kernel.old is overwritten + with the last installed kernel which may be + non-functional. Also, as soon as possible, move the + working kernel to the proper ``kernel'' location or + commands such as ps(1) will not work + properly. The proper command to unlock the + kernel file that make installs (in + order to move another kernel back permanently) is: # chflags noschg /kernel - And, if you want to lock your new - kernel into place, or any file for that matter, so that - it cannot be moved or tampered with: + And, if you want to + lock your new kernel into place, or any + file for that matter, so that it cannot be moved or + tampered with: # chflags schg /kernel -
- + @@ -5779,20 +5753,19 @@ use the facilities provided in the FreeBSD kernel to implement them. - -
- Note: People often think that - having a firewall between your companies internal network and - the Big Bad Internet will solve all your security problems. - It may help, but a poorly setup firewall system is more of a - security risk than not having one at all. A firewall can only - add another layer of security to your systems, but they will not - be able to stop a really determined hacker from penetrating your - internal network. If you let internal security lapse because you - believe your firewall to be impenetrable, you have just made the - hackers job that bit easier. -
- + + People often think that having a firewall between your + companies internal network and the Big Bad Internet + will solve all your security problems. + + It may help, but a poorly setup firewall system is more of a + security risk than not having one at all. A firewall can only add + another layer of security to your systems, but they will not be + able to stop a really determined hacker from penetrating your + internal network. If you let internal security lapse because you + believe your firewall to be impenetrable, you have just made the + hackers job that bit easier. + @@ -6428,14 +6401,12 @@ Building a packet filtering firewall - -
- Note: The following - suggestions are just that: suggestions. The requirements of - each firewall are different and I cannot tell you how to build - a firewall to meet your particular requirements. -
- + + The following suggestions are just that: suggestions. The + requirements of each firewall are different and I cannot tell + you how to build a firewall to meet your particular + requirements. + When initially setting up your firewall, unless you have a test bench setup where you can configure your firewall host in a @@ -6447,21 +6418,19 @@ tracing of possible attacks and also modification of the firewall rules if your requirements alter. - -
- Note: If you use the logging - versions of the accept command, - it can generate large amounts of log data - as one log line will be generated for every packet that passes - through the firewall, so large ftp/http transfers, etc, will - really slow the system down. It also increases the latencies - on those packets as it requires more work to be done by the - kernel before the packet can be passed on. syslogd with also - start using up a lot more processor time as it logs all the - extra data to disk, and it could quite easily fill the - partition /var/log is located on. -
- + + If you use the logging versions of the accept command, it can generate + large amounts of log data as one log line + will be generated for every packet that passes through the + firewall, so large ftp/http transfers, etc, will really slow the + system down. It also increases the latencies on those packets as + it requires more work to be done by the kernel before the packet + can be passed on. syslogd with also start using up a lot more + processor time as it logs all the extra data to disk, and it + could quite easily fill the partition + /var/log is located on. + As currently supplied, FreeBSD does not have the ability to load firewall rules at boot time. My suggestion is to put a call @@ -7226,14 +7195,18 @@ %!PS 100 100 moveto 300 300 lineto stroke 310 310 moveto /Helvetica findfont 12 scalefont setfont (Is this thing working?) show showpage - Note: When this - document refers to a printer language, I am assuming a - language like PostScript, and not Hewlett Packard's PCL. - Although PCL has great functionality, you can intermingle - plain text with its escape sequences. PostScript cannot - directly print plain text, and that is the kind of printer - language for which we must make special accommodations. + + + + When this document refers to a printer language, I am + assuming a language like PostScript, and not Hewlett + Packard's PCL. Although PCL has great functionality, you can + intermingle plain text with its escape sequences. + PostScript cannot directly print plain text, and that is the + kind of printer language for which we must make special + accommodations. + @@ -7502,12 +7475,14 @@ - - Note: Language-based printers, such as - PostScript printers, cannot directly print plain text. The - simple setup outlined above and described in the following - sections assumes that if you are installing such a printer you - will print only files that the printer can understand. + + + Language-based printers, such as PostScript printers, + cannot directly print plain text. The simple setup outlined + above and described in the following sections assumes that if + you are installing such a printer you will print only files + that the printer can understand. + Users often expect that they can print plain text to any of the printers installed on your system. Programs that interface @@ -7636,22 +7611,24 @@ mkdir /var/spool/lpd/bamboo - - Note: If you are concerned about the - privacy of jobs that users print, you might want to protect - the spooling directory so it is not publicly accessible. - Spooling directories should be owned and be readable, - writable, and searchable by user daemon and group daemon, and - no one else. We will do this for our example printers: - - - - chown daemon.daemon /var/spool/lpd/rattan chown - daemon.daemon /var/spool/lpd/bamboo chmod 770 - /var/spool/lpd/rattan chmod 770 - /var/spool/lpd/bamboo - - + + + If you are concerned about the privacy of jobs that + users print, you might want to protect the spooling + directory so it is not publicly accessible. Spooling + directories should be owned and be readable, writable, and + searchable by user daemon and group daemon, and no one else. + We will do this for our example printers: + + + + chown daemon.daemon /var/spool/lpd/rattan chown + daemon.daemon /var/spool/lpd/bamboo chmod 770 + /var/spool/lpd/rattan chmod 770 + /var/spool/lpd/bamboo + + + Finally, you need to tell LPD about these directories using the /etc/printcap file. You @@ -8048,15 +8025,16 @@ to find out how to do this. - - Note: If you boot your - system into other operating systems besides - FreeBSD, you may have to - reconfigure the printer to - use a an interpretation for CR and LF characters - that those other operating systems use. You - might prefer one of the other solutions, - below. + + + If you boot your system into other + operating systems besides FreeBSD, you may + have to reconfigure the + printer to use a an interpretation for CR and + LF characters that those other operating + systems use. You might prefer one of the + other solutions, below. + @@ -8498,26 +8476,27 @@ lprm -P rattan - - - Note: If you are working in a networked - environment, - - lprm will - let you remove jobs only from the host from which the jobs were - submitted, even if the same printer is available from other hosts. - The following command sequence demonstrates this: - - rose% lpr -P rattan myfile rose% rlogin orchid - orchid% lpq -P rattan Rank Owner Job Files - Total Size active seeyan 12 ... - 49123 bytes 2nd kelly 13 myfile - 12 bytes orchid% lprm -P rattan 13 rose: Permission denied - orchid% logout rose% lprm -P rattan 13 dfA013rose dequeued - cfA013rose dequeued rose% - - - + + + If you are working in a networked + environment, + + lprm + will let you remove jobs only from the host from which the jobs + were submitted, even if the same printer is available from other + hosts. The following command sequence demonstrates this: + + rose% lpr -P rattan myfile rose% rlogin orchid + orchid% lpq -P rattan Rank Owner Job Files Total + Size active seeyan 12 ... 49123 bytes 2nd kelly + 13 myfile 12 bytes orchid% lprm -P rattan 13 rose: + Permission denied orchid% logout rose% lprm -P rattan 13 + dfA013rose dequeued cfA013rose dequeued rose% + + + + - - Note: All of these options except - and require conversion - filters installed for the destination printer. For example, the - option requires the DVI conversion filter. - Section + All of these options except and + require conversion filters installed for + the destination printer. For example, the + option requires the DVI conversion filter. Section gives details. + @@ -8601,9 +8581,11 @@ number, indent by 8 columns. This option works only with certain conversion filters. - - Note: Do not put any space - between the and the number. + + + Do not put any space between the + and the number. + @@ -8750,13 +8732,14 @@ There is a drawback, though: since LPD will refer to the original files directly, you cannot modify or remove them until they have been printed. - - Note: If you are printing to a - remote printer, LPD will eventually have to copy files - from the local host to the remote host, so the - option will save space only on the - local spooling directory, not the remote. It is still - useful, though. + + + If you are printing to a remote printer, LPD will + eventually have to copy files from the local host to + the remote host, so the option + will save space only on the local spooling directory, + not the remote. It is still useful, though. + @@ -8812,12 +8795,14 @@ -h - Do not print any header page. - Note: At some sites, this option - may have no effect due to the way header pages are - generated. See Do not print any header page. + + + At some sites, this option may have no effect due + to the way header pages are generated. See for details. + @@ -10006,12 +9991,14 @@ Options"> for more lpr options. - - Note: LPD prints a form feed - character after the header page. If your printer uses a - different character or sequence of characters to eject a page, - specify them with the ff - capability in /etc/printcap. + + + LPD prints a form feed character after the header page. + If your printer uses a different character or sequence of + characters to eject a page, specify them with the ff capability in + /etc/printcap. + @@ -10618,10 +10605,10 @@ remap=tt>bamboo. It might be the case that we only allow certain logins on orchid anyway, and want them to have access to the printer. Or not. - - Note: there can be only one restricted - group per printer. - + + + There can be only one restricted group per printer. + mx capability. The units are in BUFSIZ blocks, which are 1024 bytes. If you put a zero for this capability, there will be no limit on file - size. Note that the limit applies to files - in a job, and not the total job size. + + + The limit applies to files in a job, + and not the total job size. + LPD will not refuse a file that is larger than the limit you place on a printer. Instead, it will queue as much of the file @@ -11517,15 +11507,23 @@ URL="http://www.asus.com.tw/Products/Motherboard/Pentiumpro/P2l97-s/index.html">P2l97-S motherboard with the on-board Adaptec SCSI WIDE controller. For Pentium machines, the ASUS P55T2P4 motherboard appears to be a good choice for mid-to-high range Pentium server and workstation systems. You might also wish to investigate ASUS's 486SP3G offering if it's a 486-class motherboard you're looking for (Note: These have become increasingly hard to get as ASUS apparently no longer manufactures them). + URL="http://www.asus.com.tw/Products/Motherboard/Pentium/P55tp4/index.html">P55T2P4 motherboard appears to be a good choice for mid-to-high range Pentium server and workstation systems. You might also wish to investigate ASUS's 486SP3G offering if it's a 486-class motherboard you're looking for. + + + These have become increasingly hard to get as ASUS + apparently no longer manufactures them). + Those wishing to build more fault-tolerant systems should also be sure to use Parity memory or, for truly 24/7 - applications, ECC memory. Note that ECC memory does involve a - slight performance trade-off (which may or may not be noticeable - depending on your application) but buys you significantly - increased fault-tolerance to memory errors. - + applications, ECC memory. + + + ECC memory does involve a slight performance trade-off + (which may or may not be noticeable depending on your + application) but buys you significantly increased + fault-tolerance to memory errors. + @@ -11892,15 +11890,16 @@ faster than what, there are zillions of web sites on the Internet that tells you one way or another. :) - - Note that various CPUs have different voltage/cooling - requirements. Make sure your motherboard can supply the exact - voltage needed by the CPU. For instance, many recent MMX chips - require split voltage (e.g., 2.9V core, 3.3V I/O). Also, some - AMD and Cyrix/IBM chips run hotter than Intel chips. In that - case, make sure you have good heatsink/fans (you can get the - list of certified parts from their web pages). - + + + Various CPUs have different voltage/cooling requirements. + Make sure your motherboard can supply the exact voltage needed + by the CPU. For instance, many recent MMX chips require split + voltage (e.g., 2.9V core, 3.3V I/O). Also, some AMD and + Cyrix/IBM chips run hotter than Intel chips. In that case, + make sure you have good heatsink/fans (you can get the list of + certified parts from their web pages). + Clock speeds @@ -12254,12 +12253,14 @@ Marks and Spaces are also equivalent to "Holes" and "No Holes" in paper tape systems. - - Note that Breaks cannot be generated from paper tape or - from any other byte value, since bytes are always sent with - Start and Stop bit. The UART is usually capable of - generating the continuous Spacing signal in response to a - special command from the host processor. + + + Breaks cannot be generated from paper tape or from any + other byte value, since bytes are always sent with Start + and Stop bit. The UART is usually capable of generating + the continuous Spacing signal in response to a special + command from the host processor. + @@ -13712,12 +13713,15 @@ slice should be within the 1024 cylinder BIOS limit. During the boot process the bad144 list is read using the BIOS and this only succeeds when the list is within the 1024 cylinder - limit. Note that the restriction is not - that only the root filesystem must be - within the 1024 cylinder limit, but rather the entire - slice that contains the root - filesystem. - + limit. + + + The restriction is not that only the root + filesystem must be within the 1024 + cylinder limit, but rather the entire + slice that contains the root + filesystem. + @@ -14038,15 +14042,16 @@ bus speeds of 20 and 40 million transfers/second are also emerging (Fast-20 == Ultra SCSI and Fast-40 == Ultra2 SCSI). - - It should be noted that the data lines > 8 are only used - for data transfers and device addressing. The transfers of - commands and status messages etc are only performed on the - lowest 8 data lines. The standard allows narrow devices to - operate on a wide bus. The usable bus width is negotiated - between the devices. You have to watch your device addressing - closely when mixing wide and narrow. - + + + The data lines > 8 are only used for data transfers and + device addressing. The transfers of commands and status + messages etc are only performed on the lowest 8 data lines. + The standard allows narrow devices to operate on a wide bus. + The usable bus width is negotiated between the devices. You + have to watch your device addressing closely when mixing wide + and narrow. + Single ended buses @@ -14068,10 +14073,12 @@ becomes 0.75 meters. Be aware that F20 is pushing the limits quite a bit, so you will quickly find out if your SCSI bus is electrically sound. - - Please note that this means that if some devices on your - bus use 'fast' to communicate your bus must adhere to the - length restrictions for fast buses! + + + If some devices on your bus use 'fast' to communicate + your bus must adhere to the length restrictions for fast + buses! + It is obvious that with the newer fast-SCSI devices the bus length can become a real bottleneck. This is why the @@ -14183,12 +14190,14 @@ external device, and not on the controller! In general, every reconfiguration of a SCSI bus must pay attention to this. - - Note that termination is to be done on a per-line basis. - This means if you have both narrow and wide buses connected to - the same host adapter, you need to enable termination on the - higher 8 bits of the bus on the adapter (as well as the last - devices on each bus, of course). + + + Termination is to be done on a per-line basis. This + means if you have both narrow and wide buses connected to + the same host adapter, you need to enable termination on the + higher 8 bits of the bus on the adapter (as well as the last + devices on each bus, of course). + What I did myself is remove all terminators from my SCSI devices and controllers. I own a couple of external @@ -14268,12 +14277,14 @@ maximum is 8 because the selection is done bitwise using the 8 data lines on the bus. For wide buses this increases to the number of data lines (usually 16). - - Note that a narrow SCSI device can not communicate with a - SCSI device with a target ID larger than 7. This means it is - generally not a good idea to move your SCSI host adapter's - target ID to something higher than 7 (or your CD-ROM will stop - working). + + + A narrow SCSI device can not communicate with a SCSI + device with a target ID larger than 7. This means it is + generally not a good idea to move your SCSI host adapter's + target ID to something higher than 7 (or your CD-ROM will + stop working). + The higher the SCSI target ID, the higher the priority the devices has. When it comes to arbitration between devices @@ -14473,13 +14484,17 @@ config file should reflect your actual hardware setup. So, interrupts, I/O addresses etc must match the kernel config file. During system boot messages will be displayed to - indicate whether the configured hardware was actually found. - Note that most of the EISA/PCI drivers (namely ahb, ahc, ncr and amd will automatically obtain the - correct parameters from the host adapters themselves at boot - time; thus, you just need to write, for instance, "controller ahc0". + indicate whether the configured hardware was actually + found. + + + Note that most of the EISA/PCI drivers (namely ahb, ahc, ncr and amd will automatically obtain the + correct parameters from the host adapters themselves at boot + time; thus, you just need to write, for instance, "controller ahc0". + An example loosely based on the FreeBSD 2.2.5-Release kernel config file LINT with some added comments (between @@ -14524,14 +14539,17 @@ number one greater than the highest 'wired down' unit number for that kind of device. So, if you had a SCSI tape at target ID 2 it would be configured as st2, as the tape at target ID 6 - is wired down to unit number 1. Note that wired down - devices need not be found to get their unit - number. The unit number for a wired down device is reserved - for that device, even if it is turned off at boot time. This - allows the device to be turned on and brought on-line at a - later time, without rebooting. Notice that a device's unit - number has no relationship with its - target ID on the SCSI bus. + is wired down to unit number 1. + + + Wired down devices need not be found to get their unit + number. The unit number for a wired down device is reserved + for that device, even if it is turned off at boot time. This + allows the device to be turned on and brought on-line at a + later time, without rebooting. Notice that a device's unit + number has no relationship with its + target ID on the SCSI bus. + Below is another example of a kernel config file as used by FreeBSD version < 2.0.5. The difference with the first @@ -16676,11 +16694,12 @@ font8x14=cp866-8x14 font8x8=cp866-8x8 - - NOTE: ^[ means that real - ESC character must be entered into - /etc/rc.conf, not just ^[ - string. + + + ^[ means that real ESC character must be entered into + /etc/rc.conf, not just ^[ + string. + This tuning means KOI8-R keyboard with Alternative screen font mapped to KOI8-R encoding to preserve @@ -16904,15 +16923,18 @@ first as described. - - NOTE: Russian KOI8-R locale may not work with - old XFree86 releases (lower than 3.3). XFree86 port from - /usr/ports/x11/XFree86 already have - most recent XFree86 version, so it will work, if you install - XFree86 from this port. XFree86 version shipped with the - latest FreeBSD distribution should work too (check XFree86 - version number not less than 3.3 first). + + + Russian KOI8-R locale may + not work with old XFree86 releases (lower than 3.3). + XFree86 port from + /usr/ports/x11/XFree86 already have + most recent XFree86 version, so it will work, if you + install XFree86 from this port. XFree86 version shipped + with the latest FreeBSD distribution should work too + (check XFree86 version number not less than 3.3 + first). + @@ -16950,15 +16972,16 @@ remap=bf>CapsLock. Old CapsLock function still available via Shift+CapsLock (in LAT mode only). - - NOTE: Russian XKB keyboard - may not work with old XFree86 versions, see for - more info. Russian XKB keyboard may not work with - non-localized applications too, minimally localized - application should call XtSetLanguageProc (NULL, NULL, NULL); - function early in the program. + + + Russian XKB keyboard may not work with old XFree86 + versions, see for more info. + Russian XKB keyboard may not work with non-localized + applications too, minimally localized application should + call XtSetLanguageProc + (NULL, NULL, NULL); function early in the program. + @@ -18061,19 +18084,21 @@ if you are using a configuration file that was previously used for a different version of FreeBSD because the device flags have changed between versions. - - Note that port "IO_COM1" is a - substitution for port 0x3f8, - IO_COM2 is 0x2f8, - IO_COM3 is 0x3e8, and - IO_COM4 is 0x2e8, which are - fairly common port addresses for their respective serial ports; - interrupts 4, 3, 5, and 9 are fairly common interrupt request - lines. Also note that regular serial ports cannot share interrupts on ISA-bus PCs - (multiport boards have on-board electronics that allow all the - 16550A's on the board to share one or two interrupt request - lines). + + + port "IO_COM1" is a + substitution for port 0x3f8, + IO_COM2 is 0x2f8, + IO_COM3 is 0x3e8, and + IO_COM4 is 0x2e8, which are + fairly common port addresses for their respective serial ports; + interrupts 4, 3, 5, and 9 are fairly common interrupt request + lines. Also note that regular serial ports cannot share interrupts on ISA-bus PCs + (multiport boards have on-board electronics that allow all the + 16550A's on the board to share one or two interrupt request + lines). + When you are finished adjusting the kernel configuration file, use the program config as documented @@ -19401,9 +19426,13 @@ You will need to create a configuration file called /etc/ppp/ppp.conf. It should look similar - to the example below. Note that lines that end in a ``:'' start - in the first column, all other lines should be indented as shown - using spaces or tabs. + to the example below. + + + Lines that end in a ``:'' start in the first column, all + other lines should be indented as shown using spaces or + tabs. + @@ -20096,13 +20125,13 @@ - - NOTE: Your authkey will be logged if you have command - logging turned on (set log - +command). Care should be taken when deciding the - ppp log file permissions. - + + + Your authkey will be logged + if you have command logging turned on (set log + +command). Care should be taken when deciding the + ppp log file permissions. + @@ -20183,22 +20212,24 @@ network_interfaces="lo0 tun0" ifconfig_tun0= - - Note, the ifconfig_tun0 variable should be - empty, and a file called /etc/start_if.tun0 - should be created. This file should contain the line - - - - ppp -auto mysystem - - - - This script is executed at network configuration time, - starting your ppp daemon in automatic mode. If you have a LAN for - which this machine is a gateway, you may also wish to use the - switch. Refer to the manual page for - further details. + + + The ifconfig_tun0 variable should be empty, + and a file called /etc/start_if.tun0 should + be created. This file should contain the line + + + + ppp -auto mysystem + + + + This script is executed at network configuration time, + starting your ppp daemon in automatic mode. If you have a LAN + for which this machine is a gateway, you may also wish to use + the switch. Refer to the manual page + for further details. + Set the router program to ``NO'' with the line @@ -20674,9 +20705,12 @@ cuaa1, and only use the modem name in my configuration files. It can become quite cumbersome when you need to fix a bunch of files in /etc and - .kermrc's all over the system! (Note that - /dev/cuaa0 is COM1, cuaa1 - is COM2, etc.) + .kermrc's all over the system! + + + /dev/cuaa0 is COM1, + cuaa1 is COM2, etc. + Make sure you have pseudo-device sl 1 in your kernel's config file. It is included in @@ -20801,11 +20835,13 @@ ***\x0d, echo \x0aCONNECTED\x0a (of course, you have to change the hostname and password to fit yours). Then you can just type "slip" from the kermit - prompt to get connected. Note: - leaving your password in plain text anywhere in the - filesystem is generally a BAD idea. Do it at your own risk. - I am just too lazy. - + prompt to get connected. + + + Leaving your password in plain text anywhere in the + filesystem is generally a BAD idea. Do it at your own + risk. I am just too lazy. + @@ -21320,14 +21356,17 @@ arp(8) desires; see the manual page on arp(8) for complete information on usage. - - Note that when you create - /etc/sliphome/slip.login and - /etc/sliphome/slip.logout, the execute - bit (ie, chmod 755 /etc/sliphome/slip.login - /etc/sliphome/slip.logout) must be set, or sliplogin will be unable to execute - it. - + + + When you create + /etc/sliphome/slip.login and + /etc/sliphome/slip.logout, the + execute bit (ie, chmod 755 + /etc/sliphome/slip.login + /etc/sliphome/slip.logout) must be set, or + sliplogin will be unable to execute + it. + @@ -23213,18 +23252,18 @@ especially true if you have installed the most recent release (&rel.current;-RELEASE at the time of this writing) since the stable branch is effectively a bug-fix stream relative to the previous release. - - Please note that the stable tree - endeavors, above all, to be fully compilable and stable at all - times, but we do occasionally make mistakes (these are still - active sources with quickly-transmitted updates, after all). We - also do our best to thoroughly test fixes in - current before bringing them into - stable, but sometimes our tests fail to catch - every case. If something breaks for you in - stable, please let us know - immediately! (see next section). - + + + The stable tree endeavors, above all, + to be fully compilable and stable at all times, but we do + occasionally make mistakes (these are still active sources with + quickly-transmitted updates, after all). We also do our best to + thoroughly test fixes in current before + bringing them into stable, but sometimes + our tests fail to catch every case. If something breaks for you + in stable, please let us know + immediately! (see next section). + @@ -23458,16 +23497,17 @@ /etc/aliases if you want to have the process run in a fully automated fashion. Check the ctm_rmail man page for more details. - - NOTE: No matter what method you use to - get the CTM deltas, you should subscribe to - the ctm-announce@FreeBSD.ORG mailing list. In - the future, this will be the only place where announcements - concerning the operations of the CTM system - will be posted. Send an email to &a.majordomo; with a single - line of ``subscribe ctm-announce'' - to get added to the list. - + + + No matter what method you use to get the + CTM deltas, you should subscribe to the + ctm-announce@FreeBSD.ORG mailing list. In the + future, this will be the only place where announcements + concerning the operations of the CTM system + will be posted. Send an email to &a.majordomo; with a single + line of ``subscribe + ctm-announce'' to get added to the list. + @@ -24009,10 +24049,12 @@ tag=. The main line of development, also known as - FreeBSD-current. Note: the "." is not - punctuation; it is the name of the tag. Valid for - all collections. - + FreeBSD-current. + + + The "." is not punctuation; it is the name + of the tag. Valid for all collections. + @@ -25920,15 +25962,18 @@ Before Starting the Port - - Note: Only a fraction of the overridable variables - (${..}) are mentioned in this - document. Most (if not all) are documented at the start of - bsd.port.mk. This file uses a non-standard - tab setting. Emacs and Vim should recognize the setting on - loading the file. vi or ex can be set to using the correct value - by typing `:set tabstop=4' once the file has - been loaded. + + + Only a fraction of the overridable variables + (${..}) are mentioned in + this document. Most (if not all) are documented at the start + of bsd.port.mk. This file uses a + non-standard tab setting. Emacs and + Vim should recognize the setting on loading + the file. vi or ex can + be set to using the correct value by typing `:set + tabstop=4' once the file has been loaded. + You may come across code that needs modifications or conditional compilation based upon what version of UNIX it is @@ -26074,20 +26119,21 @@ 3.0-current before mount(2) change: 300000 3.0-current as of Nov 1997: 300001 - (Note that 2.2-STABLE sometimes - identifies itself as "2.2.5-STABLE" after the - 2.2.5-RELEASE.) The pattern used to be year followed by - the month, but we decided to change it to a more - straightforward major/minor system starting from 2.2. - This is because the parallel development on several - branches made it infeasible to classify the releases - simply by their real release dates. (Note that if you are - making a port now, you don't have to worry about old - -current's; they are listed here just for your reference.) - + - + + + Note that 2.2-STABLE sometimes identifies itself as + "2.2.5-STABLE" after the 2.2.5-RELEASE. The pattern used to + be year followed by the month, but we decided to change it + to a more straightforward major/minor system starting from + 2.2. This is because the parallel development on several + branches made it infeasible to classify the releases simply + by their real release dates. If you are making a port now, + you don't have to worry about old -current's; they are + listed here just for your reference. + In the hundreds of ports that have been done, there have @@ -26108,12 +26154,13 @@ remap=tt>${DISTDIR}, which defaults to /usr/ports/distfiles. - Note: The following assumes that the software compiled - out-of-the-box, i.e., there was absolutely no change required - for the port to work on your FreeBSD box. If you needed to - change something, you will have to refer to the next section - too. - + + The following assumes that the software compiled + out-of-the-box, i.e., there was absolutely no change required + for the port to work on your FreeBSD box. If you needed to + change something, you will have to refer to the next section + too. + Writing the <filename>Makefile</filename> @@ -26174,11 +26221,15 @@ This is a longer description of the port. One to a few paragraphs concisely explaining what the port does is - sufficient. Note: This is not a manual - nor an in-depth description on how to use or compile the - port. In particular, please do not just copy the - README file here, unless, of - course, it is a concise description of the port. + sufficient. + + + This is not a manual nor an + in-depth description on how to use or compile the port. In + particular, please do not just copy the + README file here, unless, + of course, it is a concise description of the port. + It is recommended that you sign the name at the end of this file, as in: @@ -26407,15 +26458,17 @@ the default target, you can fix it by redefining the `do-<something>' target in your Makefile. - - Note that the `main' targets (e.g., extract, configure, etc.) do nothing more than - make sure all the stages up to that one is completed and call - the real targets or scripts, and they are not intended to be - changed. If you want to fix the extraction, fix do-extract, but never ever touch - extract! + + + The `main' targets (e.g., extract, configure, etc.) do nothing more than + make sure all the stages up to that one is completed and + call the real targets or scripts, and they are not intended + to be changed. If you want to fix the extraction, fix + do-extract, but never ever + touch extract! + Now that you understand what goes on when the user types `make', let us go through the @@ -26473,12 +26526,13 @@ new ports collection is to make each port as `plug-and-play' as possible for the end-user while using a minimum of disk space. - - Note: Unless explicitly stated, patch files, scripts, and - other files you have created and contributed to the FreeBSD - ports collection are assumed to be covered by the standard BSD - copyright conditions. - + + + Unless explicitly stated, patch files, scripts, and + other files you have created and contributed to the FreeBSD + ports collection are assumed to be covered by the standard + BSD copyright conditions. + @@ -26704,14 +26758,17 @@ patch either by running the patch command from there, or copying the patch file into the ${PATCHDIR} directory and calling it - patch-<xx>. (Note the - tarball will have been extracted alongside the regular source - by then, so there is no need to explicitly extract it if it is - a regular gzip'd or compress'd tarball.) If you do the - latter, take extra care not to overwrite something that - already exists in that directory. Also do not forget to add a - command to remove the copied patch in the pre-clean target. + patch-<xx>. + + + Note the tarball will have been extracted alongside the + regular source by then, so there is no need to explicitly + extract it if it is a regular gzip'd or compress'd tarball. + If you do the latter, take extra care not to overwrite + something that already exists in that directory. Also do + not forget to add a command to remove the copied patch in + the pre-clean target. + @@ -26753,11 +26810,13 @@ graphics/jpeg subdirectory of your ports tree to build and install it if it is not found. - - Note that the lib part is - just an argument given to `ldconfig -r | - grep', so periods should be escaped by two - backslashes like in the example above. + + + The lib part is just an argument + given to `ldconfig -r | grep', so + periods should be escaped by two backslashes like in the + example above. + The dependency is checked from within the extract target. Also, the name of the @@ -26794,11 +26853,15 @@ subdirectory of the ports tree if it is not found. It will also see if an executable called `wish' is in your search path, and descend into the x11/tk subdirectory of - your ports tree to build and install it if it is not found. - (Note that in this case, `innd' is actually an executable; if an - executable is in a place that is not expected to be in a - normal user's search path, you should use the full - pathname.) + your ports tree to build and install it if it is not + found. + + + In this case, `innd' is actually an + executable; if an executable is in a place that is not + expected to be in a normal user's search path, you should + use the full pathname. + The dependency is checked from within the install target. Also, the name of the @@ -26823,11 +26886,12 @@ archivers/unzip subdirectory of your ports tree to build and install it if it is not found. - - Note that `build' here means everything from extracting - to compilation. The dependency is checked from within the - extract target. - + + + `build' here means everything from extracting to + compilation. The dependency is checked from within the + extract target. + @@ -26956,13 +27020,14 @@ - - Note that ${MOTIFLIB} - (usually) expands to `' - or `/usr/X11R6/lib/libXm.a', so there is - no need to add `' or `' - in front. - + + + ${MOTIFLIB} (usually) + expands to `' or + `/usr/X11R6/lib/libXm.a', so there is + no need to add `' or + `' in front. + @@ -26993,11 +27058,12 @@ of the directory. : - - Note that this program will not actually - install info files; it merely inserts or - deletes entries in the dir - file. + + + This program will not actually + install info files; it merely inserts or + deletes entries in the dir file. + Here's a seven-step procedure to convert ports to use install-info. I will use @@ -27032,12 +27098,14 @@ entry indentations consistent (we recommend that all entry text start at the 4th tab stop). - Note that you can put only one info entry per file - because of a bug in `install-info - --delete' that deletes only the first entry - if you specify multiple entries in the - @direntry section. - + + Note that you can put only one info entry per file + because of a bug in `install-info + --delete' that deletes only the first entry + if you specify multiple entries in the + @direntry section. + + You can give the dir entries to install-info as arguments ( and @@ -27182,14 +27250,16 @@ - - Note that the `@unexec install-info - --delete' commands have to be listed before - the info files themselves so they can read the files. - Also, the `@exec install-info' commands - have to be after the info files and the - @exec command that creates the the - dir file. + + + The `@unexec install-info + --delete' commands have to be listed before + the info files themselves so they can read the files. + Also, the `@exec install-info' commands + have to be after the info files and the + @exec command that creates the the + dir file. + @@ -27215,12 +27285,14 @@ (export of crypto software) to name just two of them). What we can do with them vary a lot, depending on the exact wordings of the respective licenses. - - Note that it is your responsibility as a porter to read the - licensing terms of the software and make sure that the FreeBSD - project will not be held accountable of violating them by - redistributing the source or compiled binaries either via ftp or - CD-ROM. If in doubt, please contact the &a.ports;. + + + It is your responsibility as a porter to read the + licensing terms of the software and make sure that the FreeBSD + project will not be held accountable of violating them by + redistributing the source or compiled binaries either via ftp + or CD-ROM. If in doubt, please contact the &a.ports;. + There are two variables you can set in the Makefile to handle the situations that arise frequently: @@ -27259,13 +27331,16 @@ - - Note: The GNU General Public License (GPL), both version 1 - and 2, should not be a problem for ports. - - Note: If you are a committer, make sure you update the - ports/LEGAL file too. - + + + The GNU General Public License (GPL), both version 1 + and 2, should not be a problem for ports. + + + + If you are a committer, make sure you update the + ports/LEGAL file too. + @@ -27330,11 +27405,14 @@ Do include package information, i.e. COMMENT, DESCR, and PLIST, in pkg. Note that these files are not - used only for packaging anymore, and are - mandatory now, even if ${NO_PACKAGE} is set. - + remap="tt">pkg. + + + Note that these files are not used only for packaging + anymore, and are mandatory now, even if + ${NO_PACKAGE} is + set. + @@ -27365,9 +27443,11 @@ baz.8 - - Note that this is not usually necessary with ports that - are X applications and use Imake to build. + + + This is not usually necessary with ports that are X + applications and use Imake to build. + If your port anchors its man tree somewhere other than PREFIX, you can use the @@ -27435,12 +27515,15 @@ 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 information. - Note, that this script is not run automatically if you install - the port with `make install'. If - you are depending on it being run, you will have to explicitly - call it on your port's Makefile. - + pkg_add(1) for additional + information. + + + This script is not run automatically if you install the + port with `make install'. If you are + depending on it being run, you will have to explicitly call + it on your port's Makefile. + @@ -27494,9 +27577,12 @@ place the message in pkg/MESSAGE. This capibility is often useful to display additional installation steps to be taken after a pkg_add, or to display licensing - information. (note: the MESSAGE file does - not need to be added to pkg/PLIST). - + information. + + + MESSAGE does not need to be added + to pkg/PLIST). + @@ -27522,11 +27608,12 @@ remap=tt>${DISTDIR} explicitly in your Makefile will not accomplish this, so please use ${DIST_SUBDIR}.) - - Note this does not affect the ${MASTER_SITES} you define in your - Makefile. - + + + This does not affect the ${MASTER_SITES} you define in your + Makefile. + @@ -30464,12 +30551,14 @@ linker only records 3.3 in the headers, and will link with anything starting with libfoo.so.3.(anything >= 3).(highest available). - - Note that ld.so will always use the highest - "minor" revision. Ie: it will use libc.so.2.2 - in preference to libc.so.2.0, even if the - program was initially linked with - libc.so.2.0. + + + ld.so will always use the highest + "minor" revision. Ie: it will use libc.so.2.2 + in preference to libc.so.2.0, even if the + program was initially linked with + libc.so.2.0. + For non-port libraries, it is also our policy to change the shared library version number only once between releases. When you @@ -30489,11 +30578,12 @@ Adding New Kernel Configuration Options Contributed by &a.joerg; - - Note: You should be familiar with the section - about - before reading here. - + + + You should be familiar with the section about + before reading here. + What's a <emphasis>Kernel Option</emphasis>, Anyway? @@ -30680,15 +30770,18 @@ clause in the `config' line of your kernel config file. This is deprecated and should be used only if you want a crash dump from a kernel that crashes during booting. - - Note: In the following, - the term `kgdb' refers to gdb run in `kernel debug mode'. This can be - accomplished by either starting the gdb with the option , or - by linking and starting it under the name kgdb. This is not being done by default, - however, and the idea is basically deprecated since the GNU folks - do not like their tools to behave differently when called by - another name. This feature may well be discontinued in further - releases. + + + In the following, the term `kgdb' refers to + gdb run in `kernel debug mode'. This can be + accomplished by either starting the gdb with + the option , or by linking and starting it + under the name kgdb. This is not being done by + default, however, and the idea is basically deprecated since the + GNU folks do not like their tools to behave differently when + called by another name. This feature may well be discontinued in + further releases. + When the kernel has been built make a copy of it, say kernel.debug, and then run strip @@ -30910,10 +31003,14 @@ to your config file, and rebuild. (See for details on configuring the - FreeBSD kernel. Note that if you have an older version of the boot - blocks, your debugger symbols might not be loaded at all. Update the - boot blocks; the recent ones load the DDB symbols - automagically.) + FreeBSD kernel. + + + Note that if you have an older version of the boot blocks, + your debugger symbols might not be loaded at all. Update the boot + blocks; the recent ones load the DDB symbols + automagically.) + Once your DDB kernel is running, there are several ways to enter DDB. The first, and earliest way is to type the boot flag @@ -30957,9 +31054,13 @@ To get a stack trace, use trace - Note that when entering DDB via a hot-key, the - kernel is currently servicing an interrupt, so the stack trace might - be not of much use for you. + + + + Note that when entering DDB via a hot-key, the kernel is + currently servicing an interrupt, so the stack trace might be not + of much use for you. + If you want to remove a breakpoint, use @@ -30977,9 +31078,13 @@ DDB trace them until the matching return statement is reached by n - Note: this is - different from gdb's `next' statement; - it is like gdb's `finish'. + + + + + This is different from gdb's `next' + statement; it is like gdb's `finish'. + To examine data from memory, use (for example): @@ -31453,48 +31558,51 @@ -> libc.so.4.6.29 + + + Note that if you already have a Linux shared library with + a matching major revision number to the first column of the + 'ldd' output, you will not need to copy the file named in the + last column to your system, the one you already have should + work. It is advisable to copy the shared library anyway if it + is a newer version, though. You can remove the old one, as + long as you make the symbolic link point to the new one. So, + if you have these libraries on your system: + + + /compat/linux/lib/libc.so.4.6.27 + /compat/linux/lib/libc.so.4 -> libc.so.4.6.27 + + - Note that if you already have a Linux shared library with a - matching major revision number to the first column of the 'ldd' - output, you will not need to copy the file named in the last - column to your system, the one you already have should work. It - is advisable to copy the shared library anyway if it is a newer - version, though. You can remove the old one, as long as you make - the symbolic link point to the new one. So, if you have these - libraries on your system: - - /compat/linux/lib/libc.so.4.6.27 - /compat/linux/lib/libc.so.4 -> libc.so.4.6.27 - - - - and you find a new binary that claims to require a later - version according to the output of ldd: - - libc.so.4 (DLL Jump 4.5pl26) -> - libc.so.4.6.29 - - - - If it is only one or two versions out of date in the in the - trailing digit then do not worry about copying - /lib/libc.so.4.6.29 too, because the - program should work fine with the slightly older version. - However, if you like you can decide to replace the - libc.so anyway, and that should leave you - with: - - /compat/linux/lib/libc.so.4.6.29 - /compat/linux/lib/libc.so.4 -> libc.so.4.6.29 - - - - Please note that the symbolic link mechanism is - only needed for Linux binaries. The - FreeBSD runtime linker takes care of looking for matching major - revision numbers itself and you do not need to worry about - it. - + and you find a new binary that claims to require a later + version according to the output of ldd: + + libc.so.4 (DLL Jump 4.5pl26) -> + libc.so.4.6.29 + + + + If it is only one or two versions out of date in the in + the trailing digit then do not worry about copying + /lib/libc.so.4.6.29 too, because the + program should work fine with the slightly older version. + However, if you like you can decide to replace the + libc.so anyway, and that should leave you + with: + + /compat/linux/lib/libc.so.4.6.29 + /compat/linux/lib/libc.so.4 -> libc.so.4.6.29 + + + + + + The symbolic link mechanism is only + needed for Linux binaries. The FreeBSD runtime linker takes + care of looking for matching major revision numbers itself and + you do not need to worry about it. + @@ -31657,11 +31765,13 @@ Finding the necessary files - - Note: the information below is valid as of the time this - document was written, but certain details such as names of ftp - sites, directories and distribution names may have changed by the - time you read this. + + + The information below is valid as of the time this document + was written, but certain details such as names of ftp sites, + directories and distribution names may have changed by the time + you read this. + Linux is distributed by several groups that make their own set of binaries that they distribute. Each distribution has its own @@ -32291,15 +32401,13 @@ a memory address, but not between two I/O ports or two memory locations. - -
- Note: The 8237 does allow two channels - to be connected together to allow memory-to-memory DMA - operations in a non-fly-by mode, but nobody in the PC - industry uses this scarce resource this way since it is faster - to move data between memory locations using the CPU. -
- + + The 8237 does allow two channels to be connected together to + allow memory-to-memory DMA operations in a + non-fly-by mode, but nobody in the PC industry uses + this scarce resource this way since it is faster to move data + between memory locations using the CPU. + In the PC architecture, each DMA channel is normally activated only when the hardware that uses a given DMA channel requests a @@ -32447,15 +32555,13 @@ location 0x0000, not 0x10000. The results of letting this happen are probably not intended. - -
- Note: Physical 64K boundaries - should not be confused with 8086-mode 64K Segments, which - are created by mathematically adding a segment register with - an offset register. Page Registers have no address overlap - and are mathematically OR-ed together. -
- + + Physical 64K boundaries should not be + confused with 8086-mode 64K Segments, which are + created by mathematically adding a segment register with an + offset register. Page Registers have no address overlap and are + mathematically OR-ed together. + To further complicate matters, the external DMA address latches on the PC/AT hold only eight bits, so that gives us @@ -32479,15 +32585,12 @@ buffers are called Bounce Buffers. In the MS-DOS world, they are sometimes called Smart Buffers. - -
- Note: A new implementation of the - 8237, called the 82374, allows 16 bits of page register to be - specified, allows access to the entire 32 bit address space, - without the use of bounce buffers. -
- - + + A new implementation of the 8237, called the 82374, allows + 16 bits of page register to be specified, allows access to the + entire 32 bit address space, without the use of bounce + buffers. + @@ -32585,14 +32688,11 @@ 0, 1, 2, 3, 5, 6 and 7 are usable with peripherals on PC/AT systems. - -
- Note: DMA channel 0 was - reserved for refresh operations in early IBM PC - computers, but is generally available for use by - peripherals in modern systems. -
- + + DMA channel 0 was reserved for refresh operations in + early IBM PC computers, but is generally available for + use by peripherals in modern systems. + When a peripheral is performing Bus Mastering, it is important that the peripheral transmit data to or from @@ -34199,18 +34299,23 @@ the entire cvs-all tree to go from CVSup to CTM without having to rebuild their repository from scratch using a fresh CTM base delta. - - Please note that this special feature only works for the - cvs-all distribution with cvs as the release tag. CVSupping any other - distribution and/or release will get you the specified distribution, - but it will not be suitable for CTM updating. - - Also please note that, because the current version of CTM does - not preserve the timestamps of files, the timestamps at this mirror - site are not the same as those at other mirror sites. Switching - between this site and other sites is not recommended. It will work - correctly, but will be somewhat inefficient. - + + + This special feature only works for the cvs-all distribution with + cvs as the release tag. CVSupping any other + distribution and/or release will get you the specified + distribution, but it will not be suitable for CTM updating. + + + + Because the current version of CTM does not preserve the + timestamps of files, the timestamps at this mirror site are not + the same as those at other mirror sites. Switching between this + site and other sites is not recommended. It will work correctly, + but will be somewhat inefficient. + + Germany diff --git a/en_US.ISO8859-1/books/handbook/book.sgml b/en_US.ISO8859-1/books/handbook/book.sgml index c769392ae5..043f28336e 100644 --- a/en_US.ISO8859-1/books/handbook/book.sgml +++ b/en_US.ISO8859-1/books/handbook/book.sgml @@ -504,15 +504,19 @@ Some core team members also have specific , meaning that they are committed to ensuring that some large - portion of the system works as advertised. Note that most - members of the core team are volunteers when it comes to - FreeBSD development and do not benefit from the project - financially, so "commitment" should also not be misconstrued - as meaning "guaranteed support." The board of directors - analogy above is not actually very accurate, and it may be - more suitable to say that these are the people who gave up - their lives in favor of FreeBSD against their better - judgement! ;) + portion of the system works as advertised. + + + Most members of the core team are volunteers when it + comes to FreeBSD development and do not benefit from the + project financially, so "commitment" should also not be + misconstrued as meaning "guaranteed support." The + board of directors analogy above is not + actually very accurate, and it may be more suitable to say + that these are the people who gave up their lives in favor + of FreeBSD against their better judgement! ;) + @@ -717,9 +721,14 @@ If you're running DOS and have the proper drivers to access your CD, run the install.bat script provided on the CD. This will attempt to boot into the FreeBSD - installation straight from DOS (note: You must - do this from actual DOS and not a Windows DOS - box). If you also want to install FreeBSD + installation straight from DOS. + + + You must do this from actual DOS and not a Windows + DOS box. + + + If you also want to install FreeBSD from your DOS partition (perhaps because your CDROM drive is completely unsupported by FreeBSD) then run the setup program first to copy the appropriate files from the CD to @@ -741,7 +750,12 @@ If you don't have a CDROM distribution then simply download the installation boot disk image file to your hard drive, being sure to tell your browser to save rather than display the file. Note: This disk image can only be used with 1.44 megabyte 3.5 inch floppy disks. + URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/&rel.current;-RELEASE/floppies/boot.flp">installation boot disk image file to your hard drive, being sure to tell your browser to save rather than display the file. + + + This disk image can only be used with 1.44 megabyte 3.5 + inch floppy disks. + @@ -942,23 +956,27 @@ Adaptec AIC-6360 based boards, which includes the - AHA-152x and SoundBlaster SCSI cards. Note: You cannot boot from the - SoundBlaster cards as they have no on-board BIOS, which is - necessary for mapping the boot device into the system BIOS - I/O vectors. They are perfectly usable for external tapes, - CDROMs, etc, however. The same goes for any other AIC-6x60 - based card without a boot ROM. Some systems DO have a boot - ROM, which is generally indicated by some sort of message - when the system is first powered up or reset. Check your - system/board documentation for more details. - + AHA-152x and SoundBlaster SCSI cards. + + + You cannot boot from the + SoundBlaster cards as they have no on-board BIOS, which is + necessary for mapping the boot device into the system BIOS + I/O vectors. They are perfectly usable for external tapes, + CDROMs, etc, however. The same goes for any other AIC-6x60 + based card without a boot ROM. Some systems DO have a boot + ROM, which is generally indicated by some sort of message + when the system is first powered up or reset. Check your + system/board documentation for more details. + - Buslogic 545S & 545c Note: that Buslogic was formerly known - as "Bustek". + Buslogic 545S & 545c + + + Buslogic was formerly known as "Bustek". + @@ -1256,12 +1274,13 @@ - - Note: FreeBSD does not currently support - PnP (plug-n-play) features present on some ethernet cards. If - your card has PnP and is giving you problems, try disabling its - PnP features. - + + + FreeBSD does not currently support + PnP (plug-n-play) features present on some ethernet cards. If + your card has PnP and is giving you problems, try disabling its + PnP features. + + can make a boot floppy with the ``makeflp.bat'' command. + + + If you are running FreeBSD 2.1-RELEASE and have an IDE + CDROM, use the inst_ide.bat or atapiflp.bat batch files + instead. + For the easiest interface of all (from DOS), type ``view''. This will bring up a DOS menu utility that leads you through all @@ -1414,16 +1437,13 @@ to first type: umount /cdrom. Do not just remove it from the drive! - -
- Special note: Before - invoking the installation, be sure that the CDROM is in the - drive so that the install probe can find it. This is also - true if you wish the CDROM to be added to the default system - configuration automatically during the install (whether or not - you actually use it as the installation media). -
- + + Before invoking the installation, be sure that the CDROM is + in the drive so that the install probe can find it. This is + also true if you wish the CDROM to be added to the default + system configuration automatically during the install (whether + or not you actually use it as the installation media). + Finally, if you would like people to be able to FTP install FreeBSD directly from the CDROM in your machine, you will find it @@ -1547,14 +1567,11 @@ should expect to require as much temporary storage as you have stuff written on tape. - -
- Note: When going to do the - installation, the tape must be in the drive - before booting from the boot floppy. The - installation probe may otherwise fail to find it. -
- + + When going to do the installation, the tape must be in the + drive before booting from the boot floppy. + The installation probe may otherwise fail to find it. + @@ -1725,14 +1742,11 @@ - -
- Note: Active and passive - modes are not the same as a `proxy' connection, where a - proxy FTP server is listening and forwarding FTP - requests! -
- + + Active and passive modes are not the same as a `proxy' + connection, where a proxy FTP server is listening and + forwarding FTP requests! + For a proxy FTP server, you should usually give name of the server you really want as a part of the username, after an @@ -3092,9 +3106,12 @@ bsd.ports.mk and bsd.ports.subdir.mk files in your makefiles - directory. (Note: readers with an aversion to - intricate shell-scripts are advised not to follow this - link...) + directory. + + + Readers with an aversion to intricate shell-scripts are + advised not to follow this link...) + @@ -3188,15 +3205,13 @@ i386 directory is common to all platforms which FreeBSD could potentially be ported to. - -
- Note: If there is - not a /usr/src/sys - directory on your system, then the kernel source has not been - been installed. Follow the instructions for installing packages - to add this package to your system. -
- + + If there is not a + /usr/src/sys directory on your system, then + the kernel source has not been been installed. Follow the + instructions for installing packages to add this package to your + system. + Next, move to the i386/conf directory and copy the GENERIC configuration file to the name @@ -3209,13 +3224,11 @@ machine's hostname. We will call it MYKERNEL for the purpose of this example. - -
- Note: You must execute these and all of - the following commands under the root account or you will get - ``permission denied'' errors. -
- + + You must execute these and all of the following commands + under the root account or you will get ``permission denied'' + errors. + Now, edit MYKERNEL with your favorite text editor. If you are just starting out, the only editor available @@ -3236,17 +3249,15 @@ linkend="kernelconfig-config" remap="Configuration File"> section slowly and carefully. - -
- Note: 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 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 - running the next commands. -
- + + 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 + 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 + running the next commands. + When you are finished, type the following to compile and install your kernel: @@ -3263,15 +3274,13 @@ your new kernel . - -
- Note: If you have added any new devices - (such as sound cards) you may have to add some to your - /dev directory before you can use - them. -
- + + If you have added any new devices (such as sound cards) you + may have to add some to your + /dev directory before you can use + them. + @@ -3326,14 +3335,12 @@ remap=tt>machine, which, since FreeBSD only runs on Intel 386 and compatible chips, is i386. - -
- Note: that any keyword which - contains numbers used as text must be enclosed in - quotation marks, otherwise config gets confused and thinks - you mean the actual number 386. -
- + + Any keyword which contains numbers used as text + must be enclosed in quotation marks, otherwise + config gets confused and thinks you + mean the actual number 386. + @@ -3429,23 +3436,19 @@ simultaneous users (like Walnut Creek CDROM's FTP site), you can always increase this number and rebuild. - -
- Note: maxuser does - not limit the number of users - which can log into your machine. It simply sets - various table sizes to reasonable values considering - the maximum number of users you will likely have on - your system and how many processes each of them will - be running. One keyword which - does limit the number of - simultaneous remote logins is + + maxuser does + not limit the number of users which + can log into your machine. It simply sets various table + sizes to reasonable values considering the maximum + number of users you will likely have on your system and + how many processes each of them will be running. One + keyword which does limit the number + of simultaneous remote logins is . -
- + @@ -3488,18 +3491,15 @@ with a separate 387 or 487 chip, you can comment this line out. - -
- Note: The normal math - co-processor emulation routines that come with FreeBSD - are not very accurate. If you do - not have a math co-processor, and you need the best - accuracy, I recommend that you change this option to - GPL_MATH_EMULATE to use the superior - GNU math support, which is not included by default for - licensing reasons. -
- + + The normal math co-processor emulation routines that + come with FreeBSD are not very + accurate. If you do not have a math co-processor, and + you need the best accuracy, I recommend that you change + this option to GPL_MATH_EMULATE to use + the superior GNU math support, which is not included by + default for licensing reasons. + @@ -3561,14 +3561,11 @@ Support for System V messages. Again, only adds a few hundred bytes to the kernel. - -
- Note: The - ipcs(1) command will tell will list - any processes using each of these System V - facilities. -
- + + The ipcs(1) command will tell + will list any processes using each of these System V + facilities. + @@ -3661,28 +3658,22 @@ - -
- Note: Replace the - /dev/wd1s2b with the name of your - swap partition, which will be listed in your - /etc/fstab as follows: - - /dev/wd1s2b none swap sw 0 0 - - -
- + + Replace the /dev/wd1s2b with + the name of your swap partition, which will be listed in + your /etc/fstab as follows: + + /dev/wd1s2b none swap sw 0 0 + + + - -
- Note: Also, the - MFS filesystem can - not be dynamically loaded, so you - must compile it into your kernel - if you want to experiment with it. -
- + + Also, the MFS filesystem can + not be dynamically loaded, so you + must compile it into your kernel if + you want to experiment with it. + @@ -3750,14 +3741,12 @@ attached to the floppy controller. Comment out any lines corresponding to devices you do not have. - -
- Note: QIC-80 tape support - requires a separate filter program called - ft(8), see the manual page for - details. + + QIC-80 tape support requires a separate filter + program called ft(8), see the manual + page for details.
- + @@ -4089,15 +4078,13 @@ Use this device if you have a Logitech or ATI InPort bus mouse card. - -
- Note: If you have a serial - mouse, ignore these two lines, and instead, make sure - the appropriate + If you have a serial mouse, ignore these two lines, + and instead, make sure the appropriate port is enabled (probably - COM1). -
- + COM1). + @@ -4335,14 +4322,11 @@ - -
- Note: With certain cards - (notably the NE2000) you will have to change the port - and/or IRQ since there is no ``standard'' location for - these cards. -
- + + With certain cards (notably the NE2000) you will + have to change the port and/or IRQ since there is no + ``standard'' location for these cards. + @@ -4474,17 +4458,14 @@ SoundBlaster digital audio. - -
- Note: If your SoundBlaster is - on a different IRQ (such as 5), change irq 7 to, for example, irq 5 and remove the conflicts keyword. Also, you - must add the line: options - ``SBC_IRQ=5'' -
- + + If your SoundBlaster is on a different IRQ (such as + 5), change irq 7 to, for + example, irq 5 and remove + the conflicts keyword. + Also, you must add the line: options + ``SBC_IRQ=5'' + @@ -4493,15 +4474,12 @@ SoundBlaster 16 digital 16-bit audio. - -
- Note: If your SB16 is on a - different 16-bit DMA channel (such as 6 or 7), change - the drq 5 keyword - appropriately, and then add the line: options - "SB16_DMA=6" -
- + + If your SB16 is on a different 16-bit DMA channel + (such as 6 or 7), change the drq + 5 keyword appropriately, and then add the + line: options "SB16_DMA=6" + @@ -4570,16 +4548,13 @@ - -
- Note: There is some additional - documentation in - /usr/src/sys/i386/isa/sound/sound.doc. - Also, if you add any of these devices, be sure to create the - sound . -
- + + There is some additional documentation in + /usr/src/sys/i386/isa/sound/sound.doc. + Also, if you add any of these devices, be sure to create the + sound . + @@ -4750,25 +4725,26 @@ For sound cards, the command: # sh MAKEDEV snd0 - creates the appropriate entries. Note: when - creating device nodes for devices such as sound cards, if other - people have access to your machine, it may be desirable to protect - the devices from outside access by adding them to the - /etc/fbtab file. See man - fbtab for more information. + creates the appropriate entries. + + + When creating device nodes for devices such as sound cards, if + other people have access to your machine, it may be desirable to + protect the devices from outside access by adding them to the + /etc/fbtab file. See man + fbtab for more information. + Follow this simple procedure for any other non-GENERIC devices which do not have entries. - -
- Note: All SCSI controllers use the same - set of /dev entries, so you do not need to - create these. Also, network cards and SLIP/PPP pseudo-devices - do not have entries in /dev at all, so you - do not have to worry about these either. -
- + + All SCSI controllers use the same set of + /dev entries, so you do not need to create + these. Also, network cards and SLIP/PPP pseudo-devices do not + have entries in /dev at all, so you do not + have to worry about these either. + @@ -4832,33 +4808,31 @@ dmesg(8) command will print the kernel messages from the current boot. - -
- Note: If you are having trouble - building a kernel, make sure to keep a GENERIC, or some - other kernel that is known to work on hand as a - different name that will not get erased on the next - build. You cannot rely on - kernel.old because when installing - a new kernel, kernel.old is - overwritten with the last installed kernel which may be - non-functional. Also, as soon as possible, move the - working kernel to the proper ``kernel'' location or - commands such as ps(1) will not work - properly. The proper command to unlock the kernel - file that make installs - (in order to move another kernel back permanently) is: + + If you are having trouble building a kernel, make sure + to keep a GENERIC, or some other kernel that is known to + work on hand as a different name that will not get erased + on the next build. You cannot rely on + kernel.old because when installing a + new kernel, kernel.old is overwritten + with the last installed kernel which may be + non-functional. Also, as soon as possible, move the + working kernel to the proper ``kernel'' location or + commands such as ps(1) will not work + properly. The proper command to unlock the + kernel file that make installs (in + order to move another kernel back permanently) is: # chflags noschg /kernel - And, if you want to lock your new - kernel into place, or any file for that matter, so that - it cannot be moved or tampered with: + And, if you want to + lock your new kernel into place, or any + file for that matter, so that it cannot be moved or + tampered with: # chflags schg /kernel -
- + @@ -5779,20 +5753,19 @@ use the facilities provided in the FreeBSD kernel to implement them. - -
- Note: People often think that - having a firewall between your companies internal network and - the Big Bad Internet will solve all your security problems. - It may help, but a poorly setup firewall system is more of a - security risk than not having one at all. A firewall can only - add another layer of security to your systems, but they will not - be able to stop a really determined hacker from penetrating your - internal network. If you let internal security lapse because you - believe your firewall to be impenetrable, you have just made the - hackers job that bit easier. -
- + + People often think that having a firewall between your + companies internal network and the Big Bad Internet + will solve all your security problems. + + It may help, but a poorly setup firewall system is more of a + security risk than not having one at all. A firewall can only add + another layer of security to your systems, but they will not be + able to stop a really determined hacker from penetrating your + internal network. If you let internal security lapse because you + believe your firewall to be impenetrable, you have just made the + hackers job that bit easier. + @@ -6428,14 +6401,12 @@ Building a packet filtering firewall - -
- Note: The following - suggestions are just that: suggestions. The requirements of - each firewall are different and I cannot tell you how to build - a firewall to meet your particular requirements. -
- + + The following suggestions are just that: suggestions. The + requirements of each firewall are different and I cannot tell + you how to build a firewall to meet your particular + requirements. + When initially setting up your firewall, unless you have a test bench setup where you can configure your firewall host in a @@ -6447,21 +6418,19 @@ tracing of possible attacks and also modification of the firewall rules if your requirements alter. - -
- Note: If you use the logging - versions of the accept command, - it can generate large amounts of log data - as one log line will be generated for every packet that passes - through the firewall, so large ftp/http transfers, etc, will - really slow the system down. It also increases the latencies - on those packets as it requires more work to be done by the - kernel before the packet can be passed on. syslogd with also - start using up a lot more processor time as it logs all the - extra data to disk, and it could quite easily fill the - partition /var/log is located on. -
- + + If you use the logging versions of the accept command, it can generate + large amounts of log data as one log line + will be generated for every packet that passes through the + firewall, so large ftp/http transfers, etc, will really slow the + system down. It also increases the latencies on those packets as + it requires more work to be done by the kernel before the packet + can be passed on. syslogd with also start using up a lot more + processor time as it logs all the extra data to disk, and it + could quite easily fill the partition + /var/log is located on. + As currently supplied, FreeBSD does not have the ability to load firewall rules at boot time. My suggestion is to put a call @@ -7226,14 +7195,18 @@ %!PS 100 100 moveto 300 300 lineto stroke 310 310 moveto /Helvetica findfont 12 scalefont setfont (Is this thing working?) show showpage - Note: When this - document refers to a printer language, I am assuming a - language like PostScript, and not Hewlett Packard's PCL. - Although PCL has great functionality, you can intermingle - plain text with its escape sequences. PostScript cannot - directly print plain text, and that is the kind of printer - language for which we must make special accommodations. + + + + When this document refers to a printer language, I am + assuming a language like PostScript, and not Hewlett + Packard's PCL. Although PCL has great functionality, you can + intermingle plain text with its escape sequences. + PostScript cannot directly print plain text, and that is the + kind of printer language for which we must make special + accommodations. + @@ -7502,12 +7475,14 @@ - - Note: Language-based printers, such as - PostScript printers, cannot directly print plain text. The - simple setup outlined above and described in the following - sections assumes that if you are installing such a printer you - will print only files that the printer can understand. + + + Language-based printers, such as PostScript printers, + cannot directly print plain text. The simple setup outlined + above and described in the following sections assumes that if + you are installing such a printer you will print only files + that the printer can understand. + Users often expect that they can print plain text to any of the printers installed on your system. Programs that interface @@ -7636,22 +7611,24 @@ mkdir /var/spool/lpd/bamboo - - Note: If you are concerned about the - privacy of jobs that users print, you might want to protect - the spooling directory so it is not publicly accessible. - Spooling directories should be owned and be readable, - writable, and searchable by user daemon and group daemon, and - no one else. We will do this for our example printers: - - - - chown daemon.daemon /var/spool/lpd/rattan chown - daemon.daemon /var/spool/lpd/bamboo chmod 770 - /var/spool/lpd/rattan chmod 770 - /var/spool/lpd/bamboo - - + + + If you are concerned about the privacy of jobs that + users print, you might want to protect the spooling + directory so it is not publicly accessible. Spooling + directories should be owned and be readable, writable, and + searchable by user daemon and group daemon, and no one else. + We will do this for our example printers: + + + + chown daemon.daemon /var/spool/lpd/rattan chown + daemon.daemon /var/spool/lpd/bamboo chmod 770 + /var/spool/lpd/rattan chmod 770 + /var/spool/lpd/bamboo + + + Finally, you need to tell LPD about these directories using the /etc/printcap file. You @@ -8048,15 +8025,16 @@ to find out how to do this. - - Note: If you boot your - system into other operating systems besides - FreeBSD, you may have to - reconfigure the printer to - use a an interpretation for CR and LF characters - that those other operating systems use. You - might prefer one of the other solutions, - below. + + + If you boot your system into other + operating systems besides FreeBSD, you may + have to reconfigure the + printer to use a an interpretation for CR and + LF characters that those other operating + systems use. You might prefer one of the + other solutions, below. + @@ -8498,26 +8476,27 @@ lprm -P rattan - - - Note: If you are working in a networked - environment, - - lprm will - let you remove jobs only from the host from which the jobs were - submitted, even if the same printer is available from other hosts. - The following command sequence demonstrates this: - - rose% lpr -P rattan myfile rose% rlogin orchid - orchid% lpq -P rattan Rank Owner Job Files - Total Size active seeyan 12 ... - 49123 bytes 2nd kelly 13 myfile - 12 bytes orchid% lprm -P rattan 13 rose: Permission denied - orchid% logout rose% lprm -P rattan 13 dfA013rose dequeued - cfA013rose dequeued rose% - - - + + + If you are working in a networked + environment, + + lprm + will let you remove jobs only from the host from which the jobs + were submitted, even if the same printer is available from other + hosts. The following command sequence demonstrates this: + + rose% lpr -P rattan myfile rose% rlogin orchid + orchid% lpq -P rattan Rank Owner Job Files Total + Size active seeyan 12 ... 49123 bytes 2nd kelly + 13 myfile 12 bytes orchid% lprm -P rattan 13 rose: + Permission denied orchid% logout rose% lprm -P rattan 13 + dfA013rose dequeued cfA013rose dequeued rose% + + + + - - Note: All of these options except - and require conversion - filters installed for the destination printer. For example, the - option requires the DVI conversion filter. - Section + All of these options except and + require conversion filters installed for + the destination printer. For example, the + option requires the DVI conversion filter. Section gives details. + @@ -8601,9 +8581,11 @@ number, indent by 8 columns. This option works only with certain conversion filters. - - Note: Do not put any space - between the and the number. + + + Do not put any space between the + and the number. + @@ -8750,13 +8732,14 @@ There is a drawback, though: since LPD will refer to the original files directly, you cannot modify or remove them until they have been printed. - - Note: If you are printing to a - remote printer, LPD will eventually have to copy files - from the local host to the remote host, so the - option will save space only on the - local spooling directory, not the remote. It is still - useful, though. + + + If you are printing to a remote printer, LPD will + eventually have to copy files from the local host to + the remote host, so the option + will save space only on the local spooling directory, + not the remote. It is still useful, though. + @@ -8812,12 +8795,14 @@ -h - Do not print any header page. - Note: At some sites, this option - may have no effect due to the way header pages are - generated. See Do not print any header page. + + + At some sites, this option may have no effect due + to the way header pages are generated. See for details. + @@ -10006,12 +9991,14 @@ Options"> for more lpr options. - - Note: LPD prints a form feed - character after the header page. If your printer uses a - different character or sequence of characters to eject a page, - specify them with the ff - capability in /etc/printcap. + + + LPD prints a form feed character after the header page. + If your printer uses a different character or sequence of + characters to eject a page, specify them with the ff capability in + /etc/printcap. + @@ -10618,10 +10605,10 @@ remap=tt>bamboo. It might be the case that we only allow certain logins on orchid anyway, and want them to have access to the printer. Or not. - - Note: there can be only one restricted - group per printer. - + + + There can be only one restricted group per printer. + mx capability. The units are in BUFSIZ blocks, which are 1024 bytes. If you put a zero for this capability, there will be no limit on file - size. Note that the limit applies to files - in a job, and not the total job size. + + + The limit applies to files in a job, + and not the total job size. + LPD will not refuse a file that is larger than the limit you place on a printer. Instead, it will queue as much of the file @@ -11517,15 +11507,23 @@ URL="http://www.asus.com.tw/Products/Motherboard/Pentiumpro/P2l97-s/index.html">P2l97-S motherboard with the on-board Adaptec SCSI WIDE controller. For Pentium machines, the ASUS P55T2P4 motherboard appears to be a good choice for mid-to-high range Pentium server and workstation systems. You might also wish to investigate ASUS's 486SP3G offering if it's a 486-class motherboard you're looking for (Note: These have become increasingly hard to get as ASUS apparently no longer manufactures them). + URL="http://www.asus.com.tw/Products/Motherboard/Pentium/P55tp4/index.html">P55T2P4 motherboard appears to be a good choice for mid-to-high range Pentium server and workstation systems. You might also wish to investigate ASUS's 486SP3G offering if it's a 486-class motherboard you're looking for. + + + These have become increasingly hard to get as ASUS + apparently no longer manufactures them). + Those wishing to build more fault-tolerant systems should also be sure to use Parity memory or, for truly 24/7 - applications, ECC memory. Note that ECC memory does involve a - slight performance trade-off (which may or may not be noticeable - depending on your application) but buys you significantly - increased fault-tolerance to memory errors. - + applications, ECC memory. + + + ECC memory does involve a slight performance trade-off + (which may or may not be noticeable depending on your + application) but buys you significantly increased + fault-tolerance to memory errors. + @@ -11892,15 +11890,16 @@ faster than what, there are zillions of web sites on the Internet that tells you one way or another. :) - - Note that various CPUs have different voltage/cooling - requirements. Make sure your motherboard can supply the exact - voltage needed by the CPU. For instance, many recent MMX chips - require split voltage (e.g., 2.9V core, 3.3V I/O). Also, some - AMD and Cyrix/IBM chips run hotter than Intel chips. In that - case, make sure you have good heatsink/fans (you can get the - list of certified parts from their web pages). - + + + Various CPUs have different voltage/cooling requirements. + Make sure your motherboard can supply the exact voltage needed + by the CPU. For instance, many recent MMX chips require split + voltage (e.g., 2.9V core, 3.3V I/O). Also, some AMD and + Cyrix/IBM chips run hotter than Intel chips. In that case, + make sure you have good heatsink/fans (you can get the list of + certified parts from their web pages). + Clock speeds @@ -12254,12 +12253,14 @@ Marks and Spaces are also equivalent to "Holes" and "No Holes" in paper tape systems. - - Note that Breaks cannot be generated from paper tape or - from any other byte value, since bytes are always sent with - Start and Stop bit. The UART is usually capable of - generating the continuous Spacing signal in response to a - special command from the host processor. + + + Breaks cannot be generated from paper tape or from any + other byte value, since bytes are always sent with Start + and Stop bit. The UART is usually capable of generating + the continuous Spacing signal in response to a special + command from the host processor. + @@ -13712,12 +13713,15 @@ slice should be within the 1024 cylinder BIOS limit. During the boot process the bad144 list is read using the BIOS and this only succeeds when the list is within the 1024 cylinder - limit. Note that the restriction is not - that only the root filesystem must be - within the 1024 cylinder limit, but rather the entire - slice that contains the root - filesystem. - + limit. + + + The restriction is not that only the root + filesystem must be within the 1024 + cylinder limit, but rather the entire + slice that contains the root + filesystem. + @@ -14038,15 +14042,16 @@ bus speeds of 20 and 40 million transfers/second are also emerging (Fast-20 == Ultra SCSI and Fast-40 == Ultra2 SCSI). - - It should be noted that the data lines > 8 are only used - for data transfers and device addressing. The transfers of - commands and status messages etc are only performed on the - lowest 8 data lines. The standard allows narrow devices to - operate on a wide bus. The usable bus width is negotiated - between the devices. You have to watch your device addressing - closely when mixing wide and narrow. - + + + The data lines > 8 are only used for data transfers and + device addressing. The transfers of commands and status + messages etc are only performed on the lowest 8 data lines. + The standard allows narrow devices to operate on a wide bus. + The usable bus width is negotiated between the devices. You + have to watch your device addressing closely when mixing wide + and narrow. + Single ended buses @@ -14068,10 +14073,12 @@ becomes 0.75 meters. Be aware that F20 is pushing the limits quite a bit, so you will quickly find out if your SCSI bus is electrically sound. - - Please note that this means that if some devices on your - bus use 'fast' to communicate your bus must adhere to the - length restrictions for fast buses! + + + If some devices on your bus use 'fast' to communicate + your bus must adhere to the length restrictions for fast + buses! + It is obvious that with the newer fast-SCSI devices the bus length can become a real bottleneck. This is why the @@ -14183,12 +14190,14 @@ external device, and not on the controller! In general, every reconfiguration of a SCSI bus must pay attention to this. - - Note that termination is to be done on a per-line basis. - This means if you have both narrow and wide buses connected to - the same host adapter, you need to enable termination on the - higher 8 bits of the bus on the adapter (as well as the last - devices on each bus, of course). + + + Termination is to be done on a per-line basis. This + means if you have both narrow and wide buses connected to + the same host adapter, you need to enable termination on the + higher 8 bits of the bus on the adapter (as well as the last + devices on each bus, of course). + What I did myself is remove all terminators from my SCSI devices and controllers. I own a couple of external @@ -14268,12 +14277,14 @@ maximum is 8 because the selection is done bitwise using the 8 data lines on the bus. For wide buses this increases to the number of data lines (usually 16). - - Note that a narrow SCSI device can not communicate with a - SCSI device with a target ID larger than 7. This means it is - generally not a good idea to move your SCSI host adapter's - target ID to something higher than 7 (or your CD-ROM will stop - working). + + + A narrow SCSI device can not communicate with a SCSI + device with a target ID larger than 7. This means it is + generally not a good idea to move your SCSI host adapter's + target ID to something higher than 7 (or your CD-ROM will + stop working). + The higher the SCSI target ID, the higher the priority the devices has. When it comes to arbitration between devices @@ -14473,13 +14484,17 @@ config file should reflect your actual hardware setup. So, interrupts, I/O addresses etc must match the kernel config file. During system boot messages will be displayed to - indicate whether the configured hardware was actually found. - Note that most of the EISA/PCI drivers (namely ahb, ahc, ncr and amd will automatically obtain the - correct parameters from the host adapters themselves at boot - time; thus, you just need to write, for instance, "controller ahc0". + indicate whether the configured hardware was actually + found. + + + Note that most of the EISA/PCI drivers (namely ahb, ahc, ncr and amd will automatically obtain the + correct parameters from the host adapters themselves at boot + time; thus, you just need to write, for instance, "controller ahc0". + An example loosely based on the FreeBSD 2.2.5-Release kernel config file LINT with some added comments (between @@ -14524,14 +14539,17 @@ number one greater than the highest 'wired down' unit number for that kind of device. So, if you had a SCSI tape at target ID 2 it would be configured as st2, as the tape at target ID 6 - is wired down to unit number 1. Note that wired down - devices need not be found to get their unit - number. The unit number for a wired down device is reserved - for that device, even if it is turned off at boot time. This - allows the device to be turned on and brought on-line at a - later time, without rebooting. Notice that a device's unit - number has no relationship with its - target ID on the SCSI bus. + is wired down to unit number 1. + + + Wired down devices need not be found to get their unit + number. The unit number for a wired down device is reserved + for that device, even if it is turned off at boot time. This + allows the device to be turned on and brought on-line at a + later time, without rebooting. Notice that a device's unit + number has no relationship with its + target ID on the SCSI bus. + Below is another example of a kernel config file as used by FreeBSD version < 2.0.5. The difference with the first @@ -16676,11 +16694,12 @@ font8x14=cp866-8x14 font8x8=cp866-8x8 - - NOTE: ^[ means that real - ESC character must be entered into - /etc/rc.conf, not just ^[ - string. + + + ^[ means that real ESC character must be entered into + /etc/rc.conf, not just ^[ + string. + This tuning means KOI8-R keyboard with Alternative screen font mapped to KOI8-R encoding to preserve @@ -16904,15 +16923,18 @@ first as described. - - NOTE: Russian KOI8-R locale may not work with - old XFree86 releases (lower than 3.3). XFree86 port from - /usr/ports/x11/XFree86 already have - most recent XFree86 version, so it will work, if you install - XFree86 from this port. XFree86 version shipped with the - latest FreeBSD distribution should work too (check XFree86 - version number not less than 3.3 first). + + + Russian KOI8-R locale may + not work with old XFree86 releases (lower than 3.3). + XFree86 port from + /usr/ports/x11/XFree86 already have + most recent XFree86 version, so it will work, if you + install XFree86 from this port. XFree86 version shipped + with the latest FreeBSD distribution should work too + (check XFree86 version number not less than 3.3 + first). + @@ -16950,15 +16972,16 @@ remap=bf>CapsLock. Old CapsLock function still available via Shift+CapsLock (in LAT mode only). - - NOTE: Russian XKB keyboard - may not work with old XFree86 versions, see for - more info. Russian XKB keyboard may not work with - non-localized applications too, minimally localized - application should call XtSetLanguageProc (NULL, NULL, NULL); - function early in the program. + + + Russian XKB keyboard may not work with old XFree86 + versions, see for more info. + Russian XKB keyboard may not work with non-localized + applications too, minimally localized application should + call XtSetLanguageProc + (NULL, NULL, NULL); function early in the program. + @@ -18061,19 +18084,21 @@ if you are using a configuration file that was previously used for a different version of FreeBSD because the device flags have changed between versions. - - Note that port "IO_COM1" is a - substitution for port 0x3f8, - IO_COM2 is 0x2f8, - IO_COM3 is 0x3e8, and - IO_COM4 is 0x2e8, which are - fairly common port addresses for their respective serial ports; - interrupts 4, 3, 5, and 9 are fairly common interrupt request - lines. Also note that regular serial ports cannot share interrupts on ISA-bus PCs - (multiport boards have on-board electronics that allow all the - 16550A's on the board to share one or two interrupt request - lines). + + + port "IO_COM1" is a + substitution for port 0x3f8, + IO_COM2 is 0x2f8, + IO_COM3 is 0x3e8, and + IO_COM4 is 0x2e8, which are + fairly common port addresses for their respective serial ports; + interrupts 4, 3, 5, and 9 are fairly common interrupt request + lines. Also note that regular serial ports cannot share interrupts on ISA-bus PCs + (multiport boards have on-board electronics that allow all the + 16550A's on the board to share one or two interrupt request + lines). + When you are finished adjusting the kernel configuration file, use the program config as documented @@ -19401,9 +19426,13 @@ You will need to create a configuration file called /etc/ppp/ppp.conf. It should look similar - to the example below. Note that lines that end in a ``:'' start - in the first column, all other lines should be indented as shown - using spaces or tabs. + to the example below. + + + Lines that end in a ``:'' start in the first column, all + other lines should be indented as shown using spaces or + tabs. + @@ -20096,13 +20125,13 @@ - - NOTE: Your authkey will be logged if you have command - logging turned on (set log - +command). Care should be taken when deciding the - ppp log file permissions. - + + + Your authkey will be logged + if you have command logging turned on (set log + +command). Care should be taken when deciding the + ppp log file permissions. + @@ -20183,22 +20212,24 @@ network_interfaces="lo0 tun0" ifconfig_tun0= - - Note, the ifconfig_tun0 variable should be - empty, and a file called /etc/start_if.tun0 - should be created. This file should contain the line - - - - ppp -auto mysystem - - - - This script is executed at network configuration time, - starting your ppp daemon in automatic mode. If you have a LAN for - which this machine is a gateway, you may also wish to use the - switch. Refer to the manual page for - further details. + + + The ifconfig_tun0 variable should be empty, + and a file called /etc/start_if.tun0 should + be created. This file should contain the line + + + + ppp -auto mysystem + + + + This script is executed at network configuration time, + starting your ppp daemon in automatic mode. If you have a LAN + for which this machine is a gateway, you may also wish to use + the switch. Refer to the manual page + for further details. + Set the router program to ``NO'' with the line @@ -20674,9 +20705,12 @@ cuaa1, and only use the modem name in my configuration files. It can become quite cumbersome when you need to fix a bunch of files in /etc and - .kermrc's all over the system! (Note that - /dev/cuaa0 is COM1, cuaa1 - is COM2, etc.) + .kermrc's all over the system! + + + /dev/cuaa0 is COM1, + cuaa1 is COM2, etc. + Make sure you have pseudo-device sl 1 in your kernel's config file. It is included in @@ -20801,11 +20835,13 @@ ***\x0d, echo \x0aCONNECTED\x0a (of course, you have to change the hostname and password to fit yours). Then you can just type "slip" from the kermit - prompt to get connected. Note: - leaving your password in plain text anywhere in the - filesystem is generally a BAD idea. Do it at your own risk. - I am just too lazy. - + prompt to get connected. + + + Leaving your password in plain text anywhere in the + filesystem is generally a BAD idea. Do it at your own + risk. I am just too lazy. + @@ -21320,14 +21356,17 @@ arp(8) desires; see the manual page on arp(8) for complete information on usage. - - Note that when you create - /etc/sliphome/slip.login and - /etc/sliphome/slip.logout, the execute - bit (ie, chmod 755 /etc/sliphome/slip.login - /etc/sliphome/slip.logout) must be set, or sliplogin will be unable to execute - it. - + + + When you create + /etc/sliphome/slip.login and + /etc/sliphome/slip.logout, the + execute bit (ie, chmod 755 + /etc/sliphome/slip.login + /etc/sliphome/slip.logout) must be set, or + sliplogin will be unable to execute + it. + @@ -23213,18 +23252,18 @@ especially true if you have installed the most recent release (&rel.current;-RELEASE at the time of this writing) since the stable branch is effectively a bug-fix stream relative to the previous release. - - Please note that the stable tree - endeavors, above all, to be fully compilable and stable at all - times, but we do occasionally make mistakes (these are still - active sources with quickly-transmitted updates, after all). We - also do our best to thoroughly test fixes in - current before bringing them into - stable, but sometimes our tests fail to catch - every case. If something breaks for you in - stable, please let us know - immediately! (see next section). - + + + The stable tree endeavors, above all, + to be fully compilable and stable at all times, but we do + occasionally make mistakes (these are still active sources with + quickly-transmitted updates, after all). We also do our best to + thoroughly test fixes in current before + bringing them into stable, but sometimes + our tests fail to catch every case. If something breaks for you + in stable, please let us know + immediately! (see next section). + @@ -23458,16 +23497,17 @@ /etc/aliases if you want to have the process run in a fully automated fashion. Check the ctm_rmail man page for more details. - - NOTE: No matter what method you use to - get the CTM deltas, you should subscribe to - the ctm-announce@FreeBSD.ORG mailing list. In - the future, this will be the only place where announcements - concerning the operations of the CTM system - will be posted. Send an email to &a.majordomo; with a single - line of ``subscribe ctm-announce'' - to get added to the list. - + + + No matter what method you use to get the + CTM deltas, you should subscribe to the + ctm-announce@FreeBSD.ORG mailing list. In the + future, this will be the only place where announcements + concerning the operations of the CTM system + will be posted. Send an email to &a.majordomo; with a single + line of ``subscribe + ctm-announce'' to get added to the list. + @@ -24009,10 +24049,12 @@ tag=. The main line of development, also known as - FreeBSD-current. Note: the "." is not - punctuation; it is the name of the tag. Valid for - all collections. - + FreeBSD-current. + + + The "." is not punctuation; it is the name + of the tag. Valid for all collections. + @@ -25920,15 +25962,18 @@ Before Starting the Port - - Note: Only a fraction of the overridable variables - (${..}) are mentioned in this - document. Most (if not all) are documented at the start of - bsd.port.mk. This file uses a non-standard - tab setting. Emacs and Vim should recognize the setting on - loading the file. vi or ex can be set to using the correct value - by typing `:set tabstop=4' once the file has - been loaded. + + + Only a fraction of the overridable variables + (${..}) are mentioned in + this document. Most (if not all) are documented at the start + of bsd.port.mk. This file uses a + non-standard tab setting. Emacs and + Vim should recognize the setting on loading + the file. vi or ex can + be set to using the correct value by typing `:set + tabstop=4' once the file has been loaded. + You may come across code that needs modifications or conditional compilation based upon what version of UNIX it is @@ -26074,20 +26119,21 @@ 3.0-current before mount(2) change: 300000 3.0-current as of Nov 1997: 300001 - (Note that 2.2-STABLE sometimes - identifies itself as "2.2.5-STABLE" after the - 2.2.5-RELEASE.) The pattern used to be year followed by - the month, but we decided to change it to a more - straightforward major/minor system starting from 2.2. - This is because the parallel development on several - branches made it infeasible to classify the releases - simply by their real release dates. (Note that if you are - making a port now, you don't have to worry about old - -current's; they are listed here just for your reference.) - + - + + + Note that 2.2-STABLE sometimes identifies itself as + "2.2.5-STABLE" after the 2.2.5-RELEASE. The pattern used to + be year followed by the month, but we decided to change it + to a more straightforward major/minor system starting from + 2.2. This is because the parallel development on several + branches made it infeasible to classify the releases simply + by their real release dates. If you are making a port now, + you don't have to worry about old -current's; they are + listed here just for your reference. + In the hundreds of ports that have been done, there have @@ -26108,12 +26154,13 @@ remap=tt>${DISTDIR}, which defaults to /usr/ports/distfiles. - Note: The following assumes that the software compiled - out-of-the-box, i.e., there was absolutely no change required - for the port to work on your FreeBSD box. If you needed to - change something, you will have to refer to the next section - too. - + + The following assumes that the software compiled + out-of-the-box, i.e., there was absolutely no change required + for the port to work on your FreeBSD box. If you needed to + change something, you will have to refer to the next section + too. + Writing the <filename>Makefile</filename> @@ -26174,11 +26221,15 @@ This is a longer description of the port. One to a few paragraphs concisely explaining what the port does is - sufficient. Note: This is not a manual - nor an in-depth description on how to use or compile the - port. In particular, please do not just copy the - README file here, unless, of - course, it is a concise description of the port. + sufficient. + + + This is not a manual nor an + in-depth description on how to use or compile the port. In + particular, please do not just copy the + README file here, unless, + of course, it is a concise description of the port. + It is recommended that you sign the name at the end of this file, as in: @@ -26407,15 +26458,17 @@ the default target, you can fix it by redefining the `do-<something>' target in your Makefile. - - Note that the `main' targets (e.g., extract, configure, etc.) do nothing more than - make sure all the stages up to that one is completed and call - the real targets or scripts, and they are not intended to be - changed. If you want to fix the extraction, fix do-extract, but never ever touch - extract! + + + The `main' targets (e.g., extract, configure, etc.) do nothing more than + make sure all the stages up to that one is completed and + call the real targets or scripts, and they are not intended + to be changed. If you want to fix the extraction, fix + do-extract, but never ever + touch extract! + Now that you understand what goes on when the user types `make', let us go through the @@ -26473,12 +26526,13 @@ new ports collection is to make each port as `plug-and-play' as possible for the end-user while using a minimum of disk space. - - Note: Unless explicitly stated, patch files, scripts, and - other files you have created and contributed to the FreeBSD - ports collection are assumed to be covered by the standard BSD - copyright conditions. - + + + Unless explicitly stated, patch files, scripts, and + other files you have created and contributed to the FreeBSD + ports collection are assumed to be covered by the standard + BSD copyright conditions. + @@ -26704,14 +26758,17 @@ patch either by running the patch command from there, or copying the patch file into the ${PATCHDIR} directory and calling it - patch-<xx>. (Note the - tarball will have been extracted alongside the regular source - by then, so there is no need to explicitly extract it if it is - a regular gzip'd or compress'd tarball.) If you do the - latter, take extra care not to overwrite something that - already exists in that directory. Also do not forget to add a - command to remove the copied patch in the pre-clean target. + patch-<xx>. + + + Note the tarball will have been extracted alongside the + regular source by then, so there is no need to explicitly + extract it if it is a regular gzip'd or compress'd tarball. + If you do the latter, take extra care not to overwrite + something that already exists in that directory. Also do + not forget to add a command to remove the copied patch in + the pre-clean target. + @@ -26753,11 +26810,13 @@ graphics/jpeg subdirectory of your ports tree to build and install it if it is not found. - - Note that the lib part is - just an argument given to `ldconfig -r | - grep', so periods should be escaped by two - backslashes like in the example above. + + + The lib part is just an argument + given to `ldconfig -r | grep', so + periods should be escaped by two backslashes like in the + example above. + The dependency is checked from within the extract target. Also, the name of the @@ -26794,11 +26853,15 @@ subdirectory of the ports tree if it is not found. It will also see if an executable called `wish' is in your search path, and descend into the x11/tk subdirectory of - your ports tree to build and install it if it is not found. - (Note that in this case, `innd' is actually an executable; if an - executable is in a place that is not expected to be in a - normal user's search path, you should use the full - pathname.) + your ports tree to build and install it if it is not + found. + + + In this case, `innd' is actually an + executable; if an executable is in a place that is not + expected to be in a normal user's search path, you should + use the full pathname. + The dependency is checked from within the install target. Also, the name of the @@ -26823,11 +26886,12 @@ archivers/unzip subdirectory of your ports tree to build and install it if it is not found. - - Note that `build' here means everything from extracting - to compilation. The dependency is checked from within the - extract target. - + + + `build' here means everything from extracting to + compilation. The dependency is checked from within the + extract target. + @@ -26956,13 +27020,14 @@ - - Note that ${MOTIFLIB} - (usually) expands to `' - or `/usr/X11R6/lib/libXm.a', so there is - no need to add `' or `' - in front. - + + + ${MOTIFLIB} (usually) + expands to `' or + `/usr/X11R6/lib/libXm.a', so there is + no need to add `' or + `' in front. + @@ -26993,11 +27058,12 @@ of the directory. : - - Note that this program will not actually - install info files; it merely inserts or - deletes entries in the dir - file. + + + This program will not actually + install info files; it merely inserts or + deletes entries in the dir file. + Here's a seven-step procedure to convert ports to use install-info. I will use @@ -27032,12 +27098,14 @@ entry indentations consistent (we recommend that all entry text start at the 4th tab stop). - Note that you can put only one info entry per file - because of a bug in `install-info - --delete' that deletes only the first entry - if you specify multiple entries in the - @direntry section. - + + Note that you can put only one info entry per file + because of a bug in `install-info + --delete' that deletes only the first entry + if you specify multiple entries in the + @direntry section. + + You can give the dir entries to install-info as arguments ( and @@ -27182,14 +27250,16 @@ - - Note that the `@unexec install-info - --delete' commands have to be listed before - the info files themselves so they can read the files. - Also, the `@exec install-info' commands - have to be after the info files and the - @exec command that creates the the - dir file. + + + The `@unexec install-info + --delete' commands have to be listed before + the info files themselves so they can read the files. + Also, the `@exec install-info' commands + have to be after the info files and the + @exec command that creates the the + dir file. + @@ -27215,12 +27285,14 @@ (export of crypto software) to name just two of them). What we can do with them vary a lot, depending on the exact wordings of the respective licenses. - - Note that it is your responsibility as a porter to read the - licensing terms of the software and make sure that the FreeBSD - project will not be held accountable of violating them by - redistributing the source or compiled binaries either via ftp or - CD-ROM. If in doubt, please contact the &a.ports;. + + + It is your responsibility as a porter to read the + licensing terms of the software and make sure that the FreeBSD + project will not be held accountable of violating them by + redistributing the source or compiled binaries either via ftp + or CD-ROM. If in doubt, please contact the &a.ports;. + There are two variables you can set in the Makefile to handle the situations that arise frequently: @@ -27259,13 +27331,16 @@ - - Note: The GNU General Public License (GPL), both version 1 - and 2, should not be a problem for ports. - - Note: If you are a committer, make sure you update the - ports/LEGAL file too. - + + + The GNU General Public License (GPL), both version 1 + and 2, should not be a problem for ports. + + + + If you are a committer, make sure you update the + ports/LEGAL file too. + @@ -27330,11 +27405,14 @@ Do include package information, i.e. COMMENT, DESCR, and PLIST, in pkg. Note that these files are not - used only for packaging anymore, and are - mandatory now, even if ${NO_PACKAGE} is set. - + remap="tt">pkg. + + + Note that these files are not used only for packaging + anymore, and are mandatory now, even if + ${NO_PACKAGE} is + set. + @@ -27365,9 +27443,11 @@ baz.8 - - Note that this is not usually necessary with ports that - are X applications and use Imake to build. + + + This is not usually necessary with ports that are X + applications and use Imake to build. + If your port anchors its man tree somewhere other than PREFIX, you can use the @@ -27435,12 +27515,15 @@ 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 information. - Note, that this script is not run automatically if you install - the port with `make install'. If - you are depending on it being run, you will have to explicitly - call it on your port's Makefile. - + pkg_add(1) for additional + information. + + + This script is not run automatically if you install the + port with `make install'. If you are + depending on it being run, you will have to explicitly call + it on your port's Makefile. + @@ -27494,9 +27577,12 @@ place the message in pkg/MESSAGE. This capibility is often useful to display additional installation steps to be taken after a pkg_add, or to display licensing - information. (note: the MESSAGE file does - not need to be added to pkg/PLIST). - + information. + + + MESSAGE does not need to be added + to pkg/PLIST). + @@ -27522,11 +27608,12 @@ remap=tt>${DISTDIR} explicitly in your Makefile will not accomplish this, so please use ${DIST_SUBDIR}.) - - Note this does not affect the ${MASTER_SITES} you define in your - Makefile. - + + + This does not affect the ${MASTER_SITES} you define in your + Makefile. + @@ -30464,12 +30551,14 @@ linker only records 3.3 in the headers, and will link with anything starting with libfoo.so.3.(anything >= 3).(highest available). - - Note that ld.so will always use the highest - "minor" revision. Ie: it will use libc.so.2.2 - in preference to libc.so.2.0, even if the - program was initially linked with - libc.so.2.0. + + + ld.so will always use the highest + "minor" revision. Ie: it will use libc.so.2.2 + in preference to libc.so.2.0, even if the + program was initially linked with + libc.so.2.0. + For non-port libraries, it is also our policy to change the shared library version number only once between releases. When you @@ -30489,11 +30578,12 @@ Adding New Kernel Configuration Options Contributed by &a.joerg; - - Note: You should be familiar with the section - about - before reading here. - + + + You should be familiar with the section about + before reading here. + What's a <emphasis>Kernel Option</emphasis>, Anyway? @@ -30680,15 +30770,18 @@ clause in the `config' line of your kernel config file. This is deprecated and should be used only if you want a crash dump from a kernel that crashes during booting. - - Note: In the following, - the term `kgdb' refers to gdb run in `kernel debug mode'. This can be - accomplished by either starting the gdb with the option , or - by linking and starting it under the name kgdb. This is not being done by default, - however, and the idea is basically deprecated since the GNU folks - do not like their tools to behave differently when called by - another name. This feature may well be discontinued in further - releases. + + + In the following, the term `kgdb' refers to + gdb run in `kernel debug mode'. This can be + accomplished by either starting the gdb with + the option , or by linking and starting it + under the name kgdb. This is not being done by + default, however, and the idea is basically deprecated since the + GNU folks do not like their tools to behave differently when + called by another name. This feature may well be discontinued in + further releases. + When the kernel has been built make a copy of it, say kernel.debug, and then run strip @@ -30910,10 +31003,14 @@ to your config file, and rebuild. (See for details on configuring the - FreeBSD kernel. Note that if you have an older version of the boot - blocks, your debugger symbols might not be loaded at all. Update the - boot blocks; the recent ones load the DDB symbols - automagically.) + FreeBSD kernel. + + + Note that if you have an older version of the boot blocks, + your debugger symbols might not be loaded at all. Update the boot + blocks; the recent ones load the DDB symbols + automagically.) + Once your DDB kernel is running, there are several ways to enter DDB. The first, and earliest way is to type the boot flag @@ -30957,9 +31054,13 @@ To get a stack trace, use trace - Note that when entering DDB via a hot-key, the - kernel is currently servicing an interrupt, so the stack trace might - be not of much use for you. + + + + Note that when entering DDB via a hot-key, the kernel is + currently servicing an interrupt, so the stack trace might be not + of much use for you. + If you want to remove a breakpoint, use @@ -30977,9 +31078,13 @@ DDB trace them until the matching return statement is reached by n - Note: this is - different from gdb's `next' statement; - it is like gdb's `finish'. + + + + + This is different from gdb's `next' + statement; it is like gdb's `finish'. + To examine data from memory, use (for example): @@ -31453,48 +31558,51 @@ -> libc.so.4.6.29 + + + Note that if you already have a Linux shared library with + a matching major revision number to the first column of the + 'ldd' output, you will not need to copy the file named in the + last column to your system, the one you already have should + work. It is advisable to copy the shared library anyway if it + is a newer version, though. You can remove the old one, as + long as you make the symbolic link point to the new one. So, + if you have these libraries on your system: + + + /compat/linux/lib/libc.so.4.6.27 + /compat/linux/lib/libc.so.4 -> libc.so.4.6.27 + + - Note that if you already have a Linux shared library with a - matching major revision number to the first column of the 'ldd' - output, you will not need to copy the file named in the last - column to your system, the one you already have should work. It - is advisable to copy the shared library anyway if it is a newer - version, though. You can remove the old one, as long as you make - the symbolic link point to the new one. So, if you have these - libraries on your system: - - /compat/linux/lib/libc.so.4.6.27 - /compat/linux/lib/libc.so.4 -> libc.so.4.6.27 - - - - and you find a new binary that claims to require a later - version according to the output of ldd: - - libc.so.4 (DLL Jump 4.5pl26) -> - libc.so.4.6.29 - - - - If it is only one or two versions out of date in the in the - trailing digit then do not worry about copying - /lib/libc.so.4.6.29 too, because the - program should work fine with the slightly older version. - However, if you like you can decide to replace the - libc.so anyway, and that should leave you - with: - - /compat/linux/lib/libc.so.4.6.29 - /compat/linux/lib/libc.so.4 -> libc.so.4.6.29 - - - - Please note that the symbolic link mechanism is - only needed for Linux binaries. The - FreeBSD runtime linker takes care of looking for matching major - revision numbers itself and you do not need to worry about - it. - + and you find a new binary that claims to require a later + version according to the output of ldd: + + libc.so.4 (DLL Jump 4.5pl26) -> + libc.so.4.6.29 + + + + If it is only one or two versions out of date in the in + the trailing digit then do not worry about copying + /lib/libc.so.4.6.29 too, because the + program should work fine with the slightly older version. + However, if you like you can decide to replace the + libc.so anyway, and that should leave you + with: + + /compat/linux/lib/libc.so.4.6.29 + /compat/linux/lib/libc.so.4 -> libc.so.4.6.29 + + + + + + The symbolic link mechanism is only + needed for Linux binaries. The FreeBSD runtime linker takes + care of looking for matching major revision numbers itself and + you do not need to worry about it. + @@ -31657,11 +31765,13 @@ Finding the necessary files - - Note: the information below is valid as of the time this - document was written, but certain details such as names of ftp - sites, directories and distribution names may have changed by the - time you read this. + + + The information below is valid as of the time this document + was written, but certain details such as names of ftp sites, + directories and distribution names may have changed by the time + you read this. + Linux is distributed by several groups that make their own set of binaries that they distribute. Each distribution has its own @@ -32291,15 +32401,13 @@ a memory address, but not between two I/O ports or two memory locations. - -
- Note: The 8237 does allow two channels - to be connected together to allow memory-to-memory DMA - operations in a non-fly-by mode, but nobody in the PC - industry uses this scarce resource this way since it is faster - to move data between memory locations using the CPU. -
- + + The 8237 does allow two channels to be connected together to + allow memory-to-memory DMA operations in a + non-fly-by mode, but nobody in the PC industry uses + this scarce resource this way since it is faster to move data + between memory locations using the CPU. + In the PC architecture, each DMA channel is normally activated only when the hardware that uses a given DMA channel requests a @@ -32447,15 +32555,13 @@ location 0x0000, not 0x10000. The results of letting this happen are probably not intended. - -
- Note: Physical 64K boundaries - should not be confused with 8086-mode 64K Segments, which - are created by mathematically adding a segment register with - an offset register. Page Registers have no address overlap - and are mathematically OR-ed together. -
- + + Physical 64K boundaries should not be + confused with 8086-mode 64K Segments, which are + created by mathematically adding a segment register with an + offset register. Page Registers have no address overlap and are + mathematically OR-ed together. + To further complicate matters, the external DMA address latches on the PC/AT hold only eight bits, so that gives us @@ -32479,15 +32585,12 @@ buffers are called Bounce Buffers. In the MS-DOS world, they are sometimes called Smart Buffers. - -
- Note: A new implementation of the - 8237, called the 82374, allows 16 bits of page register to be - specified, allows access to the entire 32 bit address space, - without the use of bounce buffers. -
- - + + A new implementation of the 8237, called the 82374, allows + 16 bits of page register to be specified, allows access to the + entire 32 bit address space, without the use of bounce + buffers. + @@ -32585,14 +32688,11 @@ 0, 1, 2, 3, 5, 6 and 7 are usable with peripherals on PC/AT systems. - -
- Note: DMA channel 0 was - reserved for refresh operations in early IBM PC - computers, but is generally available for use by - peripherals in modern systems. -
- + + DMA channel 0 was reserved for refresh operations in + early IBM PC computers, but is generally available for + use by peripherals in modern systems. + When a peripheral is performing Bus Mastering, it is important that the peripheral transmit data to or from @@ -34199,18 +34299,23 @@ the entire cvs-all tree to go from CVSup to CTM without having to rebuild their repository from scratch using a fresh CTM base delta. - - Please note that this special feature only works for the - cvs-all distribution with cvs as the release tag. CVSupping any other - distribution and/or release will get you the specified distribution, - but it will not be suitable for CTM updating. - - Also please note that, because the current version of CTM does - not preserve the timestamps of files, the timestamps at this mirror - site are not the same as those at other mirror sites. Switching - between this site and other sites is not recommended. It will work - correctly, but will be somewhat inefficient. - + + + This special feature only works for the cvs-all distribution with + cvs as the release tag. CVSupping any other + distribution and/or release will get you the specified + distribution, but it will not be suitable for CTM updating. + + + + Because the current version of CTM does not preserve the + timestamps of files, the timestamps at this mirror site are not + the same as those at other mirror sites. Switching between this + site and other sites is not recommended. It will work correctly, + but will be somewhat inefficient. + + Germany diff --git a/en_US.ISO_8859-1/books/handbook/book.sgml b/en_US.ISO_8859-1/books/handbook/book.sgml index c769392ae5..043f28336e 100644 --- a/en_US.ISO_8859-1/books/handbook/book.sgml +++ b/en_US.ISO_8859-1/books/handbook/book.sgml @@ -504,15 +504,19 @@ Some core team members also have specific , meaning that they are committed to ensuring that some large - portion of the system works as advertised. Note that most - members of the core team are volunteers when it comes to - FreeBSD development and do not benefit from the project - financially, so "commitment" should also not be misconstrued - as meaning "guaranteed support." The board of directors - analogy above is not actually very accurate, and it may be - more suitable to say that these are the people who gave up - their lives in favor of FreeBSD against their better - judgement! ;) + portion of the system works as advertised. + + + Most members of the core team are volunteers when it + comes to FreeBSD development and do not benefit from the + project financially, so "commitment" should also not be + misconstrued as meaning "guaranteed support." The + board of directors analogy above is not + actually very accurate, and it may be more suitable to say + that these are the people who gave up their lives in favor + of FreeBSD against their better judgement! ;) + @@ -717,9 +721,14 @@ If you're running DOS and have the proper drivers to access your CD, run the install.bat script provided on the CD. This will attempt to boot into the FreeBSD - installation straight from DOS (note: You must - do this from actual DOS and not a Windows DOS - box). If you also want to install FreeBSD + installation straight from DOS. + + + You must do this from actual DOS and not a Windows + DOS box. + + + If you also want to install FreeBSD from your DOS partition (perhaps because your CDROM drive is completely unsupported by FreeBSD) then run the setup program first to copy the appropriate files from the CD to @@ -741,7 +750,12 @@ If you don't have a CDROM distribution then simply download the installation boot disk image file to your hard drive, being sure to tell your browser to save rather than display the file. Note: This disk image can only be used with 1.44 megabyte 3.5 inch floppy disks. + URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/&rel.current;-RELEASE/floppies/boot.flp">installation boot disk image file to your hard drive, being sure to tell your browser to save rather than display the file. + + + This disk image can only be used with 1.44 megabyte 3.5 + inch floppy disks. + @@ -942,23 +956,27 @@ Adaptec AIC-6360 based boards, which includes the - AHA-152x and SoundBlaster SCSI cards. Note: You cannot boot from the - SoundBlaster cards as they have no on-board BIOS, which is - necessary for mapping the boot device into the system BIOS - I/O vectors. They are perfectly usable for external tapes, - CDROMs, etc, however. The same goes for any other AIC-6x60 - based card without a boot ROM. Some systems DO have a boot - ROM, which is generally indicated by some sort of message - when the system is first powered up or reset. Check your - system/board documentation for more details. - + AHA-152x and SoundBlaster SCSI cards. + + + You cannot boot from the + SoundBlaster cards as they have no on-board BIOS, which is + necessary for mapping the boot device into the system BIOS + I/O vectors. They are perfectly usable for external tapes, + CDROMs, etc, however. The same goes for any other AIC-6x60 + based card without a boot ROM. Some systems DO have a boot + ROM, which is generally indicated by some sort of message + when the system is first powered up or reset. Check your + system/board documentation for more details. + - Buslogic 545S & 545c Note: that Buslogic was formerly known - as "Bustek". + Buslogic 545S & 545c + + + Buslogic was formerly known as "Bustek". + @@ -1256,12 +1274,13 @@ - - Note: FreeBSD does not currently support - PnP (plug-n-play) features present on some ethernet cards. If - your card has PnP and is giving you problems, try disabling its - PnP features. - + + + FreeBSD does not currently support + PnP (plug-n-play) features present on some ethernet cards. If + your card has PnP and is giving you problems, try disabling its + PnP features. + + can make a boot floppy with the ``makeflp.bat'' command. + + + If you are running FreeBSD 2.1-RELEASE and have an IDE + CDROM, use the inst_ide.bat or atapiflp.bat batch files + instead. + For the easiest interface of all (from DOS), type ``view''. This will bring up a DOS menu utility that leads you through all @@ -1414,16 +1437,13 @@ to first type: umount /cdrom. Do not just remove it from the drive! - -
- Special note: Before - invoking the installation, be sure that the CDROM is in the - drive so that the install probe can find it. This is also - true if you wish the CDROM to be added to the default system - configuration automatically during the install (whether or not - you actually use it as the installation media). -
- + + Before invoking the installation, be sure that the CDROM is + in the drive so that the install probe can find it. This is + also true if you wish the CDROM to be added to the default + system configuration automatically during the install (whether + or not you actually use it as the installation media). + Finally, if you would like people to be able to FTP install FreeBSD directly from the CDROM in your machine, you will find it @@ -1547,14 +1567,11 @@ should expect to require as much temporary storage as you have stuff written on tape. - -
- Note: When going to do the - installation, the tape must be in the drive - before booting from the boot floppy. The - installation probe may otherwise fail to find it. -
- + + When going to do the installation, the tape must be in the + drive before booting from the boot floppy. + The installation probe may otherwise fail to find it. + @@ -1725,14 +1742,11 @@ - -
- Note: Active and passive - modes are not the same as a `proxy' connection, where a - proxy FTP server is listening and forwarding FTP - requests! -
- + + Active and passive modes are not the same as a `proxy' + connection, where a proxy FTP server is listening and + forwarding FTP requests! + For a proxy FTP server, you should usually give name of the server you really want as a part of the username, after an @@ -3092,9 +3106,12 @@ bsd.ports.mk and bsd.ports.subdir.mk files in your makefiles - directory. (Note: readers with an aversion to - intricate shell-scripts are advised not to follow this - link...) + directory. + + + Readers with an aversion to intricate shell-scripts are + advised not to follow this link...) + @@ -3188,15 +3205,13 @@ i386 directory is common to all platforms which FreeBSD could potentially be ported to. - -
- Note: If there is - not a /usr/src/sys - directory on your system, then the kernel source has not been - been installed. Follow the instructions for installing packages - to add this package to your system. -
- + + If there is not a + /usr/src/sys directory on your system, then + the kernel source has not been been installed. Follow the + instructions for installing packages to add this package to your + system. + Next, move to the i386/conf directory and copy the GENERIC configuration file to the name @@ -3209,13 +3224,11 @@ machine's hostname. We will call it MYKERNEL for the purpose of this example. - -
- Note: You must execute these and all of - the following commands under the root account or you will get - ``permission denied'' errors. -
- + + You must execute these and all of the following commands + under the root account or you will get ``permission denied'' + errors. + Now, edit MYKERNEL with your favorite text editor. If you are just starting out, the only editor available @@ -3236,17 +3249,15 @@ linkend="kernelconfig-config" remap="Configuration File"> section slowly and carefully. - -
- Note: 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 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 - running the next commands. -
- + + 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 + 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 + running the next commands. + When you are finished, type the following to compile and install your kernel: @@ -3263,15 +3274,13 @@ your new kernel . - -
- Note: If you have added any new devices - (such as sound cards) you may have to add some to your - /dev directory before you can use - them. -
- + + If you have added any new devices (such as sound cards) you + may have to add some to your + /dev directory before you can use + them. + @@ -3326,14 +3335,12 @@ remap=tt>machine, which, since FreeBSD only runs on Intel 386 and compatible chips, is i386. - -
- Note: that any keyword which - contains numbers used as text must be enclosed in - quotation marks, otherwise config gets confused and thinks - you mean the actual number 386. -
- + + Any keyword which contains numbers used as text + must be enclosed in quotation marks, otherwise + config gets confused and thinks you + mean the actual number 386. + @@ -3429,23 +3436,19 @@ simultaneous users (like Walnut Creek CDROM's FTP site), you can always increase this number and rebuild. - -
- Note: maxuser does - not limit the number of users - which can log into your machine. It simply sets - various table sizes to reasonable values considering - the maximum number of users you will likely have on - your system and how many processes each of them will - be running. One keyword which - does limit the number of - simultaneous remote logins is + + maxuser does + not limit the number of users which + can log into your machine. It simply sets various table + sizes to reasonable values considering the maximum + number of users you will likely have on your system and + how many processes each of them will be running. One + keyword which does limit the number + of simultaneous remote logins is . -
- + @@ -3488,18 +3491,15 @@ with a separate 387 or 487 chip, you can comment this line out. - -
- Note: The normal math - co-processor emulation routines that come with FreeBSD - are not very accurate. If you do - not have a math co-processor, and you need the best - accuracy, I recommend that you change this option to - GPL_MATH_EMULATE to use the superior - GNU math support, which is not included by default for - licensing reasons. -
- + + The normal math co-processor emulation routines that + come with FreeBSD are not very + accurate. If you do not have a math co-processor, and + you need the best accuracy, I recommend that you change + this option to GPL_MATH_EMULATE to use + the superior GNU math support, which is not included by + default for licensing reasons. + @@ -3561,14 +3561,11 @@ Support for System V messages. Again, only adds a few hundred bytes to the kernel. - -
- Note: The - ipcs(1) command will tell will list - any processes using each of these System V - facilities. -
- + + The ipcs(1) command will tell + will list any processes using each of these System V + facilities. + @@ -3661,28 +3658,22 @@ - -
- Note: Replace the - /dev/wd1s2b with the name of your - swap partition, which will be listed in your - /etc/fstab as follows: - - /dev/wd1s2b none swap sw 0 0 - - -
- + + Replace the /dev/wd1s2b with + the name of your swap partition, which will be listed in + your /etc/fstab as follows: + + /dev/wd1s2b none swap sw 0 0 + + + - -
- Note: Also, the - MFS filesystem can - not be dynamically loaded, so you - must compile it into your kernel - if you want to experiment with it. -
- + + Also, the MFS filesystem can + not be dynamically loaded, so you + must compile it into your kernel if + you want to experiment with it. + @@ -3750,14 +3741,12 @@ attached to the floppy controller. Comment out any lines corresponding to devices you do not have. - -
- Note: QIC-80 tape support - requires a separate filter program called - ft(8), see the manual page for - details. + + QIC-80 tape support requires a separate filter + program called ft(8), see the manual + page for details.
- + @@ -4089,15 +4078,13 @@ Use this device if you have a Logitech or ATI InPort bus mouse card. - -
- Note: If you have a serial - mouse, ignore these two lines, and instead, make sure - the appropriate + If you have a serial mouse, ignore these two lines, + and instead, make sure the appropriate port is enabled (probably - COM1). -
- + COM1). + @@ -4335,14 +4322,11 @@ - -
- Note: With certain cards - (notably the NE2000) you will have to change the port - and/or IRQ since there is no ``standard'' location for - these cards. -
- + + With certain cards (notably the NE2000) you will + have to change the port and/or IRQ since there is no + ``standard'' location for these cards. + @@ -4474,17 +4458,14 @@ SoundBlaster digital audio. - -
- Note: If your SoundBlaster is - on a different IRQ (such as 5), change irq 7 to, for example, irq 5 and remove the conflicts keyword. Also, you - must add the line: options - ``SBC_IRQ=5'' -
- + + If your SoundBlaster is on a different IRQ (such as + 5), change irq 7 to, for + example, irq 5 and remove + the conflicts keyword. + Also, you must add the line: options + ``SBC_IRQ=5'' + @@ -4493,15 +4474,12 @@ SoundBlaster 16 digital 16-bit audio. - -
- Note: If your SB16 is on a - different 16-bit DMA channel (such as 6 or 7), change - the drq 5 keyword - appropriately, and then add the line: options - "SB16_DMA=6" -
- + + If your SB16 is on a different 16-bit DMA channel + (such as 6 or 7), change the drq + 5 keyword appropriately, and then add the + line: options "SB16_DMA=6" + @@ -4570,16 +4548,13 @@ - -
- Note: There is some additional - documentation in - /usr/src/sys/i386/isa/sound/sound.doc. - Also, if you add any of these devices, be sure to create the - sound . -
- + + There is some additional documentation in + /usr/src/sys/i386/isa/sound/sound.doc. + Also, if you add any of these devices, be sure to create the + sound . + @@ -4750,25 +4725,26 @@ For sound cards, the command: # sh MAKEDEV snd0 - creates the appropriate entries. Note: when - creating device nodes for devices such as sound cards, if other - people have access to your machine, it may be desirable to protect - the devices from outside access by adding them to the - /etc/fbtab file. See man - fbtab for more information. + creates the appropriate entries. + + + When creating device nodes for devices such as sound cards, if + other people have access to your machine, it may be desirable to + protect the devices from outside access by adding them to the + /etc/fbtab file. See man + fbtab for more information. + Follow this simple procedure for any other non-GENERIC devices which do not have entries. - -
- Note: All SCSI controllers use the same - set of /dev entries, so you do not need to - create these. Also, network cards and SLIP/PPP pseudo-devices - do not have entries in /dev at all, so you - do not have to worry about these either. -
- + + All SCSI controllers use the same set of + /dev entries, so you do not need to create + these. Also, network cards and SLIP/PPP pseudo-devices do not + have entries in /dev at all, so you do not + have to worry about these either. + @@ -4832,33 +4808,31 @@ dmesg(8) command will print the kernel messages from the current boot. - -
- Note: If you are having trouble - building a kernel, make sure to keep a GENERIC, or some - other kernel that is known to work on hand as a - different name that will not get erased on the next - build. You cannot rely on - kernel.old because when installing - a new kernel, kernel.old is - overwritten with the last installed kernel which may be - non-functional. Also, as soon as possible, move the - working kernel to the proper ``kernel'' location or - commands such as ps(1) will not work - properly. The proper command to unlock the kernel - file that make installs - (in order to move another kernel back permanently) is: + + If you are having trouble building a kernel, make sure + to keep a GENERIC, or some other kernel that is known to + work on hand as a different name that will not get erased + on the next build. You cannot rely on + kernel.old because when installing a + new kernel, kernel.old is overwritten + with the last installed kernel which may be + non-functional. Also, as soon as possible, move the + working kernel to the proper ``kernel'' location or + commands such as ps(1) will not work + properly. The proper command to unlock the + kernel file that make installs (in + order to move another kernel back permanently) is: # chflags noschg /kernel - And, if you want to lock your new - kernel into place, or any file for that matter, so that - it cannot be moved or tampered with: + And, if you want to + lock your new kernel into place, or any + file for that matter, so that it cannot be moved or + tampered with: # chflags schg /kernel -
- + @@ -5779,20 +5753,19 @@ use the facilities provided in the FreeBSD kernel to implement them. - -
- Note: People often think that - having a firewall between your companies internal network and - the Big Bad Internet will solve all your security problems. - It may help, but a poorly setup firewall system is more of a - security risk than not having one at all. A firewall can only - add another layer of security to your systems, but they will not - be able to stop a really determined hacker from penetrating your - internal network. If you let internal security lapse because you - believe your firewall to be impenetrable, you have just made the - hackers job that bit easier. -
- + + People often think that having a firewall between your + companies internal network and the Big Bad Internet + will solve all your security problems. + + It may help, but a poorly setup firewall system is more of a + security risk than not having one at all. A firewall can only add + another layer of security to your systems, but they will not be + able to stop a really determined hacker from penetrating your + internal network. If you let internal security lapse because you + believe your firewall to be impenetrable, you have just made the + hackers job that bit easier. + @@ -6428,14 +6401,12 @@ Building a packet filtering firewall - -
- Note: The following - suggestions are just that: suggestions. The requirements of - each firewall are different and I cannot tell you how to build - a firewall to meet your particular requirements. -
- + + The following suggestions are just that: suggestions. The + requirements of each firewall are different and I cannot tell + you how to build a firewall to meet your particular + requirements. + When initially setting up your firewall, unless you have a test bench setup where you can configure your firewall host in a @@ -6447,21 +6418,19 @@ tracing of possible attacks and also modification of the firewall rules if your requirements alter. - -
- Note: If you use the logging - versions of the accept command, - it can generate large amounts of log data - as one log line will be generated for every packet that passes - through the firewall, so large ftp/http transfers, etc, will - really slow the system down. It also increases the latencies - on those packets as it requires more work to be done by the - kernel before the packet can be passed on. syslogd with also - start using up a lot more processor time as it logs all the - extra data to disk, and it could quite easily fill the - partition /var/log is located on. -
- + + If you use the logging versions of the accept command, it can generate + large amounts of log data as one log line + will be generated for every packet that passes through the + firewall, so large ftp/http transfers, etc, will really slow the + system down. It also increases the latencies on those packets as + it requires more work to be done by the kernel before the packet + can be passed on. syslogd with also start using up a lot more + processor time as it logs all the extra data to disk, and it + could quite easily fill the partition + /var/log is located on. + As currently supplied, FreeBSD does not have the ability to load firewall rules at boot time. My suggestion is to put a call @@ -7226,14 +7195,18 @@ %!PS 100 100 moveto 300 300 lineto stroke 310 310 moveto /Helvetica findfont 12 scalefont setfont (Is this thing working?) show showpage - Note: When this - document refers to a printer language, I am assuming a - language like PostScript, and not Hewlett Packard's PCL. - Although PCL has great functionality, you can intermingle - plain text with its escape sequences. PostScript cannot - directly print plain text, and that is the kind of printer - language for which we must make special accommodations. + + + + When this document refers to a printer language, I am + assuming a language like PostScript, and not Hewlett + Packard's PCL. Although PCL has great functionality, you can + intermingle plain text with its escape sequences. + PostScript cannot directly print plain text, and that is the + kind of printer language for which we must make special + accommodations. + @@ -7502,12 +7475,14 @@ - - Note: Language-based printers, such as - PostScript printers, cannot directly print plain text. The - simple setup outlined above and described in the following - sections assumes that if you are installing such a printer you - will print only files that the printer can understand. + + + Language-based printers, such as PostScript printers, + cannot directly print plain text. The simple setup outlined + above and described in the following sections assumes that if + you are installing such a printer you will print only files + that the printer can understand. + Users often expect that they can print plain text to any of the printers installed on your system. Programs that interface @@ -7636,22 +7611,24 @@ mkdir /var/spool/lpd/bamboo - - Note: If you are concerned about the - privacy of jobs that users print, you might want to protect - the spooling directory so it is not publicly accessible. - Spooling directories should be owned and be readable, - writable, and searchable by user daemon and group daemon, and - no one else. We will do this for our example printers: - - - - chown daemon.daemon /var/spool/lpd/rattan chown - daemon.daemon /var/spool/lpd/bamboo chmod 770 - /var/spool/lpd/rattan chmod 770 - /var/spool/lpd/bamboo - - + + + If you are concerned about the privacy of jobs that + users print, you might want to protect the spooling + directory so it is not publicly accessible. Spooling + directories should be owned and be readable, writable, and + searchable by user daemon and group daemon, and no one else. + We will do this for our example printers: + + + + chown daemon.daemon /var/spool/lpd/rattan chown + daemon.daemon /var/spool/lpd/bamboo chmod 770 + /var/spool/lpd/rattan chmod 770 + /var/spool/lpd/bamboo + + + Finally, you need to tell LPD about these directories using the /etc/printcap file. You @@ -8048,15 +8025,16 @@ to find out how to do this. - - Note: If you boot your - system into other operating systems besides - FreeBSD, you may have to - reconfigure the printer to - use a an interpretation for CR and LF characters - that those other operating systems use. You - might prefer one of the other solutions, - below. + + + If you boot your system into other + operating systems besides FreeBSD, you may + have to reconfigure the + printer to use a an interpretation for CR and + LF characters that those other operating + systems use. You might prefer one of the + other solutions, below. + @@ -8498,26 +8476,27 @@ lprm -P rattan - - - Note: If you are working in a networked - environment, - - lprm will - let you remove jobs only from the host from which the jobs were - submitted, even if the same printer is available from other hosts. - The following command sequence demonstrates this: - - rose% lpr -P rattan myfile rose% rlogin orchid - orchid% lpq -P rattan Rank Owner Job Files - Total Size active seeyan 12 ... - 49123 bytes 2nd kelly 13 myfile - 12 bytes orchid% lprm -P rattan 13 rose: Permission denied - orchid% logout rose% lprm -P rattan 13 dfA013rose dequeued - cfA013rose dequeued rose% - - - + + + If you are working in a networked + environment, + + lprm + will let you remove jobs only from the host from which the jobs + were submitted, even if the same printer is available from other + hosts. The following command sequence demonstrates this: + + rose% lpr -P rattan myfile rose% rlogin orchid + orchid% lpq -P rattan Rank Owner Job Files Total + Size active seeyan 12 ... 49123 bytes 2nd kelly + 13 myfile 12 bytes orchid% lprm -P rattan 13 rose: + Permission denied orchid% logout rose% lprm -P rattan 13 + dfA013rose dequeued cfA013rose dequeued rose% + + + + - - Note: All of these options except - and require conversion - filters installed for the destination printer. For example, the - option requires the DVI conversion filter. - Section + All of these options except and + require conversion filters installed for + the destination printer. For example, the + option requires the DVI conversion filter. Section gives details. + @@ -8601,9 +8581,11 @@ number, indent by 8 columns. This option works only with certain conversion filters. - - Note: Do not put any space - between the and the number. + + + Do not put any space between the + and the number. + @@ -8750,13 +8732,14 @@ There is a drawback, though: since LPD will refer to the original files directly, you cannot modify or remove them until they have been printed. - - Note: If you are printing to a - remote printer, LPD will eventually have to copy files - from the local host to the remote host, so the - option will save space only on the - local spooling directory, not the remote. It is still - useful, though. + + + If you are printing to a remote printer, LPD will + eventually have to copy files from the local host to + the remote host, so the option + will save space only on the local spooling directory, + not the remote. It is still useful, though. + @@ -8812,12 +8795,14 @@ -h - Do not print any header page. - Note: At some sites, this option - may have no effect due to the way header pages are - generated. See Do not print any header page. + + + At some sites, this option may have no effect due + to the way header pages are generated. See for details. + @@ -10006,12 +9991,14 @@ Options"> for more lpr options. - - Note: LPD prints a form feed - character after the header page. If your printer uses a - different character or sequence of characters to eject a page, - specify them with the ff - capability in /etc/printcap. + + + LPD prints a form feed character after the header page. + If your printer uses a different character or sequence of + characters to eject a page, specify them with the ff capability in + /etc/printcap. + @@ -10618,10 +10605,10 @@ remap=tt>bamboo. It might be the case that we only allow certain logins on orchid anyway, and want them to have access to the printer. Or not. - - Note: there can be only one restricted - group per printer. - + + + There can be only one restricted group per printer. + mx capability. The units are in BUFSIZ blocks, which are 1024 bytes. If you put a zero for this capability, there will be no limit on file - size. Note that the limit applies to files - in a job, and not the total job size. + + + The limit applies to files in a job, + and not the total job size. + LPD will not refuse a file that is larger than the limit you place on a printer. Instead, it will queue as much of the file @@ -11517,15 +11507,23 @@ URL="http://www.asus.com.tw/Products/Motherboard/Pentiumpro/P2l97-s/index.html">P2l97-S motherboard with the on-board Adaptec SCSI WIDE controller. For Pentium machines, the ASUS P55T2P4 motherboard appears to be a good choice for mid-to-high range Pentium server and workstation systems. You might also wish to investigate ASUS's 486SP3G offering if it's a 486-class motherboard you're looking for (Note: These have become increasingly hard to get as ASUS apparently no longer manufactures them). + URL="http://www.asus.com.tw/Products/Motherboard/Pentium/P55tp4/index.html">P55T2P4 motherboard appears to be a good choice for mid-to-high range Pentium server and workstation systems. You might also wish to investigate ASUS's 486SP3G offering if it's a 486-class motherboard you're looking for. + + + These have become increasingly hard to get as ASUS + apparently no longer manufactures them). + Those wishing to build more fault-tolerant systems should also be sure to use Parity memory or, for truly 24/7 - applications, ECC memory. Note that ECC memory does involve a - slight performance trade-off (which may or may not be noticeable - depending on your application) but buys you significantly - increased fault-tolerance to memory errors. - + applications, ECC memory. + + + ECC memory does involve a slight performance trade-off + (which may or may not be noticeable depending on your + application) but buys you significantly increased + fault-tolerance to memory errors. + @@ -11892,15 +11890,16 @@ faster than what, there are zillions of web sites on the Internet that tells you one way or another. :) - - Note that various CPUs have different voltage/cooling - requirements. Make sure your motherboard can supply the exact - voltage needed by the CPU. For instance, many recent MMX chips - require split voltage (e.g., 2.9V core, 3.3V I/O). Also, some - AMD and Cyrix/IBM chips run hotter than Intel chips. In that - case, make sure you have good heatsink/fans (you can get the - list of certified parts from their web pages). - + + + Various CPUs have different voltage/cooling requirements. + Make sure your motherboard can supply the exact voltage needed + by the CPU. For instance, many recent MMX chips require split + voltage (e.g., 2.9V core, 3.3V I/O). Also, some AMD and + Cyrix/IBM chips run hotter than Intel chips. In that case, + make sure you have good heatsink/fans (you can get the list of + certified parts from their web pages). + Clock speeds @@ -12254,12 +12253,14 @@ Marks and Spaces are also equivalent to "Holes" and "No Holes" in paper tape systems. - - Note that Breaks cannot be generated from paper tape or - from any other byte value, since bytes are always sent with - Start and Stop bit. The UART is usually capable of - generating the continuous Spacing signal in response to a - special command from the host processor. + + + Breaks cannot be generated from paper tape or from any + other byte value, since bytes are always sent with Start + and Stop bit. The UART is usually capable of generating + the continuous Spacing signal in response to a special + command from the host processor. + @@ -13712,12 +13713,15 @@ slice should be within the 1024 cylinder BIOS limit. During the boot process the bad144 list is read using the BIOS and this only succeeds when the list is within the 1024 cylinder - limit. Note that the restriction is not - that only the root filesystem must be - within the 1024 cylinder limit, but rather the entire - slice that contains the root - filesystem. - + limit. + + + The restriction is not that only the root + filesystem must be within the 1024 + cylinder limit, but rather the entire + slice that contains the root + filesystem. + @@ -14038,15 +14042,16 @@ bus speeds of 20 and 40 million transfers/second are also emerging (Fast-20 == Ultra SCSI and Fast-40 == Ultra2 SCSI). - - It should be noted that the data lines > 8 are only used - for data transfers and device addressing. The transfers of - commands and status messages etc are only performed on the - lowest 8 data lines. The standard allows narrow devices to - operate on a wide bus. The usable bus width is negotiated - between the devices. You have to watch your device addressing - closely when mixing wide and narrow. - + + + The data lines > 8 are only used for data transfers and + device addressing. The transfers of commands and status + messages etc are only performed on the lowest 8 data lines. + The standard allows narrow devices to operate on a wide bus. + The usable bus width is negotiated between the devices. You + have to watch your device addressing closely when mixing wide + and narrow. + Single ended buses @@ -14068,10 +14073,12 @@ becomes 0.75 meters. Be aware that F20 is pushing the limits quite a bit, so you will quickly find out if your SCSI bus is electrically sound. - - Please note that this means that if some devices on your - bus use 'fast' to communicate your bus must adhere to the - length restrictions for fast buses! + + + If some devices on your bus use 'fast' to communicate + your bus must adhere to the length restrictions for fast + buses! + It is obvious that with the newer fast-SCSI devices the bus length can become a real bottleneck. This is why the @@ -14183,12 +14190,14 @@ external device, and not on the controller! In general, every reconfiguration of a SCSI bus must pay attention to this. - - Note that termination is to be done on a per-line basis. - This means if you have both narrow and wide buses connected to - the same host adapter, you need to enable termination on the - higher 8 bits of the bus on the adapter (as well as the last - devices on each bus, of course). + + + Termination is to be done on a per-line basis. This + means if you have both narrow and wide buses connected to + the same host adapter, you need to enable termination on the + higher 8 bits of the bus on the adapter (as well as the last + devices on each bus, of course). + What I did myself is remove all terminators from my SCSI devices and controllers. I own a couple of external @@ -14268,12 +14277,14 @@ maximum is 8 because the selection is done bitwise using the 8 data lines on the bus. For wide buses this increases to the number of data lines (usually 16). - - Note that a narrow SCSI device can not communicate with a - SCSI device with a target ID larger than 7. This means it is - generally not a good idea to move your SCSI host adapter's - target ID to something higher than 7 (or your CD-ROM will stop - working). + + + A narrow SCSI device can not communicate with a SCSI + device with a target ID larger than 7. This means it is + generally not a good idea to move your SCSI host adapter's + target ID to something higher than 7 (or your CD-ROM will + stop working). + The higher the SCSI target ID, the higher the priority the devices has. When it comes to arbitration between devices @@ -14473,13 +14484,17 @@ config file should reflect your actual hardware setup. So, interrupts, I/O addresses etc must match the kernel config file. During system boot messages will be displayed to - indicate whether the configured hardware was actually found. - Note that most of the EISA/PCI drivers (namely ahb, ahc, ncr and amd will automatically obtain the - correct parameters from the host adapters themselves at boot - time; thus, you just need to write, for instance, "controller ahc0". + indicate whether the configured hardware was actually + found. + + + Note that most of the EISA/PCI drivers (namely ahb, ahc, ncr and amd will automatically obtain the + correct parameters from the host adapters themselves at boot + time; thus, you just need to write, for instance, "controller ahc0". + An example loosely based on the FreeBSD 2.2.5-Release kernel config file LINT with some added comments (between @@ -14524,14 +14539,17 @@ number one greater than the highest 'wired down' unit number for that kind of device. So, if you had a SCSI tape at target ID 2 it would be configured as st2, as the tape at target ID 6 - is wired down to unit number 1. Note that wired down - devices need not be found to get their unit - number. The unit number for a wired down device is reserved - for that device, even if it is turned off at boot time. This - allows the device to be turned on and brought on-line at a - later time, without rebooting. Notice that a device's unit - number has no relationship with its - target ID on the SCSI bus. + is wired down to unit number 1. + + + Wired down devices need not be found to get their unit + number. The unit number for a wired down device is reserved + for that device, even if it is turned off at boot time. This + allows the device to be turned on and brought on-line at a + later time, without rebooting. Notice that a device's unit + number has no relationship with its + target ID on the SCSI bus. + Below is another example of a kernel config file as used by FreeBSD version < 2.0.5. The difference with the first @@ -16676,11 +16694,12 @@ font8x14=cp866-8x14 font8x8=cp866-8x8 - - NOTE: ^[ means that real - ESC character must be entered into - /etc/rc.conf, not just ^[ - string. + + + ^[ means that real ESC character must be entered into + /etc/rc.conf, not just ^[ + string. + This tuning means KOI8-R keyboard with Alternative screen font mapped to KOI8-R encoding to preserve @@ -16904,15 +16923,18 @@ first as described. - - NOTE: Russian KOI8-R locale may not work with - old XFree86 releases (lower than 3.3). XFree86 port from - /usr/ports/x11/XFree86 already have - most recent XFree86 version, so it will work, if you install - XFree86 from this port. XFree86 version shipped with the - latest FreeBSD distribution should work too (check XFree86 - version number not less than 3.3 first). + + + Russian KOI8-R locale may + not work with old XFree86 releases (lower than 3.3). + XFree86 port from + /usr/ports/x11/XFree86 already have + most recent XFree86 version, so it will work, if you + install XFree86 from this port. XFree86 version shipped + with the latest FreeBSD distribution should work too + (check XFree86 version number not less than 3.3 + first). + @@ -16950,15 +16972,16 @@ remap=bf>CapsLock. Old CapsLock function still available via Shift+CapsLock (in LAT mode only). - - NOTE: Russian XKB keyboard - may not work with old XFree86 versions, see for - more info. Russian XKB keyboard may not work with - non-localized applications too, minimally localized - application should call XtSetLanguageProc (NULL, NULL, NULL); - function early in the program. + + + Russian XKB keyboard may not work with old XFree86 + versions, see for more info. + Russian XKB keyboard may not work with non-localized + applications too, minimally localized application should + call XtSetLanguageProc + (NULL, NULL, NULL); function early in the program. + @@ -18061,19 +18084,21 @@ if you are using a configuration file that was previously used for a different version of FreeBSD because the device flags have changed between versions. - - Note that port "IO_COM1" is a - substitution for port 0x3f8, - IO_COM2 is 0x2f8, - IO_COM3 is 0x3e8, and - IO_COM4 is 0x2e8, which are - fairly common port addresses for their respective serial ports; - interrupts 4, 3, 5, and 9 are fairly common interrupt request - lines. Also note that regular serial ports cannot share interrupts on ISA-bus PCs - (multiport boards have on-board electronics that allow all the - 16550A's on the board to share one or two interrupt request - lines). + + + port "IO_COM1" is a + substitution for port 0x3f8, + IO_COM2 is 0x2f8, + IO_COM3 is 0x3e8, and + IO_COM4 is 0x2e8, which are + fairly common port addresses for their respective serial ports; + interrupts 4, 3, 5, and 9 are fairly common interrupt request + lines. Also note that regular serial ports cannot share interrupts on ISA-bus PCs + (multiport boards have on-board electronics that allow all the + 16550A's on the board to share one or two interrupt request + lines). + When you are finished adjusting the kernel configuration file, use the program config as documented @@ -19401,9 +19426,13 @@ You will need to create a configuration file called /etc/ppp/ppp.conf. It should look similar - to the example below. Note that lines that end in a ``:'' start - in the first column, all other lines should be indented as shown - using spaces or tabs. + to the example below. + + + Lines that end in a ``:'' start in the first column, all + other lines should be indented as shown using spaces or + tabs. + @@ -20096,13 +20125,13 @@ - - NOTE: Your authkey will be logged if you have command - logging turned on (set log - +command). Care should be taken when deciding the - ppp log file permissions. - + + + Your authkey will be logged + if you have command logging turned on (set log + +command). Care should be taken when deciding the + ppp log file permissions. + @@ -20183,22 +20212,24 @@ network_interfaces="lo0 tun0" ifconfig_tun0= - - Note, the ifconfig_tun0 variable should be - empty, and a file called /etc/start_if.tun0 - should be created. This file should contain the line - - - - ppp -auto mysystem - - - - This script is executed at network configuration time, - starting your ppp daemon in automatic mode. If you have a LAN for - which this machine is a gateway, you may also wish to use the - switch. Refer to the manual page for - further details. + + + The ifconfig_tun0 variable should be empty, + and a file called /etc/start_if.tun0 should + be created. This file should contain the line + + + + ppp -auto mysystem + + + + This script is executed at network configuration time, + starting your ppp daemon in automatic mode. If you have a LAN + for which this machine is a gateway, you may also wish to use + the switch. Refer to the manual page + for further details. + Set the router program to ``NO'' with the line @@ -20674,9 +20705,12 @@ cuaa1, and only use the modem name in my configuration files. It can become quite cumbersome when you need to fix a bunch of files in /etc and - .kermrc's all over the system! (Note that - /dev/cuaa0 is COM1, cuaa1 - is COM2, etc.) + .kermrc's all over the system! + + + /dev/cuaa0 is COM1, + cuaa1 is COM2, etc. + Make sure you have pseudo-device sl 1 in your kernel's config file. It is included in @@ -20801,11 +20835,13 @@ ***\x0d, echo \x0aCONNECTED\x0a (of course, you have to change the hostname and password to fit yours). Then you can just type "slip" from the kermit - prompt to get connected. Note: - leaving your password in plain text anywhere in the - filesystem is generally a BAD idea. Do it at your own risk. - I am just too lazy. - + prompt to get connected. + + + Leaving your password in plain text anywhere in the + filesystem is generally a BAD idea. Do it at your own + risk. I am just too lazy. + @@ -21320,14 +21356,17 @@ arp(8) desires; see the manual page on arp(8) for complete information on usage. - - Note that when you create - /etc/sliphome/slip.login and - /etc/sliphome/slip.logout, the execute - bit (ie, chmod 755 /etc/sliphome/slip.login - /etc/sliphome/slip.logout) must be set, or sliplogin will be unable to execute - it. - + + + When you create + /etc/sliphome/slip.login and + /etc/sliphome/slip.logout, the + execute bit (ie, chmod 755 + /etc/sliphome/slip.login + /etc/sliphome/slip.logout) must be set, or + sliplogin will be unable to execute + it. + @@ -23213,18 +23252,18 @@ especially true if you have installed the most recent release (&rel.current;-RELEASE at the time of this writing) since the stable branch is effectively a bug-fix stream relative to the previous release. - - Please note that the stable tree - endeavors, above all, to be fully compilable and stable at all - times, but we do occasionally make mistakes (these are still - active sources with quickly-transmitted updates, after all). We - also do our best to thoroughly test fixes in - current before bringing them into - stable, but sometimes our tests fail to catch - every case. If something breaks for you in - stable, please let us know - immediately! (see next section). - + + + The stable tree endeavors, above all, + to be fully compilable and stable at all times, but we do + occasionally make mistakes (these are still active sources with + quickly-transmitted updates, after all). We also do our best to + thoroughly test fixes in current before + bringing them into stable, but sometimes + our tests fail to catch every case. If something breaks for you + in stable, please let us know + immediately! (see next section). + @@ -23458,16 +23497,17 @@ /etc/aliases if you want to have the process run in a fully automated fashion. Check the ctm_rmail man page for more details. - - NOTE: No matter what method you use to - get the CTM deltas, you should subscribe to - the ctm-announce@FreeBSD.ORG mailing list. In - the future, this will be the only place where announcements - concerning the operations of the CTM system - will be posted. Send an email to &a.majordomo; with a single - line of ``subscribe ctm-announce'' - to get added to the list. - + + + No matter what method you use to get the + CTM deltas, you should subscribe to the + ctm-announce@FreeBSD.ORG mailing list. In the + future, this will be the only place where announcements + concerning the operations of the CTM system + will be posted. Send an email to &a.majordomo; with a single + line of ``subscribe + ctm-announce'' to get added to the list. + @@ -24009,10 +24049,12 @@ tag=. The main line of development, also known as - FreeBSD-current. Note: the "." is not - punctuation; it is the name of the tag. Valid for - all collections. - + FreeBSD-current. + + + The "." is not punctuation; it is the name + of the tag. Valid for all collections. + @@ -25920,15 +25962,18 @@ Before Starting the Port - - Note: Only a fraction of the overridable variables - (${..}) are mentioned in this - document. Most (if not all) are documented at the start of - bsd.port.mk. This file uses a non-standard - tab setting. Emacs and Vim should recognize the setting on - loading the file. vi or ex can be set to using the correct value - by typing `:set tabstop=4' once the file has - been loaded. + + + Only a fraction of the overridable variables + (${..}) are mentioned in + this document. Most (if not all) are documented at the start + of bsd.port.mk. This file uses a + non-standard tab setting. Emacs and + Vim should recognize the setting on loading + the file. vi or ex can + be set to using the correct value by typing `:set + tabstop=4' once the file has been loaded. + You may come across code that needs modifications or conditional compilation based upon what version of UNIX it is @@ -26074,20 +26119,21 @@ 3.0-current before mount(2) change: 300000 3.0-current as of Nov 1997: 300001 - (Note that 2.2-STABLE sometimes - identifies itself as "2.2.5-STABLE" after the - 2.2.5-RELEASE.) The pattern used to be year followed by - the month, but we decided to change it to a more - straightforward major/minor system starting from 2.2. - This is because the parallel development on several - branches made it infeasible to classify the releases - simply by their real release dates. (Note that if you are - making a port now, you don't have to worry about old - -current's; they are listed here just for your reference.) - + - + + + Note that 2.2-STABLE sometimes identifies itself as + "2.2.5-STABLE" after the 2.2.5-RELEASE. The pattern used to + be year followed by the month, but we decided to change it + to a more straightforward major/minor system starting from + 2.2. This is because the parallel development on several + branches made it infeasible to classify the releases simply + by their real release dates. If you are making a port now, + you don't have to worry about old -current's; they are + listed here just for your reference. + In the hundreds of ports that have been done, there have @@ -26108,12 +26154,13 @@ remap=tt>${DISTDIR}, which defaults to /usr/ports/distfiles. - Note: The following assumes that the software compiled - out-of-the-box, i.e., there was absolutely no change required - for the port to work on your FreeBSD box. If you needed to - change something, you will have to refer to the next section - too. - + + The following assumes that the software compiled + out-of-the-box, i.e., there was absolutely no change required + for the port to work on your FreeBSD box. If you needed to + change something, you will have to refer to the next section + too. + Writing the <filename>Makefile</filename> @@ -26174,11 +26221,15 @@ This is a longer description of the port. One to a few paragraphs concisely explaining what the port does is - sufficient. Note: This is not a manual - nor an in-depth description on how to use or compile the - port. In particular, please do not just copy the - README file here, unless, of - course, it is a concise description of the port. + sufficient. + + + This is not a manual nor an + in-depth description on how to use or compile the port. In + particular, please do not just copy the + README file here, unless, + of course, it is a concise description of the port. + It is recommended that you sign the name at the end of this file, as in: @@ -26407,15 +26458,17 @@ the default target, you can fix it by redefining the `do-<something>' target in your Makefile. - - Note that the `main' targets (e.g., extract, configure, etc.) do nothing more than - make sure all the stages up to that one is completed and call - the real targets or scripts, and they are not intended to be - changed. If you want to fix the extraction, fix do-extract, but never ever touch - extract! + + + The `main' targets (e.g., extract, configure, etc.) do nothing more than + make sure all the stages up to that one is completed and + call the real targets or scripts, and they are not intended + to be changed. If you want to fix the extraction, fix + do-extract, but never ever + touch extract! + Now that you understand what goes on when the user types `make', let us go through the @@ -26473,12 +26526,13 @@ new ports collection is to make each port as `plug-and-play' as possible for the end-user while using a minimum of disk space. - - Note: Unless explicitly stated, patch files, scripts, and - other files you have created and contributed to the FreeBSD - ports collection are assumed to be covered by the standard BSD - copyright conditions. - + + + Unless explicitly stated, patch files, scripts, and + other files you have created and contributed to the FreeBSD + ports collection are assumed to be covered by the standard + BSD copyright conditions. + @@ -26704,14 +26758,17 @@ patch either by running the patch command from there, or copying the patch file into the ${PATCHDIR} directory and calling it - patch-<xx>. (Note the - tarball will have been extracted alongside the regular source - by then, so there is no need to explicitly extract it if it is - a regular gzip'd or compress'd tarball.) If you do the - latter, take extra care not to overwrite something that - already exists in that directory. Also do not forget to add a - command to remove the copied patch in the pre-clean target. + patch-<xx>. + + + Note the tarball will have been extracted alongside the + regular source by then, so there is no need to explicitly + extract it if it is a regular gzip'd or compress'd tarball. + If you do the latter, take extra care not to overwrite + something that already exists in that directory. Also do + not forget to add a command to remove the copied patch in + the pre-clean target. + @@ -26753,11 +26810,13 @@ graphics/jpeg subdirectory of your ports tree to build and install it if it is not found. - - Note that the lib part is - just an argument given to `ldconfig -r | - grep', so periods should be escaped by two - backslashes like in the example above. + + + The lib part is just an argument + given to `ldconfig -r | grep', so + periods should be escaped by two backslashes like in the + example above. + The dependency is checked from within the extract target. Also, the name of the @@ -26794,11 +26853,15 @@ subdirectory of the ports tree if it is not found. It will also see if an executable called `wish' is in your search path, and descend into the x11/tk subdirectory of - your ports tree to build and install it if it is not found. - (Note that in this case, `innd' is actually an executable; if an - executable is in a place that is not expected to be in a - normal user's search path, you should use the full - pathname.) + your ports tree to build and install it if it is not + found. + + + In this case, `innd' is actually an + executable; if an executable is in a place that is not + expected to be in a normal user's search path, you should + use the full pathname. + The dependency is checked from within the install target. Also, the name of the @@ -26823,11 +26886,12 @@ archivers/unzip subdirectory of your ports tree to build and install it if it is not found. - - Note that `build' here means everything from extracting - to compilation. The dependency is checked from within the - extract target. - + + + `build' here means everything from extracting to + compilation. The dependency is checked from within the + extract target. + @@ -26956,13 +27020,14 @@ - - Note that ${MOTIFLIB} - (usually) expands to `' - or `/usr/X11R6/lib/libXm.a', so there is - no need to add `' or `' - in front. - + + + ${MOTIFLIB} (usually) + expands to `' or + `/usr/X11R6/lib/libXm.a', so there is + no need to add `' or + `' in front. + @@ -26993,11 +27058,12 @@ of the directory. : - - Note that this program will not actually - install info files; it merely inserts or - deletes entries in the dir - file. + + + This program will not actually + install info files; it merely inserts or + deletes entries in the dir file. + Here's a seven-step procedure to convert ports to use install-info. I will use @@ -27032,12 +27098,14 @@ entry indentations consistent (we recommend that all entry text start at the 4th tab stop). - Note that you can put only one info entry per file - because of a bug in `install-info - --delete' that deletes only the first entry - if you specify multiple entries in the - @direntry section. - + + Note that you can put only one info entry per file + because of a bug in `install-info + --delete' that deletes only the first entry + if you specify multiple entries in the + @direntry section. + + You can give the dir entries to install-info as arguments ( and @@ -27182,14 +27250,16 @@ - - Note that the `@unexec install-info - --delete' commands have to be listed before - the info files themselves so they can read the files. - Also, the `@exec install-info' commands - have to be after the info files and the - @exec command that creates the the - dir file. + + + The `@unexec install-info + --delete' commands have to be listed before + the info files themselves so they can read the files. + Also, the `@exec install-info' commands + have to be after the info files and the + @exec command that creates the the + dir file. + @@ -27215,12 +27285,14 @@ (export of crypto software) to name just two of them). What we can do with them vary a lot, depending on the exact wordings of the respective licenses. - - Note that it is your responsibility as a porter to read the - licensing terms of the software and make sure that the FreeBSD - project will not be held accountable of violating them by - redistributing the source or compiled binaries either via ftp or - CD-ROM. If in doubt, please contact the &a.ports;. + + + It is your responsibility as a porter to read the + licensing terms of the software and make sure that the FreeBSD + project will not be held accountable of violating them by + redistributing the source or compiled binaries either via ftp + or CD-ROM. If in doubt, please contact the &a.ports;. + There are two variables you can set in the Makefile to handle the situations that arise frequently: @@ -27259,13 +27331,16 @@ - - Note: The GNU General Public License (GPL), both version 1 - and 2, should not be a problem for ports. - - Note: If you are a committer, make sure you update the - ports/LEGAL file too. - + + + The GNU General Public License (GPL), both version 1 + and 2, should not be a problem for ports. + + + + If you are a committer, make sure you update the + ports/LEGAL file too. + @@ -27330,11 +27405,14 @@ Do include package information, i.e. COMMENT, DESCR, and PLIST, in pkg. Note that these files are not - used only for packaging anymore, and are - mandatory now, even if ${NO_PACKAGE} is set. - + remap="tt">pkg. + + + Note that these files are not used only for packaging + anymore, and are mandatory now, even if + ${NO_PACKAGE} is + set. + @@ -27365,9 +27443,11 @@ baz.8 - - Note that this is not usually necessary with ports that - are X applications and use Imake to build. + + + This is not usually necessary with ports that are X + applications and use Imake to build. + If your port anchors its man tree somewhere other than PREFIX, you can use the @@ -27435,12 +27515,15 @@ 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 information. - Note, that this script is not run automatically if you install - the port with `make install'. If - you are depending on it being run, you will have to explicitly - call it on your port's Makefile. - + pkg_add(1) for additional + information. + + + This script is not run automatically if you install the + port with `make install'. If you are + depending on it being run, you will have to explicitly call + it on your port's Makefile. + @@ -27494,9 +27577,12 @@ place the message in pkg/MESSAGE. This capibility is often useful to display additional installation steps to be taken after a pkg_add, or to display licensing - information. (note: the MESSAGE file does - not need to be added to pkg/PLIST). - + information. + + + MESSAGE does not need to be added + to pkg/PLIST). + @@ -27522,11 +27608,12 @@ remap=tt>${DISTDIR} explicitly in your Makefile will not accomplish this, so please use ${DIST_SUBDIR}.) - - Note this does not affect the ${MASTER_SITES} you define in your - Makefile. - + + + This does not affect the ${MASTER_SITES} you define in your + Makefile. + @@ -30464,12 +30551,14 @@ linker only records 3.3 in the headers, and will link with anything starting with libfoo.so.3.(anything >= 3).(highest available). - - Note that ld.so will always use the highest - "minor" revision. Ie: it will use libc.so.2.2 - in preference to libc.so.2.0, even if the - program was initially linked with - libc.so.2.0. + + + ld.so will always use the highest + "minor" revision. Ie: it will use libc.so.2.2 + in preference to libc.so.2.0, even if the + program was initially linked with + libc.so.2.0. + For non-port libraries, it is also our policy to change the shared library version number only once between releases. When you @@ -30489,11 +30578,12 @@ Adding New Kernel Configuration Options Contributed by &a.joerg; - - Note: You should be familiar with the section - about - before reading here. - + + + You should be familiar with the section about + before reading here. + What's a <emphasis>Kernel Option</emphasis>, Anyway? @@ -30680,15 +30770,18 @@ clause in the `config' line of your kernel config file. This is deprecated and should be used only if you want a crash dump from a kernel that crashes during booting. - - Note: In the following, - the term `kgdb' refers to gdb run in `kernel debug mode'. This can be - accomplished by either starting the gdb with the option , or - by linking and starting it under the name kgdb. This is not being done by default, - however, and the idea is basically deprecated since the GNU folks - do not like their tools to behave differently when called by - another name. This feature may well be discontinued in further - releases. + + + In the following, the term `kgdb' refers to + gdb run in `kernel debug mode'. This can be + accomplished by either starting the gdb with + the option , or by linking and starting it + under the name kgdb. This is not being done by + default, however, and the idea is basically deprecated since the + GNU folks do not like their tools to behave differently when + called by another name. This feature may well be discontinued in + further releases. + When the kernel has been built make a copy of it, say kernel.debug, and then run strip @@ -30910,10 +31003,14 @@ to your config file, and rebuild. (See for details on configuring the - FreeBSD kernel. Note that if you have an older version of the boot - blocks, your debugger symbols might not be loaded at all. Update the - boot blocks; the recent ones load the DDB symbols - automagically.) + FreeBSD kernel. + + + Note that if you have an older version of the boot blocks, + your debugger symbols might not be loaded at all. Update the boot + blocks; the recent ones load the DDB symbols + automagically.) + Once your DDB kernel is running, there are several ways to enter DDB. The first, and earliest way is to type the boot flag @@ -30957,9 +31054,13 @@ To get a stack trace, use trace - Note that when entering DDB via a hot-key, the - kernel is currently servicing an interrupt, so the stack trace might - be not of much use for you. + + + + Note that when entering DDB via a hot-key, the kernel is + currently servicing an interrupt, so the stack trace might be not + of much use for you. + If you want to remove a breakpoint, use @@ -30977,9 +31078,13 @@ DDB trace them until the matching return statement is reached by n - Note: this is - different from gdb's `next' statement; - it is like gdb's `finish'. + + + + + This is different from gdb's `next' + statement; it is like gdb's `finish'. + To examine data from memory, use (for example): @@ -31453,48 +31558,51 @@ -> libc.so.4.6.29 + + + Note that if you already have a Linux shared library with + a matching major revision number to the first column of the + 'ldd' output, you will not need to copy the file named in the + last column to your system, the one you already have should + work. It is advisable to copy the shared library anyway if it + is a newer version, though. You can remove the old one, as + long as you make the symbolic link point to the new one. So, + if you have these libraries on your system: + + + /compat/linux/lib/libc.so.4.6.27 + /compat/linux/lib/libc.so.4 -> libc.so.4.6.27 + + - Note that if you already have a Linux shared library with a - matching major revision number to the first column of the 'ldd' - output, you will not need to copy the file named in the last - column to your system, the one you already have should work. It - is advisable to copy the shared library anyway if it is a newer - version, though. You can remove the old one, as long as you make - the symbolic link point to the new one. So, if you have these - libraries on your system: - - /compat/linux/lib/libc.so.4.6.27 - /compat/linux/lib/libc.so.4 -> libc.so.4.6.27 - - - - and you find a new binary that claims to require a later - version according to the output of ldd: - - libc.so.4 (DLL Jump 4.5pl26) -> - libc.so.4.6.29 - - - - If it is only one or two versions out of date in the in the - trailing digit then do not worry about copying - /lib/libc.so.4.6.29 too, because the - program should work fine with the slightly older version. - However, if you like you can decide to replace the - libc.so anyway, and that should leave you - with: - - /compat/linux/lib/libc.so.4.6.29 - /compat/linux/lib/libc.so.4 -> libc.so.4.6.29 - - - - Please note that the symbolic link mechanism is - only needed for Linux binaries. The - FreeBSD runtime linker takes care of looking for matching major - revision numbers itself and you do not need to worry about - it. - + and you find a new binary that claims to require a later + version according to the output of ldd: + + libc.so.4 (DLL Jump 4.5pl26) -> + libc.so.4.6.29 + + + + If it is only one or two versions out of date in the in + the trailing digit then do not worry about copying + /lib/libc.so.4.6.29 too, because the + program should work fine with the slightly older version. + However, if you like you can decide to replace the + libc.so anyway, and that should leave you + with: + + /compat/linux/lib/libc.so.4.6.29 + /compat/linux/lib/libc.so.4 -> libc.so.4.6.29 + + + + + + The symbolic link mechanism is only + needed for Linux binaries. The FreeBSD runtime linker takes + care of looking for matching major revision numbers itself and + you do not need to worry about it. + @@ -31657,11 +31765,13 @@ Finding the necessary files - - Note: the information below is valid as of the time this - document was written, but certain details such as names of ftp - sites, directories and distribution names may have changed by the - time you read this. + + + The information below is valid as of the time this document + was written, but certain details such as names of ftp sites, + directories and distribution names may have changed by the time + you read this. + Linux is distributed by several groups that make their own set of binaries that they distribute. Each distribution has its own @@ -32291,15 +32401,13 @@ a memory address, but not between two I/O ports or two memory locations. - -
- Note: The 8237 does allow two channels - to be connected together to allow memory-to-memory DMA - operations in a non-fly-by mode, but nobody in the PC - industry uses this scarce resource this way since it is faster - to move data between memory locations using the CPU. -
- + + The 8237 does allow two channels to be connected together to + allow memory-to-memory DMA operations in a + non-fly-by mode, but nobody in the PC industry uses + this scarce resource this way since it is faster to move data + between memory locations using the CPU. + In the PC architecture, each DMA channel is normally activated only when the hardware that uses a given DMA channel requests a @@ -32447,15 +32555,13 @@ location 0x0000, not 0x10000. The results of letting this happen are probably not intended. - -
- Note: Physical 64K boundaries - should not be confused with 8086-mode 64K Segments, which - are created by mathematically adding a segment register with - an offset register. Page Registers have no address overlap - and are mathematically OR-ed together. -
- + + Physical 64K boundaries should not be + confused with 8086-mode 64K Segments, which are + created by mathematically adding a segment register with an + offset register. Page Registers have no address overlap and are + mathematically OR-ed together. + To further complicate matters, the external DMA address latches on the PC/AT hold only eight bits, so that gives us @@ -32479,15 +32585,12 @@ buffers are called Bounce Buffers. In the MS-DOS world, they are sometimes called Smart Buffers. - -
- Note: A new implementation of the - 8237, called the 82374, allows 16 bits of page register to be - specified, allows access to the entire 32 bit address space, - without the use of bounce buffers. -
- - + + A new implementation of the 8237, called the 82374, allows + 16 bits of page register to be specified, allows access to the + entire 32 bit address space, without the use of bounce + buffers. + @@ -32585,14 +32688,11 @@ 0, 1, 2, 3, 5, 6 and 7 are usable with peripherals on PC/AT systems. - -
- Note: DMA channel 0 was - reserved for refresh operations in early IBM PC - computers, but is generally available for use by - peripherals in modern systems. -
- + + DMA channel 0 was reserved for refresh operations in + early IBM PC computers, but is generally available for + use by peripherals in modern systems. + When a peripheral is performing Bus Mastering, it is important that the peripheral transmit data to or from @@ -34199,18 +34299,23 @@ the entire cvs-all tree to go from CVSup to CTM without having to rebuild their repository from scratch using a fresh CTM base delta. - - Please note that this special feature only works for the - cvs-all distribution with cvs as the release tag. CVSupping any other - distribution and/or release will get you the specified distribution, - but it will not be suitable for CTM updating. - - Also please note that, because the current version of CTM does - not preserve the timestamps of files, the timestamps at this mirror - site are not the same as those at other mirror sites. Switching - between this site and other sites is not recommended. It will work - correctly, but will be somewhat inefficient. - + + + This special feature only works for the cvs-all distribution with + cvs as the release tag. CVSupping any other + distribution and/or release will get you the specified + distribution, but it will not be suitable for CTM updating. + + + + Because the current version of CTM does not preserve the + timestamps of files, the timestamps at this mirror site are not + the same as those at other mirror sites. Switching between this + site and other sites is not recommended. It will work correctly, + but will be somewhat inefficient. + + Germany