diff --git a/zh_TW.Big5/books/handbook/x11/chapter.sgml b/zh_TW.Big5/books/handbook/x11/chapter.sgml index 610842dcfa..2c5bf126f0 100644 --- a/zh_TW.Big5/books/handbook/x11/chapter.sgml +++ b/zh_TW.Big5/books/handbook/x11/chapter.sgml @@ -2,7 +2,7 @@ The FreeBSD Documentation Project $FreeBSD$ - Original revision: 1.168 + Original revision: 1.184 --> @@ -26,21 +26,25 @@ 概述 FreeBSD 使用 X11 來提供使用者相當好用的 GUI 介面。 - X11 是 X Window 系統(包括 &xorg; - 以及 &xfree86; 的開放原碼實作。 - &os; 從 &os; 4.11-RELEASE 到 &os; 5.2.1-RELEASE - 可在預設的安裝程式內安裝 &xfree86; + X11 是 X Window 系統，包括 &xorg; + 以及 &xfree86; 實作的自由軟體版本 + (以及其他未在本章有介紹的軟體)。 &os; 一直到 &os; 5.2.1-RELEASE + 都仍可在預設的安裝程式內去裝 &xfree86; (由 The &xfree86; Project, Inc 發行的 X11 server)。 而 &os; 5.3-RELEASE 起，預設的 X11 改為 &xorg;(由 X.Org 基金會所開發的 - X11 server)。 + X11 server，並採用與 &os; 相當類似的 license)。 此外，當然也有商業 + X servers 的 &os; 版。 - 本章主要是介紹 X11 軟體(&xorg;) - 的安裝與設定。 + 本章主要是介紹 X11 (主要著重於 &xorg; + &xorg.version; 版部分)的安裝與設定。 若欲瞭解 + &xfree86; 的詳細資料(早期的 &os; 內， + &xfree86; 乃是預設的 X11 套件)，請參閱舊版的 + &os; Handbook，網址為 + 。 - 欲知 X11 有支援的顯示方面硬體的話，請參閱 &xorg; 或 &xfree86; 的網站。 + 欲知 X11 對於顯示方面硬體的支援情況，請參閱 &xorg; 網站。 讀完這章，您將了解： @@ -73,14 +77,6 @@ 知道如何運用 ports、packages 來安裝軟體。 () - - - 本章會介紹 &xorg; 以及 - &xfree86; 的 X11 server 安裝、設定。 - 大致而言，它們的設定檔、相關指令、語法會有些不同。 - 所以遇到這種不同情況時，我們會標註 &xorg; - 以及 &xfree86; 的不同處。 - @@ -139,11 +135,6 @@ 換句話說，也可以在 µsoft.windows; 或蘋果電腦(Apple)的 &macos; 上跑 X server，而且可以透過許多免費或商業軟體完成這些安裝、設定。 - - 自 &os; 5.3-RELEASE 起，&os; 所裝的 X server 則是 - &xorg;， - 它是採以相當類似 FreeBSD license 的授權方式，並且可自由使用。 - 當然也有商業 X servers 的 FreeBSD 版。 @@ -287,20 +278,15 @@ 安裝 X11 - &xorg; or - &xfree86; may be installed on &os;. - Beginning with &os; 5.3-RELEASE, - &xorg; is the default X11 - implementation for &os;. &xorg; is - the X server of the open source X Window System implementation released by the X.Org - Foundation. &xorg; is based on the code of - &xfree86 4.4RC2 and X11R6.6. - The X.Org Foundation released X11R6.7 in April 2004 and - X11R6.8.2 in February 2005, this latter is the version - currently available in the &os; Ports Collection. + &xorg; 是 &os; 預設的 X11 實作。 + &xorg; 是由 X.Org 基金會所發行之開放源碼軟體 + X Window 系統實作的 X server。 &xorg; + 乃是以 &xfree86 4.4RC2 以及 X11R6.6 + 為基礎所產生的。 目前 &os; Ports Collection 內的 + &xorg; 版本為 &xorg.version;。 - To build and install &xorg; from the - Ports Collection: + 從 Ports Collection 來安裝 &xorg; + 的安裝方式： &prompt.root; cd /usr/ports/x11/xorg &prompt.root; make install clean @@ -311,12 +297,6 @@ available. - To build and install &xfree86; - from the Ports Collection: - - &prompt.root; cd /usr/ports/x11/XFree86-4 -&prompt.root; make install clean - Alternatively, X11 can be installed directly from packages. Binary packages to use with &man.pkg.add.1; tool are also available for @@ -330,11 +310,6 @@ &prompt.root; pkg_add -r xorg - The &xfree86; 4.X package can be - installed by typing: - - &prompt.root; pkg_add -r XFree86 - The examples above will install the complete X11 distribution including the servers, clients, fonts etc. Separate packages and ports of X11 @@ -344,47 +319,6 @@ The rest of this chapter will explain how to configure X11, and how to set up a productive desktop environment. - - - Moving from <application>&xfree86;</application> to - <application>&xorg;</application> - - As with any port, you should check the - /usr/ports/UPDATING file for changes. - Included in this file are instructions for converting your - system from &xfree86; to - &xorg;. - - Use CVSup to update your ports - tree prior to attempting any conversion. You will also need - to install sysutils/portupgrade prior to - converting your X11 installation. - - In your /etc/make.conf you will need - to add the variable X_WINDOW_SYSTEM=xorg. - This ensures that your system knows which X11 is being used. - The older XFREE86_VERSION variable has been - deprecated and has been replaced with the - X_WINDOW_SYSTEM variable. - - Then, use the following commands: - - &prompt.root; pkg_delete -f /var/db/pkg/imake-4* /var/db/pkg/XFree86-* -&prompt.root; cd /usr/ports/x11/xorg -&prompt.root; make install clean -&prompt.root; pkgdb -F - - The &man.pkgdb.1; command is part of the - portupgrade software and will - update various package dependencies. - - - To build &xorg; in its - entirety, be sure to have at least 4 GB of free space - available. - - @@ -401,8 +335,6 @@ 設定 X11 - &xfree86; 4.X - &xfree86; &xorg; X11 @@ -439,7 +371,6 @@ resolution and color depth which the system can run at. This is important to know so the user knows the limitations of the system. - @@ -453,19 +384,12 @@ &prompt.root; Xorg -configure - In the case of &xfree86; - type: - - &prompt.root; XFree86 -configure - This will generate an X11 configuration skeleton file in the /root directory called xorg.conf.new (whether you &man.su.1; or do a direct login affects the inherited supervisor - $HOME directory variable). - For &xfree86;, this configuration - file is called XF86Config.new. The + $HOME directory variable). The X11 program will attempt to probe the graphics hardware on the system and write a configuration file to load the proper drivers for the detected @@ -479,10 +403,6 @@ &prompt.root; Xorg -config xorg.conf.new - &xfree86; users will type: - - &prompt.root; XFree86 -xf86config XF86Config.new - If a black and grey grid and an X mouse cursor appear, the configuration was successful. To exit the test, just press @@ -497,7 +417,7 @@ X11 tuning - Next, tune the xorg.conf.new (or XF86Config.new if you are running &xfree86;) + Next, tune the xorg.conf.new configuration file to taste. Open the file in a text editor such as &man.emacs.1; or &man.ee.1;. First, add the frequencies for the target system's monitor. These are usually @@ -534,11 +454,8 @@ EndSection xorg.conf - - XF86Config - - While the xorg.conf.new (or XF86Config.new) + 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: @@ -558,7 +475,7 @@ EndSection The DefaultDepth keyword describes the color depth to run at by default. This can be overridden with the command line switch to - &man.Xorg.1; (or &man.XFree86.1;). + &man.Xorg.1;. The Modes keyword describes the resolution to run at for the given color depth. Note that only VESA standard modes are supported as defined by @@ -576,48 +493,34 @@ EndSection troubleshooting process are the X11 log files, which contain information on each device that the X11 server attaches to. &xorg; log file names are in the format - of /var/log/Xorg.0.log - (&xfree86; log file names follow the - format of XFree86.0.log). The exact name + of /var/log/Xorg.0.log. The exact name of the log can vary from Xorg.0.log to Xorg.8.log and so forth. If all is well, the configuration file needs to be installed in a common location where - &man.Xorg.1; (or &man.XFree86.1;) - can find it. + &man.Xorg.1; can find it. This is typically /etc/X11/xorg.conf or - /usr/X11R6/etc/X11/xorg.conf (for - &xfree86; it is called - /etc/X11/XF86Config or - /usr/X11R6/etc/X11/XF86Config). + /usr/local/etc/X11/xorg.conf. &prompt.root; cp xorg.conf.new /etc/X11/xorg.conf - For &xfree86;: - - &prompt.root; cp XF86Config.new /etc/X11/XF86Config - The X11 configuration process is now - complete. In order to start - &xfree86; 4.X with &man.startx.1;, - install the x11/wrapper port. - &xorg; already includes the wrapper - code and does not require the installation of the wrapper port. + complete. &xorg; 目前可透過 &man.startx.1; + 來啟動之。 The X11 server may also be started with the use of &man.xdm.1;. There is also a graphical configuration tool, - &man.xorgcfg.1; (&man.xf86cfg.1; for &xfree86;), that comes with the + &man.xorgcfg.1;, which comes with the X11 distribution. It allows you to interactively define your configuration by choosing the appropriate drivers and settings. This program can be invoked from the console, by typing the command xorgcfg -textmode. For more details, - refer to the &man.xorgcfg.1; and &man.xf86cfg.1; manual pages. + refer to the &man.xorgcfg.1; manual pages. - Alternatively, there is also a tool called &man.xorgconfig.1; - (&man.xf86config.1; for &xfree86;), - this program is a console utility that is less user friendly, + Alternatively, there is also a tool called &man.xorgconfig.1;. + This program is a console utility that is less user friendly, but it may work in situations where the other tools do not. @@ -634,36 +537,7 @@ EndSection Configuration with &intel; i810 integrated chipsets requires the agpgart AGP programming interface for X11 - to drive the card. The &man.agp.4; driver is in the - GENERIC kernel since releases - 4.8-RELEASE and 5.0-RELEASE. On prior releases, you will - have to add the following line: - - device agp - - in your kernel configuration file and rebuild a new - kernel. Instead, you may want to load - the agp.ko kernel module - automatically with the &man.loader.8; at boot time. - For that, simply add this line to - /boot/loader.conf: - - agp_load="YES" - - Next, if you are running FreeBSD 4.X or earlier, a - device node needs to be created for the - programming interface. To create the AGP device node, run - &man.MAKEDEV.8; in the /dev - directory: - - &prompt.root; cd /dev -&prompt.root; sh MAKEDEV agpgart - - - FreeBSD 5.X or later will use &man.devfs.5; to allocate - device nodes transparently, therefore the - &man.MAKEDEV.8; step is not required. - + to drive the card. 詳情請參閱 &man.agp.4; 說明。 This will allow configuration of the hardware as any other graphics board. Note on systems without the &man.agp.4; @@ -671,13 +545,6 @@ EndSection with &man.kldload.8; will not work. This driver has to be in the kernel at boot time through being compiled in or using /boot/loader.conf. - - If you are using &xfree86; 4.1.0 (or - later) and messages about unresolved symbols like - fbPictureInit appear, try adding the - following line after Driver "i810" in the - X11 configuration file: - Option "NoDDC" @@ -686,7 +553,8 @@ EndSection widescreen flatpanel configuration 本節假設各位已經有些微進階設定的功力。 - 如果試著使用上述設定工具會有問題的話，請多利用相關 log 檔(會記錄相關訊息)以便找出解法。 + 如果試著使用上述設定工具會有問題的話，請多利用相關 log 檔 + (會記錄相關訊息)以便找出解法。 找尋解法過程中，可能會需要用到文字編輯器作為輔助。 目前的寬螢幕 (WSXGA, WSXGA+, WUXGA, WXGA, WXGA+ 等) @@ -733,13 +601,13 @@ EndSection (II) MGA(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1089 v_border: 0 (II) MGA(0): Ranges: V min: 48 V max: 85 Hz, H min: 30 H max: 94 kHz, PixClock max 170 MHz - 這些訊息被稱為 EDID 訊息。可以藉由這些資料，搭配下列的正確順序來產生 - ModeLine 設定： + 這些訊息被稱為 EDID 訊息。 可以藉由這些資料， + 搭配下列的正確順序來產生 ModeLine 設定： ModeLine <name> <clock> <4 horiz. timings> <4 vert. timings> - 所以這個案例 Section "Monitor" 的 ModeLine - 就會是像下面這樣： + 所以這個案例 Section "Monitor" 的 + ModeLine 就會是像下面這樣： Section "Monitor" Identifier "Monitor1" @@ -796,18 +664,15 @@ EndSection And likewise with the freefont or other collections. To have the X server detect these fonts, add an appropriate line to the - X server configuration file in /etc/X11/ - (xorg.conf for - &xorg; and - XF86Config for - &xfree86;), which reads: + X server configuration file (/etc/X11/xorg.conf), + which reads: - FontPath "/usr/X11R6/lib/X11/fonts/URW/" + FontPath "/usr/local/lib/X11/fonts/URW/" Alternatively, at the command line in the X session run: - &prompt.user; xset fp+ /usr/X11R6/lib/X11/fonts/URW + &prompt.user; xset fp+ /usr/local/lib/X11/fonts/URW &prompt.user; xset fp rehash This will work but will be lost when the X session is closed, @@ -816,7 +681,7 @@ EndSection or ~/.xsession when logging in through a graphical login manager like XDM). A third way is to use the new - /usr/X11R6/etc/fonts/local.conf file: see the + /usr/local/etc/fonts/local.conf file: see the section on anti-aliasing. @@ -829,26 +694,18 @@ EndSection TrueType - Both &xfree86; 4.X and &xorg; have built in support + &xorg; has built in support 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 back-ends. To enable the freetype module just add the following line to the "Module" section of the - /etc/X11/xorg.conf or - /etc/X11/XF86Config file. + /etc/X11/xorg.conf file. Load "freetype" - For &xfree86; 3.3.X, a separate - &truetype; font server is needed. - Xfstt is commonly used for - this purpose. To install Xfstt, - simply install the port - x11-servers/Xfstt. - Now make a directory for the &truetype; fonts (for example, - /usr/X11R6/lib/X11/fonts/TrueType) + /usr/local/lib/X11/fonts/TrueType) and copy all of the &truetype; fonts into this directory. Keep in mind that &truetype; fonts cannot be directly taken from a &macintosh;; they must be in &unix;/&ms-dos;/&windows; format for use by @@ -861,18 +718,18 @@ EndSection Ports Collection as x11-fonts/ttmkfdir. - &prompt.root; cd /usr/X11R6/lib/X11/fonts/TrueType -&prompt.root; ttmkfdir > fonts.dir + &prompt.root; cd /usr/local/lib/X11/fonts/TrueType +&prompt.root; ttmkfdir -o fonts.dir Now add the &truetype; directory to the font path. This is just the same as described above for Type1 fonts, that is, use - &prompt.user; xset fp+ /usr/X11R6/lib/X11/fonts/TrueType + &prompt.user; xset fp+ /usr/local/lib/X11/fonts/TrueType &prompt.user; xset fp rehash or add a FontPath line to the - xorg.conf (or XF86Config) file. + xorg.conf file. That's it. Now &netscape;, Gimp, @@ -908,7 +765,7 @@ EndSection Beginning with &xfree86; 4.3.0, all fonts in X11 that are found - in /usr/X11R6/lib/X11/fonts/ and + in /usr/local/lib/X11/fonts/ and ~/.fonts/ are automatically made available for anti-aliasing to Xft-aware applications. Not all applications are Xft-aware, but many have received Xft support. @@ -922,7 +779,7 @@ EndSection In order to control which fonts are anti-aliased, or to configure anti-aliasing properties, create (or edit, if it already exists) the file - /usr/X11R6/etc/fonts/local.conf. Several + /usr/local/etc/fonts/local.conf. Several advanced features of the Xft font system can be tuned using this file; this section describes only some simple possibilities. For more details, please see @@ -942,12 +799,12 @@ EndSection As previously stated, all fonts in - /usr/X11R6/lib/X11/fonts/ as well as + /usr/local/lib/X11/fonts/ as well as ~/.fonts/ are already made available to Xft-aware applications. If you wish to add another directory outside of these two directory trees, add a line similar to the following to - /usr/X11R6/etc/fonts/local.conf: + /usr/local/etc/fonts/local.conf: <dir>/path/to/my/fonts</dir> @@ -1045,11 +902,11 @@ EndSection set of default fonts can be found in the x11-fonts/bitstream-vera port. This port will install a - /usr/X11R6/etc/fonts/local.conf file + /usr/local/etc/fonts/local.conf file if one does not exist already. If the file does exist, - the port will create a /usr/X11R6/etc/fonts/local.conf-vera + the port will create a /usr/local/etc/fonts/local.conf-vera file. Merge the contents of this file into - /usr/X11R6/etc/fonts/local.conf, and the + /usr/local/etc/fonts/local.conf, and the Bitstream fonts will automatically replace the default X11 Serif, Sans Serif, and Monospaced fonts. @@ -1094,9 +951,8 @@ EndSection server is started. However, programs must know how to take advantage of it. At present, the Qt toolkit does, so the entire KDE environment can - use anti-aliased fonts (see on - KDE for details). GTK+ and + use anti-aliased fonts. + GTK+ and GNOME can also be made to use anti-aliasing via the Font capplet (see for details). By default, @@ -1152,7 +1008,7 @@ EndSection Using XDM The XDM daemon program is - located in /usr/X11R6/bin/xdm. This program + located in /usr/local/bin/xdm. This program can be run at any time as root and it will start managing the X display on the local machine. If XDM is to be run every @@ -1163,7 +1019,7 @@ EndSection /etc/ttys file for running the XDM daemon on a virtual terminal: - ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure + ttyv8 "/usr/local/bin/xdm -nodaemon" xterm off secure By default this entry is disabled; in order to enable it change field 5 from off to @@ -1179,7 +1035,7 @@ EndSection Configuring XDM The XDM configuration directory - is located in /usr/X11R6/lib/X11/xdm. In + is located in /usr/local/lib/X11/xdm. In this directory there are several files used to change the behavior and appearance of XDM. Typically these files will @@ -1257,10 +1113,10 @@ EndSection Xaccess The protocol for connecting to - XDM controlled displays is called + XDM-controlled displays is called the X Display Manager Connection Protocol (XDMCP). This file is a ruleset for controlling XDMCP connections from remote - machines. It's ignored unless the xdm-config + machines. It is ignored unless the xdm-config is changed to listen for remote connections. By default, it does not allow any clients to connect. @@ -1268,7 +1124,7 @@ EndSection Xresources This is an application-defaults file for the display - chooser and the login screens. This is where the appearance + chooser and login screens. In it, the appearance of the login program can be modified. The format is identical to the app-defaults file described in the X11 documentation. @@ -1323,7 +1179,7 @@ EndSection Running a Network Display Server In order for other clients to connect to the display - server, edit the access control rules, and enable the connection + server, you must edit the access control rules, and enable the connection listener. By default these are set to conservative values. To make XDM listen for connections, first comment out a line in the xdm-config @@ -1336,9 +1192,9 @@ DisplayManager.requestPort: 0 and then restart XDM. Remember that comments in app-defaults files begin with a ! character, not the usual #. More strict - access controls may be desired. Look at the example + access controls may be desired — look at the example entries in Xaccess, and refer to the - &man.xdm.1; manual page. + &man.xdm.1; manual page for further infomation. @@ -1405,9 +1261,7 @@ DisplayManager.requestPort: 0 Installing GNOME - The easiest way to install - GNOME is installed from a package or the ports - collection: + 可透過 package 或 Ports Collection 的方式來輕鬆安裝： To install the GNOME package from the network, simply type: @@ -1443,11 +1297,11 @@ DisplayManager.requestPort: 0 If a custom .xinitrc is already in place, simply replace the line that starts the current window manager with one that starts - /usr/X11R6/bin/gnome-session instead. + /usr/local/bin/gnome-session instead. If nothing special has been done to the configuration file, then it is enough simply to type: - &prompt.user; echo "/usr/X11R6/bin/gnome-session" > ~/.xinitrc + &prompt.user; echo "/usr/local/bin/gnome-session" > ~/.xinitrc Next, type startx, and the GNOME desktop environment will be @@ -1458,11 +1312,11 @@ DisplayManager.requestPort: 0 Instead, create an executable .xsession file with the same command in it. To do this, edit the file and replace the existing window manager command with - /usr/X11R6/bin/gnome-session: + /usr/local/bin/gnome-session: - &prompt.user; echo "#!/bin/sh" > ~/.xsession -&prompt.user; echo "/usr/X11R6/bin/gnome-session" >> ~/.xsession + &prompt.user; echo "#!/bin/sh" > ~/.xsession +&prompt.user; echo "/usr/local/bin/gnome-session" >> ~/.xsession &prompt.user; chmod +x ~/.xsession Yet another option is to configure the display manager to @@ -1542,7 +1396,7 @@ DisplayManager.requestPort: 0 - Centralized consisted dialog driven desktop + Centralized, consistent, dialog-driven desktop configuration @@ -1552,29 +1406,22 @@ DisplayManager.requestPort: 0 - 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 also - comes with a web browser called - Konqueror, which represents + KDE comes with a web browser called + Konqueror, which is a solid competitor to other existing web browsers on &unix; systems. More information on KDE can be found on the KDE website. For FreeBSD specific information and resources on KDE, consult - the FreeBSD-KDE + the KDE on FreeBSD team's website. - Installing KDE + 安裝 KDE - Just as with GNOME or any - other desktop environment, the easiest way to install - KDE is installed from a package - or from the Ports Collection: + 如同 GNOME 或其他桌面管理軟體一樣， + 也可以輕鬆透過 package 或 Ports Collection 來安裝： To install the KDE package from the network, simply type: @@ -1643,120 +1490,11 @@ DisplayManager.requestPort: 0 GNOME, or something else) to run after logging on. - To begin with, run the KDE - control panel, kcontrol, as - root. It is generally considered - unsafe to run the entire X environment as - root. Instead, run the window manager - as a normal user, open a terminal window (such as - xterm or KDE's - konsole), become root - with su (the user must 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 there are - various configurable options, which the - KDE manual will explain in greater - detail. Click on sessions on the right. - Click New type to add various window - managers and desktop environments. These are just labels, - so they can say KDE and - GNOME rather than - startkde or - gnome-session. - Include a label failsafe. - - Play with the other menus as well, they are mainly - cosmetic and self-explanatory. When you are done, click on - Apply at the bottom, and quit the - control center. - - To make sure kdm understands - what the labels (KDE, - GNOME etc) mean, edit the files used - by XDM. - In KDE 2.2 this has - changed: kdm now uses its own - configuration files. Please see the KDE - 2.2 documentation for details. - - In a terminal window, as root, - edit the file - /usr/X11R6/lib/X11/xdm/Xsession. There is - a section in the middle like this: - - case $# in -1) - case $1 in - failsafe) - exec xterm -geometry 80x24-0-0 - ;; - esac -esac - - A few lines need to be added to this section. - Assuming the labels from used were KDE and - GNOME, - use the following: - - case $# in -1) - case $1 in - kde) - exec /usr/local/bin/startkde - ;; - GNOME) - exec /usr/X11R6/bin/gnome-session - ;; - failsafe) - exec xterm -geometry 80x24-0-0 - ;; - esac -esac - - For the KDE - login-time desktop background to be honored, - the following line needs to be added to - /usr/X11R6/lib/X11/xdm/Xsetup_0: - - /usr/local/bin/krootimage - - Now, make sure 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 /usr/X11R6/bin/xdm - program with /usr/local/bin/kdm. - - - - Anti-aliased Fonts - - KDE - anti-aliased fonts - X11 - 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, with - up-to-date software, anti-aliasing is possible on a - KDE desktop. Just go to the KDE - menu, go to - - Preferences - Look and Feel - Fonts, and click on the check box - Use Anti-Aliasing for Fonts and Icons. - For a Qt application which is not part of - KDE, the environment variable - QT_XFT needs to be set to true - before starting the program. + To enable kdm, the + ttyv8 entry in /etc/ttys + has to be adapted. The line should look as follows: + ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure @@ -1782,7 +1520,7 @@ esac Fully configurable via mouse, with drag and - drop, etc + drop, etc. @@ -1792,8 +1530,7 @@ esac Integrated window manager, file manager, sound manager, - GNOME compliance module, and other - things + GNOME compliance module, and more @@ -1829,7 +1566,7 @@ esac XFce the next time X is started. Simply type this: - &prompt.user; echo "/usr/X11R6/bin/startxfce4" > ~/.xinitrc + &prompt.user; echo "/usr/local/bin/startxfce4" > ~/.xinitrc The next time X is started, XFce will be the desktop. @@ -1837,7 +1574,7 @@ esac XDM is being used, create an .xsession, as described in the section on GNOME, but - with the /usr/X11R6/bin/startxfce4 + with the /usr/local/bin/startxfce4 command; or, configure the display manager to allow choosing a desktop at login time, as explained in the section on kdm.