Make sure you’re comfortable with the licensesīe aware that Netatalk isn’t distributed under the GPL. Whatever you do, don’t try to run the Michigan version of Netatalk, even if someone tells you it’s “official.” For the details, see “Downloading Netatalk+asun,” later in this Daily Drill Down. The moral of the story: Make sure you get the Netatalk+asun source or binary packages. Lots of people have wasted their time compiling the standard version, only to find that it just won’t work. But the official home page doesn’t explain this, despite the fact that Linux users of Netatalk have pleaded with the authors to do so. The ostensibly standard version of the Netatalk package-the one developed by the University of Michigan-won’t work with recent Linux kernels (2.2 and higher) or Mac OS 8.0 or higher without a set of patches (called asun) authored by Adrian Sun. Netatalk developers haven’t exactly made things easy for would-be users. It just means that shared resources need to be stored on the Linux systems that are functioning as AppleTalk servers. Is Netatalk’s one-way functionality such a bad thing? Not really. The word is that someone has resumed development, but there’s nothing out there yet that’s safe to run. A package that formerly enabled Linux users to access Mac filesystems, afpfs, has been abandoned by its former developer and doesn’t work with recent Linux kernels. Netatalk enables Macintosh users to access shared directories and printers on the Linux server, but it doesn’t work the other way-Linux users can’t access directories or printers on the Mac systems. What’s more, Netatalk development is, at best, a sporadic process, the online documentation is out of date and downright misleading at times, and the licensing is sufficiently strange to keep Netatalk off of most Linux distribution disks. As you’ll learn in this Daily Drill Down, Netatalk isn’t as capable as Samba, a fact that’s partly attributable to the limitations of AppleTalk itself. Look before you leap department: Limitations of Netatalkīefore you leap into Netatalk, examine all of the drawbacks. Sometimes, admittedly, it doesn’t go well, which is why you should read this Daily Drill Down. If all goes well, this process can be quite easy-as easy, in fact, as installing the Netatalk+asun package and launching the server. In this Daily Drill Down, you’ll learn how to configure a Linux system so that it emulates the functions of an AppleTalk server (chiefly, making a user’s Linux directory available from a Macintosh and making Linux printers available to Macintosh users). I'm using Ubuntu Server 13.10 (the latest one as of today).The Mac Connection: Networking Linux and Macintosh systems with NetatalkĮver want to configure a Linux system so that it emulates the functions of an AppleTalk server? In this Daily Drill Down, Bryan Pfaffenberger shows you how to network Linux and Macintosh systems with Netatalk. This is a nice chance to me to learn the OS so please give me detailed steps to do things if you deem it necessary. I have found some other solutions, including to use "SHX2" in the conf file, but it hasn't worked for me.Īlso please understand I'm completely illiterate when it comes to Linux. Something when I restarted the server must have been messed up. Before restarting the server, I just put in my credentials and saw my home directory. This happened after I restarted the server. That's the reason I'm posting this here: I suspect the problem is with my Ubuntu server. I have tried all the fixes mentioned for Lion and Mountain Lion and I haven't had any luck. Please contact your system administrator to solve this problem."Īgain, I have googled like crazy for this, and everybody says it is a problem with OS X Lion and up (assuming it affects Mavericks too). "The version of the server you're trying to connect to is not supported. When the server restarted, I tried to connect to it, but I got an error message on my Mac: But later, I had to restart the file server so I could prepare a couple of other hard drives to put in. When I installed it, I was able to connect to it just fine, I connected with my Ubuntu username and password and I was able to see the home directory. I have googled like crazy and I'm on the verge of desperation here. I know it may have been asked a thousand times.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |