On Mon, 12 Aug 1996, Bertram Barth wrote:

> > > 	Can this be used in setting up a boot & root disk set to run the 
> > > VS3100-m76-spx to install a filesystem onto the HDD's ?
> > > 
> > Not for the moment. But in the long run, yes. My little program doesn't know
> > anything about the hardware. It only defaults to the rom routines for console
> > I/O.
> 
> Are there any size-limitations for those binaries loaded via MOP ??
>
Yes, I think it must be less that 2Gb :)
The only problem is that a MOP-image is larger that the original image
since the bss segment must exist in the MOP-image with all zeroed out.

> If binaries of (almost) arbitrary size can be loaded via MOP, then
> mop-ing a kernel with root on nfs and swap on nfs should be enough
> to install the machine, since all the neccessary drivers are included
> in the kernel.
> 
Yesterday I tested with edlabel and copy and they work as netbooted images.
I have a kernel with root on nfs and swap on nfs, but it don't support VS2000
or VS3100 so I tested it on a microVAX II and got a SCB2NDINT when I tried
to netboot it. I will look futher into it...

> If it's not possible to load the kernel itself via MOP, then the
> copy-program needs to be augmented with some mehtods for network-access.
> Also edlabel needs some new standalone drivers, since the ROM-routines
> won't work for non boot-devices (SCSI comes to mind).
> 
> Another possibility would be to add network-functionality to the 
> /boot-program so that this program could load the kernel (root/swap
> on nfs) via network. Then initializing/installing the local disk would
> be the same as in the mopable kernel szenario.
> 
> Ciao,
> 	bertram
> 
> 

-moj

------------------------------------------------------------------------------
Mats O Jansson, CelsiusTech Systems, Jaerfaella, Sweden
email: maja@celsiustech.se (or moj@stacken.kth.se)