[408] in Info-AFS_Redistribution
Re: AFS and NeXTs
daemon@ATHENA.MIT.EDU (Cal_Thixton@next.com)
Wed Nov 13 22:17:48 1991
Date: Wed, 13 Nov 91 22:05:42 EST
From: Cal_Thixton@next.com
To: "Michael T. Stolarchuk" <mts@terminator.cc.umich.edu>
Cc: Wallace Colyer <wally+@andrew.cmu.edu>, Info-AFS@transarc.com,
Changing the UI, of Workspace in this case, just because of the type file system you
are on is hard to justify and places a burden on the user to adapt as well.
And frankly, what useful information can a cell tell one that cannot just be faked
for all of the entries in /afs? Go and look at /Net and you will see that the dates
reflect the boot time. All the Workspace wants to know is 'is it a directory or a
file?'. The same goes for /afs, /afs/com, /afs/edu, etc...
lrwxrwxrwt 1 root 17 Nov 12 11:19 /Net/adam -> (automount)
lrwxrwxrwt 1 root 19 Nov 12 11:19 /Net/dakota -> (automount)
lrwxrwxrwt 1 root 17 Nov 12 11:19 /Net/ohio -> (automount)
lrwxrwxrwt 1 root 19 Nov 12 11:19 /Net/osprey -> (automount)
lrwxrwxrwx 1 root 17 Nov 12 11:19 /Net/pitt -> /private/Net/pitt
lrwxrwxrwt 1 root 20 Nov 12 11:19 /Net/polaris -> (automount)
lrwxrwxrwt 1 root 18 Nov 12 11:19 /Net/quark -> (automount)
lrwxrwxrwt 1 root 17 Nov 12 11:19 /Net/r2d2 -> (automount)
lrwxrwxrwt 1 root 22 Nov 12 11:19 /Net/rembrandt -> (automount)
lrwxrwxrwt 1 root 19 Nov 12 11:19 /Net/tinman -> (automount)
lrwxrwxrwt 1 root 17 Nov 12 11:19 /Net/toto -> (automount)
lrwxrwxrwt 1 root 21 Nov 12 11:19 /Net/upstairs -> (automount)
lrwxrwxrwt 1 root 17 Nov 12 11:19 /Net/vega -> (automount)
lrwxrwxrwt 1 root 20 Nov 12 11:19 /Net/vermont -> (automount)
lrwxrwxrwx 1 root 1 Nov 12 11:19 /Net/wallingford -> /
lrwxrwxrwt 1 root 17 Nov 12 11:19 /Net/west -> (automount)
lrwxrwxrwt 1 root 23 Nov 12 11:19 /Net/wintermute -> (automount)
lrwxrwxrwt 1 root 20 Nov 12 11:19 /Net/wookiee -> (automount)
lrwxrwxrwt 1 root 19 Nov 12 11:19 /Net/xerxes -> (automount)
In the above case, Workspace assumes that links like these point to directories.
cal
Begin forwarded message:
To: Wallace Colyer <wally+@andrew.cmu.edu>
Date: Wed, 13 Nov 91 19:23:38 -0500
From: "Michael T. Stolarchuk" <mts@terminator.cc.umich.edu>
Subject: Re: AFS and NeXTs
Cc: Info-AFS@transarc.com, mts@terminator.cc.umich.edu
"Another option is to have an option in the browser thas
has it not stat files/directories until someone
clicks on the specific entry."
That makes lots of sense to me too. I'm lean towards chaning
AFS cause I can do that. I can't get to the the NeXT browser...
Adding another kinds of symbolic link (another kind of
fs mkmount) to make the stat's lazy also helps anyone who
(by mistake) does ls -F's on /afs... I figure that's really
the reason I'm thinking in that direction...
Though having /afs/edu, /afs/com, /afs/org, etc
then having another element down lower (aka /afs/edu/umich)
the path does just about the same thing...
mts.
