[1401] in NetBSD-Development

home help back first fref pref prev next nref lref last post

Generating custom install material

daemon@ATHENA.MIT.EDU (Greg Hudson)
Sun Nov 3 03:57:28 1996

Date: Sun, 3 Nov 1996 03:57:03 -0500
From: Greg Hudson <ghudson@MIT.EDU>
To: netbsd-dev@MIT.EDU

Okay, the NetBSD 1.2-based Athena release isn't out yet (still
trudging along, give it another week or two), but when it is, this is
how to create custom install stuff when a user requests an install for
a card at a nonstandard location:

	* Log into a NetBSD machine as root.  I believe any NetBSD
	  machine should do, although I've only tested machines
	  running NetBSD 1.2 so far.

	* Pick a name for the custom image directory, e.g. "ed-irq9".

	* Run:

		attach netbsd
		/mit/netbsd/bin/custominst NAME DRIVER UNIT FIELD VALUE

	  where NAME is the name you chose, DRIVER is a driver
	  name like "ed", UNIT is the unit number (2 for ed2, etc.),
	  FIELD is "port", "iomem", or "irq", and VALUE is the value
	  you want to change the field to.

	  As an example, here's how I generated the ed-irq5 custom
	  directory, to set the IRQ of ed2 to 5:

		/mit/netbsd/bin/custominst ed-irq5 ed 2 irq 5

	  custominst takes a couple of minutes to run.  If all goes
	  well, it should give no output.  If it can't find the device
	  or unit number you gave it, it will give an error message,
	  so you shouldn't need to worry about it failing to make any
	  changes.  If it fails for any reason, it will usually leave
	  behind a directory named /var/tmp/custom-PID in case you
	  want the remnants.

	* The custom install images and kernels should appear in
	  /mit/netbsd/release/athena-7.7.2/i386/custom/NAME.  Don't
	  move this directory around; the install disk images know
	  where their kernels lives in AFS, and will retrieve the
	  correct one automatically at install time.

The command "tweak" can be used to change the device of a kernel (same
parameters as custominst, except the first parameter is the kernel
name), and the command "devdisplay" can be used to display a kernel
device specification ("devdisplay athena-adp ed 2", for example).  If
you're paranoid, you can run devdisplay on the athena-adp or
athena-other in the custom directory to verify that the change you
wanted was made.

Note that custominst is specifically tuned for the NetBSD 1.2-based
release, and does not apply to the NetBSD 1.1-based release at all.
The "kerntweak" command still works on 1.1 kernels (I had replaced its
cfstub.o for a few days, but I put the old one back this evening).

home help back first fref pref prev next nref lref last post