Subject: netatalk in production environments....(RFC)
From: Harry Zink/Netatalk List (netatalk@fizbin.com)
Date: Wed May 31 2000 - 02:41:00 EDT
A great many people have posted in the past how they are using netatalk
servers in genuine production environments. This puzzles me, simply because,
as much as I like netatalk, it still lacks one MAJOR feature which, in my
opinion, renders it near unusable in a heavy production environment - alias
support.
Even under pre-37, alias' for sub-folders will break and not remain attached
from session to session. Most user's I know heavily rely on alias' to
utilize server volumes - hence, I do not find it possible to deploy netatalk
servers in such environments, no matter how much I want to, because the
server is nearly unusable with alias support.
Apple's ASIP (of course) as well as Windows NT have no problems. Novell's
Netware (which is genuine crap) and netatalk don't handle alias' reliably.
My question, to those of you that DO use netatalk in production environments
- how do you do it? How do you deal with the alias issue, and what
work-arounds have you found for your users (no, telling them they can't use
alias' is NOT an answer....)
I'm really curious, as myself, and several IT friends of mine keep having
these discussions, and regardless how much we really want to deploy
netatalk, our hands are tied by the workflow of our users.
I know the problem hs to do with persistent IDs, but why can Win NT handle
it, and what's the issue with netatalk not being able to?
Harry
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:49 EST