Subject: [netatalk-admins] persistent DIDs
From: Michael M Han (han@windy.ckm.ucsf.edu)
Date: Mon Apr 13 1998 - 16:12:51 EDT
Okay, persistent DIDs have become *very* desirable to me and I'm
trying to find a short-term solution (even if it's limited) until
persistent DIDs can be issued The Right Way, which I'm assuming will
take quite a while. I'm running netatalk w/ asun's 18.2 patches on a
Solaris2.6 SparcStation2.
Is anyone aware of ways to get persistent DIDs from netatalk? The only
things I could think of, HFS-mounted filesystems, which I'm assuming
store DIDs natively, and maybe AFS (which produces an FNUM-analog but
I'm not sure about DIDs), aren't supported by netatalk from what I can
tell. Or, to be more clear, netatalk doesn't seem to care if the
filesystem is willing to provide a usable DID and generates a
non-persistent one as it goes (from my reading of
etc/afpd/directory.c). This does make a certain sense since it's all
well-and-good for a single filesystem to be providing real DIDs but
that doesn't help a volume spanning multiple, heterogenous
filesystems...
Can anyone think of any ways to get my afpd volumes to provide
persistent DIDs in the short term? Copious thanks to anyone who can
help me out here.
_____
Michael Han (han@library.ucsf.edu) voice: (415) 502-7542
Interactive Learning Center Consultant (415) 476-4309
San Francisco, California 94143-0840 fax: (415) 476-4653
"I had lately learned that another way of writing FALL IN LOVE is WALK THE
PLANK." - Jeanette Winterson
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:18 EST