home *** CD-ROM | disk | FTP | other *** search
- Message-Id: <9510122104.AA01223@mrcnext.cso.uiuc.edu>
- Subject: Re: netatalk-style resource forks? (please? :)
- To: deh@atype.com (David E. Hollingsworth)
- Date: Thu, 12 Oct 1995 16:04:50 -0500 (CDT)
- Cc: junkmail@pht.com, executor@nacm.com, brad@pht.com
- In-Reply-To: <9510121921.AA09602@ sol.atype.com > from "David E. Hollingsworth" at Oct 12, 95 03:21:23 pm
- X-Mailer: ELM [version 2.4 PL22]
- Mime-Version: 1.0
- Content-Type: text/plain; charset=US-ASCII
- Content-Transfer-Encoding: 7bit
- Content-Length: 629
- Sender: owner-paper@nacm.com
- Precedence: bulk
-
- > Of course, CAP aufs uses .resource directories, Helios EtherShare and IPT
- > uShare use .rsrc directories, Xinet KA-Share uses .HSResource directories, and
- > Pacer PacerShare uses afp_resource directories.
- >
- > There are corresponding differences for desktop representation. Many of these
- > systems also appear to have files or directories for storing finder
- > information. Fun, eh?
-
- I'm not sure what DEC Pathworks does.
-
- Who do we shoot for causing such a massive divergence? At least some
- of these people had to be aware of the other efforts, and could have made
- their own work compatible. Gratuitous difference sucks.
-
-