Instructions for getting X running on your NetBSD system
========================================================
by Bob Nestor <rnestor@metronet.com>

----------------------------
Installing and configuring X
----------------------------
Get the lastest version of the X distribution sets from the NetBSD mirror
site of your choice.  For mac68k users this is probably
<ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-1.3/mac68k/binary/sets/>

Follow the instructions in the INSTALL document on how to install the X
distribution sets and configure your system files.  Once you have finished,
type "startx" and enjoy!

-------------------------------------------
Using or emulating additional mouse buttons
-------------------------------------------

In order to access the other two mouse buttons, you can do one of two
things.  If you'd like to use your keyboard and you have a one-button
mouse, these two keys map to mouse buttons:
	<OPTION>+<left-arrow>		middle mouse button (button 2)
	<OPTION>+<right-arrow>		right mouse button (button 2)

As of NetBSD 1.3, you can also use:
	<OPTION>+1			left mouse button (button 1)
	<OPTION>+2			middle mouse button (button 2)
	<OPTION>+3			right mouse button (button 3)

Or, if you have a three-button programmable mouse, you can set your
mouse buttons to the above key-sequences.  My Animas MacPro 3-button
mouse seems to work fine for me with these settings.  Make sure that you
can set the keys to 
	OPTION down
	left-arrow down
	left-arrow up
	OPTION up
because that's what the driver expects.
(Sorry, I haven't provided keyboard alternatives for buttons 4 and 5. :)

There are a number of 3-button mice that are directly supported by the
kernel, including the MicroSpeed Mouse Deluxe, the Mouse System A3 mouse,
and the Logitech Mouseman/Trackman mice/trackballs.

----------------------------------------
NetBSD/mac68k, X11, and Shared Libraries
----------------------------------------

The NetBSD X distribution uses shared libraries, and thus you need
to tell ld.so (the dynamic loader) where the new shared libraries
reside.  The most straigtforward way to do this is to create
/etc/ld.so.conf (if it doesn't already exist) and add the following to it:

# add the X shared libraries to the runtime linker search path
/usr/X11R6/lib

If ld.so complains about shared library version mismatches or
undefined symbols, this is because your shared libraries are most likely
older than the version of X you have installed, and you need to get new
shared libraries which are at least as recent as those the X11 distribution
was compiled against.  You can find newer libraries in the same release
directory as the X distribution sets.  The shared libraries are in the
base.tgz set.

----------------------------------
Re-Enabling the Up/Down Arrow Keys
----------------------------------

If you're using an older X11 release, you'll probably find that the up/down
arrow keys no longer work under X.  Try creating a .xmodmaprc file with the
following contents:

! .xmodmaprc  OTH 4/19/95
! Fix the Macintosh "Up" and "Down" keys.
keysym 0xffe8 = Up
keysym 0xffe4 = Down

	...and adding the following to your .xinitrc file:

xmodmap .xmodmaprc

Of course, if you upgrade to NetBSD 1.3 (and the X distribution that goes
along with it), the above won't be necessary.

-------------------------------------
Additional instructions for xdm setup
-------------------------------------

If you wish to use xdm (the X Display Manager), you'll need to change the
line in /etc/rc.conf to read like so:

xdm=NO			xdm_flags=""            # x11 display manager


Now create or modify the following files:

----- file /usr/X11R6/lib/X11/xdm/Xlogin
#!/bin/sh
#
# Nothing needed in this file for a standard setup.

---- file /usr/X11R6/lib/X11/xdm/Xreset
#!/bin/sh
#
# Update the utmp file and remove the name of the user who was using
# the display
#
sessreg -d -l $DISPLAY -x /usr/X11R6/lib/X11/xdm/Xservers $USER
exit 0

---- file /usr/X11R6/lib/X11/xdm/Xresources
!
! This is a standard X Resource file.  Check the xdm documentation for
!  what resources can be defined here.  The only one currently defined
!  is the Login Banner which would otherwise default to "X Window Server".
!
xlogin*greeting: NetBSD/mac68k

----- file /usr/X11R6/lib/X11/xdm/Xservers
!
! Define all the display terminals and systems we are willing to Serve.
!  The only definition currently here is the one for our System Console.
!
:0 Mac-display local /usr/X11R6/bin/X :0


----- file /usr/X11R6/lib/X11/xdm/Xsession
#!/bin/sh
# Xsession
#
# This is the program that is run as the client for the display manager.
#
# If the users ".xsession" file contains errors we'll never get a
#  display up for him.  In this case put up a standrd "xterm"
#  window so he at least has some ability to fix his ".xsession"
#  file without SysAdmin assistance (we hope).
#
case $# in
1)
     case $1 in
     failsafe)
          exec xterm -geometry 80x24-0-0
          ;;
     esac
esac

startup=$HOME/.xsession
resources=$HOME/.Xresources

#
# If the user account has a ".xsession" file then we'll try to
#  bring up the clients defined in that file.  Otherwise we will
#  give the user a couple of standard clients to play with.
#
if [ -f "$startup" ]; then
     exec "$startup"
else
     if [ -f "$resources" ]; then
          xrdb -load "$resources"
     fi
     xman -geometry +10-10 &
     exec xterm &
     twm
fi

----- file /usr/X11R6/lib/X11/xdm/Xstartup
#!/bin/sh
#
# Update the utmp file so we know who is currently running on the display.
#  We could check the /etc/nologins file at this point and prevent the
#  user from getting logged on by returning an exit status of "1".  See
#  the xdm documentation for examples.
#
sessreg -a -l $DISPLAY -x /usr/X11R6/lib/X11/xdm/Xservers $USER
exit 0

----- file /usr/X11R6/lib/X11/xdm/Xsetup
#!/bin/sh
#
# Before we even get the Login window up, put up a "Console Log" window.
#  We always keep this up even when a user logs in. He can always minimize
#  this window if he wants.  The reason for putting this window up is to
#  catch all the messages that are normally logged to the console and/or to
#  syslog.  If we don't catch them they will really mess up our windows when
#  a message is sent to the console.  On some systems its possible for the
#  user to fire up the "xconsole" client himself, but on BSD systems this
#  requires ownership of the console device.  Putting up the console
#  window here solves that problem since this script is executed by xdm
#  with root privs.  As an added benefit messages that get logged to the
#  console when nobody is logged onto the console get displayed in this
#  window which peacefully co-exists with the standard xdm Login Window.
#
xconsole -geometry 280x60-0-0 -notify -verbose -exitOnFail &

----- file /usr/X11R6/lib/X11/xdm/xdm-config
!
! Another standard X Resource file, but this one controls xdm itself.
!  Note that if this file doesn't exist (or isn't named xdm-config)
!  then xdm won't be started during the boot process as defined in
!  /etc/rc.
!
DisplayManager.servers:       /usr/X11R6/lib/X11/xdm/Xservers
DisplayManager.errorLogFile:  /usr/X11R6/lib/X11/xdm/xdm-errors
DisplayManager.pidFile:       /usr/X11R6/lib/X11/xdm/xdm-pid
DisplayManager*resources:     /usr/X11R6/lib/X11/xdm/Xresources
DisplayManager*reset:         /usr/X11R6/lib/X11/xdm/Xreset
DisplayManager*setup:         /usr/X11R6/lib/X11/xdm/Xsetup
DisplayManager*startup:       /usr/X11R6/lib/X11/xdm/Xstartup
DisplayManager*session:       /usr/X11R6/lib/X11/xdm/Xsession
DisplayManager._0.authorize:  true
DisplayManager*authorize:     false
DisplayManager.daemonMode:    true


----------------------------------------------------------------------------
files which go into the user directories

----- file $HOME/.xinitrc
#!/bin/sh
#
# This file is only used if the user starts X with the "startx" or "xinit"
#  command.  You can add as many client startups as you want to, just
#  remember to put all of them into the background with the "&". One, and
#  only one, command which starts a client must be placed in the
#  foreground, i.e. started without the trailing "&".  The foregrond
#  client should not terminate, for when it does xdm will assume the user
#  session has completed and will terminal all the remaining user clients.
#  Most Window Managers have an "exit" function defined in the pop-up
#  menu that is used to terminate the session.  Therefore, if the Window
#  Manager is the designated foreground client program, the "exit" option
#  can be used to terminate the entire user session.
#
# Another "cute" trick is to use a client like "xclock" for the foreground
#  process.  That way when you "punch the clock", you terminate the session.
#
#  (The choice of shell is arbitrary.  Use the one you are most comfortable
#   with, just make sure you have the proper syntax on the first line.)
#
/usr/X11R6/bin/xterm &
exec twm

----- file $HOME/.xsession
#!/bin/csh
#
# This file is only used if the user X session is started with "xdm".
#  You can add as many client startups as you want to, just
#  remember to put all of them into the background with the "&". One, and
#  only one, command which starts a client must be placed in the
#  foreground, i.e. started without the trailing "&".  The foregrond
#  client should not terminate, for when it does xdm will assume the user
#  session has completed and will terminal all the remaining user clients.
#  Most Window Managers have an "exit" function defined in the pop-up
#  menu that is used to terminate the session.  Therefore, if the Window
#  Manager is the designated foreground client program, the "exit" option
#  can be used to terminate the entire user session.
#
#  (The choice of shell is arbitrary.  Use the one you are most comfortable
#   with, just make sure you have the proper syntax on the first line. This
#   is especially true for csh and ksh users as xdm by default uses sh.)
#
xterm &
twm

----- file $HOME/.twmrc
(This assumes you're using the default "twm" window manager that comes with
BSD.  The system-wide default configuration file for "twm" is in
 /usr/X11R6/lib/X11/twm/system.twmrc.  Usually this file is copied into a
file in the users directory and given the name $HOME/.twmrc.  When the "twm"
Window Manager starts it will look for this file in the user $HOME directory
first and use it if found, otherwise it will default to the system-wide file.
Many users choose to modify the "menu" section to include additional entries
for useful Client applications.  Having "xterm" on this menu is very handy
and allows the user to open new windows as needed.  The changed line that
provides this is marked with a ">" in column 1.  Notice the "Exit" function
on the last entry.  This will cause the Window Manager to terminate. If the
Window Manager is the X Session foreground process, this termination will
bring down all the other Client applications as well returning control to
"xdm" who in turn will prompt for a new user login.)

     #
     # And a menus with the usual things
     #
     menu "defops"
     {
     "Twm"	f.title
     "Iconify"	f.iconify
     "Resize"	f.resize
     "Move"		f.move
     "Raise"		f.raise
     "Lower"		f.lower
     ""		f.nop
     "Focus"		f.focus
     "Unfocus"	f.unfocus
     "Show Iconmgr"	f.showiconmgr
     "Hide Iconmgr"	f.hideiconmgr
     ""		f.nop
>    "New Xterm"	f.exec "xterm &"
     "Kill"		f.destroy
     "Delete"	f.delete
     ""		f.nop
     "Restart"	f.restart
     "Exit"		f.quit
     }