Subject: Re: netatalk in production environments....(RFC)
From: Ron Chmara (ron@Opus1.COM)
Date: Wed May 31 2000 - 21:58:51 EDT
"S.Ecker" wrote:
> (slightly OT) What I want to know is what the
> commercial linux hardware/software resellers are using
> when they say they support Appletalk protocol for file
> sharing.
Depends on the vendor. Helios wrote their own, but most
vendors are using a bundled, or customised, version of
netatalk+asun. I rarely see CAP in use anymore.
> Cobalt (www.cobalt.com) sells linux
> file/mail/dns/etc servers for windows/unix/mac
> environments, but they don't say what they use for
> their Appletalk server protocol.
Er... tee hee<g>.
netatalk+asun is the software package used by most
vendors, including Cobalt.
asun@cobalt.net wrote most of the current appleshareIP
code. (See anything in common?)
ASun=Adrian Sun. Cobalt is employing an *author* of the
code. Much like actully having the programmers of software
working for you, an _extremely_ rare thing at OS and
systems vendors (most current Microsoft Employees did not
write the original code for windows, they just support and
maintain the code.) I guess cobalt gets the most of
Adrian's time, but he's not the only netatalk hacker.
Other people have released GUI's, patched code, etc.
> If they're using
> netatalk, aren't they taking a great risk by deploying
> unsupported server code to their customers?
What do you mean by "unsupported"? Cobalt supports their
packages. If you want to buy support from Linuxcare you
can, if you wish to take the code apart, line by line,
and change it, you can. If you wish to use, oh, Torque
for your systems, you can get support from them.
How is netatalk "unsupported"? Do you want 1-800 numbers
where you can pay on a company credit card by the minute,
or what?
-Ronabop
-- Brought to you from iBop the iMac, a MacOS, Win95, Win98, LinuxPPC machine, which is currently in MacOS land. Your bopping may vary.
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:50 EST