Slashdot Mirror
Netatalk 2.0.0 Released
SuperBanana writes "After what seems like an eternity, Netatalk (an Appletalk server suite for unix) has caught up with the latest version of the Apple Filing Protocol (aka Appleshare). This means long filenames, files larger than 2GB, and other goodies that will bring much happiness for Unix sysadmins supporting Macintosh users (check out the human-friendly release notes for the full list). As with any major release, even though this has been through several release candidates- read the gotchas, review the known bugs in their bug tracker, test it out on something non-critical...and help stabilize the release by reporting any bugs you find. Of course, make sure you read a guide to reporting bugs first!"
... especially when dealing with the evil AFP and OS9 gods.
.AppleDB directory - even if you set the dir 2775.
1.6.4 has a nasty habit of b0rking the CNID database (A berkely DB that contains all of those wonderful resource forks for the Mac files). You have to shut down the AFP service, repair the DB, then connect one Mac so you can fix permissions in the
I haven't played too much with version 2 yet, but it does seem faster and more stable. I'm hoping that the DB will stay unscrambled for more than 2 weeks at a time, and that the DB daemon will honour the directory permissions.
I compiled it from source, and the included SPEC file didn't want to let me create an RPM - if anyone has one of netatalk 2 for FC2, I would appreciate it.
Soko
"Depression is merely anger without enthusiasm." - Anonymous
"Netatalk is a freely-available, kernel level implementation of the AppleTalk Protocol Suite, originally for BSD-derived systems. A *NIX/*BSD system running netatalk is capable of serving many macintosh clients simultaneously as an AppleTalk router, AppleShare file server (AFP), *NIX/*BSD print server, and for accessing AppleTalk printers via Printer Access Protocol (PAP). Included are a number of minor printing and debugging utilities."
So if I understand the functionality correctly: Netatalk:OSX :: Samba:windows
I just know someone is going to ask this, so I'm writing this as a preemptive strike.
Yes, there really *are* people who have files greater than 2 GB. A perfect example is hard drive images. At a previous place of employment, we imaged entire iMac hard drives and put them on a server so that the HDs could be reimaged at any time. Seeing as the iMac HD was about 6 GB, it was absolutely essential to have support for 2+ gig files. Just one example.
the JoshMeister on Security
I just installed 2.0 on freebsd last night, from what little tests I have done so far afpd seems to be alot faster in this version and is just as fast as nfs.v3. I got an average of 8.43MBps with netatalk and an average of 8.54MBps with nfs. Both were bouncing back and forth on which was faster.
Longer file names are also supported! This is a huge plus if you have long file names (ie. mp3s)
AFP is the standard filing protocol on Mac OS X and has (at least for Mac Users) many advantages over NFS, SMB etc.
AFP is based on TCP/IP, AppleTalk is used for older legacy Mac support - maybe you confused AFP with AppleTalk
If you totally can't stand NFS, you *might* want to give OpenAFS a try. It's probably total overkill, but is is really neat, and once you get an AFS cell up and running it is very good. It just takes a lot of work when you first start out of the gate. I did it for these guys, and we wrote a bunch of documentation, and about a year later, things are really good. AFS rocks.
Aside from the !(> 2g) limit, I've had NO problems with NFS. None to speak of. Share the share, mount the share, copy shit over- no problems with Special Characters, no filename limitations... fuck, even the resource forks copy over.... and they move over CLEANER than they do with netatalk!
Netatalk 1.6.x was a pain in the ass with OS X, and I've had too many problems with Samba to make it worth my time anymore.
As I recall, there were problems doing AppleTalk over serial stuff. I have an old Mac IIsi that I might hook up for grins if so. I have an Ethernet card, but it's busy in my SE/30 running my website. :->
PHEM - party like it's 1997-2003!
see /etc/login.conf
man login.conf
man umask
IIRC (so don't take this for gospel):
AppleTalk over serial == LocalTalk,
AppleTalk over ethernet == EtherTalk,
AppleTalk over token ring == TokenTalk.
You'd need something to convert the physical layer to get the IIsi online though. I bought a relatively rare LT/EN bridge by lurking on a Mac list several months ago. Now I've got my ancient LaserWriter 4/600 (serial connection only) on my network, and Panther prints to it just fine.
Constitutionally Correct
So the Linux box would capture the print job and then do something with it? I'd love to help, but this kind of thing (serial protocols, etc) is outside my bailiwick. I'll point you to the MaX list at LEM though. That's where I ask all these sorts of questions, since it involves *n*x. Signal to noise there is very high, which is nice.
Constitutionally Correct
Also, if you could find one of those bridges, you could put the Mac on your network via its serial port. If your other devices spoke AppleTalk, you might have a solution. Using netatalk on the Linux box to translate and route print jobs? You can find these bridges on eBay, though they tend to go for a bit more than I really wanted to pay. There's actually one there right now, ending today.
Like I've said, I may be talking out of my butt here. Networking and low-level protocol stuff really is not a strength of mine.
Constitutionally Correct