vtserver

[Steven M. Schultz]

> From: Warren Toomey <wkt at cs.adfa.edu.au>
> > To: Kirk Davis <kbd at ndx.net>
> > Do you know of anyone that has used it on a /34? I've punched in the
> > bootstrap and ran it. It loads the boot file from my Linux system.
> > It appears to call it but it halts somewhere in the 70000-70040 region.
> > Nothing comes up on the console. Looks like the memory is over written 
> > with the same values over and over again in this area. Any thoughts?
> > 
> Sorry for the delay Kirk. It could be that the V7 bootstrap expects
> split I/D, or a different I/O mapping then what's provided on the /34.
> 
> I'll punt this to the PUPS mailing list. I have a suspicion that
> you won't be able to install V7, but you should be able to install V6
> or 2.9BSD instead.

	I _think_ I know what the problem is...

	While the /34 (and /40, etc) can run a stripped down V7 (the necessary
	mch.s code exists for example) the kernels that come with the 
	distribution are split I&D kernels.  /hptmunix, etc are all split I/D
	executables.   Thus you'll be able to toggle in the bootstrap and
	get /boot loaded but then fault when loading and/or trying to execute
	the kernel.

	As I recall the usual way to get Unix on to a /23, 34,etc was to
	have a 11/70 around to do the build on, then stage/create the media
	(usually an RL02 or similar) on the 70 and sneakernet the pack over
	to the /34.

	At least that is how it was done when we shoehorned V7 into an 11/23.
	Of course we "cheated" in that we had a fellow around who made the
	necessary changes to the assembler/compiler/linker to handle kernel
	overlays (preceeded the use of them in 2BSD by several years).  Thus
	we could run a larger kernel than a pure/stock V7.  It was an
	"interesting" experience running V7 on an 11/23 (maxed out with 248kb
	of memory which was fairly expensive at the time).   There was just
	enough memory left after the kernel was loaded for a couple user 
	processes.  Thus as the '#' prompt you would run "ls" the shell ('sh')
	would get swapped out, the 'ls' would run, and then 'sh' would get
	swapped back in.   Uh, slowed things down just a _little_ bit :-)

	Steven Schultz
	sms at moe.2bsd.com