Subject: Re: [netatalk-admins] Problems With AppleVolumes.System
From: Bill Stewart-Cole (bill@finan.com)
Date: Tue Jan 20 1998 - 11:56:01 EST
At 9:48 AM -0600 1/20/98, Jonathan R. Wilner wrote:
>Forgive me if this is a FAQ, but It was my impression that using
>AppleVolumes.System in ETCDIR would allow the Mac to interpret the
>various UNIX, PCs, etc extensions as the correct file types, even
>without resource forks. Unfortunately, unless I create files from the
>Mac, or use FileTyper to change the fork, everything shows up as text
>files.
To be a bit pedantic: types and creators are not directly related to
resource forks. The only connection is that both the extra data stream in
some Mac files and the extra meta-information connected to most Mac files
set Mac files apart from files in simpler filesystems.
>Is there any way to do this? Is AppleVolumes supposed to do it? I would
>greatly appreciate any help & would definitely summarize for a FAQ.
That's certainly what AppleVolumes.system is supposed to do, but
AppleVolumes.System will probably do nothing. :)
The pitfalls:
1. Unix filesystems are case-sensitive.
2. AppleVolumes.system in a user's home directory will override
ETCDIR/AppleVolumes.system.
3. Wherever it is, AppleVolumes.system must be readable by the user. If it
is mode 0600 root.root you will not be using it...
---- Bill Stewart-Cole This space for rent. Inquire within.
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:30:25 EST