diff --git a/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml b/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml index c7d6ac5bb5..af061f6c6e 100644 --- a/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml @@ -234,7 +234,7 @@ Be sure to always check the file /usr/src/UPDATING, before you perform any update steps, in the case you sync your source-tree with the + linkend="cutting-edge">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 @@ -357,7 +357,7 @@ The new kernel will be copied to the root directory as /kernel and the old kernel will be moved to /kernel.old. Now, shutdown the system and - reboot to use your kernel. In case something goes wrong, there are + reboot to use your new kernel. In case something goes wrong, there are some troubleshooting instructions at the end of this chapter. Be sure to read the section which explains how to recover in case your new kernel sure whether you should use I586_CPU or I686_CPU), however, for a custom kernel, it is best to specify only the CPU you have. If you are unsure of your CPU type, - you can use the dmesg command to + you can use the &man.dmesg.8; command to view your boot up messages. kernel options @@ -615,10 +615,10 @@ options FFS_ROOT #FFS usable as root device [keep this!]options SOFTUPDATES #Enable FFS soft updates support - This option enables soft updates in the kernel, this will help speed + This option enables Soft Updates in the kernel, this will help speed up write access on the disks. They are enabled by default in the 4.X branch but may not be turned on. Review the output from &man.mount.8; to see - if you have them enabled. If you do not see the soft-updates option then + if you have them enabled. If you do not see the soft-updates option then you will need to activate it using the &man.tunefs.8; or &man.newfs.8; for new filesystems. @@ -702,9 +702,9 @@ options CD9660_ROOT #CD-ROM usable as root, CD9660 requiredoptions UCONSOLE #Allow users to grab the console Allow users to grab the console, which is useful for X users. - For example, you can create a console xterm by typing xterm - -C, which will display any write, - talk, and any other messages you receive, as well + For example, you can create a console xterm by typing xterm + -C, which will display any &man.write.1;, + &man.talk.1;, and any other messages you receive, as well as any console messages sent by the kernel. options USERCONFIG #boot -c editor @@ -778,8 +778,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), you cannot run FreeBSD at - this time (support is being worked on). + IBM PS/2 (Micro Channel Architecture), FreeBSD provides some limited support at + this time. For more information about the MCA support, see /usr/src/sys/i386/conf/LINT. device eisa @@ -1112,7 +1112,7 @@ pseudo-device pty # Pseudo-ttys (telnet etc) It is used by incoming telnet and rlogin sessions, xterm, and some other applications such - as emacs. A + as Emacs. A number after pty indicates the number of ptys to create. If you need more than the default of 16 simultaneous xterm windows @@ -1123,7 +1123,7 @@ pseudo-device pty # Pseudo-ttys (telnet etc) Memory disk pseudo-devices. - pesudo-device gif + pseudo-device gif or @@ -1258,16 +1258,16 @@ pseudo-device bpf # Berkeley packet filter config fails: - If the config command fails when you + If the &man.config.8; command fails when you give it your kernel description, you have probably made a simple error somewhere. Fortunately, - config will print the line number that it + &man.config.8; will print the line number that it had trouble with, so you can quickly skip to it with - vi. For example, if you see: + vi. For example, if you see: config: line 17: syntax error - You can skip to the problem in vi by + You can skip to the problem in vi by typing 17G in command mode. Make sure the keyword is typed correctly, by comparing it to the GENERIC kernel or another @@ -1281,7 +1281,7 @@ pseudo-device bpf # Berkeley packet filter If the make command fails, it usually signals an error in your kernel description, but not severe - enough for config to catch it. Again, look + enough for &man.config.8; to catch it. Again, look over your configuration, and if you still cannot resolve the problem, send mail to the &a.questions; with your kernel configuration, and it should be diagnosed very quickly. @@ -1289,7 +1289,7 @@ pseudo-device bpf # Berkeley packet filter - Installing the new kernel fails + Installing the new kernel fails: If the kernel compiled fine, but failed to install @@ -1306,17 +1306,17 @@ pseudo-device bpf # Berkeley packet filter - The kernel will not boot:The kernel does not boot: If your new kernel does not boot, or fails to - recognize your devices, do not panic! Fortunately, BSD has + recognize your devices, do not panic! Fortunately, FreeBSD 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 counts down from 10. Hit any key except for the - enter key, type unload + Enter key, type unload and then type boot kernel.old, or the filename of any other kernel that will boot properly. @@ -1365,8 +1365,8 @@ pseudo-device bpf # Berkeley packet filter - The kernel works, but ps does not work - any more!: + The kernel works, but &man.ps.1; does not work + any more: If you have installed a different version of the kernel