stuart@rochester.UUCP (Stuart Friedberg) (10/25/85)
> > Does anyone know anything about the 'V' window system? Allegedly, > > it was produced at MIT and is being used as the basis for various CAD/CAM > > systems at Berkeley. > > dirk grunwald > You sure you don't mean the "X" window system? > L S Chabot Actually, I assumed he was talking about the "V" distributed kernel which has been used for a variety of graphics applications and simply didn't know it was developed at Stanford. Since I'm not longer sure what the original request was about, I'd like to provide the following references to distributed graphics using the "V" system at Stanford. There are many other refs to "V" in the systems literature; these are the ones that I know focus on graphics. (I have no connection with "V") Lantz, K.A., D.R. Cheriton, W.I.Nowicki "Structured graphics for distributed systems" ACM Transactions on Graphics, 3, 1, (January 1984), pp. 23-51 also as "Third generation graphics for distributed systems" TR STAN-CS-83-958, Stanford University, February 1983 Lantz, K.A., W.I.Nowicki "Virtual terminal services in workstation-based distributed systems" Proceedings 17th Hawaii International Conference on System Sciences, pp. 196-205 January 1984 Lantz, K.A., W.I.Nowicki, M.M.Theimer "Factors affecting the performance of distributed applications" manuscript dated 7 February 1984, sorry, don't know where that one appeared Stu Friedberg {seismo, allegra}!rochester!stuart stuart@rochester
jg@mit-eddie.UUCP (Jim Gettys) (10/25/85)
In article <12631@rochester.UUCP> stuart@rochester.UUCP (Stuart Friedberg) writes: >> > Does anyone know anything about the 'V' window system? Allegedly, >> > it was produced at MIT and is being used as the basis for various CAD/CAM >> > systems at Berkeley. >> > dirk grunwald >> You sure you don't mean the "X" window system? >> L S Chabot > >Actually, I assumed he was talking about the "V" distributed kernel.... Well, I hate to do this but.... We (MIT Project Athena and MIT Laboratory for Computer Science) have developed a network transparent window system called "X" for 4.2BSD Unix and Ultrix. It currently runs on Vs100 displays, Vs1 and Vs2 uVax workstations, among other things. Its name could cause confusion. We started from code written by Paul Asente at Stanford called "W", written originally for the "V" kernel. (Another letter bites the dust). Publications on it will be forthcoming eventually. It is indeed being used in the Berkeley Cad group, among other places. It is available from MIT for $100. For further information on getting X, send a mail request to "Xrequest@mit-athena.arpa" ("Xrequest@athena.mit.edu for those out there running domain name servers on the internet). US snail requests go to "Project Athena, X request, MIT E40, 77 Massachusetts Avenue, Cambridge, Mass. 02139. X is completely network transparent, supports overlapping windows, text and graphics in windows, etc, etc. X attempts to not predefine a user interface; instead manipulation of existing windows is done through a seperate "window manager" program; if you don't like ours, write your own.... At this point there is a terminal emulator (~Vt102 and 4010), clock, load monitor, imagen previewer, some cute hacks, programmers interface in C, menu package, several window window managers, demo programs, screen dump to LN03 laser printer, and some other stuff. X does deal with color displays. X will be on the 4.3 tape as User Contributed Software. MIT does not "support" X, but we are interested in feedback from people using it. Jim Gettys MIT/Project Athena Digital Equipment Corporation
jbn@wdl1.UUCP (10/30/85)
The V kernel is a scheme for supporting very intelligent terminals using a large host as a master machine. It's a lot like the support for the Teletype 5620 in system V; you download editors and graphics packages, but anything big is done in the host. The terminal at Stanford is typically an early-model diskless SUN, and the host is typically a VAX running UNIX. It's a interesting idea technically, but the machine it runs on is powerful to act as a workstation in its own right, so why bother? John Nagle
hutch@sdcsvax.UUCP (Jim Hutchison) (11/11/85)
In article <815@wdl1.UUCP> jbn jbn@wdl1.UUCP writes: > > The V kernel is a scheme for supporting very intelligent terminals using >a large host as a master machine. It's a lot like the support for the Teletype >5620 in system V; you download editors and graphics packages, but anything big >is done in the host. The terminal at Stanford is typically an early-model >diskless SUN, and the host is typically a VAX running UNIX. It's a interesting >idea technically, but the machine it runs on is powerful to act as a >workstation in its own right, so why bother? > > John Nagle Because the kernel eats up about 1/2 meg of memory, and the various it and the daemons eat processor time. A Real-time Unix (Fert? No, Mert :-), would solve that, but I don't know if Sun has one, or if you would want to use it. As a Intelligent terminal, a sun would not get the trouble you sometimes experience when you compile something and try to run a large graphics program at the same time (all in 1/2 meg, yuch!). -- /* Jim Hutchison UUCP: {dcdwest,ucbvax}!sdcsvax!hutch ARPA: hutch@sdcsvax [ Of course, these statements were typed into my terminal while I was away. ] */