summaryrefslogtreecommitdiff
path: root/sgml/OpenBSD.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'sgml/OpenBSD.sgml')
-rw-r--r--sgml/OpenBSD.sgml559
1 files changed, 222 insertions, 337 deletions
diff --git a/sgml/OpenBSD.sgml b/sgml/OpenBSD.sgml
index 37d274f..142ae16 100644
--- a/sgml/OpenBSD.sgml
+++ b/sgml/OpenBSD.sgml
@@ -1,10 +1,16 @@
-<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN">
+<!DOCTYPE linuxdoc PUBLIC "-//XFree86//DTD linuxdoc//EN" [
+<!ENTITY % defs SYSTEM "defs.ent"> %defs;
+]>
<article>
-<title>README for XFree86 3.3.2 on OpenBSD
+<title>README for XFree86 &relvers; on OpenBSD
<author>
Matthieu Herrb
-<Date>Last modified on: 20 February 1998
+<Date>Last modified on: 9 November 2002
+
+<ident>
+$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/OpenBSD.sgml,v 1.30 2003/02/25 19:31:01 dawes Exp $
+</ident>
<toc>
@@ -12,66 +18,131 @@ Matthieu Herrb
<sect>What and Where is XFree86?
<p>
-XFree86 3.3.2 is a port of X11R6.3 that supports several versions of
-Intel-based Unix. It is derived from X386 1.2, which was the X server
-distributed with X11R5. This release consists of many new features
-and performance improvements as well as many bug fixes. The release
-is available as source patches against the X Consortium X11R6.3 code, as
-well as binary distributions for many architectures.
+XFree86 is an Open Source version of the X Window System that supports
+several UNIX(R) and UNIX-like operating systems (such as Linux, the BSDs
+and Solaris x86) on Intel and other platforms. This version is compatible
+with X11R6.6.
See the <htmlurl url="COPYRIGHT.html" name="Copyright Notice">.
-The sources for XFree86 are available by anonymous ftp from:
+<![ %notsnapshot [
+The sources for XFree86 &relvers; are available by anonymous ftp from:
-<htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/current"
-url="ftp://ftp.XFree86.org/pub/XFree86/current">
+<htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/&relvers;"
+url="ftp://ftp.XFree86.org/pub/XFree86/&relvers;">
-Binaries for OpenBSD 2.2 are available from:
+Binaries for OpenBSD/i386 3.2 and later are available from:
-<htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/current/binaries/"
-url="ftp://ftp.XFree86.org/pub/XFree86/current/binaries/OpenBSD">
+<htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/&relvers;/binaries/OpenBSD"
+url="ftp://ftp.XFree86.org/pub/XFree86/&relvers;/binaries/OpenBSD">
A list of mirror sites is provided by
-<htmlurl name="ftp://ftp.XFree86.org/pub/XFree86/MIRRORS"
-url="ftp://ftp.XFree86.org/pub/XFree86/MIRRORS">
+<htmlurl name="http://www.xfree86.org/MIRRORS.shtml"
+url="http://www.xfree86.org/MIRRORS.shtml">
+]]>
<p>
-XFree86 3.3.2 also builds on other OpenBSD architectures. See section
+XFree86 also builds on other OpenBSD architectures. See section
<ref id="otherarch" name="Building on other architectures"> for details.
<sect>Bug Reports for This Document
<p>
-Send email to <em/matthieu@laas.fr/ (Matthieu Herrb) or
-<em/XFree86@XFree86.org/ if you have comments or suggestions about
+Send email to <email>herrb@xfree86.org</email> (Matthieu Herrb) or
+<email>XFree86@XFree86.org</email> if you have comments or suggestions about
this file and we'll revise it.
-<sect>New features in this release
+<sect>New OS dependent features
+<p>
+See the <htmlurl url="RELNOTES.html" name="Release Notes"> for
+non-OS dependent new features in XFree86 &relvers;.
+
+<sect1>New OS related features in 4.3
+<p>
+<itemize>
+<item>Support for some VGA cards on OpenBSD/alpha
+</itemize>
+
+<sect1>New OS dependent features in 4.2
+<p>
+<itemize>
+<item>Support for OpenBSD/macppc on the ATI Rage128 based
+Power Macintoshes.
+<item>Support for building clients on OpenBSD/sparc64.
+</itemize>
+
+<sect1>New OS dependent features in 4.0.3
+<p>
+<itemize>
+<item>Support for the wscons console driver in post 2.8 OpenBSD.
+<item>A fix for multi-threaded libraries support.
+</itemize>
+
+<sect1>New OS dependent features in 4.0.2
+<p>
+<itemize>
+<item>Support for the OpenBSD ports tree,
+<item>Preliminary support for the macppc architecture (clients build
+and work, the server doesn't work yet),
+<item>xdm now writes an utmp entry,
+<item>startx now creates an Xauthority magic cookie for the display.
+</itemize>
+
+<sect1>New OS dependent features in 4.0.1
<p>
-<enum>
-<item>See the <htmlurl url="RELNOTES.html" name="Release Notes"> for
-non-OS dependent new features in XFree86 3.3.2.
-</enum>
+<itemize>
+<item>Several features from the OpenBSD X11 tree were merged into xdm:
+<itemize>
+<item> support for Kerberos IV authentication
+<item>use the arc4random(4) random number generator
+<item>add a new resource "allowRootLogin", which can be used to disable
+ root logins through xdm
+<item>log failed logins to syslogd
+<item>verify that the shell is valid using /etc/shell
+<item>verify that the account hasn't expired
+</itemize>
+<item>The Xsun server can be built again on OpenBSD/sparc.
+</itemize>
+
+<sect1>New OS dependent features in 4.0
+<p>
+<itemize>
+<item>Multi-thread safe libraries are built by default on OpenBSD 2.6
+ and later,
+<item>Preliminary APM support.
+</itemize>
+
+<sect1>New OS dependent features in 3.9.18
+<p>
+<itemize>
+<item>Support for USB mices has been added on OpenBSD.
+<item>Soft-booting secondary cards through the int10 BIOS interface is
+now possible using the x86emu real mode emulator.
+</itemize>
+
+<sect1>New OS dependent features in 3.9.17
+<p>
+<itemize>
+<item><em>Silken mouse</em> is supported for serial mices, and, under
+post 2.6 OpenBSD-current for PS/2 mices.
+<item>MTRR Write Combining is enabled under post 2.6 OpenBSD-current.
+</itemize>
<sect>Installing the Binaries
<p>
-Refer to section 5 of the <htmlurl url="RELNOTES.html" name="Release
-Notes"> for detailed installation instructions.
+Refer to the <htmlurl url="Install.html" name="Installation Document">
+for detailed installation instructions.
<sect>Configuring X for Your Hardware
-
<p>
-The <tt/XF86Config/ file tells the X server what kind of monitor,
+The <tt>/etc/X11/XF86Config</tt> file tells the X server what kind of
+monitor,
video card and mouse you have. You <em/must/ create it to tell the
server what specific hardware you have.
<p>
-XFree86 3.2 introduced a new, user-friendly configuration utility
-called <bf/XF86Setup/. It has to be run as root. Refer to its
-documentation for details about its use.
-<p>
You'll need info on your hardware:
<itemize>
<item>Your mouse type, baud rate and its /dev entry.
@@ -79,21 +150,15 @@ You'll need info on your hardware:
<item>Your monitor's sync frequencies.
</itemize>
-
The recommended way to generate an <tt/XF86Config/ file is to use the
-<tt/XF86Setup/ utility. The xf86config text utility is still there
-for the (few) cases where XF86Setup can't be used. Also, there is a
+<tt/xf86cfg/ utility. The xf86config text utility is still there
+for the (few) cases where xf86cfg can't be used. Also, there is a
sample file installed as <tt>/usr/X11R6/lib/X11/XF86Config.eg</tt>,
which can be used as a starting point.
-For details about the <tt/XF86Config/ file format, refer to the
-<em>XF86Config(5)</em> manual page.
-In order to protect your hardware from damage, the server will no
-longer read <tt>XF86Config</tt> files from a user's home directory,
-but requires that it be in <tt>/etc/XF86Config</tt>,
-<tt>/usr/X11R6/lib/X11/XF86Config.hostname</tt> or
-<tt>/usr/X11R6/lib/X11/XF86Config</tt>.
+For details about the <tt/XF86Config/ file format, refer to the
+<em><htmlurl name="XF86Config(5)" url="XF86Config.5.html"></em> manual page.
Once you've set up a XF86Config file, you can fine tune the video
modes with the <tt>xvidtune</tt> utility.
@@ -101,115 +166,44 @@ modes with the <tt>xvidtune</tt> utility.
<sect1>About mouse configuration
<p>
-If your serial mouse does not work try using <tt>kermit</tt> or
-<tt>tip</tt> to connect to the mouse serial port and verify that it
-does indeed generate characters.
-<p>
-The OpenBSD pms driver provides both "raw" and "cooked"
-(translated) modes. "raw" mode does not do protocol translation, so
-XFree86 would use the <bf>PS/2</bf> protocol for talking to the device
-in that mode. "cooked" mode is the old BusMouse translation.
-By default, the driver runs in "cooked" mode. It can be switched using
-ioctls or by opening the first minor device which is <tt>/dev/psm0</tt>.
-<p>
-Only standard PS/2 mice are supported by this driver. Newest PS/2
-mice that send more than three bytes at a time (especially
-intellimouse, or mouseman+ with a "3D" roller) are not supported yet.
+XFree86 &relvers; has support for the mouse driver included in
+the new <bf/wscons/ console driver introduced by OpenBSD-2.9.
+Specify ``<tt/wsmouse/'' as the protocol and
+``<tt>/dev/wsmouse0</tt>'' as the device in <tt>/etc/X11/XF86Config</tt>
+if you're using OpenBSD-2.9 or later with a PS/2 or USB mouse.
<p>
See <htmlurl url="mouse.html" name="README.mouse"> for general
instruction on mouse configuration in XFree86.
-<sect1>Other input devices
-<p>
-XFree86 supports the dynamic loading of drivers for external
-input devices using the <tt/XInput/ extension. Currently supported
-devices are:
-<itemize>
-<item>Joystick (<tt/xf86Jstk.so/)
-<item>Wacom tablets (Wacom IV protocol only, <tt/xf86Wacom.so/)
-<item>SummaSketch tablets (<tt/xf86Summa.so/)
-<item>Elographics touchscreen (<tt/xf86Elo.so/)
-</itemize>
-To use a specific device, add the line
-<tscreen>
-<tt/load/ <tt/"/<em/module/<tt/"/
-</tscreen>
-in the <bf/Module/ section of <tt/XF86Config/, where <em/module/ is
-the name of the <tt/.so/ file corresponding to your device.
-You also need to set up a <bf/XInput/ section in <tt/XF86Config/.
-Refer to the <em>XF86Config(5)</em> man page for detailed
-configuration instructions.
-<p>
-You can then change the device used to drive the X pointer with the
-<em/xsetpointer(1)/ command.
-<p>
-For joystick support, you'll need to enable the joystick device
-driver in the kernel. See <em/joy(4)/ for details.
+<sect>Running X
-<sect1>Configuring PEX and XIE extensions
<p>
-The PEX and XIE extensions are supported as external modules.
-If you want to have access to these extensions, add the following
-lines to the <bf/Module/ section of <tt/XF86Config/:
-<tscreen><verb>
- load "pex5.so"
- load "xie.so"
-</verb></tscreen>
-<sect>Installing Xdm, the display manager
+<sect1>Starting xdm, the display manager
<p>
-The file <tt>xc/lib/Xdmcp/WrapHelp.c</tt> is not available in
-France (where the binary distribution is built) so support for
-XDM-AUTHORIZATION-1 is not included here. You'll have to get
-WrapHelp.c and rebuild xdm after having set <tt/HasXdmAuth/ in
-<tt/host.def/.
-
-The file is available within the US; for
-details see <htmlurl name="ftp.x.org:/pub/R6/xdm-auth/README"
-url="ftp://ftp.x.org/pub/R6/xdm-auth/README">.
-
To start the display manager, log in as root on the console and type:
``<tt/xdm -nodaemon/''.
-You can start xdm automatically on bootup un-commenting the following
-code in <tt>/etc/rc.local</tt>:
-
+You can start xdm automatically on bootup by changing the line
<tscreen><verb>
- if [ -x /usr/X11R6/bin/xdm ]; then
- echo -n ' xdm'; /usr/X11R6/bin/xdm
- fi
+xdm_flags=NO # for normal use: xdm_flags=""
</verb></tscreen>
-
-On the default OpenBSD 2.2 installation, you will also need to create
-the virtual console device for the X server:
+to:
<tscreen><verb>
-cd /dev
- ./MAKEDEV ttyC5
+xdm_flags="" # for normal use: xdm_flags=""
</verb></tscreen>
-
-It's also better to specify explicitly the virtual console to be used
-by the X server. If you're experimenting keyboards lockup with xdm, in
-<tt>/usr/X11R6/lib/X11/xdm/Xservers</tt>, replace the line:
-<tscreen><verb>
-:0 local /usr/X11R6/bin/X
-</verb></tscreen>
-by:
-<tscreen><verb>
-:0 local /usr/X11R6/bin/X vt06
-</verb></tscreen>
-
-<sect>Running X
+in <tt>/etc/rc.conf</tt>.
<p>
-8mb of memory is a recommended minimum for running X. The server,
-window manager and an xterm take about 4 Mb of memory themselves. On
-a 4Mb system that would leave nothing left over for other applications
-like gcc that expect a few meg free. X will work with 4Mb of memory,
-but in practice compilation while running X can take 5 or 10 times as
-long due to constant paging.
+Note that the binary distributions of XFree86 for OpenBSD on
+ftp.xfree86.org and its mirrors don't include
+support for the XDM-AUTHORIZATION-1 protocol, because of the US export
+rules.
+<sect1>Running X without the display manager
+<p>
The easiest way for new users to start X windows is to type: ``<tt/startx
>&amp; startx.log/''. Error messages are lost unless you redirect them
because the server takes over the screen.
@@ -226,224 +220,127 @@ To make sure X support is enabled under OpenBSD, the following
line must be in your config file in <tt>/sys/arch/i386/conf</tt>:
<tscreen>
- options XSERVER
+ option APERTURE
</tscreen>
-The server supports the two standard OpenBSD/i386
-console drivers: pccons and pcvt. They are detected at runtime and no
-configuration of the server itself is required.
-
-
+<sect1>Console drivers
<p>
-The pcvt console driver is now the default in OpenBSD. It offers
-several virtual consoles and international keyboard support.
+The server supports the standard OpenBSD/i386
+console drivers: pcvt and wscons. They are detected at runtime and no
+configuration of the server itself is required.
<p>
-When not using XKB, the server can read the actual keymap from
-the keyboard driver and use to build the X keymap. Be sure to use
-``<tt/RightAlt ModeShift/'' in <tt/XF86Config/ to have the right <bf/Alt/ key
-behave as <bf/AltGr/.
+The pcvt console driver is the default in OpenBSD up to OpenBSD 2.8.
+It offers several virtual consoles and international keyboard support.
<p>
-Syscons and codrv are not bundled with OpenBSD. They are available by
-anonymous FTP from a number of sites. They are not supported by the
-XFree86 binary distribution anymore. You can compile support for them
-by adding -DSYSCONS_SUPPORT or -DCODRV_SUPPORT to
-<tt/XFree86ConsoleDefines/ in <tt/xf86site.def/. See the section <ref
-id="console-drivers" name="Console drivers"> for details.
-
-
+OpenBSD 2.9 and later has switched to the wscons console
+driver. This console driver has a pcvt compatibility mode for X
+support.
<sect1>Aperture Driver
<p>
By default OpenBSD includes the BSD 4.4 kernel security
-feature that disable access to the <tt>/dev/mem</tt> device when in
-multi-users mode. But XFree86 servers can take advantage (or require)
-linear access to the display memory.
-
-The P9000, Mach64 and AGX servers require linear memory access, other
-accelerated servers can take advantage of it, but do not require it.
-Some drivers in the SVGA server require linear memory access too,
-notably the Matrox driver.
-
-There are two ways to allow XFree86 to access linear memory:
-<enum>
-<item>Disable the kernel security feature by adding
- `option INSECURE' in the kernel configuration file and build a new
- kernel.
-
-In OpenBSD 2.2 and later, you will also need to comment out the line
-initializing <tt/securelevel/ to 1 in <tt>/etc/rc.securelevel</tt>.
+feature that disables access to the <tt>/dev/mem</tt> device when in
+multi-user mode. But the XFree86 server requires
+linear access to the display memory in most cases.
-
-<item>Install the aperture driver:
-<enum>
-<item> The first step is highly dependent from your exact operating
-system version:
-<itemize>
-<item> OpenBSD 2.0
- <p>
- Use the aperture driver from /usr/lkm:
-
- add the following lines to the end of <tt>/etc/rc.local</tt>:
+OpenBSD now requires the aperture driver to be enabled for all X
+servers, because the aperture driver also controls access to the
+I/O ports of the video boards.
+<p>
+To enable the aperture driver, once included in the kernel, set
<tscreen><verb>
- KERNDIR=/usr/lkm
- if [ -f ${KERNDIR}/ap.o ]; then
- modload -o ${KERNDIR}/ap -e ap -p ${KERNDIR}/apinstall ${KERNDIR}/ap.o
- fi
+machdep.allowaperture=2
</verb></tscreen>
-
-<item> OpenBSD 2.1, 2.2
- <p>
- Uncomment the lines loading the aperture driver from
- <tt>/etc/rc.securelevel</tt>
-
-<item> OpenBSD-current
- <p>
- In addition to the loadable kernel module, you can now use an
- in-kernel aperture driver. Add 'option APERTURE' to your kernel
- configuration file, build and install the new kernel and run
- <tt>./MAKEDEV std</tt> in <tt>/dev</tt>. Edit
- <tt>/etc/sysctl.conf</tt> to set the variable
- <bf>machdep.allowaperture</bf> to 1.
-</itemize>
-
-<item> Reboot your system. XFree86 will auto-detect the aperture
- driver if available.
-</enum>
-
- <bf/Warning:/ if you boot another kernel than <tt>/bsd</tt>,
- loadable kernel modules can crash your system. Always boot in
- single user mode when you want to run another kernel.
-
+in <tt>/etc/sysctl.conf</tt>. See the
+<htmlurl name="xf86(4)" url="http://www.openbsd.org/cgi-bin/man.cgi?query=xf86&amp;apropos=0&amp;sektion=4&amp;manpath=OpenBSD+Current&amp;arch=i386&amp;format=html">
+manual page for details.
+<p>
+Another (less recommended) way to enable linear memory and I/O ports
+access is to disable the kernel security feature by
+initializing <tt/securelevel/ to -1 in <tt>/etc/rc.securelevel</tt>.
<p>
<quote>
- <bf/Caveat:/ the aperture driver only allows one access at a time
- (so that the system is in the same security state once X is
- launched). This means that if you run multiple servers on multiples
- VT, only the first one will have linear memory access.
- Use 'option INSECURE' if you need more that one X server at a time.
+<bf/Caveat:/ the aperture driver only allows one access at a time
+(so that the system is in the same security state once X is
+launched). This means that if you run multiple servers on multiple
+virtual terminals, only the first one will have linear memory access.
+Set <tt/securelevel/ to -1 if you need more that one X server at a time.
</quote>
-</enum>
-
-
<sect1>MIT-SHM
<p>
OpenBSD supports System V shared memory. If XFree86
detects this support in your kernel, it will support the MIT-SHM
extension.
- To add support for system V shared memory to your kernel add the
- lines:
-
-<tscreen><verb>
- # System V-like IPC
- options SYSVMSG
- options SYSVSEM
- options SYSVSHM
-</verb></tscreen>
-
- to your kernel config file. Then from <tt>/sys/arch/i386/config</tt>, type:
-
-<tscreen><verb>
- # rm -f ../compile/<KERNEL-NAME>/*
- # config <KERNEL-NAME>
- # cd ../compile/<KERNEL-NAME>
- # make depend
- # make
-</verb></tscreen>
-
- Then install your new kernel and re-boot:
-
-<tscreen><verb>
- # cp /bsd /obsd
- # cp bsd /
- # reboot
-</verb></tscreen>
-
-
<sect> Rebuilding the XFree86 Distribution
-<p>
-The server link kit allow you to rebuild just the X server with a
-minimum amount of disk space. Just unpack it, make the appropriate
-changes to the <tt/xf86site.def/, type ``<tt>./mkmf</tt>'' and
-``<tt/make/'' to link the server. See <tt>/usr/X11R6/lib/Server/README</tt>
-for more info.
-
-See <htmlurl url="INSTALL.html" name="INSTALL"> for instructions on
-unbundling and building the source distribution.
-
You should configure the distribution by editing
-<tt>xc/config/cf/xf86site.def</tt> before compiling. To compile the
+<tt>xc/config/cf/host.def</tt> before compiling. To compile the
sources, invoke ``<tt/make World/'' in the xc directory.
-<sect1>Console drivers<label id="console-drivers">
+<p>
+Note that OpenBSD project now has its own source tree, based on
+the XFree86 source tree, with some local modifications. You may want
+to start with this tree to rebuild from sources. The OpenBSD XF4
+source tree is available by anoncvs from all OpenBSD anoncvs
+servers. See <htmlurl url="http://www.openbsd.org/anoncvs.html"
+name="http://www.openbsd.org/anoncvs.html"> for details on anoncvs.
+
+<label id="otherarch">
+
+<p>
+XFree86 also compiles on other OpenBSD architectures.
+<sect1>XFree86 on OpenBSD/alpha
<p>
-XFree86 3.3.2 has a configuration option to select the console
-drivers to use in <tt/xf86site.def/:
+The XFree86 server is known to work on some VGA cards in alpha
+machines that support BWX I/O, with OpenBSD 3.2 and higher.
+<p>
+The following cards have been successfully tested for now:
<itemize>
-<item> if you're using pccons put:
-<tscreen><verb>
- #define XFree86ConsoleDefines -DPCCONS_SUPPORT
-</verb></tscreen>
-<item>if you're using pcvt put:
-<tscreen><verb>
- #define XFree86ConsoleDefines -DPCVT_SUPPORT
-</verb></tscreen>
-<item>if you're using syscons put:
-<tscreen><verb>
- #define XFree86ConsoleDefines -DSYSCONS_SUPPORT
-</verb></tscreen>
-<item>if you're running codrv put:
-<tscreen><verb>
- #define XFree86ConsoleDefines -DCODRV_SUPPORT
-</verb></tscreen>
+<item>3DLabs Permedia 2 (8, 15, 16 and 24 bits depth)
+<item>ATI Rage Pro (works with 'Option "NoAccel"')
+<item>Cirrus Logic CL5430 (works with 'Option "NoAccel"')
+<item>Cirrus Logic GD5446 (8, 16 and 24 bits depth)
+<item>Matrox MGA 2064 (8, 16 and 24 bits depth)
</itemize>
-If you don't define <bf/XFree86ConsoleDefines/ in <tt/xf86site.def/ the
-pccons and pcvt drivers will be supported.
-
-
-<sect1>console.h and ioctl_pc.h files:
-
<p>
-If you want to build a server supporting codrv and you
-don't already have the corresponding header file
-<tt/ioctl_pc.h/ installed in <tt>/usr/include/machine</tt>, then
-install the copy that is supplied in
-<tt>xc/programs/Xserver/hw/xfree86/etc</tt>. If you run
-OpenBSD-current you probably want to install it in
-<tt>/usr/src/sys/arch/i386/include</tt> too, so that it get
-reinstalled each time you run <tt/make includes/.
-
-If you have installed the codrv console driver, this
-file should be taken from your installed version of the driver.
-
-The <tt/console.h/ file for syscons isn't distributed with XFree86
-anymore. You should get it from the syscons distribution.
-
-
-<sect1>Building on other architectures<label id="otherarch">
+Note that this version of XFree86 doesn't work on TGA cards. The
+version shipped with OpenBSD 3.1 and higher includes an OS-specific
+driver <em/wsfb/ that is used to support TGA cards.
+<sect1>XFree86 on OpenBSD/macppc
<p>
-XFree86 3.3.2 also compiles on other OpenBSD architectures.
-
-The XFree86 servers can also been built on OpenBSD/mips. The S3 server
-has been tested on an Acer Mips system with a S3/928 board. Contact
-Per Fogelstrom (pefo@OpenBSD.org) for details.
+The XFree86 server is currently known to work on the G4 Macs and new
+iBooks with ATI Rage 128 cards running OpenBSD 3.0 or later.
+Other machines are more or less untested. Earlier OpenBSD versions
+lack some kernel support for it.
+<p>
+Use xf86config to build a /etc/X11/XF86Config file before starting
+the server for the first time.
+<p>
+For the Titanium Powerbook G4, you can try the following mode line in
+<tt>/etc/X11/XF86Config</tt> to match the flat panel resolution:
-The Xsun server patches from Dennis Ferguson and Matthew Green for
-NetBSD have been integrated in
-<tt>xc/programs/Xserver/hw/sun</tt>. The Xsun server can be built on
-the sparc and the sun3.
+<tscreen><verb>
+Modeline "1152x768" 64.995 1152 1213 1349 1472 768 771 777 806 -HSync -VSync
+</verb></tscreen>
-The client side of XFree86 also builds on the alpha, pmax, amiga,
-mac68k and mvme68k architectures.
+<sect1>XFree86 on OpenBSD/sparc
+<p>
+OpenBSD 3.2 on sparc switched to the wscons device driver and now uses
+the OS specific <em/wsfb/ driver in the XFree86 server. This driver is
+not included in XFree86 4.3. Please use the version shipped with
+OpenBSD instead.
-Problems with this port should be reported directly to the OpenBSD
-mailing lists rather than to the xfree86 mailing list.
+<sect1>XFree86 on OpenBSD/sparc64
+<p>
+This version of XFree68 only has support for X clients on
+OpenBSD/sparc64. Note that the version shipped with OpenBSD also has
+support for the X server on both SBus and PCI based machines.
<sect>Building New X Clients
@@ -456,33 +353,21 @@ necessary and type ``<tt/make/''. Whenever you install additional man
pages you should update <tt/whatis.db/ by running ``<tt>makewhatis
/usr/X11R6/man</tt>''.
-To avoid the ``Virtual memory exhausted'' message from cc while
-compiling, increase the data and stack size limits (in csh type ``<tt/limit
-datasize 32M/'' and ``<tt/limit stacksize 16M/'').
-
-
<sect> Thanks
<p>
-Many thanks to:
-<itemize>
-<item><bf/Pace Willison/ for providing the initial port to 386BSD.
-<item><bf/Amancio Hasty/ for fixing cursor restoration, mouse bugs
-and many others.
-<item><bf/Christoph Robitschko/ for fixing <tt/com.c/ and thus select().
-<item><bf/Nate Williams/ for the patchkit support for X.
-<item><bf/Rod Grimes/ and <bf/Jack Velte/ of Walnut Creek Cdrom for use
- of their machines in preparing the FreeBSD binary release.
-</itemize>
-
-<verb>
-$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/OpenBSD.sgml,v 1.1.2.5 1998/02/26 13:59:07 dawes Exp $
-
-
-
-
-
-$Xorg: OpenBSD.sgml,v 1.3 2000/08/17 19:51:02 cpqbld Exp $
-</verb>
+Many thanks to all people who contributed to make XFree86 work on
+*BSD, in particular:
+<bf/David Dawes/,
+<bf/Todd Fries/,
+<bf/Rod Grimes/,
+<bf/Charles Hannum/,
+<bf/Amancio Hasty/,
+<bf/Christoph Robitschko/,
+<bf/Matthias Scheler/,
+<bf/Michael Smith/,
+<bf/Ignatios Souvatzis/,
+<bf/Jack Velte/,
+<bf/Nate Williams/ and
+<bf/Pace Willison/.
</article>
-