diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml index fce829e4f2..a81b1f6b03 100644 --- a/en_US.ISO8859-1/books/faq/book.xml +++ b/en_US.ISO8859-1/books/faq/book.xml @@ -3262,7 +3262,7 @@ kern.sched.name: ULE - Install LILO at the start of your &linux; boot + Install LILO at the start of the &linux; boot partition instead of in the Master Boot Record. You can then boot LILO from BootEasy. @@ -3889,7 +3889,7 @@ kern.sched.name: ULE -a -t ufs to mount the file system where your favorite editor is defined. If that editor is on a network file system, either configure - the network manually before you mounting the network file + the network manually before mounting the network file systems, or use an editor which resides on a local file system, such as &man.ed.1;. @@ -4343,7 +4343,7 @@ options SYSVMSG # enable for messaging vnlru flushes and frees vnodes when the system hits the kern.maxvnodes limit. This kernel thread sits mostly idle, and only - activates if you have a huge amount of RAM and are + activates when there is a huge amount of RAM and users are accessing tens of thousands of tiny files. @@ -4443,8 +4443,7 @@ options SYSVMSG # enable for messaging - What is /var/empty? I can not - delete it! + What is /var/empty? @@ -4453,14 +4452,8 @@ options SYSVMSG # enable for messaging separation. The /var/empty directory is empty, owned by root and has the - schg flag set. - - Although it is not recommended to delete this - directory, to do so you will need to unset the - schg flag first. See the - &man.chflags.1; manual page for more information (and bear - in mind the answer to the - question on unsetting the schg flag). + schg flag set. This directory should + not be deleted. @@ -4472,7 +4465,7 @@ options SYSVMSG # enable for messaging - To see what &man.newsyslog.8; will do use the + To see what &man.newsyslog.8; will do, use the following: &prompt.user; newsyslog -nrvv @@ -4509,8 +4502,8 @@ options SYSVMSG # enable for messaging Foundation administers the X protocol standards, with the current reference - implementation, version 11 release &xorg.version;, so you - will often see references shortened to + implementation, version 11 release &xorg.version;, so + references are often shortened to X11. Many implementations are available for different @@ -4560,7 +4553,7 @@ options SYSVMSG # enable for messaging - Your system is probably running at a raised + The system is probably running at a raised securelevel. It is not possible to start X at a raised securelevel because X requires write access to &man.io.4;. For more @@ -4582,20 +4575,20 @@ options SYSVMSG # enable for messaging - If you are using &man.syscons.4; (the default console - driver), you can configure &os; to support a mouse pointer + When using &man.syscons.4;, the default console + driver, &os; can be configured to support a mouse pointer on each virtual screen. To avoid conflicting with X, &man.syscons.4; supports a virtual device called /dev/sysmouse. All mouse events received from the real mouse device are written to the - &man.sysmouse.4; device via &man.moused.8;. To use your + &man.sysmouse.4; device via &man.moused.8;. To use the mouse on one or more virtual consoles, and use X, see and set up &man.moused.8;. Then edit /etc/X11/xorg.conf and - make sure you have the following lines: + make sure the following lines exist: Section "InputDevice" Option "Protocol" "SysMouse" @@ -4635,19 +4628,12 @@ options SYSVMSG # enable for messaging - Yes. - - You need to tell X that you have a 5 button mouse. To + Yes, if you configure X for a 5 button mouse. To do this, add the lines Buttons 5 and ZAxisMapping 4 5 to the InputDevice section of - /etc/X11/xorg.conf. For example, you - might have the following InputDevice - section in /etc/X11/xorg.conf. - - - <quote>InputDevice</quote> Section for Wheeled - Mouse in &xorg; Configuration File + /etc/X11/xorg.conf, as seen in this + example: Section "InputDevice" Identifier "Mouse1" @@ -4657,16 +4643,14 @@ options SYSVMSG # enable for messaging Option "Buttons" "5" Option "ZAxisMapping" "4 5" EndSection - - - <quote>.emacs</quote> Example for Naive Page - Scrolling with Wheeled Mouse (optional) + To use the mouse in + Emacs, also add the following + lines to~/.emacs: ;; wheel mouse (global-set-key [mouse-4] 'scroll-down) (global-set-key [mouse-5] 'scroll-up) - @@ -4677,23 +4661,20 @@ EndSection - Yes, you will have to configure a few things to make + Yes, after configuring a few things to make it work. - If you plan to use the Xorg synaptics driver you - must remove moused_enable from - rc.conf. Xorg can not use the - synaptics mouse if the moused already sits on - /dev/psm0. + In order to use the Xorg synaptics driver, + first remove moused_enable from + rc.conf. - To enable synaptics in the &man.psm.4; driver you need - to add the following into + To enable synaptics, add the following line to /boot/loader.conf: hw.psm.synaptics_support="1" - You also need the following into - xorg.conf: + Add the following to + /etc/X11/xorg.conf: Section "InputDevice" Identifier "Touchpad0" @@ -4733,27 +4714,26 @@ EndSection - Virtual consoles enable you to have + Virtual consoles provide several simultaneous sessions on the same machine without doing anything complicated like setting up a network or running X. When the system starts, it will display a login prompt on the monitor after displaying all the boot messages. - You can then type in your login name and password and - start working (or playing!) on the first virtual + Type in your login name and password to + start working on the first virtual console. - At some point, you will probably wish to start another + To start another session, perhaps to look at documentation for a program - you are running or to read your mail while waiting for an - FTP transfer to finish. Just do AltF2 - (hold down Alt and press - F2), and you will find a login prompt - waiting for you on the second virtual - console! When you want to go back to the - original session, do Alt and press + F2. This will display the login prompt + for the second virtual + console. To go back to the + original session, press AltF1. The default &os; installation has eight virtual @@ -4766,10 +4746,10 @@ EndSection and so on will switch between these virtual consoles. - To enable more of them, edit + To enable more of virtual consoles, edit /etc/ttys (see &man.ttys.5;) and add entries for ttyv8 to - ttyvc after the comment on + ttyvc, after the comment on Virtual terminals: # Edit the existing entry for ttyv8 in /etc/ttys and change @@ -4779,63 +4759,34 @@ ttyv9 "/usr/libexec/getty Pc" xterm on secure ttyva "/usr/libexec/getty Pc" xterm on secure ttyvb "/usr/libexec/getty Pc" xterm on secure - Use as many or as few as you want. The more virtual - terminals you have, the more resources that are used; this - can be important if you have 8 MB RAM or less. You - may also want to change the secure to + The more virtual + terminals, the more resources that are used. This can be + problematic on systems with 8 MB RAM or less. Consider + changing secure to insecure. Versions of &os; prior to 9.0 used the cons25 terminal type, and not - xterm. Existing entries in - /etc/ttys can be used on which to - base new additions. + xterm. Use the format of existing entries in + when adding entries to /etc/ttys. - If you want to run an X server you - must leave at least one virtual - terminal unused (or turned off) for it to use. That is - to say that if you want to have a login prompt pop up - for all twelve of your Alt-function keys, you are out of - luck — you can only do this for eleven of them if - you also want to run an X server on the same - machine. + In order to run an X server, at least one virtual + terminal must be left to off for it to use. This + means that only eleven of the Alt-function keys can be + used as virtual consoles so that one is left for the + X server. - The easiest way to disable a console is by turning it - off. For example, if you had the full 12 terminal - allocation mentioned above and you wanted to run X, you - would change settings for virtual terminal 12 from: - - ttyvb "/usr/libexec/getty Pc" xterm on secure - - to: + For example, to run X and eleven virtual consoles, the + setting for virtual terminal 12 should be: ttyvb "/usr/libexec/getty Pc" xterm off secure - If your keyboard has only ten function keys, you would - end up with: - - ttyv9 "/usr/libexec/getty Pc" xterm off secure -ttyva "/usr/libexec/getty Pc" xterm off secure -ttyvb "/usr/libexec/getty Pc" xterm off secure - - (You could also just delete these lines.) - - Next, the easiest (and cleanest) way to activate the - virtual consoles is to reboot. However, if you really do - not want to reboot, you can just shut down the X Window - system and execute (as root): - - &prompt.root; kill -HUP 1 - - It is imperative that you completely shut down X - Window if it is running, before running this command. If - you do not, your system will probably appear to hang or - lock up after executing kill. + The easiest way to activate the + virtual consoles is to reboot. @@ -4851,20 +4802,19 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure action="simul">CtrlAltF1 would return you to the first virtual console. - Once you are back to a text console, you can then use + Once at a text console, use AltFn - as normal to move between them. + to move between them. - To return to the X session, you must switch to the - virtual console running X. If you invoked X from the - command line, (e.g., using startx) then + To return to the X session, switch to the + virtual console running X. If X was started from the + command line using startx, the X session will attach to the next unused virtual console, not the text console from which it was invoked. - If you have eight active virtual terminals then X will be - running on the ninth, and you would use AltF9 - to return. + For eight active virtual terminals, X will + run on the ninth, so use AltF9. @@ -4903,12 +4853,12 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure this is to have the script sleep 10 seconds or so then launch xdm. - If you are to start xdm from + When starting xdm from /etc/ttys, there still is a chance of conflict between xdm and &man.getty.8;. One way to avoid this is to add the vt number in - /usr/local/lib/X11/xdm/Xservers + /usr/local/lib/X11/xdm/Xservers: :0 local /usr/local/bin/X vt4 @@ -4927,7 +4877,7 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure - If you start X with + When X is started with startx, the permissions on /dev/console will not get changed, resulting in things @@ -4959,18 +4909,12 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure - Your mouse and the mouse driver may have somewhat - become out of synchronization. - - In rare cases the driver may erroneously report - synchronization problem and you may see the kernel - message: + The mouse and the mouse driver may have + become out of synchronization. In rare cases, the driver may also erroneously report + synchronization errors: psmintr: out of sync (xxxx != yyyy) - and notice that your mouse does not work - properly. - If this happens, disable the synchronization check code by setting the driver flags for the PS/2 mouse driver to 0x100. This can be easiest achieved @@ -4986,11 +4930,10 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure - Run the command - xmodmap -e "pointer = 3 2 1". - You add the above command to - .xinitrc or - .xsession to make it happen + Type + xmodmap -e "pointer = 3 2 1". Add this command to + ~/.xinitrc or + ~/.xsession to make it happen automatically. @@ -5017,11 +4960,11 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure - Yes. All you need to do is use &man.xmodmap.1; to - define what function you wish them to perform. + Yes. Use &man.xmodmap.1; to + define which functions the keys should perform. - Assuming all Windows keyboards are - standard then the keycodes for these three keys are the + Assuming all Windows keyboards are + standard, the keycodes for these three keys are the following: @@ -5051,7 +4994,7 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure &prompt.root; xmodmap -e "keycode 115 = comma" To have the Windows key-mappings - enabled automatically every time you start X either put + enabled automatically every time X is started, either put the xmodmap commands in ~/.xinitrc or, preferably, create a ~/.xmodmaprc and include the @@ -5061,31 +5004,29 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure xmodmap $HOME/.xmodmaprc - For example, you could map the 3 keys to be + For example, to map the 3 keys to be F13, F14, and F15, respectively. This would make it easy to map them to useful functions within applications - or your window manager, as demonstrated further - down. + or the window manager. - To do this put the following in + To do this, put the following in ~/.xmodmaprc. keycode 115 = F13 keycode 116 = F14 keycode 117 = F15 - If you use the x11-wm/fvwm2 port, - for example, you could map the keys so that - F13 iconifies (or de-iconifies) the + For the x11-wm/fvwm2 desktop manager, + one could map the keys so that + F13 iconifies or de-iconifies the window the cursor is in, F14 brings the window the cursor is in to the front or, if it is already at the front, pushes it to the back, and F15 pops up the main Workplace - (application) menu even if the cursor is not on the - desktop, which is useful if you do not have any part of - the desktop visible (and the logo on the key matches its - functionality). + menu even if the cursor is not on the + desktop, which is useful when no part of + the desktop is visible. The following entries in ~/.fvwmrc implement the @@ -5105,8 +5046,8 @@ Key F15 A A Menu Workplace Nop The availability of 3D acceleration depends on the - version of &xorg; that you are using and the type of video - chip you have. If you have an nVidia chip, you can use + version of &xorg; and the type of video + chip. For an nVidia chip, use the binary drivers provided for &os; by installing one of the following ports: