# "@(#)config	6.4	3/25/87"
#
#	This is the file /etc/config.  It is used to control which drivers are
#	run at boot time.  Lines consist of 3 fields:
#	   1) a set of run-levels for which the entry applies
#	      (default is 0123456),
#	   2) a device type (either name or decimal number), and
#	   3) a command line.
#	Empty lines are ignored.  Comments begin with either # or ; and
#	extend to the end of the current line.
#
#	If the run-level specified in the configure command invocation is in
#	the set in the first field, and if a device of the specified type is
#	found, the specified driver is started.  The command used is:
#
#	    sh -c 'field-3' configure devAddr boardOrdinal
#
#	where devAddr and boardOrdinal are decimal numbers determined by
#	scanning the current system configuration.
#
#	The following lines are a template for an administrator to set up the
#	/etc/config file.  Each type of board has a section below.  If your
#	system has a board of that type you should be able to use this file as
#	is.
#
#	This file is processed sequentially.  Each line controlling a driver
#	is parsed and processed by scanning the configuration read by the
#	configure command from device address 0 to 255.  If a device of the
#	specified type is found, the driver is started and the device address
#	is marked in use (so it will not be reused in this invocation of
#	configure even if the driver failed).  To prevent a driver from being
#	started at some address arange for a driver named SKIP to be started
#	(i.e., :50:SKIP at the beginning of this file would cause the lowest
#	addressed DR11/UB to be skipped).  To summarize, drivers are started
#	in the order in which they appear in this file and device addresses
#	are assigned in ascending numerical order.
#
#	One special case to be aware of is that you should only start one copy
#	of the network server, ns.  If you have more than one type of board
#	that serves as a network interface, you must edit this file.  For
#	instance if you have a DR11/UB and a CIO board, you must edit this file
#	to make sure one of them does not cause a copy of ns to start.
#	(Multiple CIO boards take care of themselves in this file.)

###############################################################################
#			Single User Mode Only
###############################################################################
#	If you do NOT want a tape driver to run in single user mode then comment
#	out the following lines.  The diagnostics are run on the first CIO/ENET
#	board before the cartridge tape driver is run.  The second CIO/CT is
#	skipped in case you add entries later in this file that are run for
#	single user mode.
s:32:/drivers/tapedriver $1 $2		# tape in single user mode
s:33:/drivers/tapedriver $1 $2		# tape in single user mode, extd board
s:7:/usr/test/sys/ciodiag $1 $2		# run diagnostics
s:13:/drivers/cioct $1 $2		# CIO/CT in single user mode
s:13:SKIP				# skip second CIO/CT

###############################################################################
#			FDLPs
###############################################################################
#	Since the FDLP driver is still started by startup, you will find no
#	entry here.  Instead see the /ros/conf file.

###############################################################################
#			Disc Controllers
###############################################################################
#	ANSI and SMD disc boards are automatically handled by the system.
#	There should be no entries here for them.

###############################################################################
#			Displays
###############################################################################
#	For each display board there should be an entry.  Displays are local
#	to the system and are therefore started at any run-level.
:4:/drivers/disp $1 $2
:4:/drivers/disp $1 $2
:4:/drivers/disp $1 $2
:4:/drivers/disp $1 $2

###############################################################################
#			1/2" Tape
###############################################################################
#	For each tape board there should be an entry of the form:
:32:/drivers/tapedriver $1 $2		# tape at any level
:33:/drivers/tapedriver $1 $2		# tape at any level, extd board

###############################################################################
#			Color Displays using DR11
###############################################################################
#	Type 48 is reserved for DR11 boards with either Metheus, Rastertech,
#	or Lexidata controllers.  For each of these boards there should be a
#	line of the form: (these are commented out due to the fact that you
#	may not want these lines in this order):
#:48:/drivers/metheus $1 $2		# DR11/Metheus
#:48:/drivers/rastertech $1 $2		# DR11/Rastertech
#:48:/drivers/lexidata $1 $2		# DR11/Lexidata

###############################################################################
#			UB-NIU using DR11
###############################################################################
#	Remember to make sure only one copy of ns is started.
123456:50:/ros/ns $1 $2	-b800 -B200	# DR11/UB at levels 1-6
# 					  default mbuf allocation = 800
# 					  default big buffer allocation = 200

###############################################################################
#			ENET (type 64 board)
###############################################################################
#	Remember to make sure only one copy of ns is started.
:17:/usr/test/sys/ciodiag $1 $2		# always run diagnostics
123456:19:/ros/ns $1 $2 -b800 -B200	# ENET is up for levels 1-6
# 					  default mbuf allocation = 800
# 					  default big buffer allocation = 200

###############################################################################
#			CIO (type 65 board)
###############################################################################
#	Each CIO board (type 65) supports a variety of devices.  A typical
#	configuration for the first CIO board would look like:
d:6:/ros/ciodebug -d $1			# download board for level d
:7:/usr/test/sys/ciodiag $1 $2		# always run diagnostics
123456:9:/ros/ns $1 $2 -b800 -B200 	# CIO/ENET is up for levels 1-6
# 					  default mbuf allocation = 800
# 					  default big buffer allocation = 200
:10:/drivers/ciotty $1 $2		# CIO/TTYs at levels 0-6
:11:/drivers/ciolp $1 $2		# CIO/LP at levels 0-6
:13:/drivers/cioct $1 $2		# CIO/CT at any level
:13:SKIP				# always skip second CIO/CT on board
#	A typical configuration for the second CIO boards would look like:
d:6:/ros/ciodebug -d $1			# download board for level d
:7:/usr/test/sys/ciodiag $1 $2		# always run diagnostics
123456:9:SKIP			 	# CIO/ENET only used on first CIO board
:10:/drivers/ciotty $1 $2		# CIO/TTYs at levels 0-6
:11:SKIP				# CIO/LP only on first CIO board
:13:SKIP				# CIO/CT only on first CIO board
:13:SKIP				# always skip second CIO/CT on board
#	A typical configuration for the third CIO boards would look like:
d:6:/ros/ciodebug -d $1			# download board for level d
:7:/usr/test/sys/ciodiag $1 $2		# always run diagnostics
123456:9:SKIP			 	# CIO/ENET only used on first CIO board
:10:/drivers/ciotty $1 $2		# CIO/TTYs at levels 0-6
:11:SKIP				# CIO/LP only on first CIO board
:13:SKIP				# CIO/CT only on first CIO board
:13:SKIP				# always skip second CIO/CT on board
#	A typical configuration for the fourth CIO boards would look like:
d:6:/ros/ciodebug -d $1			# download board for level d
:7:/usr/test/sys/ciodiag $1 $2		# always run diagnostics
123456:9:SKIP			 	# CIO/ENET only used on first CIO board
:10:/drivers/ciotty $1 $2		# CIO/TTYs at levels 0-6
:11:SKIP				# CIO/LP only on first CIO board
:13:SKIP				# CIO/CT only on first CIO board
:13:SKIP				# always skip second CIO/CT on board
