From 1e99114452f0a372fd16d2e075d13d09f6cee346 Mon Sep 17 00:00:00 2001 From: Chern Lee Date: Fri, 20 Jul 2001 21:09:39 +0000 Subject: [PATCH] Markup: Placed applications in Placed commands in Placed hostnames in Placed usernames in Placed some terms in / Places some commands in man entities Changed some to tags Placed files in Spelling: linux -> Linux pc -> PC reckognized -> recognized initialise -> initialize behaviour -> behavior mountpath -> mount path (to spell check nicely although mountpoint would probably be more correct) Reviewed by: murray --- .../books/handbook/linuxemu/chapter.sgml | 223 +++--- .../books/handbook/x11/chapter.sgml | 673 ++++++++++-------- 2 files changed, 509 insertions(+), 387 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml index aca2a11be0..8cd484d370 100644 --- a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml @@ -1,7 +1,7 @@ @@ -37,11 +37,16 @@ In a nutshell, the compatibility allows FreeBSD users to run about 90% of all Linux applications without modification. This - includes applications such as Star Office, the Linux version of - Netscape, Adobe Acrobat, RealPlayer 5 and 7, VMWare, Oracle, - WordPerfect, Doom, Quake, and more. It is also reported that in - some situations, Linux binaries perform better on FreeBSD than they - do under Linux. + includes applications such as Star Office, + the Linux version of Netscape, + Adobe Acrobat, + RealPlayer + 5 and 7, VMWare, + Oracle, + WordPerfect, Doom, + Quake, and more. It is also reported + that in some situations, Linux binaries perform better on FreeBSD + than they do under Linux. Linux /proc filesystem @@ -293,7 +298,7 @@ multi on The order here specifies that /etc/hosts is searched first and DNS is searched second. When /compat/linux/etc/host.conf is not - installed, linux applications find FreeBSD's + installed, Linux applications find FreeBSD's /etc/host.conf and complain about the incompatible FreeBSD syntax. You should remove bind if you have not configured a name server @@ -301,10 +306,11 @@ multi on - + Installing Mathematica - Updated for Mathematica version 4.X by &a.murray + Updated for Mathematica + version 4.X by &a.murray and merged with work by Bojan Bistrovic bojanb@physics.odu.edu. @@ -313,13 +319,16 @@ multi on This document describes the process of installing the Linux - version of Mathematica 4.X onto a FreeBSD system. + version of Mathematica 4.X onto + a FreeBSD system. - The Linux version of Mathematica runs perfectly under FreeBSD + The Linux version of Mathematica + runs perfectly under FreeBSD however the binaries shipped by Wolfram need to be branded so that FreeBSD knows to use the Linux ABI to execute them. - The Linux version of Mathematica or Mathematica for Students can + The Linux version of Mathematica + or Mathematica for Students can be ordered directly from Wolfram at http://www.wolfram.com/. @@ -327,7 +336,8 @@ multi on Branding the Linux binaries The Linux binaries are located in the Unix - directory of the Mathematica CDROM distributed by Wolfram. You + directory of the Mathematica CDROM + distributed by Wolfram. You need to copy this directory tree to your local hard drive so that you can brand the Linux binaries with &man.brandelf.1; before running the installer: @@ -354,7 +364,8 @@ multi on Obtaining your Mathematica Password - Before you can run Mathematica you will have to obtain a + Before you can run Mathematica + you will have to obtain a password from Wolfram that corresponds to your machine ID. @@ -363,7 +374,8 @@ multi on Once you have installed the Linux compatibility runtime - libraries and unpacked Mathematica you can obtain the + libraries and unpacked Mathematica + you can obtain the machine ID by running the program mathinfo in the Install directory. This machine ID is based solely on the MAC address of your first @@ -377,18 +389,21 @@ disco.example.com 7115-70839-20412 you will give them the machine ID and they will respond with a corresponding password consisting of groups of numbers. You can then enter this information when you attempt to - run Mathematica for the first time exactly as you would for any - other Mathematica platform. + run Mathematica for the first time + exactly as you would for any other + Mathematica platform. Running the Mathematica front end over a network - Mathematica uses some special fonts to display characters not - present in any of the standard font sets (integrals, sums, greek + Mathematica uses some special + fonts to display characters not + present in any of the standard font sets (integrals, sums, Greek letters, etc.). The X protocol requires these fonts to be install locally. This means you will have to copy - these fonts from the CDROM or from a host with Mathematica + these fonts from the CDROM or from a host with + Mathematica installed to your local machine. These fonts are normally stored in /cdrom/Unix/Files/SystemFiles/Fonts on the CDROM, or @@ -622,8 +637,8 @@ export PATH root.sh. root.sh is written in the orainst directory. Apply the following patch to root.sh, to have it use to proper location of - chown or alternatively run the script under a Linux native - shell. + chown or alternatively run the script under a + Linux native shell. *** orainst/root.sh.orig Tue Oct 6 21:57:33 1998 --- orainst/root.sh Mon Dec 28 15:58:53 1998 @@ -652,7 +667,8 @@ export PATH Patching genclntsh - The script genclntsh is used to create a single shared client + The script genclntsh is used to create + a single shared client library. It is used when building the demos. Apply the following patch to comment out the definition of PATH: @@ -680,7 +696,8 @@ export PATH Running Oracle When you have followed the instructions, you should be able to run - Oracle as if it was run on Linux itself. + Oracle as if it was run on Linux + itself. @@ -700,18 +717,24 @@ export PATH Preface - This document describes a possible way of installing a SAP - R/3 4.6B IDES-System with Oracle 8.0.5 for Linux onto a - FreeBSD 4.3 machine, including the installation of FreeBSD 4.3 - stable and Oracle 8.0.5. + This document describes a possible way of installing a + SAP R/3 4.6B IDES-System + with Oracle 8.0.5 + for Linux onto a FreeBSD 4.3 machine, including the installation + of FreeBSD 4.3-STABLE and + Oracle 8.0.5. Even though this document tries to describe all important steps in a greater detail, it is not intended as a replacement - for the Oracle and SAP R/3 installation guides. + for the Oracle and + SAP R/3 installation guides. - Please see the documentation that comes with the SAP R/3 - Linux edition for SAP- and Oracle-specific questions, as well - as resources from Oracle and SAP OSS. + Please see the documentation that comes with the + SAP R/3 + Linux edition for SAP- and + Oracle-specific questions, as well + as resources from Oracle and + SAP OSS. @@ -948,10 +971,10 @@ export PATH - I had to configure and initialise the two logical drives + I had to configure and initialize the two logical drives with the Mylex software beforehand. It is located on the board itself and can be started during the boot phase of the - pc. + PC. Please note that this disk layout differs slightly from the SAP recommendations, as SAP suggests mounting the @@ -967,7 +990,8 @@ export PATH For FreeBSD 4.3 stable onwards, it is quite easy to get the latest stable sources. With the older versions of FreeBSD, I had my own script located in /etc/cvsup. Setting - up cvsup for FreeBSD 4.3 is quite easy. As user + up CVSup for FreeBSD 4.3 is quite + easy. As user root do the following: &prompt.root; cp /etc/defaults/make.conf /etc/make.conf @@ -989,8 +1013,8 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile /usr/share/examples/cvsup should be fine. If you don't want to load all the docfiles, leave the corresponding DOCSUPFILE-entry - inactive. Starting cvsup to get the latest stable-sources - is then very easy: + inactive. Starting cvsup + to get the latest stable-sources is then very easy: &prompt.root; cd /usr/src &prompt.root; make update @@ -1010,8 +1034,8 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile If this goes through, one can then continue creating and configuring the new kernel. Usually this is where to customize the kernel configuration file. As the computer is - named troubadix, the natural name for the config file also - is troubadix: + named troubadix, the natural name for the + config file also is troubadix: &prompt.root; cd /usr/src/sys/i386/conf &prompt.root; cp GENERIC TROUBADIX @@ -1055,7 +1079,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile Installing Linux base-system - First the linux base-system needs to be installed (as root): + First the Linux base-system needs to be installed (as root): &prompt.root; cd /usr/ports/emulators/linux_base &prompt.root; make package @@ -1064,7 +1088,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile Installing Linux development - Next, the linux development is needed: + Next, the Linux development is needed: &prompt.root; cd /usr/ports/devel/linux_devtools &prompt.root; make package @@ -1160,14 +1184,16 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile Creating users and directories - SAP R/3 needs two users and three groups. The usernames - depend on the SAP system id (SID) which consists of three - letters. Some of these SIDs are reserved by SAP (for example - SAP and NIX. For - a complete list please see the SAP documentation). For the - IDES installation I used IDS. We have - therefore the following groups (group ids might differ, - these are just the values I used with my installation): + SAP R/3 needs two users and + three groups. The usernames depend on the + SAP system id (SID) which consists + of three letters. Some of these SIDs are reserved + by SAP (for example + SAP and NIX. For a + complete list please see the SAP documentation). For the IDES + installation I used IDS. We have + therefore the following groups (group ids might differ, these + are just the values I used with my installation): @@ -1298,8 +1324,8 @@ Shell: /bin/sh &prompt.root; mkdir saparch sapreorg &prompt.root; exit - In the third step we create directories as user idsadm - (<sid>adm): + In the third step we create directories as user + idsadm (<sid>adm): &prompt.root; su - idsadm &prompt.root; cd /usr/sap @@ -1401,10 +1427,13 @@ options SEMUME=100 #number of UNDO keys /oracle/IDS/sapreorg/<cd-name> - where <cd-name> was one of KERNEL, RDBMS, EXPORT1, - EXPORT2, EXPORT3, EXPORT4, EXPORT5 and EXPORT6. All the - filenames should be in capital letters, otherwise use the -g - option for mounting. So use the following commands: + where <cd-name> was one of KERNEL, + RDBMS, EXPORT1, + EXPORT2, EXPORT3, + EXPORT4, EXPORT5 and + EXPORT6. All the + filenames should be in capital letters, otherwise use the -g + option for mounting. So use the following commands: &prompt.root; mount_cd9660 -g /dev/cd0a /mnt &prompt.root; cp -R /mnt/* /oracle/IDS/sapreorg/<cd-name> @@ -1618,7 +1647,7 @@ options SEMUME=100 #number of UNDO keys then the SAP-Installer can't find the CD needed (identified by the LABEL.ASC-File on CD) and would then ask you to insert / mount the CD and confirm or enter - the mountpath. + the mount path. The CENTRDB.R3S might not be error-free. In my case, it requested EXPORT4 again (but @@ -1627,7 +1656,7 @@ options SEMUME=100 #number of UNDO keys values. Don't get irritated. Apart from some problems mentioned below, everything - should go straight throught up to the point where the Oracle + should go straight through up to the point where the Oracle database software needs to be installed. @@ -1691,7 +1720,8 @@ options SEMUME=100 #number of UNDO keys . Due to time constrains I decided to use the binaries - from an Oracle 8.0.5 PreProduction release, after the first + from an Oracle 8.0.5 PreProduction + release, after the first attempt at getting the version from the RDBMS-CD working, failed, and finding / accessing the correct RPMs was a nightmare at that time. @@ -1716,8 +1746,10 @@ options SEMUME=100 #number of UNDO keys Continue with SAP R/3 installation - First check the environment settings of users idsamd - (<sid>adm) and oraids (ora<sid>). They should now + First check the environment settings of users + idsamd + (<sid>adm) and + oraids (ora<sid>). They should now both have the files .profile , .login and .cshrc which are all using hostname. In case the @@ -1777,14 +1809,15 @@ options SEMUME=100 #number of UNDO keys - At this point I had a few problems with dipgntab. + At this point I had a few problems with + dipgntab. Listener - Start the Oracle-Listener as user oraids (ora<sid>) as - follows: + Start the Oracle-Listener as user + oraids (ora<sid>) as follows: umask 0; lsnrctl start @@ -1842,8 +1875,8 @@ LICENSE KEY = <license key, 24 chars> Configure Transport System, Profile, Operation Modes, etc. - Within client 000, user different from ddic and sap*, do - at least the following: + Within client 000, user different from ddic + and sap*, do at least the following: @@ -1900,7 +1933,7 @@ tape_address_rew = /dev/sa0 which does hardware compression. archive_function This defines the - default behaviour for saving Oracle archive logs: New logfiles + default behavior for saving Oracle archive logs: New logfiles are saved to tape, already saved logfiles are saved again and are then deleted. This prevents lots of trouble if one needs to recover the database, and one of the archive-tapes has gone @@ -1910,12 +1943,13 @@ tape_address_rew = /dev/sa0 sets blocksize to 5120 Bytes. For DLT-Tapes, HP recommends at least 32K blocksize, so I used --block-size=128 for 64K. --format=newc is needed I have inode numbers greater than - 65535. The last option --quiet is needed as otherwise brbackup - complains as soon as cpio outputs the numbers of blocks - saved. + 65535. The last option --quiet is needed as otherwise + brbackup + complains as soon as cpio outputs the + numbers of blocks saved. cpio_in_flags Flags needed for - loading data back from tape. Format is reckognized + loading data back from tape. Format is recognized automagically. tape_size This usually gives the raw @@ -1926,7 +1960,7 @@ tape_address_rew = /dev/sa0 actual value. tape_address The non-rewindable - device to be used with cpio. + device to be used with cpio. tape_address_rew The rewindable device to be used with cpio. @@ -1979,16 +2013,18 @@ STATUS=OK (had status ERROR) TEXTENV_INVALID during R3SETUP, RFC or SAPGUI start If this error is encountered, the correct locale is - missing. SAP note 0171356 lists the necessary RPMs that - need be installed (eg saplocales-1.0-3, - saposcheck-1.0-1 for RedHat 6.1). In - case you ignored all the related errors and set the - corresponding status from ERROR to OK (in CENTRDB.R3S) every - time R3SETUP complained and just restarted R3SETUP, the - SAP-System will not be properly configured and you will then - not be able to connect to the system with a sapgui, even - though the system can be started. Trying to connect with the - old Linux sapgui gave the following messages: + missing. SAP note 0171356 lists the necessary RPMs that need + be installed (eg saplocales-1.0-3, + saposcheck-1.0-1 for RedHat 6.1). In case + you ignored all the related errors and set the corresponding + status from ERROR to OK (in CENTRDB.R3S) every time R3SETUP + complained and just restarted R3SETUP, the SAP-System will not + be properly configured and you will then not be able to + connect to the system with a + sapgui, even though the system + can be started. Trying to connect with the old Linux + sapgui gave the following + messages: Sat May 5 14:23:14 2001 *** ERROR => no valid userarea given [trgmsgo. 0401] @@ -1999,7 +2035,7 @@ Sat May 5 14:23:22 2001 *** ERROR => no socket operation allowed [trxio.c 3363] Speicherzugriffsfehler - This behaviour is due to SAP R/3 being unable to + This behavior is due to SAP R/3 being unable to correctly assign a locale and also not being properly configured itself (missing entries in some database tables). To be able to connect to SAP, add the following @@ -2034,7 +2070,8 @@ rscp/TCP0B =TCP0B [DIPGNTAB_IND_IND] during R3SETUP - In general, see SAP note 0130581 (R3SETUP step DIPGNTAB + In general, see SAP note 0130581 (R3SETUP step + DIPGNTAB terminates). During this specific installation, for some reasons the installation process was not using the proper SAP system name "IDS", but the empty string "" instead. This @@ -2064,27 +2101,29 @@ drwxrwxr-x 2 idsadm sapsys 512 May 5 13:00 tmp drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans I also found SAP notes (0029227 and 0008401) describing - this behaviour. + this behavior. [RFCRSWBOINI_IND_IND] during R3SETUP Set STATUS of the offending step from ERROR to OK (file - CENTRDB.R3S) and restart R3SETUP. After - installation, you have to execute the report RSWBOINS from - transaction SE38. See SAP note 0162266 for additional - information about phase RFCRSWBOINI and RFCRADDBDIF. + CENTRDB.R3S) and restart R3SETUP. After + installation, you have to execute the report + RSWBOINS from transaction SE38. See SAP + note 0162266 for additional information about phase + RFCRSWBOINI and + RFCRADDBDIF. [RFCRADDBDIF_IND_IND] during R3SETUP Set STATUS of the offending step from ERROR to OK (file - CENTRDB.R3S) and restart R3SETUP. After - installation, you have to execute the report RADDBDIF from - transaction SE38. See SAP note 0162266 for further - information. + CENTRDB.R3S) and restart R3SETUP. After + installation, you have to execute the report + RADDBDIF from transaction SE38. + See SAP note 0162266 for further information. diff --git a/en_US.ISO8859-1/books/handbook/x11/chapter.sgml b/en_US.ISO8859-1/books/handbook/x11/chapter.sgml index 5040b09af4..b27000549f 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,8 +12,8 @@ url="http://www.wccdrom.com/titles/freebsd/bsdcomp_bkx.phtml">The Complete FreeBSD, and remains copyright of him. Modifications for the handbook made by &a.jim;. The section on - fonts in XFree86 was contributed by &a.murray; and the section on - XDM was contributed by &a.sethk;. + fonts in XFree86 was contributed by &a.murray; + and the section on XDM was contributed by &a.sethk;. Synopsis @@ -26,11 +26,13 @@ Overview - FreeBSD comes with XFree86, a port of X11R6 that supports - several versions of Intel-based Unix. This chapter describes how - to set up your XFree86 server. It is based on material supplied - with the FreeBSD release, specifically the files README.FreeBSD - and README.Config in the directory + FreeBSD comes with XFree86, a + port of X11R6 that supports several versions of Intel-based Unix. + This chapter describes how to set up your + XFree86 server. It is based on + material supplied with the FreeBSD release, specifically the files + README.FreeBSD and + README.Config in the directory /usr/X11R6/lib/X11/doc. If you find any discrepancy, the material in those files will be more up-to-date than this description. In addition, the file @@ -62,7 +64,8 @@ Installing XFree86 - The easiest way to install XFree86 is with the sysinstall + The easiest way to install XFree86 + is with the &man.sysinstall.8; program, either when you are installing the system, or later by starting the program /stand/sysinstall. In the rest of this chapter, we will look at what makes up the @@ -72,7 +75,8 @@ The XFree86 Distribution - XFree86 is distributed as a bewildering number of archives. + XFree86 is distributed as a bewildering + number of archives. In the following section, we will take a look at what you should install. Do not worry too much, though; if you cannot decide what to pick and you have 200MB of disk space free, it's safe to @@ -359,8 +363,9 @@ to install ports of X software. - XFree86 also includes a number of optional parts, such as - documentation, and setup programs. + XFree86 also includes a number + of optional parts, such as documentation, and setup + programs. @@ -420,11 +425,12 @@ - XF86Setup is a graphical mode setup - program for XFree86, and you may prefer it to the standard setup - program xf86config. You do not need any - special archives for xf86config; it is - included in Xbin.tgz. + XF86Setup is a graphical mode setup + program for XFree86, and you may + prefer it to the standard setup program + xf86config. You do not need any special + archives for xf86config; it is included in + Xbin.tgz. The first time you install, you will need Xcfg.tgz to create your initial configuration @@ -432,7 +438,7 @@ configuration files. There are also additional fonts that are available with - XFree86: + XFree86: @@ -510,8 +516,8 @@ Installing XFree86 Manually - If you do not use sysinstall to install X, you need to perform - a number of steps: + If you do not use sysinstall + to install X, you need to perform a number of steps: @@ -579,7 +585,7 @@ Password: &prompt.root; tar xzf X$i.tgz &prompt.root; done - If you are using csh, enter: + If you are using csh, enter: &prompt.root; mkdir -p /usr/X11R6 &prompt.root; cd /usr/X11R6 @@ -622,7 +628,8 @@ Password: Next, check that the directory /usr/X11R6/bin is in the default path for - sh in /etc/profile and for csh in + sh in /etc/profile and for + csh in /etc/csh.login, and add it if it is not. It is best to do this with an editor, but if you want to take a shortcut, you can enter: @@ -637,8 +644,8 @@ Password: /usr/X11R6/bin in their shell's PATH variable. - Next, invoke ldconfig to put the shared libraries in - ld.so's cache: + Next, invoke ldconfig to put the + shared libraries in ld.so's cache: &prompt.root; ldconfig -m /usr/X11R6/lib @@ -656,7 +663,7 @@ Password: Assigning a virtual terminal to X Next, make sure you have a spare virtual console which is - running a getty. First check how many virtual consoles you + running a &man.getty.8;. First check how many virtual consoles you have: &prompt.root; dmesg | grep virtual @@ -664,7 +671,7 @@ sc0: VGA color <16 virtual consoles, flags=0x0> Then check /etc/ttys to make sure there is at least one virtual terminal (ttyvxx device) which - does not have a getty enabled. Look for the keyword + does not have a &man.getty.8; enabled. Look for the keyword off: &prompt.root; grep ttyv /etc/ttys @@ -674,9 +681,10 @@ ttyv2 "/usr/libexec/getty Pc" cons25 on secure ttyv3 "/usr/libexec/getty Pc" cons25 off secure In this case, /dev/ttyv3 is - available, if your kernel has least 4 VTs. If not, either - disable a getty in /etc/ttys by - changing on to off, or build another kernel with more virtual + available, if your kernel has least 4 + vts. If not, either disable a + &man.getty.8; in /etc/ttys by changing on + to off, or build another kernel with more virtual terminals. @@ -737,7 +745,8 @@ ttyv3 "/usr/libexec/getty Pc" cons25 off secure Occasionally SuperProbe can crash your system. Make sure you are not doing anything important when - you run it. Running SuperProbe looks like this: + you run it. Running SuperProbe looks like + this: &prompt.root; SuperProbe (warnings and acknowledgments omitted) @@ -779,7 +788,8 @@ SuperProbe: Cannot open video hardware, so I personally prefer xf86config. - You can also use sysinstall, but this does not change + You can also use sysinstall, + but this does not change much; sysinstall just starts xf86config for you, and it is easier to start it directly. In this section, we will use an example to @@ -806,7 +816,8 @@ SuperProbe: Cannot open video The XF86Config file usually resides in /usr/X11R6/lib/X11 or /etc. A sample - XF86Config file is supplied with XFree86; + XF86Config file is supplied with + XFree86; it is configured for a standard VGA card and monitor with 640x480 resolution. This program will ask for a pathname when it is ready to write the file. @@ -933,7 +944,7 @@ Enter a number to choose the keymap. two critical parameters are the vertical refresh rate, which is the rate at which the whole screen is refreshed, and most importantly the horizontal sync rate, which is the rate - at which scanlines are displayed. + at which scan-lines are displayed. The valid range for horizontal sync and vertical sync should be documented in the manual of your monitor. If in @@ -1139,7 +1150,8 @@ the SVGA server. Please answer the following question with either 'y' or 'n'. Do you want me to set the symbolic link? y - All the programs that start X (xinit, startx, and xdm) + All the programs that start X (xinit, + startx, and xdm) start a program /usr/X11R6/bin/X. This symbolic link makes /usr/X11R6/bin/X point to your X server. If you don't have a link, you will @@ -1326,7 +1338,8 @@ For further configuration, refer to /usr/X11R6/lib/X11/doc/README.Config.Introduction This chapter will introduce the steps necessary to install - and configure the XFree86 X Windows System under FreeBSD. + 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. @@ -1339,9 +1352,10 @@ For further configuration, refer to /usr/X11R6/lib/X11/doc/README.Config. Before You Start - Before the user is to start configuration of XFree86-4, - the the following information will need to be known about the - target system: + Before the user is to start configuration of + XFree86-4, the the following + information will need to be known about the target + system: Monitor specifications @@ -1353,18 +1367,18 @@ For further configuration, refer to /usr/X11R6/lib/X11/doc/README.Config.vertical scan rate The specifications for the target system's monitor are - used by XFree86 to determine the resolution and refresh rate - to run at. These specifications can usually be obtained from - the documentation that came with the target system's monitor - or from the manufacturer's website. There are two ranges of - numbers that are needed, the horizontal scan rate and the - vertical synchronization rate. + used by XFree86 to determine the + resolution and refresh rate to run at. These specifications can + usually be obtained from the documentation that came with the + target system's monitor or from the manufacturer's website. + There are two ranges of numbers that are needed, the horizontal + scan rate and the vertical synchronization rate. The video adapter's chipset defines what driver module - XFree86 uses to talk to the graphics hardware. With most - chipsets, this can be automatically determined, but it is still - useful to know in case the automatic detection doesn't work - correctly. + XFree86 uses to talk to the graphics + hardware. With most chipsets, this can be automatically + determined, but it is still useful to know in case the automatic + detection doesn't work correctly. Video memory on the graphic adapter determines the resolution and color depth the target system can run at. This @@ -1376,13 +1390,14 @@ For further configuration, refer to /usr/X11R6/lib/X11/doc/README.Config. 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 + 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 + files/ sub-directory before the port is built. @@ -1390,21 +1405,26 @@ For further configuration, refer to /usr/X11R6/lib/X11/doc/README.Config. Configuring XFree86 4.X - Configuration of XFree86 4.1 is a several step process. - The first step is to build an initial configuration file with - the configure option to XFree86. As the super user, simply run: + 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 + XFree86. As the super user, simply + run: &prompt.root; XFree86 -configure - This will generate a skeleton XFree86 configuration file - in the current working directory called - XF86Config.new. The XFree86 program will - attempt to probe the graphics hardware on the system and will - write a configuration file to load the proper drivers for the - detected hardware on the target system. + This will generate a skeleton + XFree86 configuration file in the + current working directory called + XF86Config.new. The + XFree86 program will attempt to probe + the graphics hardware on the system and will write a + configuration file to load the proper drivers for the detected + hardware on the target system. The next step is to test the currently existing - configuration to verify that XFree86 can work with the graphics + configuration to verify that XFree86 + can work with the graphics hardware on the target system. To preform this task, the user needs to run: @@ -1494,7 +1514,7 @@ EndSection &prompt.root; cp XF86Config.new /etc/X11/XF86Config Once the configuration file has been placed in a common - location, XFree86 can then be used through &man.xdm.1;. In + location, XFree86 can then be used through &man.xdm.1;. In order to use startx 1 the user will have to install the X11/wrapper port. @@ -1510,19 +1530,20 @@ EndSection Intel i810 graphic chipset Configuration with Intel i810 integrated chipsets - requires the agpgart AGP programming interface for XFree86 to - be able to drive the card. To enable the agpgart programming + requires the agpgart AGP programming interface for + XFree86 to be able to drive the + card. To enable the agpgart programming interface, the agp.ko kernel loadable module needs to be loaded into the kernel with &man.kldload.8;. This can be done automatically with the &man.loader.8;. Simply add this line to /boot/loader.conf to have the loader load - agp.ko at boot time: + agp.ko at boot time: agp_load="YES" Next, a device node needs to be created for the - programming interface. To create the agp device node, run + programming interface. To create the AGP device node, run &man.MAKEDEV.8; in the /dev directory as such: @@ -1583,11 +1604,12 @@ EndSection This will work but will be lost when you log out from this session, unless you add it to your startup file - (~/.xinitrc for a normal startx session, + (~/.xinitrc for a normal + startx session, or ~/.xsession when logging in through a graphical login manager like XDM). A third way is to use the new - XftConfig file: see the + XftConfig file: see the section on anti-aliasing, later. @@ -1599,7 +1621,7 @@ EndSection for rendering TrueType fonts. There are two different modules that can enable this functionality. The "freetype" module is used in this example because it is more consistent with the other font - rendering backends. To enable the freetype module just add the + rendering back-ends. To enable the freetype module just add the following line to the module section of your /etc/X11/XF86Config file. @@ -1632,24 +1654,31 @@ EndSection linkend="type1">Type1 fonts, that is, use &prompt.user; xset fp+ /usr/X11R6/lib/X11/fonts/TrueType &prompt.user; xset fp rehash - or add a FontPath line to the XF86Config file. - - That's it. Now Netscape, Gimp, StarOffice, and all of your - other X applications should now recognize your 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. + or add a line to the + XF86Config file. + + That's it. Now Netscape, + Gimp, + StarOffice, and all of your other X + applications should now recognize your 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. Anti-Aliasing your fonts - Starting with version 4.0.2, XFree86 supports anti-aliased + Starting with version 4.0.2, XFree86 + supports anti-aliased fonts. Currently, most software has not been updated to take advantage of this new functionality. However, Qt (the toolkit - for the KDE desktop) does; so if you are running XFree86 4.0.2 - (or higher), Qt 2.3 (or higher) and KDE, all your KDE/Qt - applications can be made to use anti-aliased fonts. + for the KDE desktop) does; so if you + are running XFree86 4.0.2 + (or higher), Qt 2.3 (or higher) and KDE, + all your KDE/Qt applications can be made to use anti-aliased + fonts. To configure anti-aliasing, you need to create (or edit, if it already exists) the file @@ -1685,7 +1714,8 @@ edit You may also find that the spacing for some monospaced fonts gets messed up when you turn on anti-aliasing. This seems to - be an issue with KDE, in particular. One possible fix for this + be an issue with KDE, in particular. + One possible fix for this is to force the spacing for such fonts to be 100: add the following lines: @@ -1697,10 +1727,11 @@ match any family == "console" edit family =+ "mono"; match any family == "mono" edit spacing = 100; - Supposing you want to use the Lucidux fonts whenever monospaced - fonts are required (these look nice, and don't seem to suffer - from the spacing problem), you could replace that last line - with these: + Supposing you want to use the + Lucidux fonts whenever + monospaced fonts are required (these look nice, and don't seem + to suffer from the spacing problem), you could replace that last + line with these: match any family == "mono" edit family += "LuciduxMono"; match any family == "Lucidux Mono" edit family += "LuciduxMono"; @@ -1717,13 +1748,16 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono";That's all; anti-aliasing should be enabled the next time you start the X server. However, note that your programs must know how to take advantage of it. At the present time, the toolkit - Qt does, so the entire KDE environment can use anti-aliased fonts - (see on KDE for + Qt does, so the entire KDE environment + can use anti-aliased fonts + (see on + KDE for details); there are patches for gtk+ to do the same, so if compiled against such a patched gtk+, the GNOME environment and Mozilla can also use anti-aliased fonts. - Anti-aliasing is still new to FreeBSD and XFree86; + Anti-aliasing is still new to FreeBSD and + XFree86; configuring it should get easier with time, and it will soon be supported by many more applications. @@ -1733,42 +1767,46 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono";The X Display Manager Overview - 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 + 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 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 - connected by a network. XDM provides a graphical interface for - choosing which display server to connect to, and entering - authorization information such as a login and password - combination. - - You may think of XDM as providing the same functionality to - the user as the &man.getty.8; utility (see for details). That is, it performs system - logins to the display being connected to and then runs a session - manager on behalf of the user (usually an X window manager). XDM - then waits for this program to exit, signaling that the user is - done and should be logged out of the display. At this point, XDM - can display the login and display chooser screens for the next - user to login. + connected by a network. XDM provides + a graphical interface for choosing which display server to + connect to, and entering authorization information such as a + login and password combination. + + You may think of XDM as + providing the same functionality to the user as the + &man.getty.8; utility (see for + details). That is, it performs system logins to the display + being connected to and then runs a session manager on behalf of + the user (usually an X window + manager). XDM then waits for this + program to exit, signaling that the user is done and should be + logged out of the display. At this point, + XDM can display the login and display + chooser screens for the next user to login. Using XDM - 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 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 adding an entry to /etc/ttys. - For more information about the format and usage of this file, - see . There is a line in the - default /etc/ttys file for running the xdm - daemon on a virtual terminal: + + 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 + 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 + adding an entry to /etc/ttys. For more + information about the format and usage of this file, see . There is a line in the default + /etc/ttys file for running the + XDM daemon on a virtual terminal: ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure @@ -1777,16 +1815,19 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono";on and then restart &man.init.8; using the directions in . The first field, the name of the terminal this program will manage, is - ttyv8. This means that XDM will start running - on the 9th virtual terminal. + ttyv8. This means that XDM + will start running on the 9th virtual terminal. Configuring XDM - The XDM configuration directory is located in - /usr/X11R6/lib/X11/xdm. In this directory - you will see several files used to change the behavior and - appearance of XDM. Typically you will find these files: + + The XDM configuration directory + is located in /usr/X11R6/lib/X11/xdm. In + this directory you will see several files used to change the + behavior and appearance of + XDM. Typically you will find these + files: @@ -1843,27 +1884,29 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono"; Also in this directory are a few scripts and programs used - to setup the desktop when XDM is running. In the next few - sections I will briefly describe the purpose of each of these - files. The exact syntax and usage of all of these files is - described in &man.xdm.1; + to setup the desktop when XDM is + running. In the next few sections I will briefly describe the + purpose of each of these files. The exact syntax and usage of + all of these files is described in &man.xdm.1; The default configuration is a simple rectangular login window with the hostname of the machine displayed at the top in a large font and Login: and Password: prompts below. This is a good starting point if you are planning to design your own look and feel for - the XDM screens. + the XDM screens. Xaccess - The protocol for connecting to XDM controlled displays is - called the X Display Manager Connection Protocol (XDMCP). This - file is basically just a ruleset for controlling XDMCP - connections from remote machines. By default, it allows any - client to connect, but you will see this will not matter - because the default xdm-config file does not listen for remote - connections. + + The protocol for connecting to + XDM controlled displays is called + the X Display Manager Connection Protocol (XDMCP). This file + is basically just a ruleset for controlling XDMCP connections + from remote machines. By default, it allows any client to + connect, but you will see this will not matter because the + default xdm-config file does not listen + for remote connections. @@ -1871,7 +1914,7 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono";This is an application-defaults file for the display chooser and the login screens. This is where you can customize the appearance of the login program. The format is identical - to the app-defaults file described in the XFree86 + to the app-defaults file described in the XFree86 documentation. @@ -1883,10 +1926,11 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono"; Xsession - This is the default session script for XDM to run after a - user has logged in. Normally each user will have a customized - session script in ~/.xsessionrc that - overrides this script. + This is the default session script for + XDM to run after a user has logged + in. Normally each user will have a customized session script + in ~/.xsessionrc that overrides this + script. @@ -1909,11 +1953,13 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono"; xdm-errors - This file contains the output of the X servers that XDM is - trying to run. If a display that XDM is trying to start hangs + This file contains the output of the X servers that + XDM is trying to run. If a display + that XDM is trying to start hangs for some reason, this is a good place to look for error messages. These messages are also written to the user's - ~/.xsession-errors file on a per-session basis + ~/.xsession-errors file on a per-session + basis @@ -1923,29 +1969,32 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono";xdm-config file: + get XDM to listen for connections + first comment out a line in the xdm-config + file: ! SECURITY: do not listen for XDMCP or Chooser requests ! Comment out this line if you want to manage X terminals with xdm 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 put more strict - access controls in place. Look at the example entries in - Xaccess file, and refer to the &man.xdm.1; - manual page. + and then restart XDM. Remember that + comments in app-defaults files begin with a ! + character, not a #. 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. 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. + 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. @@ -1958,8 +2007,9 @@ DisplayManager.requestPort: 0 This section describes the different desktop environments available for X-Windows 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. + manager, to a complete suite of desktop applications such as + KDE or GNOME. + GNOME @@ -1967,48 +2017,54 @@ DisplayManager.requestPort: 0 About GNOME - GNOME is a user-friendly desktop environment that - enables users to easily use and configure their computers. - GNOME includes a panel (for starting applications and displaying - status), a desktop (where data and applications can be placed), - a set of standard desktop tools and applications, and a set of - conventions that make it easy for applications to cooperate and - be consistent with each other. Users of other operating systems - or environments should feel right at home using the powerful - graphics-driven environment that GNOME provides. + GNOME is a user-friendly + desktop environment that enables users to easily use and + configure their computers. GNOME + includes a panel (for starting applications and displaying + status), a desktop (where data and applications can be + placed), a set of standard desktop tools and applications, and + a set of conventions that make it easy for applications to + cooperate and be consistent with each other. Users of other + operating systems or environments should feel right at home + using the powerful graphics-driven environment that + GNOME provides. Installing GNOME - To install GNOME from the network, simply type: + To install GNOME from the network, + simply type: &prompt.root; pkg_add -r gnome - If you would rather build GNOME from source, then use - the ports tree: + If you would rather build + GNOME from source, then use the + ports tree: &prompt.root; cd /usr/ports/x11/gnome &prompt.root; make install clean - Once GNOME is installed, we must have the X server start - GNOME instead of a default window mananger. If you have - already customized your .xinitrc file - then you should simply replace the line that starts your - current window manager with one that starts - /usr/X11R6/bin/gnome-wm instead. If - you haven't added anything special to your configuration - file, then it is enough to simply type: + Once GNOME is installed, we + must have the X server start GNOME + instead of a default window manager. If you have already + customized your .xinitrc file then you + should simply replace the line that starts your current window + manager with one that starts + /usr/X11R6/bin/gnome-wm instead. If you + haven't added anything special to your configuration file, + then it is enough to simply type: &prompt.root; echo "/usr/X11R6/bin/gnome-wm" > ~/.xinitrc - That's it. Type 'startx' and you will be in the - GNOME desktop environment. - Note: if you're running a display manager like xdm, - this will not work. Instead, you should create an - executable .xsession file with the same - command in it. To do this, edit your file (if you already - have one) and replace the existing wm command with - /usr/X11R6/bin/gnome-wm; or - else, + That's it. Type startx and you will be in the + GNOME desktop environment. + + If you're running a display manager like + XDM, this will not work. Instead, + you should create an executable .xsession + file with the same command in it. To do this, edit your file + (if you already have one) and replace the existing + window manager command with + /usr/X11R6/bin/gnome-wm; or else, &prompt.root; echo "#!/bin/sh" > ~/.xsession &prompt.root; echo "/usr/X11R6/bin/gnome-wm" >> ~/.xsession @@ -2018,7 +2074,7 @@ DisplayManager.requestPort: 0 allow choosing the window manager at login time; the section on KDE2 details explains how to do this for kdm, the - display manager of KDE. + display manager of KDE. @@ -2027,30 +2083,40 @@ DisplayManager.requestPort: 0 About KDE2 - KDE is an easy to use contemporary desktop environment. - Some of the things that KDE brings to the user are: + KDE is an easy to use + contemporary desktop environment. Some of the things that + KDE brings to the user are: + A beautiful contemporary desktop A desktop exhibiting complete network transparency An integrated help system allowing for convenient, - consistent access to help on the use of the KDE desktop and its - applications - Consistent look and feel of all KDE applications + consistent access to help on the use of the + KDE desktop and its + applications + Consistent look and feel of all + KDE applications Standardized menu and toolbars, keybindings, color-schemes, etc. - Internationalization: KDE is available in more than 40 languages + Internationalization: KDE + is available in more than 40 languages Centralized consisted dialog driven desktop configuration - A great number of useful KDE applications + A great number of useful + KDE applications - KDE has an office application suite based on KDE's - KParts technology consisting 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 a solid competitor to other - existing web browsers on Unix systems. More information on - KDE can be found on the KDE + KDE has an office application + suite based on KDE's + KParts technology consisting + 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 + a solid competitor to other existing web browsers on Unix + systems. More information on KDE + can be found on the KDE website + Installing KDE2 @@ -2058,22 +2124,23 @@ DisplayManager.requestPort: 0 At the time of writing, a package for kde2 doesn't exist yet. No problem! The ports tree hides all the complexity of building a package from source. To install - KDE2, do this : + KDE2, do this : &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. + Internet, configure and compile KDE2, + install the applications, and then clean up after itself. Now you're going to have to tell the X server to launch - KDE2 instead of a default window manager. Do this by typing - this: + KDE2 instead of a default window manager. + Do this by typing this: &prompt.root; echo "/usr/X11R6/bin/startkde" > ~/.xinitrc - Now, whenever you go into X-Windows, KDE2 will be your + Now, whenever you go into X-Windows, + KDE2 will be your desktop. (Note: this will not work if you're logging in via a display manager like xdm. In that case you have two options: create an @@ -2083,71 +2150,81 @@ DisplayManager.requestPort: 0 command instead of the gnome-wm 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.) + to do this for kdm, + KDE's display manager.) More details on KDE2 - Now that KDE2 is installed on your system, you'll find - that you can learn a lot from its help pages, or just by - pointing and clicking at various menus. Windows or Mac - users will feel quite at home. - - The best reference for KDE is 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. + Now that KDE2 is installed on + your system, you'll find that you can learn a lot from its + help pages, or just by pointing and clicking at various menus. + Windows or Mac users will feel quite at home. + + The best reference for KDE is + 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. The KDE display manager If you're an administrator on a multi-user system, you - may like to have a graphical login screen to welcome users. - You can use xdm, as - described earlier. However, KDE includes an alternative, - kdm, which is designed to look more attractive and include - more login-time options. In particular, users can easily - choose (via a menu) which desktop environment (KDE2, GNOME, - or something else) to run after logging on. If you're slightly - adventurous and you want this added flexibility and visual - appeal, read on. + may like to have a graphical login screen to welcome users. + You can use xdm, as described + earlier. However, KDE includes an + alternative, KDM, which is designed + to look more attractive and include more login-time options. + In particular, users can easily choose (via a menu) which + desktop environment (KDE2, + GNOME, or something else) to run + after logging on. If you're slightly adventurous and you want + this added flexibility and visual appeal, read on. - To begin with, run the KDE2 control panel, - kcontrol, as root. Note: it is - generally considered unsafe to run your entire X environment - as root. Instead, run your window manager as a normal user, - open a terminal window (such as xterm - or KDE's konsole, become root with - su (you need to be in the "wheel" + To begin with, run the KDE2 + control panel, kcontrol, as + root. Note: it is generally considered + unsafe to run your entire X environment as + root. Instead, run your window manager + as a normal user, open a terminal window (such as + xterm or KDE's + konsole, become root + with su (you need to be in the + wheel 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'll see various - configurable options, which the KDE manual will 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 - commands, so you can write "KDE" and "GNOME" rather than - "startkde" or "gnome-wm".) Include a label - "failsafe". + "Login manager". On the right you'll see various configurable + options, which the KDE manual will + 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 + commands, so you can write KDE and + GNOME rather than + startkde or gnome-wm.) + Include a label failsafe. Play with the other menus as you like (those are mainly cosmetic and self-explanatory). When you're done, click on "Apply" at the bottom, and quit the control center. - To make sure kdm understands what your above labels - (KDE, GNOME etc) mean, you need to edit some more files: the - same ones used by xdm. 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 default): + To make sure kdm understands + what your above labels (KDE, + GNOME etc) mean, you need to edit + some more files: the same ones used by xdm. 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 + default): + case $# in 1) case $1 in @@ -2174,17 +2251,18 @@ esac esac esac - To make sure your KDE choice of a login-time desktop - background is also honored, you will need to add the - following line to - /usr/X11R6/lib/X11/xdm/Xsetup_0: + To make sure your KDE choice + of a login-time desktop background is also honored, you will + need to add the following line to + /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 + 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. That's it. Your next login screen should have a pretty face and lots of menus. @@ -2197,19 +2275,20 @@ esac 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 toolkit used by KDE) supports this - extension. Configuring this is described in on antialiasing X11 fonts. - So if you're running up-to-date software, - anti-aliasing is possible on your KDE2 desktop. Just go to - your KDE2 menu, go to Preferences -> Look and Feel -> Style, - and click on the checkbox "Use Anti-Aliasing for Fonts and - Icons". That's all. If you're running a Qt application - which is not part of KDE, you may need to set the - environment variable QT_XFT to true before starting your - program. + Starting with version 4.0.2, + XFree86 supports anti-aliasing via + its "RENDER" extension, and starting with version 2.3, Qt (the + toolkit used by KDE) supports this + extension. Configuring this is described in on antialiasing X11 fonts. So if you're + running up-to-date software, anti-aliasing is possible on your + KDE2 desktop. Just go to your KDE2 + menu, go to Preferences -> Look and Feel -> Style, and click + on the checkbox "Use Anti-Aliasing for Fonts and Icons". + That's all. If you're running a Qt application which is not + part of KDE, you may need to set + the environment variable QT_XFT to true before starting your + program. @@ -2218,35 +2297,39 @@ esac XFCE About XFCE - XFCE is 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 - configure. Visually, it looks very much like CDE, found on - commercial Unix systems. - Some of XFCE's features are: + + XFCE is 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 + configure. Visually, it looks very much like + CDE, found on commercial Unix + systems. Some of XFCE's features + are: A simple, easy-to-handle desktop Fully configurable via mouse, with drag and drop, etc - Main panel similar to CDE, with menus, applets and + Main panel similar to CDE, with menus, applets and app launchers Integrated window manager, file manager, - sound manager, GNOME compliance module, and other things - Themable (since it uses gtk+) + sound manager, GNOME compliance module, and other things + Themeable (since it uses gtk+) Fast, light and efficient: ideal for - older/slower machines or machiens with memory limitations + older/slower machines or machines with memory limitations - More information on - XFCE can be found on the XFCE - website. + More information on XFCE + can be found on the XFCE + website. Installing XFCE - A binary package for xfce exists (at the time of - writing). To install, simply do this: + A binary package for xfce + exists (at the time of writing). To install, simply do + this: &prompt.root; pkg_add -r xfce @@ -2261,12 +2344,12 @@ esac the build areas cleaned up afterwards. Now you want to tell the X server to launch - XFCE the next time you start X. Simply type - this: + XFCE the next time you start + X. Simply type this: &prompt.root; echo "/usr/X11R6/bin/startxfce" > ~/.xinitrc - The next time you start X, XFCE will be your + The next time you start X, XFCE will be your desktop. (Note, as before: if you're logging in via a display manager like xdm, you should either create an