Date: Thu, 10 Jan 2013 08:46:43 -0800 (PST) From: Dru Lavigne <dru.lavigne@att.net> To: freebsd-doc@freebsd.org Subject: [patch] white space only fix for handbook x11 chapter Message-ID: <1357836403.24458.YahooMailClassic@web184905.mail.gq1.yahoo.com>
index | next in thread | raw e-mail
[-- Attachment #1 --]
This patch is igor fixes only for the x11 chapter. Igor is now much happier. There are still some bad indent fixes that I can't figure out as they look OK to me. I found a typo in this file which I did not fix.
The next patch will be a content patch on this chapter and will provide significant content changes for the x11 chapter in preparation for the published version of the handbook.
Cheers,
Dru
[-- Attachment #2 --]
Index: x11/chapter.xml
===================================================================
--- x11/chapter.xml (revision 40561)
+++ x11/chapter.xml (working copy)
@@ -29,13 +29,12 @@
a powerful graphical user interface. X11
is a freely available version of the X Window System that
is implemented in <application>&xorg;</application>
- (and other software
- packages not discussed here).
- The
+ (and other software packages not discussed here). The
default and official flavor of X11 in &os; is
<application>&xorg;</application>, the X11 server developed by
- the X.Org Foundation under a license very similar to the one used
- by &os;. Commercial X servers for &os; are also available.</para>
+ the X.Org Foundation under a license very similar to the one
+ used by &os;. Commercial X servers for &os; are also
+ available.</para>
<para>For more information on the video hardware that X11
supports, check the <ulink
@@ -45,8 +44,8 @@
<itemizedlist>
<listitem>
- <para>The various components of the X Window System, and how they
- interoperate.</para>
+ <para>The various components of the X Window System, and how
+ they interoperate.</para>
</listitem>
<listitem>
@@ -80,138 +79,154 @@
<sect1 id="x-understanding">
<title>Understanding X</title>
- <para>Using X for the first time can be somewhat of a shock to someone
- familiar with other graphical environments, such as µsoft.windows; or
- &macos;.</para>
+ <para>Using X for the first time can be somewhat of a shock to
+ someone familiar with other graphical environments, such as
+ µsoft.windows; or &macos;.</para>
- <para>While it is not necessary to understand all of the details of various
- X components and how they interact, some basic knowledge makes
- it possible to take advantage of X's strengths.</para>
+ <para>While it is not necessary to understand all of the details
+ of various X components and how they interact, some basic
+ knowledge makes it possible to take advantage of X's
+ strengths.</para>
<sect2>
<title>Why X?</title>
- <para>X is not the first window system written for &unix;, but it is the
- most popular of them. X's original development team had worked on another
- window system prior to writing X. That system's name was
- <quote>W</quote> (for <quote>Window</quote>). X was just the next
- letter in the Roman alphabet.</para>
+ <para>X is not the first window system written for &unix;, but
+ it is the most popular of them. X's original development team
+ had worked on another window system prior to writing X. That
+ system's name was <quote>W</quote> (for
+ <quote>Window</quote>). X was just the next letter in the
+ Roman alphabet.</para>
- <para>X can be called <quote>X</quote>, <quote>X Window System</quote>,
- <quote>X11</quote>, and a number of other terms. You may find
- that using the term <quote>X Windows</quote> to describe X11
- can be offensive to some people; for a bit more insight on
- this, see &man.X.7;.</para>
+ <para>X can be called <quote>X</quote>, <quote>X Window
+ System</quote>, <quote>X11</quote>, and a number of other
+ terms. You may find that using the term <quote>X
+ Windows</quote> to describe X11 can be offensive to some
+ people; for a bit more insight on this, see &man.X.7;.</para>
</sect2>
<sect2>
<title>The X Client/Server Model</title>
- <para>X was designed from the beginning to be network-centric, and
- adopts a <quote>client-server</quote> model.</para>
+ <para>X was designed from the beginning to be network-centric,
+ and adopts a <quote>client-server</quote> model.</para>
<para>In the X model, the
- <quote>X server</quote> runs on the computer that has the keyboard,
- monitor, and mouse attached. The server's responsibility includes tasks such as managing
- the display, handling input from the keyboard and mouse, and other
- input or output devices (i.e., a <quote>tablet</quote> can be used as
- an input device, and a video projector may be an alternative output
- device).
- Each X application (such as <application>XTerm</application>, or
- <application>&netscape;</application>) is a <quote>client</quote>. A
- client sends messages to the server such as <quote>Please draw a
- window at these coordinates</quote>, and the server sends back
- messages such as <quote>The user just clicked on the OK
+ <quote>X server</quote> runs on the computer that has the
+ keyboard, monitor, and mouse attached. The server's
+ responsibility includes tasks such as managing the
+ display, handling input from the keyboard and mouse, and
+ other input or output devices (i.e., a <quote>tablet</quote>
+ can be used as an input device, and a video projector
+ may be an alternative output device). Each X application
+ (such as <application>XTerm</application>, or
+ <application>&netscape;</application>) is a
+ <quote>client</quote>. A client sends messages to the server
+ such as <quote>Please draw a window at these
+ coordinates</quote>, and the server sends back messages such
+ as <quote>The user just clicked on the OK
button</quote>.</para>
- <para>In a home or small
- office environment, the X server and the X clients commonly run on
- the same computer. However, it is perfectly possible to run the X
- server on a less powerful desktop computer, and run X applications
- (the clients) on, say, the powerful and expensive machine that serves
- the office. In this scenario the communication between the X client
- and server takes place over the network.</para>
+ <para>In a home or small office environment, the X server and
+ the X clients commonly run on the same computer. However, it
+ is perfectly possible to run the X server on a less powerful
+ desktop computer, and run X applications (the clients) on,
+ say, the powerful and expensive machine that serves the
+ office. In this scenario the communication between the X
+ client and server takes place over the network.</para>
<para>This confuses some people, because the X terminology is
- exactly backward to what they expect. They expect the <quote>X
- server</quote> to be the big powerful machine down the hall, and
- the <quote>X client</quote> to be the machine on their desk.</para>
+ exactly backward to what they expect. They expect the
+ <quote>X server</quote> to be the big powerful machine down
+ the hall, and the <quote>X client</quote> to be the machine
+ on their desk.</para>
- <para>It is important to remember that the X server is the machine with the monitor and
- keyboard, and the X clients are the programs that display the
- windows.</para>
+ <para>It is important to remember that the X server is the
+ machine with the monitor and keyboard, and the X clients are
+ the programs that display the windows.</para>
- <para>There is 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 certainly possible to
- run an X server on µsoft.windows; or Apple's &macos;, and there are
- various free and commercial applications available that do exactly
- that.</para>
+ <para>There is 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
+ certainly possible to run an X server on µsoft.windows;
+ or Apple's &macos;, and there are various free and commercial
+ applications available that do exactly that.</para>
</sect2>
<sect2>
<title>The Window Manager</title>
- <para>The X design philosophy is much like the &unix; design philosophy,
- <quote>tools, not policy</quote>. This means that X does not try to
- dictate how a task is to be accomplished. Instead, tools are provided
- to the user, and it is the user's responsibility to decide how to use
- those tools.</para>
+ <para>The X design philosophy is much like the &unix; design
+ philosophy, <quote>tools, not policy</quote>. This means
+ that X does not try to dictate how a task is to be
+ accomplished. Instead, tools are provided to the user, and
+ it is the user's responsibility to decide how to use those
+ tools.</para>
- <para>This philosophy extends to X not dictating what windows should
- look like on screen, how to move them around with the mouse, what
- keystrokes should be used to move between windows (i.e.,
+ <para>This philosophy extends to X not dictating what windows
+ should look like on screen, how to move them around with the
+ mouse, what keystrokes should be used to move between windows
+ (i.e.,
<keycombo action="simul">
<keycap>Alt</keycap>
<keycap>Tab</keycap>
- </keycombo>, in the case of µsoft.windows;), what the title bars
- on each window should look like, whether or not they have close
- buttons on them, and so on.</para>
+ </keycombo>, in the case of µsoft.windows;), what the
+ title bars on each window should look like, whether or not
+ they have close buttons on them, and so on.</para>
- <para>Instead, X delegates this responsibility to an application called
- a <quote>Window Manager</quote>. There are dozens of window
- managers available for X: <application>AfterStep</application>,
- <application>Blackbox</application>, <application>ctwm</application>,
+ <para>Instead, X delegates this responsibility to an
+ application called a <quote>Window Manager</quote>. There
+ are dozens of window managers available for X:
+ <application>AfterStep</application>,
+ <application>Blackbox</application>,
+ <application>ctwm</application>,
<application>Enlightenment</application>,
- <application>fvwm</application>, <application>Sawfish</application>,
+ <application>fvwm</application>,
+ <application>Sawfish</application>,
<application>twm</application>,
- <application>Window Maker</application>, and more. Each of these
- window managers provides a different look and feel; some of them
- support <quote>virtual desktops</quote>; some of them allow customized
- keystrokes to manage the desktop; some have a <quote>Start</quote>
- button or similar device; some are <quote>themeable</quote>, allowing
- a complete change of look-and-feel by applying a new theme. These
- window managers, and many more, are available in the
- <filename>x11-wm</filename> category of the Ports Collection.</para>
+ <application>Window Maker</application>, and more. Each of
+ these window managers provides a different look and feel;
+ some of them support <quote>virtual desktops</quote>; some
+ of them allow customized keystrokes to manage the desktop;
+ some have a <quote>Start</quote> button or similar device;
+ some are <quote>themeable</quote>, allowing a complete change
+ of look-and-feel by applying a new theme. These window
+ managers, and many more, are available in the
+ <filename>x11-wm</filename> category of the Ports
+ Collection.</para>
<para>In addition, the <application>KDE</application> and
- <application>GNOME</application> desktop environments both have their
- own window managers which integrate with the desktop.</para>
+ <application>GNOME</application> desktop environments both
+ have their own window managers which integrate with the
+ desktop.</para>
- <para>Each window manager also has a different configuration mechanism;
- some expect configuration file written by hand, others feature
- GUI tools for most of the configuration tasks; at least one
- (<application>Sawfish</application>) has a configuration file written
- in a dialect of the Lisp language.</para>
+ <para>Each window manager also has a different configuration
+ mechanism; some expect configuration file written by hand,
+ others feature GUI tools for most of the configuration tasks;
+ at least one (<application>Sawfish</application>) has a
+ configuration file written in a dialect of the Lisp
+ language.</para>
<note>
<title>Focus Policy</title>
- <para>Another feature the window manager is responsible for is the
- mouse <quote>focus policy</quote>. Every windowing system
- needs some means of choosing a window to be actively receiving
- keystrokes, and should visibly indicate which window is active as
- well.</para>
+ <para>Another feature the window manager is responsible for
+ is the mouse <quote>focus policy</quote>. Every windowing
+ system needs some means of choosing a window to be actively
+ receiving keystrokes, and should visibly indicate which
+ window is active as well.</para>
- <para>A familiar focus policy is called <quote>click-to-focus</quote>.
- This is the model utilized by µsoft.windows;, in which a window
- becomes active upon receiving a mouse click.</para>
+ <para>A familiar focus policy is called
+ <quote>click-to-focus</quote>. This is the model utilized
+ by µsoft.windows;, in which a window becomes active
+ upon receiving a mouse click.</para>
- <para>X does not support any particular focus policy. Instead, the
- window manager controls which window has the focus at any one time.
- Different window managers will support different focus methods. All
- of them support click to focus, and the majority of them support
- several others.</para>
+ <para>X does not support any particular focus policy.
+ Instead, the window manager controls which window has the
+ focus at any one time. Different window managers will
+ support different focus methods. All of them support
+ click to focus, and the majority of them support several
+ others.</para>
<para>The most popular focus policies are:</para>
@@ -220,11 +235,12 @@
<term>focus-follows-mouse</term>
<listitem>
- <para>The window that is under the mouse pointer is the
- window that has the focus. This may not necessarily be
- the window that is on top of all the other windows.
- The focus is changed by pointing at another window, there
- is no need to click in it as well.</para>
+ <para>The window that is under the mouse pointer is
+ the window that has the focus. This may not
+ necessarily be the window that is on top of all the
+ other windows. The focus is changed by pointing at
+ another window, there is no need to click in it as
+ well.</para>
</listitem>
</varlistentry>
@@ -232,12 +248,14 @@
<term>sloppy-focus</term>
<listitem>
- <para>This policy is a small extension to focus-follows-mouse.
- With focus-follows-mouse, if the mouse is moved over the
- root window (or background) then no window has the focus,
- and keystrokes are simply lost. With sloppy-focus, focus is
- only changed when the cursor enters a new window, and not
- when exiting the current window.</para>
+ <para>This policy is a small extension to
+ focus-follows-mouse. With focus-follows-mouse, if
+ the mouse is moved over the root window (or
+ background) then no window has the focus, and
+ keystrokes are simply lost. With sloppy-focus, focus
+ is only changed when the cursor enters a new
+ window, and not when exiting the current
+ window.</para>
</listitem>
</varlistentry>
@@ -245,52 +263,56 @@
<term>click-to-focus</term>
<listitem>
- <para>The active window is selected by mouse click. The
- window may then be <quote>raised</quote>, and appear in
- front of all other windows. All keystrokes will now be
- directed to this window, even if the cursor is moved to
- another window.</para>
+ <para>The active window is selected by mouse click.
+ The window may then be <quote>raised</quote>, and
+ appear in front of all other windows. All keystrokes
+ will now be directed to this window, even if the
+ cursor is moved to another window.</para>
</listitem>
</varlistentry>
</variablelist>
- <para>Many window managers support other policies, as well as
- variations on these. Be sure to consult the documentation for
- the window manager itself.</para>
+ <para>Many window managers support other policies, as well
+ as variations on these. Be sure to consult the
+ documentation for the window manager itself.</para>
</note>
</sect2>
<sect2>
<title>Widgets</title>
- <para>The X approach of providing tools and not policy extends to the
- widgets seen on screen in each application.</para>
+ <para>The X approach of providing tools and not policy
+ extends to the widgets seen on screen in each
+ application.</para>
- <para><quote>Widget</quote> is a term for all the items in the user
- interface that can be clicked or manipulated in some way; buttons,
- check boxes, radio buttons, icons, lists, and so on. µsoft.windows;
- calls these <quote>controls</quote>.</para>
+ <para><quote>Widget</quote> is a term for all the items in
+ the user interface that can be clicked or manipulated in
+ some way; buttons, check boxes, radio buttons, icons, lists,
+ and so on. µsoft.windows; calls these
+ <quote>controls</quote>.</para>
- <para>µsoft.windows; and Apple's &macos; both have a very rigid widget
- policy. Application developers are supposed to ensure that their
- applications share a common look and feel. With X, it was not
- considered sensible to mandate a particular graphical style, or set
- of widgets to adhere to.</para>
+ <para>µsoft.windows; and Apple's &macos; both have a
+ very rigid widget policy. Application developers are
+ supposed to ensure that their applications share a common
+ look and feel. With X, it was not considered sensible to
+ mandate a particular graphical style, or set of widgets to
+ adhere to.</para>
- <para>As a result, do not expect X applications to have a common
- look and feel. There are several popular widget sets and
- variations, including the original Athena widget set from MIT,
- <application>&motif;</application> (on which the widget set in
- µsoft.windows; was modeled, all bevelled edges and three shades of
- grey), <application>OpenLook</application>, and others.</para>
+ <para>As a result, do not expect X applications to have a
+ common look and feel. There are several popular widget sets
+ and variations, including the original Athena widget set from
+ MIT, <application>&motif;</application> (on which the widget
+ set in µsoft.windows; was modeled, all bevelled edges and
+ three shades of grey), <application>OpenLook</application>,
+ and others.</para>
- <para>Most newer X applications today will use a modern-looking widget
- set, either Qt, used by <application>KDE</application>, or
- GTK+, used by the
- <application>GNOME</application>
- project. In this respect, there is some convergence in
- look-and-feel of the &unix; desktop, which certainly makes things
- easier for the novice user.</para>
+ <para>Most newer X applications today will use a
+ modern-looking widget set, either Qt, used by
+ <application>KDE</application>, or GTK+, used by the
+ <application>GNOME</application> project. In this respect,
+ there is some convergence in look-and-feel of the &unix;
+ desktop, which certainly makes things easier for the novice
+ user.</para>
</sect2>
</sect1>
@@ -298,15 +320,16 @@
<title>Installing X11</title>
<para><application>&xorg;</application> is the default X11
- implementation for &os;. <application>&xorg;</application> is
- the X server of the open source X Window System implementation released by the X.Org
- Foundation. <application>&xorg;</application> is based on the code of
+ implementation for &os;. <application>&xorg;</application>
+ is the X server of the open source X Window System
+ implementation released by the X.Org Foundation.
+ <application>&xorg;</application> is based on the code of
<application>&xfree86; 4.4RC2</application> and X11R6.6.
The version of <application>&xorg;</application> currently
available in the &os; Ports Collection is &xorg.version;.</para>
- <para>To build and install <application>&xorg;</application> from the
- Ports Collection:</para>
+ <para>To build and install <application>&xorg;</application>
+ from the Ports Collection:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/x11/xorg</userinput>
&prompt.root; <userinput>make install clean</userinput></screen>
@@ -319,10 +342,10 @@
<para>Alternatively, X11
can be installed directly from packages.
- Binary packages to use with &man.pkg.add.1; tool are also available for
- X11. When the remote fetching
- feature of &man.pkg.add.1; is used, the version number of the
- package must be removed. &man.pkg.add.1; will automatically fetch
+ Binary packages to use with &man.pkg.add.1; tool are also
+ available for X11. When the remote fetching feature of
+ &man.pkg.add.1; is used, the version number of the package
+ must be removed. &man.pkg.add.1; will automatically fetch
the latest version of the application.</para>
<para>So to fetch and install the package of
@@ -336,7 +359,8 @@
are also
available.</para>
- <para>To install a minimal X11 distribution you can alternatively install
+ <para>To install a minimal X11 distribution you can
+ alternatively install
<filename role="package">x11/xorg-minimal</filename>.</para>
</note>
@@ -414,9 +438,10 @@
<para><application>&xorg;</application>
uses <acronym>HAL</acronym> to autodetect keyboards and mice.
The <filename role="package">sysutils/hal</filename> and
- <filename role="package">devel/dbus</filename> ports are installed
- as dependencies of <filename role="package">x11/xorg</filename>, but
- must be enabled by the following entries in the
+ <filename role="package">devel/dbus</filename> ports are
+ installed as dependencies of <filename
+ role="package">x11/xorg</filename>, but must be enabled by
+ the following entries in the
<filename>/etc/rc.conf</filename> file:</para>
<programlisting>hald_enable="YES"
@@ -427,14 +452,14 @@
configuration or use is attempted.</para>
<para><application>&xorg;</application> can
- often work without any further configuration steps by simply typing at
- prompt:</para>
+ often work without any further configuration steps by
+ simply typing at prompt:</para>
<screen>&prompt.user; <userinput>startx</userinput></screen>
- <para>The automatic configuration may fail to work with some hardware,
- or may not set things up quite as desired. In these cases, manual
- configuration will be necessary.</para>
+ <para>The automatic configuration may fail to work with some
+ hardware, or may not set things up quite as desired. In
+ these cases, manual configuration will be necessary.</para>
<note>
<para>Desktop environments like
@@ -475,14 +500,14 @@
<screen>&prompt.root; <userinput>Xorg -config xorg.conf.new -retro</userinput></screen>
<para>If a black and grey grid and an X mouse cursor appear,
- the configuration was successful. To exit the test, switch to the
- virtual console used to start it by pressing
+ the configuration was successful. To exit the test, switch
+ to the virtual console used to start it by pressing
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Alt</keycap>
<keycap>F<replaceable>n</replaceable></keycap>
- </keycombo> (<keycap>F1</keycap> for the first virtual console)
- and press
+ </keycombo> (<keycap>F1</keycap> for the first virtual
+ console) and press
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>C</keycap>
@@ -523,8 +548,8 @@
<para>The following line will also have to be added to
<filename>xorg.conf.new</filename>, in the
- <literal>ServerLayout</literal> or <literal>ServerFlags</literal>
- section:</para>
+ <literal>ServerLayout</literal> or
+ <literal>ServerFlags</literal> section:</para>
<programlisting>Option "DontZap" "off"</programlisting>
</note>
@@ -541,9 +566,9 @@
<programlisting>Option "AutoAddDevices" "false"</programlisting>
- <para>Input devices may then be configured as in previous versions,
- along with any other options needed (e.g., keyboard layout
- switching).</para>
+ <para>Input devices may then be configured as in previous
+ versions, along with any other options needed (e.g.,
+ keyboard layout switching).</para>
<note>
<para>As previously explained
@@ -597,11 +622,11 @@
<indexterm><primary>X11 tuning</primary></indexterm>
<para>The <filename>xorg.conf.new</filename>
- configuration file may now be tuned to taste. Open the file in a text editor such
- as &man.emacs.1; or &man.ee.1;. If the monitor is an older
- or unusual model that does not support autodetection of
- sync frequencies, those settings can
- be added to <filename>xorg.conf.new</filename>
+ configuration file may now be tuned to taste. Open the
+ file in a text editor such as &man.emacs.1; or &man.ee.1;.
+ If the monitor is an older or unusual model that does not
+ support autodetection of sync frequencies, those settings
+ can be added to <filename>xorg.conf.new</filename>
under the <literal>"Monitor"</literal> section:</para>
<programlisting>Section "Monitor"
@@ -612,20 +637,19 @@
VertRefresh 48-120
EndSection</programlisting>
- <para>Most monitors support sync frequency autodetection, making
- manual entry of these values unnecessary. For the few
- monitors that do not support autodetection, avoid potential
- damage by only entering values provided by the
+ <para>Most monitors support sync frequency autodetection,
+ making manual entry of these values unnecessary. For the
+ few monitors that do not support autodetection, avoid
+ potential damage by only entering values provided by the
manufacturer.</para>
- <para>X allows DPMS (Energy Star) features to be used with capable
- monitors. The &man.xset.1; program controls the time-outs and can force
- standby, suspend, or off modes. If you wish to enable DPMS features
- for your monitor, you must add the following line to the monitor
- section:</para>
+ <para>X allows DPMS (Energy Star) features to be used with
+ capable monitors. The &man.xset.1; program controls the
+ time-outs and can force standby, suspend, or off modes. If
+ you wish to enable DPMS features for your monitor, you must
+ add the following line to the monitor section:</para>
- <programlisting>
- Option "DPMS"</programlisting>
+ <programlisting>Option "DPMS"</programlisting>
<indexterm>
<primary><filename>xorg.conf</filename></primary>
@@ -657,21 +681,21 @@
Note that only VESA standard modes are supported as defined by
the target system's graphics hardware.
In the example above, the default color depth is twenty-four
- bits per pixel. At this color depth, the accepted resolution is
- 1024 by 768
- pixels.</para>
+ bits per pixel. At this color depth, the accepted
+ resolution is 1024 by 768 pixels.</para>
<para>Finally, write the configuration file and test it using
the test mode given above.</para>
<note>
<para>One of the tools available to assist you during
- troubleshooting process are the X11 log files, which contain
- information on each device that the X11 server attaches to.
- <application>&xorg;</application> log file names are in the format
- of <filename>/var/log/Xorg.0.log</filename>. The exact name
- of the log can vary from <filename>Xorg.0.log</filename> to
- <filename>Xorg.8.log</filename> and so forth.</para>
+ troubleshooting process are the X11 log files, which
+ contain information on each device that the X11 server
+ attaches to. <application>&xorg;</application> log file
+ names are in the format of
+ <filename>/var/log/Xorg.0.log</filename>. The exact name
+ of the log can vary from <filename>Xorg.0.log</filename>
+ to <filename>Xorg.8.log</filename> and so forth.</para>
</note>
<para>If all is well, the configuration
@@ -693,7 +717,8 @@
<title>Advanced Configuration Topics</title>
<sect3>
- <title>Configuration with &intel; <literal>i810</literal> Graphics Chipsets</title>
+ <title>Configuration with &intel; <literal>i810</literal>
+ Graphics Chipsets</title>
<indexterm><primary>Intel i810 graphic chipset</primary></indexterm>
@@ -703,12 +728,13 @@
to drive the card. See the &man.agp.4; driver manual page
for more information.</para>
- <para>This will allow configuration of the hardware as any other
- graphics board. Note on systems without the &man.agp.4;
- driver compiled in the kernel, trying to load the module
- with &man.kldload.8; will not work. This driver has to be
- in the kernel at boot time through being compiled in or
- using <filename>/boot/loader.conf</filename>.</para>
+ <para>This will allow configuration of the hardware as any
+ other graphics board. Note on systems without the
+ &man.agp.4; driver compiled in the kernel, trying to load
+ the module with &man.kldload.8; will not work. This
+ driver has to be in the kernel at boot time through being
+ compiled in or using
+ <filename>/boot/loader.conf</filename>.</para>
</sect3>
<sect3>
@@ -716,16 +742,18 @@
<indexterm><primary>widescreen flatpanel configuration</primary></indexterm>
- <para>This section assumes a bit of advanced configuration knowledge.
- If attempts to use the standard configuration tools above have not
- resulted in a working configuration, there is information enough
- in the log files to be of use in getting the setup working.
- Use of a text editor will be necessary.</para>
+ <para>This section assumes a bit of advanced configuration
+ knowledge. If attempts to use the standard configuration
+ tools above have not resulted in a working configuration,
+ there is information enough in the log files to be of use
+ in getting the setup working. Use of a text editor will
+ be necessary.</para>
- <para>Current widescreen (WSXGA, WSXGA+, WUXGA, WXGA, WXGA+, et.al.)
- formats support 16:10 and 10:9 formats or aspect ratios that can
- be problematic. Examples of some common screen resolutions for
- 16:10 aspect ratios are:</para>
+ <para>Current widescreen (WSXGA, WSXGA+, WUXGA, WXGA,
+ WXGA+, et.al.) formats support 16:10 and 10:9 formats or
+ aspect ratios that can be problematic. Examples of some
+ common screen resolutions for 16:10 aspect ratios
+ are:</para>
<itemizedlist>
<listitem><para>2560x1600</para></listitem>
@@ -736,8 +764,8 @@
</itemizedlist>
<para>At some point, it will be as easy as adding one of these
- resolutions as a possible <literal>Mode</literal> in the <literal>Section
- "Screen"</literal> as such:</para>
+ resolutions as a possible <literal>Mode</literal> in the
+ <literal>Section "Screen"</literal> as such:</para>
<programlisting>Section "Screen"
Identifier "Screen0"
@@ -751,16 +779,18 @@
EndSubSection
EndSection</programlisting>
- <para><application>&xorg;</application> is smart enough to pull the
- resolution information from the widescreen via I2C/DDC information
- so it knows what the monitor can handle as far as frequencies
- and resolutions.</para>
+ <para><application>&xorg;</application> is smart enough to
+ pull the resolution information from the widescreen via
+ I2C/DDC information so it knows what the monitor can
+ handle as far as frequencies and resolutions.</para>
- <para>If those <literal>ModeLines</literal> do not exist in the drivers,
- one might need to give <application>&xorg;</application> a little hint.
- Using <filename>/var/log/Xorg.0.log</filename> one can extract
- enough information to manually create a <literal>ModeLine</literal> that
- will work. Simply look for information resembling this:</para>
+ <para>If those <literal>ModeLines</literal> do not exist in
+ the drivers, one might need to give
+ <application>&xorg;</application> a little hint. Using
+ <filename>/var/log/Xorg.0.log</filename> one can extract
+ enough information to manually create a
+ <literal>ModeLine</literal> that will work. Simply look
+ for information resembling this:</para>
<programlisting>(II) MGA(0): Supported additional Video Mode:
(II) MGA(0): clock: 146.2 MHz Image Size: 433 x 271 mm
@@ -769,12 +799,13 @@
(II) MGA(0): Ranges: V min: 48 V max: 85 Hz, H min: 30 H max: 94 kHz, PixClock max 170 MHz</programlisting>
<para>This information is called EDID information. Creating a
- <literal>ModeLine</literal> from this is just a matter of putting the
- numbers in the correct order:</para>
+ <literal>ModeLine</literal> from this is just a matter of
+ putting the numbers in the correct order:</para>
<programlisting>ModeLine <name> <clock> <4 horiz. timings> <4 vert. timings></programlisting>
- <para>So that the <literal>ModeLine</literal> in <literal>Section "Monitor"</literal>
+ <para>So that the <literal>ModeLine</literal> in
+ <literal>Section "Monitor"</literal>
for this example would look like this:</para>
<programlisting>Section "Monitor"
@@ -785,8 +816,8 @@
Option "DPMS"
EndSection</programlisting>
- <para>Now having completed these simple editing steps, X should start
- on your new widescreen monitor.</para>
+ <para>Now having completed these simple editing steps, X
+ should start on your new widescreen monitor.</para>
</sect3>
</sect2>
</sect1>
@@ -805,36 +836,40 @@
<sect2 id="type1">
<title>Type1 Fonts</title>
- <para>The default fonts that ship with
- X11 are less than ideal for typical
- desktop publishing applications. Large presentation fonts show up
- jagged and unprofessional looking, and small fonts in
- <application>&netscape;</application> are almost completely unintelligible.
- However, there are several free, high quality Type1 (&postscript;) fonts
- available which can be readily used
- with X11. For instance, the URW font collection
- (<filename role="package">x11-fonts/urwfonts</filename>) includes
- high quality versions of standard type1 fonts (<trademark class="registered">Times Roman</trademark>,
- <trademark class="registered">Helvetica</trademark>, <trademark class="registered">Palatino</trademark> and others). The Freefonts collection
- (<filename role="package">x11-fonts/freefonts</filename>) includes
- many more fonts, but most of them are intended for use in
- graphics software such as the <application>Gimp</application>, and are not
- complete enough to serve as screen fonts. In addition,
- X11 can be configured to use
- &truetype; fonts with a minimum of effort. For more details on
- this, see the &man.X.7; manual page or the
- <link linkend="truetype">section on &truetype; fonts</link>.</para>
+ <para>The default fonts that ship with X11 are less than ideal
+ for typical desktop publishing applications. Large
+ presentation fonts show up jagged and unprofessional looking,
+ and small fonts in <application>&netscape;</application> are
+ almost completely unintelligible. However, there are several
+ free, high quality Type1 (&postscript;) fonts available which
+ can be readily used with X11. For instance, the URW font
+ collection (<filename
+ role="package">x11-fonts/urwfonts</filename>) includes high
+ quality versions of standard type1 fonts (<trademark
+ class="registered">Times Roman</trademark>,
+ <trademark class="registered">Helvetica</trademark>, <trademark
+ class="registered">Palatino</trademark> and others). The
+ Freefonts collection (<filename
+ role="package">x11-fonts/freefonts</filename>) includes
+ many more fonts, but most of them are intended for use in
+ graphics software such as the <application>Gimp</application>,
+ and are not complete enough to serve as screen fonts. In
+ addition, X11 can be configured to use &truetype; fonts with
+ a minimum of effort. For more details on this, see the
+ &man.X.7; manual page or the <link linkend="truetype">section
+ on &truetype; fonts</link>.</para>
+
<para>To install the above Type1 font collections from the
Ports Collection, run the following commands:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/x11-fonts/urwfonts</userinput>
&prompt.root; <userinput>make install clean</userinput></screen>
- <para>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 (<filename>/etc/X11/xorg.conf</filename>),
- which reads:</para>
+ <para>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
+ (<filename>/etc/X11/xorg.conf</filename>), which reads:</para>
<programlisting>FontPath "/usr/local/lib/X11/fonts/URW/"</programlisting>
@@ -844,14 +879,16 @@
<screen>&prompt.user; <userinput>xset fp+ /usr/local/lib/X11/fonts/URW</userinput>
&prompt.user; <userinput>xset fp rehash</userinput></screen>
- <para>This will work but will be lost when the X session is closed,
- unless it is added to the startup file (<filename>~/.xinitrc</filename>
- for a normal <command>startx</command> session,
- or <filename>~/.xsession</filename> when logging in through a
- graphical login manager like <application>XDM</application>).
- A third way is to use the new
- <filename>/usr/local/etc/fonts/local.conf</filename> file: see the
- section on <link linkend="antialias">anti-aliasing</link>.</para>
+ <para>This will work but will be lost when the X session is
+ closed, unless it is added to the startup file
+ (<filename>~/.xinitrc</filename> for a normal
+ <command>startx</command> session, or
+ <filename>~/.xsession</filename> when logging in through a
+ graphical login manager like <application>XDM</application>).
+ A third way is to use the new
+ <filename>/usr/local/etc/fonts/local.conf</filename> file: see
+ the section on <link
+ linkend="antialias">anti-aliasing</link>.</para>
</sect2>
<sect2 id="truetype">
@@ -863,25 +900,26 @@
</indexterm>
<para><application>&xorg;</application> 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 <literal>"Module"</literal> section of the
- <filename>/etc/X11/xorg.conf</filename> file.</para>
+ 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
+ <literal>"Module"</literal> section of the
+ <filename>/etc/X11/xorg.conf</filename> file.</para>
<programlisting>Load "freetype"</programlisting>
- <para>Now make a directory for the &truetype; fonts (for example,
+ <para>Now make a directory for the &truetype; fonts (for
+ example,
<filename>/usr/local/lib/X11/fonts/TrueType</filename>)
- 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
- X11. Once the files have been
- copied into this directory, use
- <application>ttmkfdir</application> to create a
- <filename>fonts.dir</filename> file, so that the X font renderer
- knows that these new files have been installed.
+ 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 X11. Once the files have been copied into
+ this directory, use <application>ttmkfdir</application> to
+ create a <filename>fonts.dir</filename> file, so that the X
+ font renderer knows that these new files have been installed.
<command>ttmkfdir</command> is available from the FreeBSD
Ports Collection as
<filename role="package">x11-fonts/ttmkfdir</filename>.</para>
@@ -901,12 +939,12 @@
<para>That's it. Now <application>&netscape;</application>,
<application>Gimp</application>,
- <application>&staroffice;</application>, and all of the other X
- applications should now recognize the installed &truetype;
- fonts. Extremely small fonts (as with text in a high resolution
- display on a web page) and extremely large fonts (within
- <application>&staroffice;</application>) will look much better
- now.</para>
+ <application>&staroffice;</application>, and all of the
+ other X applications should now recognize the installed
+ &truetype; fonts. Extremely small fonts (as with text in a
+ high resolution display on a web page) and extremely large
+ fonts (within <application>&staroffice;</application>) will
+ look much better now.</para>
</sect2>
<sect2 id="antialias">
@@ -931,7 +969,8 @@
<filename>~/.fonts/</filename> are automatically
made available for anti-aliasing to Xft-aware applications.
Most recent applications are Xft-aware, including
- <application>KDE</application>, <application>GNOME</application>, and
+ <application>KDE</application>,
+ <application>GNOME</application>, and
<application>Firefox</application>.</para>
<para>In order to control which fonts are anti-aliased, or to
@@ -945,16 +984,16 @@
<indexterm><primary>XML</primary></indexterm>
- <para>This file must be in XML format. Pay careful attention to
- case, and make sure all tags are properly closed. The file
- begins with the usual XML header followed by a DOCTYPE
- definition, and then the <literal><fontconfig></literal> tag:</para>
+ <para>This file must be in XML format. Pay careful attention
+ to case, and make sure all tags are properly closed. The
+ file begins with the usual XML header followed by a DOCTYPE
+ definition, and then the <literal><fontconfig></literal>
+ tag:</para>
<programlisting>
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
- <fontconfig>
- </programlisting>
+ <fontconfig></programlisting>
<para>As previously stated, all fonts in
<filename>/usr/local/lib/X11/fonts/</filename> as well as
@@ -972,11 +1011,12 @@
<screen>&prompt.root; <userinput>fc-cache -f</userinput></screen>
- <para>Anti-aliasing makes borders slightly fuzzy, which makes very
- small text more readable and removes <quote>staircases</quote> from
- large text, but can cause eyestrain if applied to normal text. To
- exclude font sizes smaller than 14 point from anti-aliasing, include
- these lines:</para>
+ <para>Anti-aliasing makes borders slightly fuzzy, which makes
+ very small text more readable and removes
+ <quote>staircases</quote> from large text, but can cause
+ eyestrain if applied to normal text. To exclude font sizes
+ smaller than 14 point from anti-aliasing, include these
+ lines:</para>
<programlisting> <match target="font">
<test name="size" compare="less">
@@ -1000,9 +1040,9 @@
<para>Spacing for some monospaced fonts may also be inappropriate
with anti-aliasing. This seems to be an issue with
- <application>KDE</application>, in particular. One possible fix for
- this is to force the spacing for such fonts to be 100. Add the
- following lines:</para>
+ <application>KDE</application>, in particular. One possible
+ fix for this is to force the spacing for such fonts to be 100.
+ Add the following lines:</para>
<programlisting> <match target="pattern" name="family">
<test qual="any" name="family">
@@ -1051,23 +1091,25 @@
<para>Once you have finished editing
<filename>local.conf</filename> make sure you end the file
- with the <literal></fontconfig></literal> tag. Not doing this will cause
- your changes to be ignored.</para>
+ with the <literal></fontconfig></literal> tag. Not
+ doing this will cause your changes to be ignored.</para>
- <para>Finally, users can add their own settings via their personal
- <filename>.fonts.conf</filename> files. To do this, each user should
- simply create a <filename>~/.fonts.conf</filename>. This file must
- also be in XML format.</para>
+ <para>Finally, users can add their own settings via their
+ personal <filename>.fonts.conf</filename> files. To do
+ this, each user should simply create a
+ <filename>~/.fonts.conf</filename>. This file must also be
+ in XML format.</para>
<indexterm><primary>LCD screen</primary></indexterm>
<indexterm><primary>Fonts</primary>
<secondary>LCD screen</secondary></indexterm>
- <para>One last point: with an LCD screen, sub-pixel sampling may be
- desired. This basically treats the (horizontally separated)
- red, green and blue components separately to improve the horizontal
- resolution; the results can be dramatic. To enable this, add the
- line somewhere in the <filename>local.conf</filename> file:</para>
+ <para>One last point: with an LCD screen, sub-pixel sampling
+ may be desired. This basically treats the (horizontally
+ separated) red, green and blue components separately to
+ improve the horizontal resolution; the results can be
+ dramatic. To enable this, add the line somewhere in the
+ <filename>local.conf</filename> file:</para>
<programlisting>
<match target="font">
@@ -1077,14 +1119,14 @@
<edit name="rgba" mode="assign">
<const>rgb</const>
</edit>
- </match>
- </programlisting>
+ </match></programlisting>
<note>
<para>Depending on the sort of display,
- <literal>rgb</literal> may need to be changed to <literal>bgr</literal>,
- <literal>vrgb</literal> or <literal>vbgr</literal>: experiment and
- see which works best.</para>
+ <literal>rgb</literal> may need to be changed to
+ <literal>bgr</literal>, <literal>vrgb</literal> or
+ <literal>vbgr</literal>: experiment and see which works
+ best.</para>
</note>
</sect2>
</sect1>
@@ -1101,61 +1143,63 @@
</sect1info>
<title>The X Display Manager</title>
<sect2>
+
<title>Overview</title>
<indexterm><primary>X Display Manager</primary></indexterm>
- <para>The X Display Manager (<application>XDM</application>) 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 <quote>X Terminals</quote>,
- 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. <application>XDM</application> provides
- a graphical interface for choosing which display server to
- connect to, and entering authorization information such as a
- login and password combination.</para>
+ <para>The X Display Manager (<application>XDM</application>)
+ 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 <quote>X Terminals</quote>,
+ 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. <application>XDM</application> provides a graphical
+ interface for choosing which display server to connect to,
+ and entering authorization information such as a login and
+ password combination.</para>
<para>Think of <application>XDM</application> as
providing the same functionality to the user as the
&man.getty.8; utility (see <xref linkend="term-config"/> 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). <application>XDM</application> then waits for this
- program to exit, signaling that the user is done and should be
+ being connected to and then runs a session manager on
+ behalf of the user (usually an X window manager).
+ <application>XDM</application> then waits for this program
+ to exit, signaling that the user is done and should be
logged out of the display. At this point,
- <application>XDM</application> can display the login and display
- chooser screens for the next user to login.</para>
+ <application>XDM</application> can display the login and
+ display chooser screens for the next user to login.</para>
</sect2>
<sect2>
<title>Using XDM</title>
- <para>To start using <application>XDM</application>, install the
- <filename role="package">x11/xdm</filename> port (it is not
- installed by default in recent versions of
- <application>&xorg;</application>).
- The <application>XDM</application> daemon program may then be
- found in <filename>/usr/local/bin/xdm</filename>. This program
- can be run at any time as <username>root</username> and it will
- start managing the X display on the local machine. If
- <application>XDM</application> is to be run every
+ <para>To start using <application>XDM</application>, install
+ the <filename role="package">x11/xdm</filename> port (it is
+ not installed by default in recent versions of
+ <application>&xorg;</application>). The
+ <application>XDM</application> daemon program may then be
+ found in <filename>/usr/local/bin/xdm</filename>. This
+ program can be run at any time as <username>root</username>
+ and it will start managing the X display on the local machine.
+ If <application>XDM</application> is to be run every
time the machine boots up, a convenient way to do this is by
adding an entry to <filename>/etc/ttys</filename>. For more
information about the format and usage of this file, see <xref
linkend="term-etcttys"/>. There is a line in the default
<filename>/etc/ttys</filename> file for running the
- <application>XDM</application> daemon on a virtual terminal:</para>
+ <application>XDM</application> daemon on a virtual
+ terminal:</para>
<screen>ttyv8 "/usr/local/bin/xdm -nodaemon" xterm off secure</screen>
<para>By default this entry is disabled; in order to enable it
change field 5 from <literal>off</literal> to
<literal>on</literal> and restart &man.init.8; using the
- directions in <xref linkend="term-hup"/>. The first field, the
- name of the terminal this program will manage, is
+ directions in <xref linkend="term-hup"/>. The first field,
+ the name of the terminal this program will manage, is
<literal>ttyv8</literal>. This means that
<application>XDM</application> will start running on the 9th
virtual terminal.</para>
@@ -1165,8 +1209,8 @@
<title>Configuring XDM</title>
<para>The <application>XDM</application> configuration directory
- is located in <filename>/usr/local/lib/X11/xdm</filename>. In
- this directory there are several files used to change the
+ is located in <filename>/usr/local/lib/X11/xdm</filename>.
+ In this directory there are several files used to change the
behavior and appearance of
<application>XDM</application>. Typically these files will
be found:</para>
@@ -1193,7 +1237,8 @@
<row>
<entry><filename>Xservers</filename></entry>
- <entry>List of remote and local displays to manage.</entry>
+ <entry>List of remote and local displays to
+ manage.</entry>
</row>
<row>
@@ -1209,8 +1254,8 @@
<row>
<entry><filename>xdm-config</filename></entry>
- <entry>Global configuration for all displays running on
- this machine.</entry>
+ <entry>Global configuration for all displays running
+ on this machine.</entry>
</row>
<row>
@@ -1220,74 +1265,81 @@
<row>
<entry><filename>xdm-pid</filename></entry>
- <entry>The process ID of the currently running XDM.</entry>
+ <entry>The process ID of the currently running
+ XDM.</entry>
</row>
</tbody>
</tgroup>
</informaltable>
- <para>Also in this directory are a few scripts and programs used
- to set up the desktop when <application>XDM</application> is
- running. The purpose of each of these files will be briefly
- described. The exact syntax and usage of all of these files is
- described in &man.xdm.1;.</para>
+ <para>Also in this directory are a few scripts and programs
+ used to set up the desktop when <application>XDM</application>
+ is running. The purpose of each of these files will be
+ briefly described. The exact syntax and usage of all of
+ these files is described in &man.xdm.1;.</para>
<para>The default configuration is a simple rectangular login
- window with the hostname of the machine displayed at the top in
- a large font and <quote>Login:</quote> and
- <quote>Password:</quote> prompts below. This is a good starting
- point for changing the look and feel of
+ window with the hostname of the machine displayed at the
+ top in a large font and <quote>Login:</quote> and
+ <quote>Password:</quote> prompts below. This is a good
+ starting point for changing the look and feel of
<application>XDM</application> screens.</para>
<sect3>
<title>Xaccess</title>
<para>The protocol for connecting to
- <application>XDM</application>-controlled displays is called
- the X Display Manager Connection Protocol (XDMCP). This file
- is a ruleset for controlling XDMCP connections from remote
- machines. It is ignored unless the <filename>xdm-config</filename>
- is changed to listen for remote connections. By default, it does
- not allow any clients to connect.</para>
+ <application>XDM</application>-controlled displays is
+ called the X Display Manager Connection Protocol (XDMCP).
+ This file is a ruleset for controlling XDMCP connections
+ from remote machines. It is ignored unless the
+ <filename>xdm-config</filename> is changed to listen for
+ remote connections. By default, it does not allow any
+ clients to connect.</para>
</sect3>
<sect3>
<title>Xresources</title>
+
<para>This is an application-defaults file for the display
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
+ of the login program can be modified. The format is
+ identical to the app-defaults file described in the
X11 documentation.</para>
</sect3>
<sect3>
<title>Xservers</title>
+
<para>This is a list of the remote displays the chooser should
provide as choices.</para>
</sect3>
<sect3>
<title>Xsession</title>
+
<para>This is the default session script for
- <application>XDM</application> to run after a user has logged
- in. Normally each user will have a customized session script
- in <filename>~/.xsession</filename> that overrides this
- script.</para>
+ <application>XDM</application> to run after a user has
+ logged in. Normally each user will have a customized
+ session script in <filename>~/.xsession</filename> that
+ overrides this script.</para>
</sect3>
<sect3>
<title>Xsetup_*</title>
+
<para>These will be run automatically before displaying the
chooser or login interfaces. There is a script for each
- display being used, named <filename>Xsetup_</filename> followed
- by the local display number (for instance
- <filename>Xsetup_0</filename>). Typically these scripts will
- run one or two programs in the background such as
+ display being used, named <filename>Xsetup_</filename>
+ followed by the local display number (for instance
+ <filename>Xsetup_0</filename>). Typically these scripts
+ will run one or two programs in the background such as
<command>xconsole</command>.</para>
</sect3>
<sect3>
<title>xdm-config</title>
+
<para>This contains settings in the form of app-defaults
that are applicable to every display that this installation
manages.</para>
@@ -1295,13 +1347,14 @@
<sect3>
<title>xdm-errors</title>
+
<para>This contains the output of the X servers that
- <application>XDM</application> is trying to run. If a display
- that <application>XDM</application> 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
- <filename>~/.xsession-errors</filename> file on a per-session
- basis.</para>
+ <application>XDM</application> is trying to run. If a
+ display that <application>XDM</application> 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 <filename>~/.xsession-errors</filename> file on a
+ per-session basis.</para>
</sect3>
</sect2>
@@ -1309,22 +1362,22 @@
<title>Running a Network Display Server</title>
<para>In order for other clients to connect to the display
- server, you must edit the access control rules and enable the connection
- listener. By default these are set to conservative values.
- To make <application>XDM</application> listen for connections,
- first comment out a line in the <filename>xdm-config</filename>
- file:</para>
+ server, you must edit the access control rules and enable
+ the connection listener. By default these are set to
+ conservative values. To make <application>XDM</application>
+ listen for connections, first comment out a line in the
+ <filename>xdm-config</filename> file:</para>
<screen>! 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</screen>
- <para>and then restart <application>XDM</application>. Remember that
- comments in app-defaults files begin with a <quote>!</quote>
- character, not the usual <quote>#</quote>. More strict
- access controls may be desired — look at the example
- entries in <filename>Xaccess</filename>, and refer to the
- &man.xdm.1; manual page for further information.</para>
+ <para>and then restart <application>XDM</application>.
+ Remember that comments in app-defaults files begin with a
+ <quote>!</quote> character, not the usual <quote>#</quote>.
+ More strict access controls may be desired — look at the
+ example entries in <filename>Xaccess</filename>, and refer to
+ the &man.xdm.1; manual page for further information.</para>
</sect2>
<sect2>
@@ -1334,10 +1387,10 @@
<application>XDM</application> program exist. One of them,
<application>KDM</application> (bundled with
<application>KDE</application>) is described later in this
- chapter. The <application>KDM</application> display manager 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.</para>
+ chapter. The <application>KDM</application> display
+ manager 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.</para>
</sect2>
</sect1>
@@ -1356,10 +1409,11 @@
<title>Desktop Environments</title>
<para>This section describes the different desktop environments
- available for X on FreeBSD. A <quote>desktop environment</quote>
- can mean anything ranging from a simple window manager to a
- complete suite of desktop applications, such as
- <application>KDE</application> or <application>GNOME</application>.</para>
+ available for X on FreeBSD. A <quote>desktop
+ environment</quote> can mean anything ranging from a simple
+ window manager to a complete suite of desktop applications, such
+ as <application>KDE</application> or
+ <application>GNOME</application>.</para>
<sect2 id="x11-wm-gnome">
<title>GNOME</title>
@@ -1373,39 +1427,40 @@
configure their computers. <application>GNOME</application>
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
+ placed), a set of standard desktop tools and applications,
+ anda 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
<application>GNOME</application> provides. More
information regarding <application>GNOME</application> on
FreeBSD can be found on the <ulink
url="http://www.FreeBSD.org/gnome">FreeBSD GNOME
- Project</ulink>'s web site. The web site also contains fairly
- comprehensive FAQs about installing, configuring, and managing
- <application>GNOME</application>.</para>
+ Project</ulink>'s web site. The web site also contains
+ fairly comprehensive FAQs about installing, configuring,
+ and managing <application>GNOME</application>.</para>
</sect3>
<sect3 id="x11-wm-gnome-install">
<title>Installing GNOME</title>
- <para>The software can be easily installed from a package or the
- Ports Collection:</para>
+ <para>The software can be easily installed from a package
+ or the Ports Collection:</para>
<para>To install the <application>GNOME</application> package
from the network, simply type:</para>
<screen>&prompt.root; <userinput>pkg_add -r gnome2</userinput></screen>
- <para>To build <application>GNOME</application> from source, use
- the ports tree:</para>
+ <para>To build <application>GNOME</application> from source,
+ use the ports tree:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/x11/gnome2</userinput>
&prompt.root; <userinput>make install clean</userinput></screen>
- <para>For proper operation, <application>GNOME</application> requires
- the <filename>/proc</filename> filesystem to be mounted. Add</para>
+ <para>For proper operation, <application>GNOME</application>
+ requires the <filename>/proc</filename> filesystem to be
+ mounted. Add</para>
<programlisting>proc /proc procfs rw 0 0</programlisting>
@@ -1429,7 +1484,8 @@
<programlisting>gdm_enable="YES"</programlisting>
<para>Once you have rebooted,
- <application>GDM</application> will start automatically.</para>
+ <application>GDM</application> will start
+ automatically.</para>
<para>It is often desirable to start all
<application>GNOME</application> services together with
@@ -1442,23 +1498,24 @@
from the command-line by properly configuring a file named
<filename>.xinitrc</filename>.
If a custom <filename>.xinitrc</filename> is already in
- place, simply replace the line that starts the current window
- manager with one that starts
- <application>/usr/local/bin/gnome-session</application> instead.
- If nothing special has been done to the configuration file,
- then it is enough simply to type:</para>
+ place, simply replace the line that starts the current
+ window manager with one that starts
+ <application>/usr/local/bin/gnome-session</application>
+ instead. If nothing special has been done to the
+ configuration file, then it is enough simply to type:</para>
<screen>&prompt.user; <userinput>echo "/usr/local/bin/gnome-session" > ~/.xinitrc</userinput></screen>
<para>Next, type <command>startx</command>, and the
- <application>GNOME</application> desktop environment will be
- started.</para>
+ <application>GNOME</application> desktop environment will
+ be started.</para>
<note><para>If an older display manager, like
- <application>XDM</application>, is being used, this will not work.
- Instead, create an executable <filename>.xsession</filename>
- file with the same command in it. To do this, edit the file
- and replace the existing window manager command with
+ <application>XDM</application>, is being used, this will
+ not work. Instead, create an executable
+ <filename>.xsession</filename> file with the same command
+ in it. To do this, edit the file and replace the existing
+ window manager command with
<application>/usr/local/bin/gnome-session</application>:
</para></note>
@@ -1466,11 +1523,13 @@
&prompt.user; <userinput>echo "/usr/local/bin/gnome-session" >> ~/.xsession</userinput>
&prompt.user; <userinput>chmod +x ~/.xsession</userinput></screen>
- <para>Yet another option is to configure the display manager to
- allow choosing the window manager at login time; the section on
+ <para>Yet another option is to configure the display manager
+ to allow choosing the window manager at login time; the
+ section on
<link linkend="x11-wm-kde-details">KDE details</link>
- explains how to do this for <application>KDM</application>, the
- display manager of <application>KDE</application>.</para>
+ explains how to do this for <application>KDM</application>,
+ the display manager of
+ <application>KDE</application>.</para>
</sect3>
</sect2>
@@ -1482,8 +1541,9 @@
<title>About KDE</title>
<para><application>KDE</application> is an easy to use
- contemporary desktop environment. Some of the things that
- <application>KDE</application> brings to the user are:</para>
+ contemporary desktop environment. Some of the things
+ that <application>KDE</application> brings to the user
+ are:</para>
<itemizedlist>
<listitem>
@@ -1491,7 +1551,8 @@
</listitem>
<listitem>
- <para>A desktop exhibiting complete network transparency</para>
+ <para>A desktop exhibiting complete network
+ transparency</para>
</listitem>
<listitem>
@@ -1507,8 +1568,8 @@
</listitem>
<listitem>
- <para>Standardized menu and toolbars, keybindings, color-schemes,
- etc.</para>
+ <para>Standardized menu and toolbars, keybindings,
+ color-schemes, etc.</para>
</listitem>
<listitem>
@@ -1527,20 +1588,22 @@
</listitem>
</itemizedlist>
- <para><application>KDE</application> comes with a web browser called
- <application>Konqueror</application>, which is
- a solid competitor to other existing web browsers on &unix;
- systems. More information on <application>KDE</application>
- can be found on the <ulink url="http://www.kde.org/">KDE
- website</ulink>. For FreeBSD specific information and
- resources on <application>KDE</application>, consult
- the <ulink url="http://freebsd.kde.org/">KDE/FreeBSD
- initiative</ulink>'s website.</para>
+ <para><application>KDE</application> comes with a web
+ browser called <application>Konqueror</application>, which
+ is a solid competitor to other existing web browsers on
+ &unix; systems. More information on
+ <application>KDE</application> can be found on the <ulink
+ url="http://www.kde.org/">KDE website</ulink>. For FreeBSD
+ specific information and resources on
+ <application>KDE</application>, consult the <ulink
+ url="http://freebsd.kde.org/">KDE/FreeBSD
+ initiative</ulink>'s website.</para>
- <para>There are two versions of <application>KDE</application>
- available on FreeBSD. Version 3 has been around for a long
- time, and is still available in the Ports Collection though
- it's now unmaintained and partially broken. Version 4 is
+ <para>There are two versions of
+ <application>KDE</application> available on FreeBSD.
+ Version 3 has been around for a long time, and is still
+ available in the Ports Collection though it's now
+ unmaintained and partially broken. Version 4 is
punctually updated and is the default choice for
<application>KDE</application> users. They can even be
installed side by side.</para>
@@ -1550,8 +1613,8 @@
<title>Installing KDE</title>
<para>Just as with <application>GNOME</application> or any
- other desktop environment, the software can be easily installed
- from a package or the Ports Collection:</para>
+ other desktop environment, the software can be easily
+ installed from a package or the Ports Collection:</para>
<para>To install the <application>KDE 3</application> package
from the network, type:</para>
@@ -1563,8 +1626,8 @@
<screen>&prompt.root; <userinput>pkg_add -r kde4</userinput></screen>
- <para>&man.pkg.add.1; will automatically fetch the latest version
- of the application.</para>
+ <para>&man.pkg.add.1; will automatically fetch the latest
+ version of the application.</para>
<para>To build <application>KDE 3</application> from source,
use the ports tree:</para>
@@ -1605,44 +1668,46 @@
</sect2>
<sect2 id="x11-wm-kde-details">
- <title>More Details on KDE</title>
+ <title>More Details on KDE</title>
- <para>Now that <application>KDE</application> is installed on
- the system, most things can be discovered through the
- help pages, or just by pointing and clicking at various menus.
- &windows; or &mac; users will feel quite at home.</para>
+ <para>Now that <application>KDE</application> is installed
+ on the system, most things can be discovered through the
+ help pages, or just by pointing and clicking at various
+ menus. &windows; or &mac; users will feel quite at
+ home.</para>
- <para>The best reference for <application>KDE</application> is
- the on-line documentation. <application>KDE</application>
- comes with its own web browser,
- <application>Konqueror</application>, dozens of useful
- applications, and extensive documentation. The remainder of
- this section discusses the technical items that are
- difficult to learn by random exploration.</para>
+ <para>The best reference for <application>KDE</application>
+ is the on-line documentation.
+ <application>KDE</application> comes with its own web
+ browser, <application>Konqueror</application>, dozens of
+ useful applications, and extensive documentation. The
+ remainder of this section discusses the technical items
+ that are difficult to learn by random exploration.</para>
<sect3 id="x11-wm-kde-kdm">
<title>The KDE Display Manager</title>
<indexterm><primary>KDE</primary>
<secondary>display manager</secondary></indexterm>
- <para>An administrator of a multi-user system may wish to have
- a graphical login screen to welcome users.
- <link linkend="x-xdm">XDM</link> can be
- used, as described earlier. However,
- <application>KDE</application> includes an
- alternative, <application>KDM</application>, 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 (<application>KDE</application>,
- <application>GNOME</application>, or something else) to run
- after logging on.</para>
+ <para>An administrator of a multi-user system may wish to
+ have a graphical login screen to welcome users.
+ <link linkend="x-xdm">XDM</link> can be used, as described
+ earlier. However, <application>KDE</application> includes
+ an alternative, <application>KDM</application>, 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
+ (<application>KDE</application>,
+ <application>GNOME</application>, or something else) to
+ run after logging on.</para>
- <para>To enable <application>KDM</application>, different files
- need to be edited depending on the version of
+ <para>To enable <application>KDM</application>, different
+ files need to be edited depending on the version of
<application>KDE</application>.</para>
- <para>For <application>KDE 3</application>, the <literal>ttyv8</literal>
- entry in <filename>/etc/ttys</filename> has to be adapted as
+ <para>For <application>KDE 3</application>, the
+ <literal>ttyv8</literal> entry in
+ <filename>/etc/ttys</filename> has to be adapted as
follows:</para>
<programlisting>ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure</programlisting>
@@ -1659,12 +1724,13 @@
<sect2 id="x11-wm-xfce">
<title>Xfce</title>
<sect3 id="x11-wm-xfce-about">
+
<title>About Xfce</title>
<para><application>Xfce</application> is a desktop environment
based on the GTK+
- toolkit used by <application>GNOME</application>, but is much
- more lightweight and meant for those who want a simple,
+ toolkit used by <application>GNOME</application>, 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
<application>CDE</application>, found on commercial &unix;
@@ -1682,13 +1748,15 @@
</listitem>
<listitem>
- <para>Main panel similar to <application>CDE</application>, with
- menus, applets and applications launchers</para>
+ <para>Main panel similar to
+ <application>CDE</application>, with menus, applets
+ and applications launchers</para>
</listitem>
<listitem>
- <para>Integrated window manager, file manager, sound manager,
- <application>GNOME</application> compliance module, and more</para>
+ <para>Integrated window manager, file manager, sound
+ manager, <application>GNOME</application> compliance
+ module, and more</para>
</listitem>
<listitem>
@@ -1696,8 +1764,8 @@
</listitem>
<listitem>
- <para>Fast, light and efficient: ideal for older/slower machines
- or machines with memory limitations</para>
+ <para>Fast, light and efficient: ideal for older/slower
+ machines or machines with memory limitations</para>
</listitem>
</itemizedlist>
@@ -1710,7 +1778,8 @@
<title>Installing Xfce</title>
<para>A binary package for <application>Xfce</application>
- exists (at the time of writing). To install, simply type:</para>
+ exists (at the time of writing). To install, simply
+ type:</para>
<screen>&prompt.root; <userinput>pkg_add -r xfce4</userinput></screen>
@@ -1735,7 +1804,8 @@
with the <filename>/usr/local/bin/startxfce4</filename>
command; or, configure the display manager to allow
choosing a desktop at login time, as explained in
- the section on <link linkend="x11-wm-kde-kdm">kdm</link>.</para>
+ the section on
+ <link linkend="x11-wm-kde-kdm">kdm</link>.</para>
</sect3>
</sect2>
</sect1>
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1357836403.24458.YahooMailClassic>