Patch-ID#  100072-01
Keywords: modload vector
Synopsis: The modload(8) utility does not recognize the "vector" keyword
        in modload configuration files
Date: 17/May/90
 
SunOS release: 4.1
 
Unbundled Product: 
 
Unbundled Release:
 
Topic: 
 
BugId's fixed with this patch: 1031577, 1038344, 1037370

Architectures for which this patch is available: sun3 sun4

Obsoleted by:

Problem Description:

	The modload(8) utility does not recognize the "vector" keyword
	in modload configuration files.    The binaries on this patch
	tape correct that problem.

	There is one very important caveat for the Sun-3.   That is,
	config(8) generates assembly-language "glue" (using the VECINTR
	macro is <sun3/asm_linkage.h>) which does some housekeeping before
	and after the call to the driver's interrupt handler.   The new
	version of modload supplied with this patch does NOT do this for you.
	The entry point that you specify in the config line will be called
	_directly_ when an interrupt occurs.    


Installation Instructions:

	This tar tape should contain the following files:

		README
		modload.sun3
		modload.sun4
		vdconf.o.sun3
		vdconf.o.sun4

	Be sure to save the original binaries.

	ie:	# cd /usr/kvm
		# mv modload modload.orig  --> make sure you are not writing 
						over another previously saved
						file before doing this!
		# cd /usr/sys/sun[34]/OBJ
		# mv vdconf.o vdconf.o.orig

	Then, move the new binaries from the temporary directory
	into which they were extracted.

	ie:	# cd /usr/tmp              --> or whichever directory was used
		# mv modload.sun[34] /usr/kvm/modload
		# mv vdconf.o.sun[34] /usr/sys/sun[34]/OBJ/vdconf.o

	Set the modes and ownership of the new binary.

	ie:	# cd /usr/kvm
		# chmod 755 modload
		# chown root modload
		# chgrp staff modload
		# cd /usr/sys/sun[34]/OBJ
		# chmod 444 vdconf.o
		# chown root vdconf.o
		# chgrp staff vdconf.o

	And, finally, follow the procedures given in the "System and
	Network Administration" manual for building and installing a 
	new kernel.