Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!ginosko!uunet!wuarchive!wupost!kuhub.cc.ukans.edu!zeus!unocc07
From: unocc07@zeus.unl.edu (Dave Caplinger)
Newsgroups: comp.sys.mac.programmer
Subject: Re: System 7.0
Message-ID: <3214@zeus.unl.edu>
Date: 23 Aug 89 18:26:41 GMT
References: <227700026@uxa.cso.uiuc.edu> <483@sunfs3.camex.uucp> <9173@thorin.cs.unc.edu> <13784@shamash.cdc.com> <490@sunfs3.camex.uucp> <8368@hoptoad.uucp>
Lines: 26

In article <8368@hoptoad.uucp>, tim@hoptoad.uucp (Tim Maroney) writes:
> 
> On a semi-related note, what is this file id crap?  How are network
> file system implementors supposed to implement yet another
> Mac-file-system-only feature on servers on other operating systems?
> Is Apple expecting all the other operating systems to just give up
> eventually and implement Mac file systems, throwing away their own?
> This seems like a bloody stupid decision and a feature of very limited
> utility.  We've all had enough problems with directory ids, now this.
> -- 
> Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

Isn't the file-id information just taken straight out of AppleShare?
(the new format for the Desktop file(s))  If so, it's not really "yet
another" different thing in the Mac file system.  (That, and the
"file-id" that AppleShare uses is limited to 8 characters and an 3
character extension (with some character replacing to make the filenames
unique) specificaly for MS-DOS compatibility. 

(At least, I hope that this is what they mean by file-id's!)

-/ Dave Caplinger /------------------+-----------------------------------
 Microcomputer Specialist            |  Internet: unocc07@zeus.unl.edu
 "Computing and Data Communications" |  UUCP:     uunet!btni!unocss!dent
 University of Nebraska at Omaha     |  Bitnet:   UNOCC07@UNOMA1
 Omaha, NE 68182                     |    or      dc3a+@andrew.cmu.edu