Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 beta 3/9/83; site mot.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!ut-sally!oakhill!mot!fred
From: fred@mot.UUCP (Fred Christiansen)
Newsgroups: net.wanted,net.lan,net.dcom
Subject: characteristics of these servers?
Message-ID: <124@mot.UUCP>
Date: Wed, 20-Mar-85 12:59:30 EST
Article-I.D.: mot.124
Posted: Wed Mar 20 12:59:30 1985
Date-Received: Fri, 22-Mar-85 02:36:03 EST
Organization: Motorola Microsystems, Phoenix AZ
Lines: 24
Xref: watmath net.wanted:6074 net.lan:732 net.dcom:908

[]
Looking for descriptions of (or pointers to articles describing) the salient
characteristics of these servers.  As I understand it, a server provides
me access (via a set of functionalities/commands) to some resource.  In a LAN
setting (typical), this resource is potentially remote to my system.

- communications server -- maybe my system doesn't have X.25 or SNA hw/sw
	but another does?
- disk server -- how does this differ from a file server?
- file server -- access to a remote file system?  how does this compare with
	a networked/distributed/virtual file system?  are networked/distributed/
	virtual synonymous with reference to file systems?
- terminal server -- a glorified port selector like Micom or Bridge CS/1?
- print server -- thar's this printah ovah thay-ah ah'd lak to use?
- time server -- keeps subscribers in synch?

others?

I am familiar with Fusion, and have a passing acquaintance with
TCP/IP & friends, ISO protocols, and GM-MAP.
-- 
<< Generic disclaimer >>
Fred Christiansen, Motorola Microsystems         {ihnp4,allegra}!sftig!mot!fred
{ihnp4,seismo}!ut-sally!oakhill!mot!fred         {ihnp4,amdahl}!drivax!mot!fred