On Tue, 21 Nov 2000, Mike Pumford wrote:

> >     At a first guess:
> > 	- Find someone with the time (probably the hardest part).
>
> I would imagine so. I don't think I can do it, at least not if people
> expected a reasonably quick turn around on things. Can sysinst be scripted
> to automate some of this or is that part of it still under development?
>
	I would suggest a single manual install, add in a good set of
	packages and configure X etc, then tar up the contents onto
	another disk. Then write a simple script (I could provide)
	to disklabel, newfs, extract, and install boot blocks.

	Then to make a new disk would be:
		run hdform
		format ADFS partition
		run bt_riscbsd
		boot netbsd from another disk and run generate_disk script.
		reboot into generated disk and test
		ship :)

> The rest of your strategy looks good though and it would be an excellent
> way of making sure that the arm32 install system gets tested regularly.

	I'd expect it would only be manually installed once or twice per
	OS release (1.5, 1.5.1 etc). What may happen more often would be
	updating the set of installed packages. On a 15-20GB disk you can
	afford to have a _lot_ of packages installed :)

	We should try to setup something for the Dec2 show, to see what
	people think.

                David/absolute
			       -- www.netbsd.org: A pmap for every occasion --