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
Out of curiosity, how long does it usually take for something like this to show up in urpmi? I'd like to install it that way on my Mandrake server if at all possible but right now its only offering me 1.6. Also, I've been a longtime fan of AFP. As an OS X user it offers many great advantages over SMB, specifically the ability to move a file around on the server while it is open without the application losing track of it (just like a local file on an HFS+ disk). Also, most ISPs block the SMB port since Windows viruses spread through shares but they don't block the AFP port, which makes connecting to AFP shares over IP a breeze. Although for the record I'm not so much a fan of AFP over AppleTalk. AT was good about 15 years ago but Rendezvous has made it useless nowadays.
Finally I can't tell you how dead-awful it is when you have a Linux box serving files, and then sitting on a Mac OS X client in all its Unicode glory having to deal with long Japanese filenames on the server (that Windows users put there) and being f***ed, because the "old" AFP protocol can't handle long filenames and going in via SMB doesn't work either, because the filenames being in Japanese cause problems, too.
There are two rules for success:
1. Never tell everything you know.
This is exactly why I switched to gentoo. Check out http://packages.gentoo.com/ and see how up to date everything is.
I've had to deal with 2 years of complaints from Mac users. I had to ditch the netatalk thing alltogether... due to millions of compatibility issues.
For a brief time we thought webdav was the answer.. it seemed to work well for PCs with proper webdav clients installed, linux as well.
OSX native webdav support is buggy as shit. So yet again all my users are happy but the OSX users.
I might have to bite the bullet and do NFS.
Fuck I hate nfs.
Love,
Zaq
That would really be great.
http://saveie6.com/
Just look at the iMac, iPod and PowerBooks.
However I don't understand why they try to revive AppleTalk.
There are really better methods to talk to deceased operating systems, e.g. psychics are an old estabilished one while these days occult seances are becoming more and more popular.
Now that we have an updated Netatalk, will we also get an updated Webmin module.
Please, please also update the Webmin module.
Out of curiosity, does anyone know if Apple developers (officially or not) contribute to Netatalk development?
Facts speak louder than FUD. :-)
Nearly 2.5 Million Active Sites running FreeBSD
"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
Or maybe I should ask, does anyone still use AFP in *new* installations? We have a mix of Win/Unix/Mac(OSX). The Unix/Linux workstations and Macs automount several servers via NFS when a user logs in. The Win PCs use a Samba server (ugh). More "important" data is sent via scp. Telnet and ftp have been pretty much abandoned.
I thought that AFP was only used to support old legacy Macs running 9.2.2 or older.
Granted there are NFS clients for Windows and for "Classic" Mac OS 9.2.2 and earlier, but most are pretty ugly.
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)
I'm using AFP to connect to our file server here from my main desktop, but other machines connect using Samba. The problem is that I constantly have to change permissions on files I create because they default to 755 or 644, whereas in Samba I can force this to 775 or 664. Anyone know how to configure AFP to force a different mask?
sig != null
I just built from source LAST WEEK.
:D
On the upside, it was the first bit of anything I've had to build from source that actually Built and Worked. o.o
This FINALLY solves some SERIOUS data moving problems I've been having at work for the past couple of years.
Because Samba Is Shit(tm).
Between resource forks, HUGE files (16g+) and Special Characters SKULLFUCKERY- not to mention hideously incompetent Windows domain administration at the highest levels of corporate IT... around here, it's AFP or it's shuffled around on Firewire drives.
Our network sucks so goddamned bad that any OS X client with Samba enabled becomes the PDC inside of a few minutes. IT insists that their incompetent administration is somehow our fault. It rules.
Also, AFP is to Apple as SMB is to Windows. SMB isn't there for Windows boxes running WinME and older, is it? NO. It's the damned OS networking protocol. Apple didn't throw in samba support to replace AFP or NFS, they threw it in so macs can talk to PCs.
Ideally, you'd use AFP to talk to Macs, NFS to talk to Unices, and SMB to talk to Windows boxes.
But for some reason, every linux admin under the SUN seems to have a GIANT BONER for samba, despite its limitations.
Which is great, as anyone who's moved off of OS 9 onto OS X has likely generated a few long file names, and anyone who does video gets to deal with Big Shit.
Previously, I had to use NFS for all of the files under two gigs and Samba for everything over (NFS version in Debian Stable doesn't do > 2g files), which made drag-and-drop backups extremely tedious.
Now, it just totally rules. I can drop a media drive onto a netatalk mount and walk away. No need to babysit anymore.
Since this has been a huge issue for me for years (work being too cheap to buy useable OS X server hardware), I'm extremely happy about this.
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.
DVD images out of DVD Studio Pro are typically in the 2.5-3.8 gig range for me. Raw video files of the projects I work on start around a gig and a half and have reached upwards of 19 gigs. If you use final cut pro and don't check off the little check box that tells it to auto-segment in 2g increments, you'll wind up with some extremely large files under certain circumstances.
Basically, anybody who deals with video has been dealing with Very Large Files for many years. Anybody who has to back the shit up from a Mac and can't afford an Apple server has been itching for something like this for quite awhile.
Netatalk's behaivor can change depending on the underlying filesystem. More to the point, Netatalk is Case Indifferent. If you set up a Netatalk share on a case sensitive filesystem (the most common deployment case) the you have just created a case-sensitive AFP share. Many Mac apps Do Not Like That. For instance, I had two reading assessment apps that I could never get to work with Netatalk. The clients talked to a filebased database on an AFP share. If made an hpfs or hfs+ filesystem and shared that, then lo and behold they would start working.
Basically, Netatalk preserves the case handling of the filesystems it is serving up. It often isn't the correct thing to do. It is possible to make Samba behave in a case-preserving fashion even when serving from case-sensitive filesystems. I really wish they would do this for Netatalk as well. And no, casefolding didn't work either.
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!
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
Nice.
I've actually got an old 700 (quadra) and some SE-30s that want to talk to my serial laserwriter, but the laserwriter's fuser hardware has gotten melty and gummed up. Do you know of a good way to emulate an apple laserwriter on a serial port on a linux box and hook up the apple's RS-422 to the serial port and make it think that the linux-box is a post-script level one printer?
I've tried simple things like making a linux serial console and running GS on it but the mac's couldn't make it through. And my old computer with two serial ports on it which I could use to peek at serial protocols is stuck in storage (mold problems... water leakage everywhere... >$30k hardware damaged as attic-collapsed-from-water-weight... ) so I can't probe it to make a serial emulator. Is there a quick and dirty way to do this for older macs that don't have ethernet availability?
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