Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!BOULDER.COLORADO.EDU!cdash
From: cdash@BOULDER.COLORADO.EDU (Charles Shub)
Newsgroups: comp.os.v
Subject: Re: Monthly Description of Info-V
Message-ID: <8912011931.AA07964@moet.colorado.edu>
Date: 1 Dec 89 19:31:08 GMT
References: <8912010810.AA03414@Pescadero.Stanford.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: University of Colorado at Colorado Springs
Lines: 29

Gee, this group has not had a whole lot in it lately. Maybe it's time
to spark some interest with some questions?

In article <8912010810.AA03414@Pescadero.Stanford.EDU> you write:
>This is a monthly posting describing the role of comp.os.v.
>
> [ role and licensing info deleted ]
>
>The currently distributed version runs on DEC Microvaxes and SUN-2 and -3
>workstations.

And OF COURSE you need a server. What does the server run on??

anybody got the server up and not regularly crashing on a microvax running
Mt. Xinu 4.3 with NFS (and /V and /usr/V remotely mounted) ???

The server can run on a sun, but if you run the server on a sun, you can't
really boot microvaxen because the mvaxbootserver distributed only runs
on vaxen or microvaxen running unix, or have i missed someone solving this?
Will this problem go away if we upgrade our suns to version 4.whatever?

I understand some of these problems will go away under release 7 because
release 7 has V storage servers.  When will release 7 happen? What other
hardware will V run on? Has it been ported to a RISC processor? Which one(s)?

-- 

charlie shub  cdash@boulder.Colorado.EDU  -or-  ..!{ncar|nbires}!boulder!cdash
  or even     cdash@colospgs (BITNET)     -or-  (719) 593-3492