From ff88de96a43ed5822fd1aefe7e4a0258a480134b Mon Sep 17 00:00:00 2001 From: Murray Stokely Date: Mon, 3 Sep 2001 06:58:19 +0000 Subject: [PATCH] First pass in turning this collection of topics into a more coherent chapter. Add missing words to form complete sentences, rephrase difficult to understand paragraphs, add additional markup tags such as , , etc.. --- .../books/handbook/x11/chapter.sgml | 270 +++++++++--------- 1 file changed, 140 insertions(+), 130 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/x11/chapter.sgml b/en_US.ISO8859-1/books/handbook/x11/chapter.sgml index 3ff6bd501e..dfaf7e320c 100644 --- a/en_US.ISO8859-1/books/handbook/x11/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/x11/chapter.sgml @@ -1,7 +1,7 @@ @@ -12,7 +12,7 @@ FreeBSD uses XFree86 to provide users with a powerful graphical user interface. XFree86 is a open-source - implementation of the X Window System. The following chapter + implementation of the X Window System. This chapter will cover installation and configuration of XFree86 on your FreeBSD system. For more information on X11 and to see whether your video card is supported, check the Installing XFree86 - XFree86 is available as a port - and as a package, making it easy to install. You can also - download the binaries directly from the XFree86 organization and - install them by hand, following the instructions provided by the - XFree86 group. - - Your only decision is which version of XFree86 to run. - XFree86 3.X is the maintenance branch of XFree86 development. - It is very stable, and it supports a huge number of graphics - cards. However, no new development is happening there. XFree86 - 4.X is a redesign of XFree86. As well as introducing many new - features (including much better support for fonts and - anti-aliasing), XFree86 4.X supports slightly fewer graphics - cards. - - If your card is supported we recommend you run 4.X. If it - is not then run 3.X. + Before installing XFree86 you must decide which version to + run. XFree86 3.X is a maintenance + branch of XFree86 development. It is very stable, and it + supports a huge number of graphics cards. However, no new + development is happening there. XFree86 + 4.X is a complete redesign of the system with many + new features such as better support for fonts and + anti-aliasing. Unfortunately this new architecture requires + that the video drivers be rewritten, and some of the older + cards that were supported in 3.X are not yet supported in 4.X. + + If your card is supported, then by all means run 4.X. The + FreeBSD setup program offers users the opportunity to install + and configure XFree86 3.3.6 during installation (covered in + ). If you would like to run + XFree86 4.X, then you should wait + until after the base FreeBSD system is installed and then + install XFree86. For example, to build and install + XFree86 4.X from the ports collection + : + + &prompt.root; cd /usr/ports/x11/XFree86-4 +&prompt.root; make all install clean + + Alternatively, XFree86 4.X can be + installed from a binary package with the + pkg_add tool or directly from the FreeBSD + binaries provided on the XFree86 web site. The rest of this chapter will explain how to configure - XFree86, and suggest various programs for X that you might want - to try. + XFree86 for your hardware, and how to setup a productive + desktop environment. @@ -80,26 +92,15 @@ XFree86 Configuration - - Introduction - This chapter will introduce the steps necessary to install - and configure the XFree86 - X Windows System under FreeBSD. - Once the server is installed and configured properly. The user - can read to setup their desktop - environment. - - XFree86 4.X - XFree86 - - + XFree86 4.X + XFree86 Before You Start Before the user is to start configuration of - XFree86-4, the the following + XFree86 4.X, the the following information will need to be known about the target system: @@ -133,27 +134,12 @@ - - Installing XFree86 4.X Software - - XFree86 4 can be installed - using the FreeBSD ports system or using &man.pkg.add.1;. If the - user is building XFree86-4 from - source and has USA_RESIDENT set in - /etc/make.conf, the user may first have to - fetch Wraphelp.c if XDM-AUTHORIZATION-1 - support is desired. This file is to be placed in the port's - files/ sub-directory before the port is - built. - - - Configuring XFree86 4.X Configuration of XFree86 4.X is - a several step process. The first step is to build an initial - configuration file with the configure option to + a multi-step process. The first step is to build an initial + configuration file with the option to XFree86. As the super user, simply run: @@ -168,7 +154,7 @@ configuration file to load the proper drivers for the detected hardware on the target system. - The next step is to test the currently existing + The next step is to test the existing configuration to verify that XFree86 can work with the graphics hardware on the target system. To preform this task, the user @@ -177,9 +163,13 @@ &prompt.root; XFree86 -xf86config XF86Config.new If the user is presented with a black and grey grid and an - X mouse cursor, then the configuration was successful. To exit - the test, just press Ctrl, Alt - and Backspace simultaneously. + X mouse cursor, then the configuration was successful. To + exit the test, just press + Ctrl + Alt + Backspace + simultaneously. XFree86 4 Tuning @@ -373,7 +363,7 @@ EndSection display the windows you will not get confused. There is an interesting side-effect to this design. There is - nothing in the forces the client and server machines to be running + nothing in the protocol that forces the client and server machines to be running the same operating system, or even to be running on the same type of computer. It is perfectly feasible to run an X server on Microsoft Windows or Apple's MacOS, and there are various free and commercial @@ -421,7 +411,7 @@ EndSection window managers, and many more, are available in the x11-wm category of the Ports Collection. - In addition, the KDE and GNOME desktop environments both have + In addition, the KDE and GNOME desktop environments both have their own window managers which integrate tightly with the desktop, although both of them allow you to replace the default window manager with your own choice. @@ -539,9 +529,9 @@ EndSection project. In this respect we are beginning to see a convergence in look-and-feel on the Unix desktop, which certainly makes things easier for the novice user. However, the sudden rise in popularity of - theming, where window managers make it possible to - dramatically personally your desktop and alter the look and feel of - the widgets risks confusing the issue once more. + theming, alows users to confuse the issue once + more by dramatically altering the look and feel of desktop + widgets. @@ -633,7 +623,7 @@ EndSection /usr/ports/x11-servers/Xfstt You should now make a directory for your TrueType fonts - (e.g. /usr/X11R6/lib/X11/fonts/TrueType) + (For example, /usr/X11R6/lib/X11/fonts/TrueType) and copy all of your TrueType fonts into this directory. Keep in mind that you cannot take TrueType fonts directly from a Macintosh; they must be in Unix/DOS/Windows format for use by @@ -641,9 +631,10 @@ EndSection files into this directory you need to use ttmkfdir to create a fonts.dir file so that the X font renderer - knows that you have installed these new files. There is a FreeBSD - port for x11-fonts/ttmkfdir in - /usr/ports/x11-fonts/ttmkfdir. + knows that you have installed these new + files. ttmkfdir is available from the FreeBSD + Ports Collection as x11-fonts/ttmkfdir. + &prompt.root; cd /usr/X11R6/lib/X11/fonts/TrueType &prompt.root; ttmkfdir > fonts.dir @@ -685,8 +676,8 @@ EndSection describes only the simplest possibilities. First, you need to tell the X server about the fonts which you - want anti-aliased. To do that, for each font directory you have - a line, which looks like this: + want anti-aliased. For each font directory, add a line similar + to this: dir "/usr/X11R6/lib/X11/Type1" @@ -777,8 +768,8 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono";The X Display Manager (XDM) is an optional part of the X Window System that is used for login session management. This is useful for several types of - situations, including minimal X Terminals (see - ), desktops, and large network display + situations, including minimal X Terminals, + desktops, and large network display servers. Since the X Window System is network and protocol independent, there are a wide variety of possible configurations for running X clients and servers on different machines @@ -805,7 +796,7 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono";The XDM daemon program is located in /usr/X11R6/bin/xdm. You can run - this program at any time as root and it will start managing the + this program at any time as root and it will start managing the X display on the local machine. If you want XDM to run in the background every time the machine boots up, a convenient way to do this is by @@ -836,7 +827,7 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono";XDM. Typically you will find these files: - + @@ -868,7 +859,8 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono"; Xsetup_* - + Script to launch applications before the login + interface. @@ -945,7 +937,7 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono";These files contain scripts that will be run automatically before displaying the chooser or login interfaces. There is a script for each display being used, named - Xsetup_followed by the local display + Xsetup_ followed by the local display number (for instance Xsetup_0). Typically these scripts will run one or two programs in the background such as xconsole. @@ -986,7 +978,7 @@ DisplayManager.requestPort: 0 and then restart XDM. Remember that comments in app-defaults files begin with a ! - character, not a #. After this, you may need to + character, not the usual #. After this, you may need to put more strict access controls in place. Look at the example entries in Xaccess file, and refer to the &man.xdm.1; manual page. @@ -994,14 +986,15 @@ DisplayManager.requestPort: 0 Replacements for XDM + Several replacements for the default - XDM program exist. One of them, - KDM (bundled with - KDE) is described in a later section. Apart from various - visual improvements and cosmetic frills, it can be easily - configured to let users choose their window manager of choice - at the time they log in. + XDM program exist. One of them, + KDM (bundled with + KDE) is described later in this + chapter. KDM offers many visual + improvements and cosmetic frills, as well as the + functionality to allow users to choose their window manager + of choice at login time. @@ -1022,7 +1015,7 @@ DisplayManager.requestPort: 0 Desktop Environments This section describes the different desktop environments - available for X-Windows on FreeBSD. For our purposes a "desktop + available for X on FreeBSD. For our purposes a "desktop environment" will mean anything ranging from a simple window manager, to a complete suite of desktop applications such as KDE or GNOME. @@ -1049,8 +1042,18 @@ DisplayManager.requestPort: 0 Installing GNOME - To install GNOME from the network, - simply type: + + The easiest way to install + GNOME is through the + Desktop Configuration menu during the FreeBSD + installation process as described in Chapter 2. If for some + reason you didn't install a desktop environment at that + time, then you can easily install one from the package or + ports collections. + + To install the GNOME package + from the network, simply type: + &prompt.root; pkg_add -r gnome If you would rather build @@ -1128,7 +1131,7 @@ DisplayManager.requestPort: 0 of a spread-sheet, a presentation application, an organizer, a news client and more. KDE is also comes with a web browser called - Konqeuror, which represents already + Konqeuror, which represents a solid competitor to other existing web browsers on Unix systems. More information on KDE can be found on the KDE @@ -1138,37 +1141,46 @@ DisplayManager.requestPort: 0 Installing KDE2 - At the time of writing, a package for kde2 does not - exist yet. No problem! The ports tree hides all the - complexity of building a package from source. To install - KDE2, do this : + Just like with GNOME or any + other desktop environment, the easiest way to install + KDE is through the Desktop + Configuration menu during the FreeBSD installation + process as described in Chapter 2. If for some reason you + didn't install a desktop environment at that time, then you + can easily install one from the package or ports + collections. + + To install the KDE2 package + from the network, simply type: + + &prompt.root; pkg_add -r kde2 + + If you would rather build + KDE from source, then use the + ports tree: &prompt.root; cd /usr/ports/x11/kde2 &prompt.root; make install clean - This command will fetch all the necessary files from the - Internet, configure and compile KDE2, - install the applications, and then clean up after itself. - - Now you are going to have to tell the X server to launch - KDE2 instead of a default window manager. - Do this by typing this: + After you've installed KDE2, + you must tell the X server to launch this application + instead of the default window manager. This is accomplished + by editing the .xinitrc file in your + home directory : &prompt.root; echo "/usr/X11R6/bin/startkde" > ~/.xinitrc - Now, whenever you go into X-Windows, + Now, whenever invoke X-Windows with startx, KDE2 will be your - desktop. (Note: this will not work if you are logging in via - a display manager like xdm. In that - case you have two options: create an - .xsession file as described in the - section on GNOME, but - with the /usr/X11R6/bin/startkde - command instead of the gnome-session - command; or, configure your display manager to allow - choosing a desktop at login time. Below it is explained how - to do this for kdm, - KDE's display manager.) + desktop. + + If you are using a display manager such as + xdm, then configuration is + slightly different. You must edit the + .xsession file instead. Instructions + for kdm are described later in + this chapter. + @@ -1183,9 +1195,9 @@ DisplayManager.requestPort: 0 the on-line documentation. KDE comes with its own web browser, Konqueror, dozens of useful - applications, and extensive documentation. This section only - discusses somewhat technical things which are difficult to - learn just by random exploration. + applications, and extensive documentation. The remainder of + this section discusses the technical items that are + difficult to learn by random exploration. The KDE display manager @@ -1216,13 +1228,13 @@ DisplayManager.requestPort: 0 group in /etc/group for this), and then type kcontrol. - Click on the icon on the left marked "System", then on - "Login manager". On the right you will see various configurable + Click on the icon on the left marked System, then on + Login manager. On the right you will see various configurable options, which the KDE manual will - explain in greater detail. Click on "sessions" on the right. + explain in greater detail. Click on sessions on the right. Depending on what window managers or desktop environments you - have currently installed, you can type their names in "New - type" and add them. (These are just labels so far, not + have currently installed, you can type their names in New + type and add them. (These are just labels so far, not commands, so you can write KDE and GNOME rather than startkde or gnome-session.) @@ -1230,7 +1242,7 @@ DisplayManager.requestPort: 0 Play with the other menus as you like (those are mainly cosmetic and self-explanatory). When you are done, click on - "Apply" at the bottom, and quit the control center. + Apply at the bottom, and quit the control center. To make sure kdm understands what your above labels (KDE, @@ -1242,7 +1254,7 @@ DisplayManager.requestPort: 0 configuration files. Please see the KDE 2.2 documentation for details. - In your terminal window, as root, + In your terminal window, as root, edit the file /usr/X11R6/lib/X11/xdm/Xsession. You will come across a section in the middle looking like this (by @@ -1280,12 +1292,13 @@ esac /usr/X11R6/lib/X11/xdm/Xsetup_0: /usr/X11R6/bin/kdmdesktop - Now, you need only to make sure - kdm is started at the next bootup. - To learn how to do this, read the section on xdm, and do the same thing replacing - references to the xdm program by - kdm. + Now, you need only to make sure that + kdm is listed in + /etc/ttys to be started at the next bootup. + To do this, simply follow the instructions from the previous + section on xdm and replace + references to the xdm program with + kdm. That's it. Your next login screen should have a pretty face and lots of menus. @@ -1294,10 +1307,6 @@ esac Anti-aliased Fonts - Tired of blocky staircase edges to your fonts under X11? - Tired of unreadable text in web browsers? Well, no - more. - Starting with version 4.0.2, XFree86 supports anti-aliasing via its "RENDER" extension, and starting with version 2.3, Qt (the @@ -1321,7 +1330,8 @@ esac About XFCE - XFCE is based on the gtk+ + XFCE is a desktop environment + based on the gtk+ toolkit used by GNOME, but is much more lightweight and meant for those who want a simple, efficient desktop which is nevertheless easy to use and @@ -1360,7 +1370,7 @@ esac The ports tree comes to the rescue again: &prompt.root; cd /usr/ports/x11-wm/xfce - &prompt.root; make install clean +&prompt.root; make install clean All necessary source packages (including dependencies) will be automagically fetched, built and installed, and