From owner-svn-doc-head@FreeBSD.ORG Fri Jun 12 03:10:25 2015 Return-Path: Delivered-To: svn-doc-head@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D214241; Fri, 12 Jun 2015 03:10:25 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89F1914BD; Fri, 12 Jun 2015 03:10:25 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t5C3APs1087104; Fri, 12 Jun 2015 03:10:25 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id t5C3APlS087103; Fri, 12 Jun 2015 03:10:25 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201506120310.t5C3APlS087103@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Fri, 12 Jun 2015 03:10:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r46816 - head/en_US.ISO8859-1/books/handbook/x11 X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2015 03:10:25 -0000 Author: bcr Date: Fri Jun 12 03:10:24 2015 New Revision: 46816 URL: https://svnweb.freebsd.org/changeset/doc/46816 Log: Whitespace cleanup. Translators can ignore. Modified: head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/x11/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Fri Jun 12 02:21:25 2015 (r46815) +++ head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Fri Jun 12 03:10:24 2015 (r46816) @@ -30,18 +30,17 @@ An installation of &os; using bsdinstall does not automatically - install a graphical user interface. This chapter describes - how to install and configure &xorg;, - which provides the open source X Window System used to provide - a graphical environment. It then describes how to find and + install a graphical user interface. This chapter describes how + to install and configure &xorg;, + which provides the open source X Window System used to provide a + graphical environment. It then describes how to find and install a desktop environment or window manager. Users who prefer an installation method that automatically - configures the &xorg; and offers - a choice of window managers during installation should - refer to the pcbsd.org + configures the &xorg; and offers a + choice of window managers during installation should refer to + the pcbsd.org website. @@ -103,17 +102,17 @@ X was designed from the beginning to be network-centric, and adopts a client-server - model. In this model, the X server runs - on the computer that has the keyboard, monitor, and mouse - attached. The server's responsibility includes tasks - such as managing the display, handling input from the - keyboard and mouse, and handling input or output from - other devices such as a tablet or a video projector. - This confuses some people, because the X terminology is - exactly backward to what they expect. They expect the - X server to be the big powerful machine - down the hall, and the X client to be the - machine on their desk. + model. In this model, the X server runs on + the computer that has the keyboard, monitor, and mouse + attached. The server's responsibility includes tasks such + as managing the display, handling input from the keyboard + and mouse, and handling input or output from other devices + such as a tablet or a video projector. This confuses some + people, because the X terminology is exactly backward to + what they expect. They expect the X server + to be the big powerful machine down the hall, and the + X client to be the machine on their + desk. @@ -133,10 +132,9 @@ In a home or small office environment, the X server and the X clients commonly run on the same computer. It is also possible to run the X server on a less powerful - computer and to run the X applications on a more - powerful system. In this scenario, the communication - between the X client and server takes place over the - network. + computer and to run the X applications on a more powerful + system. In this scenario, the communication between the X + client and server takes place over the network. @@ -147,23 +145,23 @@ X does not dictate what windows should look like on screen, how to move them around with the mouse, which keystrokes should be used to move between windows, what - the title bars on each window should look like, whether - or not they have close buttons on them, and so on. - Instead, X delegates this responsibility to a separate - window manager application. There are dozens of window - managers available. Each window manager - provides a different look and feel: some support virtual - desktops, some allow customized keystrokes to manage the - desktop, some have a Start button, and - some are themeable, allowing a complete change of the - desktop's look-and-feel. Window managers are available - in the x11-wm category of the - Ports Collection. + managers available. Each window manager provides + a different look and feel: some support virtual desktops, + some allow customized keystrokes to manage the desktop, + some have a Start button, and some are + themeable, allowing a complete change of the desktop's + look-and-feel. Window managers are available in the + x11-wm category of the Ports + Collection. Each window manager uses a different configuration - mechanism. Some expect configuration file written by - hand while others provide graphical tools for most + mechanism. Some expect configuration file written by hand + while others provide graphical tools for most configuration tasks. @@ -193,26 +191,26 @@ One focus policy is called click-to-focus. In this model, a window becomes active upon receiving a mouse click. In the - focus-follows-mouse policy, the window - that is under the mouse pointer has focus and the focus - is changed by pointing at another window. If the mouse - is over the root window, then this window is focused. - In the sloppy-focus model, if the mouse - is moved over the root window, the most recently used - window still has the focus. With sloppy-focus, focus - is only changed when the cursor enters a new window, and - not when exiting the current window. In the - click-to-focus policy, the active window - is selected by mouse click. The window may then be - raised and appear in front of all other windows. All - keystrokes will now be directed to this window, even if - the cursor is moved to another window. + focus-follows-mouse policy, the window that + is under the mouse pointer has focus and the focus is + changed by pointing at another window. If the mouse is + over the root window, then this window is focused. In the + sloppy-focus model, if the mouse is moved + over the root window, the most recently used window still + has the focus. With sloppy-focus, focus is only changed + when the cursor enters a new window, and not when exiting + the current window. In the click-to-focus + policy, the active window is selected by mouse click. The + window may then be raised and appear in front of all other + windows. All keystrokes will now be directed to this + window, even if the cursor is moved to another + window. Different window managers support different focus models. All of them support click-to-focus, and the - majority of them also support other policies. Consult - the documentation for the window manager to determine - which focus models are available. + majority of them also support other policies. Consult the + documentation for the window manager to determine which + focus models are available. @@ -229,8 +227,8 @@ KDE, and GTK+, used by GNOME. As a result, applications will have a different look and feel, - depending upon which widget toolkit was used to create - the application. + depending upon which widget toolkit was used to create the + application. @@ -250,8 +248,8 @@ section install the complete &xorg; distribution. - To build and install &xorg; - from the Ports Collection: + To build and install &xorg; from + the Ports Collection: &prompt.root; cd /usr/ports/x11/xorg &prompt.root; make install clean @@ -312,8 +310,8 @@ dbus_enable="YES" Test the system by moving the mouse and typing text into the windows. If both mouse and keyboard work as expected, - see and - . + see and . If the mouse or keyboard do not work, continue with . @@ -338,9 +336,9 @@ dbus_enable="YES" &xorg; &xorg; - Those with older or unusual equipment may - find it helpful to gather some hardware information before - beginning configuration. + Those with older or unusual equipment may find it helpful to + gather some hardware information before beginning + configuration. @@ -374,16 +372,16 @@ dbus_enable="YES" Screen resolution and refresh rate are determined by the - monitor's horizontal and vertical sync frequencies. Almost - all monitors support electronic autodetection of these values. - A few monitors do not provide these values, and the - specifications must be determined from the printed manual or - manufacturer web site. + monitor's horizontal and vertical sync frequencies. Almost all + monitors support electronic autodetection of these values. A + few monitors do not provide these values, and the specifications + must be determined from the printed manual or manufacturer web + site. The video card chipset is also autodetected, and used to select the proper video driver. It is beneficial for the user - to be aware of which chipset is installed for when - autodetection does not provide the desired result. + to be aware of which chipset is installed for when autodetection + does not provide the desired result. Video card memory determines the maximum resolution and color depth which can be displayed. @@ -455,29 +453,23 @@ dbus_enable="YES" This will generate a file named /root/xorg.conf.new which attempts to - load the proper drivers for the detected hardware. Next, - test that the automatically generated configuration file - works with the graphics hardware by typing: + load the proper drivers for the detected hardware. Next, test + that the automatically generated configuration file works with + the graphics hardware by typing: &prompt.root; Xorg -config xorg.conf.new -retro - If a black and grey grid and an X mouse cursor appear, - the configuration was successful. To exit the test, switch - to the virtual console used to start it by pressing - - Ctrl - Alt - Fn - (F1 for the first virtual - console) and press - - Ctrl - C - . + If a black and grey grid and an X mouse cursor appear, the + configuration was successful. To exit the test, switch to the + virtual console used to start it by pressing Ctrl Alt + Fn + (F1 for the first virtual console) and press + Ctrl + C . - The - + The Ctrl Alt Backspace @@ -526,10 +518,10 @@ dbus_enable="YES" Desktop environments like GNOME, KDE or - Xfce provide graphical tools - to set parameters such as video resolution. If the default - configuration works, skip to - for examples on how to install a desktop environment. + Xfce provide graphical tools to + set parameters such as video resolution. If the default + configuration works, skip to for + examples on how to install a desktop environment. @@ -558,24 +550,24 @@ dbus_enable="YES" fonts are almost completely unintelligible. However, there are several free, high quality Type1 (&postscript;) fonts available which can be readily used with - &xorg;. For instance, the URW - font collection (x11-fonts/urwfonts) - includes high quality versions of standard type1 fonts - (Times Roman, - Helvetica, - Palatino and - others). The Freefonts collection - (x11-fonts/freefonts) includes many more - fonts, but most of them are intended for use in graphics - software such as the Gimp, and are - not complete enough to serve as screen fonts. In addition, + &xorg;. For instance, the URW font + collection (x11-fonts/urwfonts) includes + high quality versions of standard type1 fonts (Times Roman, Helvetica, Palatino and others). The + Freefonts collection (x11-fonts/freefonts) + includes many more fonts, but most of them are intended for + use in graphics software such as the + Gimp, and are not complete enough + to serve as screen fonts. In addition, &xorg; can be configured to use &truetype; fonts with a minimum of effort. For more details on this, see the &man.X.7; manual page or . - To install the above Type1 font collections from the - Ports Collection, run the following commands: + To install the above Type1 font collections from the Ports + Collection, run the following commands: &prompt.root; cd /usr/ports/x11-fonts/urwfonts &prompt.root; make install clean @@ -634,8 +626,8 @@ dbus_enable="YES" format for use by &xorg;. Once the files have been copied into this directory, use ttmkfdir to create a - fonts.dir, so that the X font - renderer knows that these new files have been installed. + fonts.dir, so that the X font renderer + knows that these new files have been installed. ttmkfdir is available from the FreeBSD Ports Collection as x11-fonts/ttmkfdir. @@ -654,12 +646,12 @@ dbus_enable="YES" xorg.conf. Now Gimp, - OpenOffice, and all of the - other X applications should now recognize the installed - &truetype; fonts. Extremely small fonts (as with text in a - high resolution display on a web page) and extremely large - fonts (within &staroffice;) will - look much better now. + OpenOffice, and all of the other X + applications should now recognize the installed &truetype; + fonts. Extremely small fonts (as with text in a high + resolution display on a web page) and extremely large fonts + (within &staroffice;) will look + much better now. @@ -852,13 +844,13 @@ dbus_enable="YES" - The X Display Manager + The X Display Manager - - Seth - Kingsley + + Seth + Kingsley Contributed by @@ -873,7 +865,7 @@ dbus_enable="YES" to connect to and for entering authorization information such as a login and password combination. - This section demonstrates how to configure the X Display + This section demonstrates how to configure the X Display Manager on &os;. Some desktop environments provide their own graphical login manager. Refer to for instructions on how to configure @@ -982,8 +974,8 @@ dbus_enable="YES" If a display that XDM is trying to start hangs, look at this file for error messages. These messages are also written to the - user's ~/.xsession-errors on - a per-session basis. + user's ~/.xsession-errors on a + per-session basis. @@ -1023,13 +1015,13 @@ DisplayManager.requestPort: 0 - Desktop Environments + Desktop Environments - - Valentino - Vaschetto + + Valentino + Vaschetto Contributed by @@ -1040,9 +1032,9 @@ DisplayManager.requestPort: 0This section describes how to install three popular desktop environments on a &os; system. A desktop environment can range from a simple window manager to a complete suite of desktop - applications. Over a hundred desktop environments are - available in the x11-wm category of the - Ports Collection. + applications. Over a hundred desktop environments are available + in the x11-wm category of the Ports + Collection. GNOME @@ -1055,7 +1047,7 @@ DisplayManager.requestPort: 0GNOME on &os; can be found at http://www.FreeBSD.org/gnome. + xlink:href="http://www.FreeBSD.org/gnome">http://www.FreeBSD.org/gnome. That web site contains additional documentation about installing, configuring, and managing GNOME on &os;. @@ -1075,10 +1067,9 @@ DisplayManager.requestPort: 0make install clean For proper operation, GNOME - requires /proc to be - mounted. Add this line to /etc/fstab to - mount this file system automatically during system - startup: + requires /proc to be mounted. Add this + line to /etc/fstab to mount this file + system automatically during system startup: proc /proc procfs rw 0 0 @@ -1095,8 +1086,7 @@ DisplayManager.requestPort: 0It is often desirable to also start all GNOME services. To achieve this, - add a second line to - /etc/rc.conf: + add a second line to /etc/rc.conf: gnome_enable="YES" @@ -1159,9 +1149,9 @@ DisplayManager.requestPort: 0 KDE requires - /proc to be mounted. Add - this line to /etc/fstab to mount this - file system automatically during system startup: + /proc to be mounted. Add this line to + /etc/fstab to mount this file system + automatically during system startup: proc /proc procfs rw 0 0 @@ -1245,50 +1235,50 @@ DisplayManager.requestPort: 0One way to increase the pleasantness of using a desktop computer is by having nice 3D effects. - Installing the Compiz Fusion + Installing the Compiz Fusion package is easy, but configuring it requires a few steps that are not described in the port's documentation. Setting up the &os; nVidia driver - Desktop effects can cause quite a load on the graphics card. - For an an nVidia-based graphics card, the proprietary driver - is required for good performance. Users of other graphics - cards can skip this section and continue with the + Desktop effects can cause quite a load on the graphics + card. For an an nVidia-based graphics card, the proprietary + driver is required for good performance. Users of other + graphics cards can skip this section and continue with the xorg.conf configuration. - - To determine which nVidia driver is needed see the FAQ question - on the subject. - + To determine which nVidia driver is needed see the FAQ question + on the subject. Having determined the correct driver to use for your card, - installation is as simple as installing any other package. + installation is as simple as installing any other + package. For example, to install the latest driver: &prompt.root; pkg install x11/nvidia-driver - The driver will create a kernel module, which needs to be loaded - at system startup. Add the following line to + The driver will create a kernel module, which needs to be + loaded at system startup. Add the following line to /boot/loader.conf: nvidia_load="YES" - To immediately load the kernel module into the - running kernel by issuing a command like - kldload nvidia, however it has been noted that - the some versions of &xorg; will not - function properly if the driver is not loaded at boot time. After - editing /boot/loader.conf, a reboot is - recommended. + To immediately load the kernel module into the running + kernel by issuing a command like kldload + nvidia, however it has been noted that the some + versions of &xorg; will not + function properly if the driver is not loaded at boot time. + After editing /boot/loader.conf, a + reboot is recommended. - With the kernel module loaded, you normally only need to change - a single line in your xorg.conf file to enable - the proprietary driver: + With the kernel module loaded, you normally only need to + change a single line in your xorg.conf + file to enable the proprietary driver: Find the following line in /etc/X11/xorg.conf: @@ -1300,7 +1290,7 @@ DisplayManager.requestPort: 0Driver "nvidia" Start the GUI as usual, and you should be greeted by the - nVidia splash. Everything should work as usual. + nVidia splash. Everything should work as usual. @@ -1310,14 +1300,15 @@ DisplayManager.requestPort: 0/etc/X11/xorg.conf needs to be modified: - Add the following section to enable composite effects: + Add the following section to enable composite + effects: Section "Extensions" Option "Composite" "Enable" EndSection - Locate the Screen section which should look similar - to the one below: + Locate the Screen section which should look + similar to the one below: Section "Screen" Identifier "Screen0" @@ -1325,25 +1316,25 @@ DisplayManager.requestPort: 0 - and add the following two lines (after Monitor will - do): + and add the following two lines (after + Monitor will do): DefaultDepth 24 Option "AddARGBGLXVisuals" "True" Locate the Subsection that refers to the - screen resolution that you wish to use. For example, if you wish to - use 1280x1024, locate the section that follows. If the desired - resolution does not appear in any subsection, you may add the relevant - entry by hand: + screen resolution that you wish to use. For example, if you + wish to use 1280x1024, locate the section that follows. If + the desired resolution does not appear in any subsection, you + may add the relevant entry by hand: SubSection "Display" Viewport 0 0 Modes "1280x1024" EndSubSection - A color depth of 24 bits is needed for desktop composition, - change the above subsection to: + A color depth of 24 bits is needed for desktop + composition, change the above subsection to: SubSection "Display" Viewport 0 0 @@ -1352,8 +1343,8 @@ DisplayManager.requestPort: 0 Finally, confirm that the glx and - extmod modules are loaded in the Module - section: + extmod modules are loaded in the + Module section: Section "Module" Load "extmod" @@ -1364,7 +1355,7 @@ DisplayManager.requestPort: 0x11/nvidia-xconfig by running (as root): - &prompt.root; nvidia-xconfig --add-argb-glx-visuals + &prompt.root; nvidia-xconfig --add-argb-glx-visuals &prompt.root; nvidia-xconfig --composite &prompt.root; nvidia-xconfig --depth=24 @@ -1377,69 +1368,70 @@ DisplayManager.requestPort: 0&prompt.root; pkg install x11-wm/compiz-fusion - When the installation is finished, start your graphic desktop and - at a terminal, enter the following commands (as a normal user): + When the installation is finished, start your graphic + desktop and at a terminal, enter the following commands (as a + normal user): &prompt.user; compiz --replace --sm-disable --ignore-desktop-hints ccp & &prompt.user; emerald --replace & - Your screen will flicker for a few seconds, as your window manager - (e.g. Metacity if you are using - GNOME) is replaced by + Your screen will flicker for a few seconds, as your window + manager (e.g. Metacity if you are + using GNOME) is replaced by Compiz Fusion. Emerald takes care of the window - decorations (i.e. close, minimize, maximize buttons, title bars - and so on). + decorations (i.e. close, minimize, maximize buttons, title + bars and so on). - You may convert this to a trivial script and have it run at - startup automatically (e.g. by adding to Sessions in - a GNOME desktop): + You may convert this to a trivial script and have it run + at startup automatically (e.g. by adding to + Sessions in a GNOME + desktop): #! /bin/sh compiz --replace --sm-disable --ignore-desktop-hints ccp & emerald --replace & Save this in your home directory as, for example, - start-compiz and make it executable: + start-compiz and make it + executable: &prompt.user; chmod +x ~/start-compiz - Then use the GUI to add it to - Startup Programs - (located in System, + Then use the GUI to add it to Startup + Programs (located in + System, Preferences, Sessions on a GNOME desktop). - To actually select all the desired effects and their settings, - execute (again as a normal user) the + To actually select all the desired effects and their + settings, execute (again as a normal user) the Compiz Config Settings Manager: &prompt.user; ccsm - In GNOME, this can also be found in - the System, + In GNOME, this can also be + found in the System, Preferences menu. - If you have selected gconf support during the build, - you will also be able to view these settings using - gconf-editor under apps/compiz. - + If you have selected gconf support during + the build, you will also be able to view these settings using + gconf-editor under + apps/compiz. - Troubleshooting - If the mouse does not work, you will need to first - configure it before proceeding. See - in the &os; install chapter. In recent - Xorg versions, the - InputDevice sections in + If the mouse does not work, you will need to first configure + it before proceeding. See in the &os; + install chapter. In recent Xorg + versions, the InputDevice sections in xorg.conf are ignored in favor of the autodetected devices. To restore the old behavior, add the following line to the ServerLayout or @@ -1493,8 +1485,7 @@ DisplayManager.requestPort: 0&prompt.user; setxkbmap -model pc102 -layout fr - - /usr/local/share/X11/xkb/rules/base.lst + /usr/local/share/X11/xkb/rules/base.lst lists the various keyboard, layouts and options available. @@ -1518,8 +1509,8 @@ DisplayManager.requestPort: 0 - Most monitors support sync frequency autodetection, - making manual entry of these values unnecessary. For the few + Most monitors support sync frequency autodetection, making + manual entry of these values unnecessary. For the few monitors that do not support autodetection, avoid potential damage by only entering values provided by the manufacturer. @@ -1536,10 +1527,10 @@ EndSection xorg.conf - While the xorg.conf.new - configuration file is still open in an editor, select the - default resolution and color depth desired. This is defined - in the "Screen" section: + While the xorg.conf.new configuration + file is still open in an editor, select the default resolution + and color depth desired. This is defined in the + "Screen" section: Section "Screen" Identifier "Screen0" @@ -1602,10 +1593,10 @@ EndSection Configuration with &intel; i810 integrated chipsets - requires the agpgart AGP - programming interface for &xorg; - to drive the card. See the &man.agp.4; driver manual page - for more information. + requires the agpgart AGP programming + interface for &xorg; to drive the + card. See the &man.agp.4; driver manual page for more + information. This will allow configuration of the hardware as any other graphics board. Note on systems without the @@ -1713,48 +1704,53 @@ EndSection should start on your new widescreen monitor. - - Troubleshooting Compiz Fusion - - - - - I have installed - Compiz Fusion, - and after running the commands you mention, my windows are left - without title bars and buttons. What is wrong? - - - - You are probably missing a setting in - /etc/X11/xorg.conf. Review this file - carefully and check especially the DefaultDepth - and AddARGBGLXVisuals directives. - - + + Troubleshooting Compiz Fusion - - - When I run the command to start - Compiz Fusion, the X server - crashes and I am back at the console. What is wrong? - - - - If you check your /var/log/Xorg.0.log - file, you will probably find error messages during the X - startup. The most common would be: + + + + I have installed + Compiz Fusion, and + after running the commands you mention, my windows are + left without title bars and buttons. What is + wrong? + + + + You are probably missing a setting in + /etc/X11/xorg.conf. Review this + file carefully and check especially the + DefaultDepth and + AddARGBGLXVisuals + directives. + + + + + + When I run the command to start + Compiz Fusion, the X + server crashes and I am back at the console. What is + wrong? + + + + If you check your + /var/log/Xorg.0.log file, you + will probably find error messages during the X + startup. The most common would be: - (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X + (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X (EE) NVIDIA(0): log file that the GLX module has been loaded in your X (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If (EE) NVIDIA(0): you continue to encounter problems, Please try (EE) NVIDIA(0): reinstalling the NVIDIA driver. This is usually the case when you upgrade - &xorg;. You will need to reinstall the - x11/nvidia-driver package so - glx is built again. + &xorg;. You will need to + reinstall the x11/nvidia-driver + package so glx is built again.