Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!sdcsvax!beowulf!velasco From: velasco@beowulf.ucsd.edu (Gabriel Velasco) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: OS/2 vs. Unix Message-ID: <8011@sdcsvax.UCSD.Edu> Date: 16 Mar 90 05:19:55 GMT References: <90052.182144CMH117@psuvm.psu.edu> <6937@tekgvs.LABS.TEK.COM> <16155@smunews.UUCP> <25e6d6ed.26a3@polyslo.CalPoly.EDU> <25e85897.57ec@polyslo.CalPoly.EDU> <21786@watdragon.waterloo.edu> <27788@cup.port <4475@daffy Sender: nobody@sdcsvax.UCSD.Edu Reply-To: velasco@beowulf.UCSD.EDU (Gabriel Velasco) Organization: EE/CS Dept. U.C. San Diego Lines: 19 schaut@cat9.cs.wisc.edu (Rick Schaut) writes: >Well, give me a for-instance. >One interesting development within the department here at UW is that large >multi-user machines are being replaced by networked workstations with >distributed processing facilities. Where in such an environment do I need >multi-user capabilities? In a "truely" distributed system, when you logged onto your workstation, you would not know which workstation's cpu was taking care of you. Your jobs would be loaded onto whichever workstation had the lightest load. The whole network would act as a single, multiprocessor, multitasking, multiuser system. This is one of the goals of distributed systems research. ________________________________________________ <>___, / / | ... and he called out and said, "Gabriel, give | /___/ __ / _ __ ' _ / | this man an understanding of the vision." | /\__/\(_/\/__)\/ (_/_(/_/|_ |_______________________________________Dan_8:16_|