Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!uwvax!rutgers!ames!oliveb!pyramid!prls!philabs!sbcs!root From: root@sbcs.UUCP (Root) Newsgroups: comp.sys.amiga Subject: Re: tcp/ip for amiga Message-ID: <602@sbcs.UUCP> Date: Thu, 17-Sep-87 18:07:48 EDT Article-I.D.: sbcs.602 Posted: Thu Sep 17 18:07:48 1987 Date-Received: Sun, 20-Sep-87 11:58:16 EDT References: <503@louie.udel.EDU> <1929@umd5.umd.edu> <2009@megaron.arizona.edu> Organization: Computer Science Dept, SUNY@Stony Brook Lines: 47 > I have been thinking about this approach, too. It seems useful to > embed TCP (and UDP?) in the filesystem. For example, > type I agree that it might not be possible to model all of TCP's semantics > this way. Note that BSD sockets provide an incomplete but still useful Ameristar supports BSD style socket interface, also. Not in general release, yet (~4 alpha testers have socket stuff now).. > > Then there's a NFS device: perhaps mount each remote machine? > So > copy c:foobar to cholla:/usr/rogerh/amiga/archive > copies a file to a server's disk. If this works, some of us > might be faced with a decision: hard disk or network interface? > What model does Ameristar present to the user? Right. One volume per remote mounted machine:partition. For development, I used to use a hard disk + NFS, but lately (and probably UNTIL I can get Commodores FFS + real fast SCSI iron) I use only NFS. Really flies when loading 300K+ NeWS binaries.. Of course if you have a room full of Amigas or you want to share files off'n a Vax or Sun somewhere, you definitely want NFS. > Roger Hayes > rogerh@arizona.edu > Rick Spanbauer SUNY/Stony Brook PS. I've said it before, and here it is again: I'm am definitely biased in matters Ameristar - I do development for them..