o Update content:
- Copyright year. - X11 related stuff.
This commit is contained in:
Chin-San Huang
parent
cb069bbb36
commit
9d2e1b673f
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=30431
1 changed files with 25 additions and 83 deletions
|
|
@ -25,6 +25,7 @@
|
|||
<year>2004</year>
|
||||
<year>2005</year>
|
||||
<year>2006</year>
|
||||
<year>2007</year>
|
||||
<holder>The FreeBSD Documentation Project</holder>
|
||||
</copyright>
|
||||
|
||||
|
|
@ -6836,14 +6837,16 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
|
||||
<answer>
|
||||
|
||||
<para>The X Window System is the most widely available windowing system
|
||||
capable of running on &unix; or &unix; like systems, including
|
||||
<para>The X Window System (commonly <literal>X11</literal>) is the
|
||||
most widely available windowing system capable of running on
|
||||
&unix; or &unix; like systems, including
|
||||
&os;. <ulink url= "http://www.x.org">The X.Org
|
||||
Foundation</ulink> administers the <ulink
|
||||
url="http://www.x.org/X11_protocol.html">X protocol
|
||||
standards</ulink>. The current release of the specification
|
||||
is 11.6, so you will often see references shortened to
|
||||
<literal>X11R6</literal> or even just <literal>X11</literal>.
|
||||
url="http://en.wikipedia.org/wiki/X_Window_System_core_protocol">
|
||||
X protocol standards</ulink>, with the current reference
|
||||
implementation, version 11 release &xorg.version;,
|
||||
so you will often see references shortened to
|
||||
<literal>X11</literal>.
|
||||
</para>
|
||||
|
||||
<para>Many implementations are available for different
|
||||
|
|
@ -6894,8 +6897,12 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
&xfree86; has been replaced with &xorg; as the default
|
||||
implementation. The &xfree86; ports
|
||||
(<filename role="package">x11/XFree86-4</filename> and
|
||||
subports) remain in the ports collection and are still
|
||||
the default for &os.stable;.</para>
|
||||
subports) remain in the ports collection. But &xorg; is
|
||||
the default X11 implementation for &os; 5.3 and later.</para>
|
||||
|
||||
<para>For further information, read the <ulink
|
||||
url="&url.books.handbook;/x11.html">X11</ulink> section of the
|
||||
FreeBSD Handbook.</para>
|
||||
|
||||
<note>
|
||||
<para>The above describes the default X implementation installed.
|
||||
|
|
@ -6909,15 +6916,6 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
possible to mix-and-match pieces of each implementation;
|
||||
one must choose one or the other.</para>
|
||||
</warning>
|
||||
|
||||
<note>
|
||||
<para>The following paragraphs refer to the
|
||||
&xfree86; implementation, but most should also be applicable
|
||||
to the &xorg; implementation as well. While the default
|
||||
configuration filename for the &xorg; implementation is
|
||||
<filename>xorg.conf</filename>, it will search for
|
||||
<filename>XF86Config</filename> if it cannot find it.</para>
|
||||
</note>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
@ -6978,9 +6976,6 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
|
||||
<answer>
|
||||
|
||||
<para>The easiest way is to simply specify that you want to
|
||||
run X during the installation process.</para>
|
||||
|
||||
<para>If you would like to add X to an existing installation, you
|
||||
should use the <filename role="package">x11/xorg</filename>
|
||||
meta-port, which will build and install all the necessary
|
||||
|
|
@ -7046,24 +7041,9 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
<xref linkend="moused" remap="another section"> and set up
|
||||
moused.</para>
|
||||
|
||||
<para>Then edit <filename>/etc/X11/XF86Config</filename> and make
|
||||
<para>Then edit <filename>/etc/X11/xorg.conf</filename> and make
|
||||
sure you have the following lines:</para>
|
||||
|
||||
<programlisting>Section Pointer
|
||||
Protocol "SysMouse"
|
||||
Device "/dev/sysmouse"
|
||||
.....</programlisting>
|
||||
|
||||
<para>The above example is for &xfree86; 3.3.2 or later, and
|
||||
for &xorg; 6.7.0. For earlier versions, the
|
||||
<emphasis>Protocol</emphasis> should be
|
||||
<emphasis>MouseSystems</emphasis>.</para>
|
||||
|
||||
<para>For &xorg;, <filename>/etc/X11/xorg.conf</filename> should
|
||||
be edited. Although the pointer section format above is supported
|
||||
for compatibility reasons, the preferred format is to use an
|
||||
InputDevice section similar to the following example:</para>
|
||||
|
||||
<programlisting>Section "InputDevice"
|
||||
Option "Protocol" "SysMouse"
|
||||
Option "Device" "/dev/sysmouse"
|
||||
|
|
@ -7094,13 +7074,13 @@ Device "/dev/sysmouse"
|
|||
<literal>Buttons 5</literal> and
|
||||
<literal>ZAxisMapping 4 5</literal> to the
|
||||
<quote>InputDevice</quote> section of
|
||||
<filename>/etc/XF86Config</filename>. For example, you
|
||||
<filename>/etc/X11/xorg.conf</filename>. For example, you
|
||||
might have the following <quote>InputDevice</quote> section
|
||||
in <filename>/etc/XF86Config</filename>.</para>
|
||||
in <filename>/etc/X11/xorg.conf</filename>.</para>
|
||||
|
||||
<example>
|
||||
<title><quote>InputDevice</quote> Section for Wheeled Mouse
|
||||
in &xfree86; and &xorg; configuration file</title>
|
||||
in &xorg; configuration file</title>
|
||||
|
||||
<programlisting>Section "InputDevice"
|
||||
Identifier "Mouse1"
|
||||
|
|
@ -7135,8 +7115,8 @@ EndSection</programlisting>
|
|||
<para>To enable this feature, simply start
|
||||
<application>X</application> with the optional
|
||||
<option>-listen_tcp</option> argument:</para>
|
||||
<screen>&prompt.user; <userinput>startx
|
||||
-listen_tcp</userinput></screen>
|
||||
<screen>&prompt.user; <userinput>startx -listen_tcp</userinput>
|
||||
</screen>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
@ -7152,7 +7132,7 @@ EndSection</programlisting>
|
|||
<para>If your <keycap>Num Lock</keycap> key is on by default
|
||||
at boot-time, you may add the following line in the
|
||||
<literal>Keyboard</literal> section of the
|
||||
<filename>XF86Config</filename> file.</para>
|
||||
<filename>/etc/X11/xorg.conf</filename> file.</para>
|
||||
|
||||
<programlisting># Let the server do the NumLock processing. This should only be
|
||||
# required when using pre-R6 clients
|
||||
|
|
@ -7251,21 +7231,6 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
|
|||
|
||||
<para>(You could also just delete these lines.)</para>
|
||||
|
||||
<para>Once you have edited <filename>/etc/ttys</filename>,
|
||||
the next step is to make sure that you have enough virtual
|
||||
terminal devices. The easiest way to do this is:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /dev</userinput>
|
||||
&prompt.root; <userinput>sh MAKEDEV vty12</userinput></screen>
|
||||
|
||||
<note>
|
||||
<para>On FreeBSD 5.X and beyond you do not have to create devices
|
||||
manually if you are using <literal>DEVFS</literal>,
|
||||
since the proper device nodes will be automatically
|
||||
created under <filename
|
||||
class="directory">/dev</filename>.</para>
|
||||
</note>
|
||||
|
||||
<para>Next, the easiest (and cleanest) way to activate the
|
||||
virtual consoles is to reboot. However, if you really do not
|
||||
want to reboot, you can just shut down the X Window system
|
||||
|
|
@ -7350,10 +7315,10 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
|
|||
conflict between <command>xdm</command> and
|
||||
&man.getty.8;. One way to avoid this is to add the
|
||||
<literal>vt</literal> number in the
|
||||
<filename>/usr/X11R6/lib/X11/xdm/Xservers</filename>
|
||||
<filename>/usr/local/lib/X11/xdm/Xservers</filename>
|
||||
file.</para>
|
||||
|
||||
<programlisting>:0 local /usr/X11R6/bin/X vt4</programlisting>
|
||||
<programlisting>:0 local /usr/local/bin/X vt4</programlisting>
|
||||
|
||||
<para>The above example will direct the X server to run in
|
||||
<devicename>/dev/ttyv3</devicename>. Note the number is offset by
|
||||
|
|
@ -7508,24 +7473,6 @@ UserConfig> <userinput>quit</userinput></screen>
|
|||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="imake-tmpl">
|
||||
<para>When building an X app, <command>imake</command> cannot
|
||||
find <filename>Imake.tmpl</filename>. Where is it?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
|
||||
<para><filename>Imake.tmpl</filename> is part of the Imake
|
||||
package, a standard X application building tool.
|
||||
<filename>Imake.tmpl</filename>, as well as several header
|
||||
files that are required to build X apps, is contained in
|
||||
the X prog distribution. You can install this from
|
||||
sysinstall or manually from the X distribution
|
||||
files.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="xfree86-version">
|
||||
<para>I want to install different X server.</para>
|
||||
|
|
@ -7719,12 +7666,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
|
|||
information on hardware acceleration is available on the
|
||||
<ulink
|
||||
url="http://people.FreeBSD.org/~anholt/dri/">XFree86-4
|
||||
Direct Rendering on FreeBSD</ulink> page. Users of
|
||||
&xfree86; version 3.3 can use the Utah-GLX port found in
|
||||
<filename role="package">graphics/utah-glx</filename> to
|
||||
get limited accelerated &opengl; on the Matrox Gx00, ATI
|
||||
Rage Pro, SiS 6326, i810, Savage, and older NVIDIA
|
||||
chips.</para>
|
||||
Direct Rendering on FreeBSD</ulink> page.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
|
|
|
|||
Loading…
Reference in a new issue