Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!jarthur!nntp-server.caltech.edu!toddpw
From: toddpw@nntp-server.caltech.edu (Todd P. Whitesel)
Newsgroups: comp.protocols.appletalk
Subject: Re: Apple IIgs to Sun 2/120?
Message-ID: <1990Nov20.100930.26991@nntp-server.caltech.edu>
Date: 20 Nov 90 10:09:30 GMT
References: <90323.150258UD169430@NDSUVM1.BITNET>
Organization: California Institute of Technology, Pasadena
Lines: 26

If you don't already have a fastpath, you're stuck. Unless you can get an
ethernet interface for the IIgs (doubt it) you'll need a fastpath to get
from the IIgs' LocalTalk to the Sun. The same is true for any group of //'s or
Mac's without ethernet interfaces.

FastPaths cost on the order of a thousand, so I guess you're sunk. It helps a
lot if you already have a Fastpath around to support the computer labs (or the
student's personal machines, which is how I get at the AUFS server here at
Caltech).

The second half of this question is the one I'm working on: putting real
ProDOS support into AUFS. The server already maintains fields earmarked for
prodos file info, but doesn't initialize them to anything meaningful. This
effectively neutralizes any attempt to read a file from the server because
no programs will recognize the invalid file types, and Finder can't copy
files onto a local disk because it passes the invalid filetype to the prodos
file system translator without checking it -- and gets a 'parameter out of
range' error back.

I've discovered _more_or_less_ where in AUFS the code needs to be added, but
I am not at all sure that I am compiling AUFS correctly (I tried setting the
debug option because it said that all the files would be stashed in a
subdirectory for easy checking, but did that work? NOOoooooOOO...)

Todd Whitesel
toddpw @ tybalt.caltech.edu