From a7368f51bbee7b105a7edbb0a8972e6bfd79f31c Mon Sep 17 00:00:00 2001 From: Tom Rhodes Date: Sat, 29 Mar 2003 15:27:47 +0000 Subject: [PATCH] Make a few areas more clear to the reader. Make use of the &os; entity. Add a few tabs. Grammar. --- .../books/handbook/kernelconfig/chapter.sgml | 135 +++++++++--------- 1 file changed, 69 insertions(+), 66 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml b/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml index 4abe6b380a..453d0e3e3c 100644 --- a/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml @@ -34,9 +34,9 @@ building a custom kernel - The kernel is the core of the FreeBSD operating system. It is + The kernel is the core of the &os; operating system. It is responsible for managing memory, enforcing security controls, - networking, disk access, and much more. While more and more of FreeBSD + networking, disk access, and much more. While more and more of &os; becomes dynamically configurable it is still occasionally necessary to reconfigure and recompile your kernel. @@ -75,19 +75,19 @@ Why Build a Custom Kernel? - Traditionally, FreeBSD has had what is called a + Traditionally, &os; has had what is called a monolithic kernel. This means that the kernel was one large program, supported a fixed list of devices, and if you wanted to change the kernel's behavior then you had to compile a new kernel, and then reboot your computer with the new kernel. - Today, FreeBSD is rapidly moving to a model where much of the + Today, &os; is rapidly moving to a model where much of the kernel's functionality is contained in modules which can be dynamically loaded and unloaded from the kernel as necessary. This allows the kernel to adapt to new hardware suddenly becoming available (such as PCMCIA cards in a laptop), or for new functionality to be brought into the kernel that was not necessary when the kernel was originally - compiled. Colloquially these are called KLDs. + compiled. This is known as a modular kernel. Colloquially these are called KLDs. Despite this, it is still necessary to carry out some static kernel configuration. In some cases this is because the functionality is so @@ -97,7 +97,7 @@ Building a custom kernel is one of the most important rites of passage nearly every Unix user must endure. This process, while - time consuming, will provide many benefits to your FreeBSD system. + time consuming, will provide many benefits to your &os; system. Unlike the GENERIC kernel, which must support a wide range of hardware, a custom kernel only contains support for your PC's hardware. This has a number of @@ -147,10 +147,12 @@ pc98 (an alternative development branch of PC hardware, popular in Japan). Everything inside a particular architecture's directory deals with that architecture only; the rest - of the code is common to all platforms to which FreeBSD could + of the code is common to all platforms to which &os; could potentially be ported. Notice the logical organization of the directory structure, with each supported device, filesystem, and - option in its own subdirectory. + option in its own subdirectory. &os; 5.X and up has support for + sparc64, and a few other architectures under + development. If there is not a @@ -161,7 +163,7 @@ then Distributions, then src, then sys. If you have an aversion to sysinstall and - you have access to an official FreeBSD CDROM, then + you have access to an official &os; CDROM, then you can also install the source from the command line: &prompt.root; mount /cdrom @@ -179,7 +181,7 @@ &prompt.root; cp GENERIC MYKERNEL Traditionally, this name is in all capital letters and, if you - are maintaining multiple FreeBSD machines with different hardware, + are maintaining multiple &os; machines with different hardware, it is a good idea to name it after your machine's hostname. We will call it MYKERNEL for the purpose of this example. @@ -214,7 +216,7 @@ editor. If you are just starting out, the only editor available will probably be vi, which is too complex to explain here, but is covered well in many books in the bibliography. However, FreeBSD does + linkend="bibliography">bibliography. However, &os; does offer an easier editor called ee which, if you are a beginner, should be your editor of choice. Feel free to change the comment lines at the top to reflect your configuration or @@ -235,16 +237,16 @@ /usr/src/UPDATING, before you perform any update steps, in the case you sync your source tree with the - latest sources of the FreeBSD project. - In this file all important issues with updating FreeBSD - are written down. /usr/src/UPDATING always fits - to your version of the FreeBSD source, and is therefore more accurate - for those information than the handbook. + latest sources of the &os; project. + In this file all important issues with updating &os; + are typed out. /usr/src/UPDATING always fits + your version of the &os; source, and is therefore more accurate + for new information than the handbook. You must now compile the source code for the kernel. There are two procedures you can use to do this, and the one you will use depends on - why you are rebuilding the kernel, and the version of FreeBSD you are + why you are rebuilding the kernel, and the version of &os; you are running. @@ -254,8 +256,8 @@ - If you are running a FreeBSD version prior to 4.0, and you are - not upgrading to FreeBSD 4.0 or higher using + If you are running a &os; version prior to 4.0, and you are + not upgrading to &os; 4.0 or higher using the make world procedure, use procedure 1. @@ -283,11 +285,12 @@ - Change into the build directory. + Change into the build directory. This is printed out after running the aformentioned + command.. &prompt.root; cd ../compile/MYKERNEL - For FreeBSD version prior to 5.0, use instead: + For &os; version prior to 5.0, use instead: &prompt.root; cd ../../compile/MYKERNEL @@ -330,7 +333,7 @@ - In FreeBSD 4.2 and older you must replace + In &os; 4.2 and older you must replace KERNCONF= with KERNEL=. 4.2-STABLE that was fetched before Feb 2nd, 2001 does not recognize KERNCONF=. @@ -368,22 +371,22 @@ linkend="kernelconfig-noboot">does not boot. - As of FreeBSD 5.0, kernels are installed along with their + As of &os; 5.0, kernels are installed along with their modules in /boot/kernel, and old kernels will be backed up as /boot/kernel.old. Other files relating to the boot process, such as the boot &man.loader.8; and configuration are also stored in /boot. Third party or custom modules - may be placed in /boot/modules, although - users should be aware that keeping modules in sync with the - compiled kernel is very important. Modules not intended - to run with the compiled kernel may result in instability - or incorrectness. + may be placed in /boot/modules, although + users should be aware that keeping modules in sync with the + compiled kernel is very important. Modules not intended + to run with the compiled kernel may result in instability + or incorrectness. If you have added any new devices (such as sound cards) and you - are running FreeBSD 4.X or previous versions, you + are running &os; 4.X or previous versions, you may have to add some device nodes to your /dev directory before you can use them. For more information, take a look at Making @@ -422,7 +425,7 @@ Quoting numbers - In all versions of FreeBSD up to and including 3.X, + In all versions of &os; up to and including 3.X, &man.config.8; required that any strings in the configuration file that contained numbers used as text had to be enclosed in double quotes. @@ -446,23 +449,23 @@ /usr/src/sys/i386/conf/LINT. # -# GENERIC -- Generic kernel configuration file for FreeBSD/i386 +# GENERIC -- Generic kernel configuration file for &os;/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # -# http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html +# http://www.&os;.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the -# FreeBSD World Wide Web server (http://www.FreeBSD.ORG/) for the +# &os; World Wide Web server (http://www.&os;.ORG/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # -# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246 2000/03/09 16:32:55 jlemon Exp $ +# $&os;: src/sys/i386/conf/GENERIC,v 1.246 2000/03/09 16:32:55 jlemon Exp $ The following are the mandatory keywords required in every kernel you build: @@ -494,7 +497,7 @@ cpu I686_CPU CPU type, you can check the /var/run/dmesg.boot file to view your boot up messages. - In FreeBSD 5.0, support for I386_CPU + In &os; 5.0, support for I386_CPU is disabled by default. kernel options @@ -535,12 +538,12 @@ cpu EV5 equal to the number of simultaneous users you expect to have on your machine. - Starting with FreeBSD 4.5, the system will auto-tune this setting + Starting with &os; 4.5, the system will auto-tune this setting for you if you explicitly set it to 0 The auto-tuning algorithm sets maxuser equal to the amount of memory in the system, with a minimum of 32, and a maximum of 384.. If you are - using an earlier version of FreeBSD, or you want to manage it + using an earlier version of &os;, or you want to manage it yourself you will want to set maxusers to at least 4, especially if you are using the X Window System or compiling software. The reason is that @@ -576,7 +579,7 @@ cpu EV5 device npx0 at nexus? port IO_NPX irq 13 npx0 is the interface to the floating point - math unit in FreeBSD, which is either the hardware co-processor or + math unit in &os;, which is either the hardware co-processor or the software math emulator. This is not optional. @@ -602,17 +605,17 @@ options MATH_EMULATE #Support for x87 emulation The normal math co-processor emulation routines that come with - FreeBSD are not very accurate. If you do not + &os; are not very accurate. If you do not have a math co-processor, and you need the best accuracy, it is recommended that you change this option to GPL_MATH_EMULATE to use the GNU math support, which is not included by default for licensing reasons. - In FreeBSD 5.0, math emulation is disabled by default, + In &os; 5.0, math emulation is disabled by default, as older CPUs that do not have native floating point math support are far less common, and in many cases not supported by the native - FreeBSD kernel without other additional options. + &os; kernel without other additional options. options INET #InterNETworking @@ -631,12 +634,12 @@ options FFS_ROOT #FFS usable as root device [keep this!]This is the basic hard drive filesystem. Leave it in if you boot from the hard disk. - In FreeBSD 5.0, FFS_ROOT is no longer + In &os; 5.0, FFS_ROOT is no longer required. options UFS_ACL #Support for access control lists - This option, present only in FreeBSD 5.0, enables kernel support + This option, present only in &os; 5.0, enables kernel support for access control lists. This relies on the use of extended attributes and UFS2, and the feature is described in detail in the . ACLs are enabled by default, and should not be @@ -649,7 +652,7 @@ options FFS_ROOT #FFS usable as root device [keep this!]This option includes some code to speed up disk operations on large directories, at the expense of using a some additional memory. You would normally keep this for a large server, or interactive workstation, - and remove it if you are using FreeBSD on a smaller system where memory + and remove it if you are using &os; on a smaller system where memory is at a premium and disk access speed is less important, such as a firewall. @@ -680,7 +683,7 @@ options MD_ROOT #MD is a potential root device Now you simply need to either reboot, or run the command mount /tmp. - In FreeBSD 5.0, &man.md.4;-backed UFS file systems are + In &os; 5.0, &man.md.4;-backed UFS file systems are used for memory file systems rather than MFS. Information on configuring MD-backed file systems may be found in the man pages for &man.mdconfig.8; and &man.mdmfs.8;. As a result, the @@ -729,7 +732,7 @@ options CD9660_ROOT #CD-ROM usable as root, CD9660 requiredThe process filesystem. This is a pretend filesystem mounted on /proc which allows programs like &man.ps.1; to give you more information on what - processes are running. In FreeBSD 5.0, use of PROCFS + processes are running. In &os; 5.0, use of PROCFS is not required under most circumstances, as most debugging and monitoring tools have been adapted to run without PROCFS. In addition, 5.0-CURRENT kernels @@ -738,8 +741,8 @@ options CD9660_ROOT #CD-ROM usable as root, CD9660 requiredoptions PSEUDOFS #Pseudo-filesystem framework - PSEUDOFS is not available in FreeBSD 4.X. - Unlike in FreeBSD 4.X, new installs of FreeBSD 5.0 will not mount + PSEUDOFS is not available in &os; 4.X. + Unlike in &os; 4.X, new installs of &os; 5.0 will not mount the process file system by default. options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] @@ -747,10 +750,10 @@ options CD9660_ROOT #CD-ROM usable as root, CD9660 requiredCompatibility with 4.3BSD. Leave this in; some programs will act strangely if you comment this out. - options COMPAT_FREEBSD4 #Compatible with FreeBSD4 + options COMPAT_FREEBSD4 #Compatible with &os;4 - This option is required on FreeBSD 5.0 i386 and alpha systems - to support applications compiled on older versions of FreeBSD + This option is required on &os; 5.0 i386 and alpha systems + to support applications compiled on older versions of &os; that use older system call interfaces. It is recommended that this option be used on all i386 and alpha systems that may run older applications; platforms that gained support only in @@ -762,7 +765,7 @@ options CD9660_ROOT #CD-ROM usable as root, CD9660 required options UCONSOLE #Allow users to grab the console @@ -774,7 +777,7 @@ options CD9660_ROOT #CD-ROM usable as root, CD9660 required - In FreeBSD 5.0, UCONSOLE is no + In &os; 5.0, UCONSOLE is no longer required. options USERCONFIG #boot -c editor @@ -787,7 +790,7 @@ options CD9660_ROOT #CD-ROM usable as root, CD9660 requiredThis option allows you to boot the visual configuration editor from the boot menu. - From FreeBSD versions 5.0 and later, userconfig has been depreciated + From &os; versions 5.0 and later, userconfig has been depreciated in favor of the new &man.device.hints.5; method. For more information on &man.device.hints.5; please visit @@ -826,7 +829,7 @@ options _KPOSIX_PRIORITY_SCHEDULING applications in the ports collection use these (such as StarOffice). - In FreeBSD 5.0, all of this functionality is now + In &os; 5.0, all of this functionality is now provided by the _KPOSIX_PRIORITY_SCHEDULING option, and P1003_1B is no longer required. @@ -844,7 +847,7 @@ options _KPOSIX_PRIORITY_SCHEDULING typically want this option as it will help protect the machine from denial of service packet attacks. - In FreeBSD 5.0, this feature is enabled by default and + In &os; 5.0, this feature is enabled by default and the ICMP_BANDLIM option is not required. @@ -860,8 +863,8 @@ options _KPOSIX_PRIORITY_SCHEDULING device isa - All PCs supported by FreeBSD have one of these. If you have an - IBM PS/2 (Micro Channel Architecture), FreeBSD provides some limited support at + All PCs supported by &os; have one of these. If you have an + IBM PS/2 (Micro Channel Architecture), &os; provides some limited support at this time. For more information about the MCA support, see /usr/src/sys/i386/conf/LINT. device eisa @@ -1049,7 +1052,7 @@ device sio3 at isa? disable port IO_COM4 irq 9 If you have an internal modem on COM4 and a serial port at COM2, you will have to change the IRQ of the modem to 2 (for obscure technical reasons, IRQ2 = IRQ 9) in order to access it - from FreeBSD. If you have a multiport serial card, check the + from &os;. If you have a multiport serial card, check the manual page for &man.sio.4; for more information on the proper values for these lines. Some video cards (notably those based on S3 chips) use IO addresses in the form of @@ -1214,10 +1217,10 @@ pseudo-device pty # Pseudo-ttys (telnet etc) This implements IPv6 over IPv4 tunneling, IPv4 over IPv6 tunneling, IPv4 over IPv4 tunneling, and IPv6 over IPv6 tunneling. Beginning with - FreeBSD 4.4 the gif device is + &os; 4.4 the gif device is auto-cloning, and you should use the first example (without the number after gif). Earlier versions of - FreeBSD require the number. + &os; require the number. pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) @@ -1259,7 +1262,7 @@ pseudo-device bpf # Berkeley packet filter Support for various USB devices. For more information and additional devices supported by - FreeBSD, see + &os;, see /usr/src/sys/i386/conf/LINT. @@ -1271,7 +1274,7 @@ pseudo-device bpf # Berkeley packet filter MAKEDEV - If you are running FreeBSD 5.0 or later + If you are running &os; 5.0 or later you can safely skip this section. These versions use &man.devfs.5; to allocate device nodes transparently for the user. @@ -1399,10 +1402,10 @@ pseudo-device bpf # Berkeley packet filter If your new kernel does not boot, or fails to - recognize your devices, do not panic! Fortunately, FreeBSD has + recognize your devices, do not panic! Fortunately, &os; has an excellent mechanism for recovering from incompatible kernels. Simply choose the kernel you want to boot from at - the FreeBSD boot loader. You can access this when the system + the &os; boot loader. You can access this when the system counts down from 10. Hit any key except for the Enter key, type unload and then type @@ -1450,7 +1453,7 @@ pseudo-device bpf # Berkeley packet filter &prompt.root; chflags schg /kernel - In FreeBSD 5.0, kernels are not installed with the + In &os; 5.0, kernels are not installed with the system immutable flag, so this is unlikely to be the source of the problem you're experiencing.