Jump to content

Netatalk

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Himasaram (talk | contribs) at 05:54, 13 January 2023. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Netatalk
Developer(s)Netatalk Team
Initial release1990; 34 years ago (1990)
Stable release
3.1.14 / January 10, 2023 (2023-01-10)
Repositorygithub.com/Netatalk/Netatalk
Operating systemPOSIX-compliant *NIX/*BSD systems
TypeRemote Access
License2001: GPL-2.0-or-later[a]
1990: Other permissive licenses[1]
Websitenetatalk.sourceforge.io

Netatalk (pronounced "ned-talk")[2] is a free, open-source implementation of the Apple Filing Protocol. It allows Unix-like operating systems to serve as file server for Macintosh computers running macOS or Classic Mac OS.

Netatalk was originally developed by the Research Systems Unix Group at the University of Michigan starting in 1990, moved to SourceForge for revision control in July 2000, then re-licensed under the terms of the GNU General Public License with version 1.5pre7 in August 2001.[3]

Since Classic Mac OS used a forked file system, unlike the host operating systems where Netatalk would be running, Netatalk originally implemented the AppleDouble format for storing the resource fork separately from the data fork when a Mac OS file was transferred to the Unix-like computer's file system. This was required in order not to ruin most files by discarding the resource fork when copied to the Netatalk served AppleShare volume. With the release of Netatalk 3.0, the backend was re-implemented to use the Extended Attributes format that Apple had introduced with Mac OS X for backwards compatibility with Classic Mac OS resource forks.

Version History

Up until version 2.2, Netatalk implemented the AppleTalk (DDP) protocol suite, allowing Unix-like operating systems to serve also as print (PAP via a CUPS backend) and time (Timelord)[4] servers for Apple Macintosh computers and Apple II computers, as well as a netboot server for networked Apple II computers. In fact, this version contains an entire suite of tools for inspecting and manipulating AppleTalk networks from a Unix-like operating system. For this reason, version 2.2 is still being actively developed and new versions released.

In October 2004 Netatalk 2.0 was released, which brought major improvements, including: support for Apple Filing Protocol version 3.1 (providing long UTF-8 filenames, file sizes > 2 gigabytes, full Mac OS X compatibility), CUPS integration, Kerberos V support allowing true "single sign-on", reliable and persistent storage of file and directory IDs and countless bug fixes compared to previous versions.

Since version 2.0.5, Netatalk supports the use of Time Machine over a network in a similar fashion to Apple's own Time Capsule. Starting with version 2.2, Netatalk supports AFP protocol level 3.3, which is inter-operable with all subsequent OS versions through at least macOS Ventura (13.1).

Version 3.0 of Netatalk was released in July 2012 and added ini style configuration, Mac OS X compatible Extended Attributes as default, and removed AppleTalk networking support. The latest version supports the AFP level 3.4, introduced in OS X Mountain Lion.

In 2010, a company called NetAFP run by a group of Netatalk maintainers started providing commercial support for enterprise deployments of Netatalk.[5] The company merged with SerNet in December 2013, signaling the end of commercial support for Netatalk in favor of Samba which Apple had made the primary file sharing protocol with the release of Mac OS X Mavericks that same year.[6] The NetAFP website was shut down in early 2022.

Currently Netatalk supports the FreeBSD, Linux, OpenBSD, NetBSD, Solaris and OpenSolaris operating systems.

Netatalk Logo, captured from the University of Michigan's website in 2000

While a project at the University of Michigan, Netatalk's logo was the head of the BSD Daemon on a serving tray, mimicking the design of the icons that Apple used in Mac OS for AppleShare volumes.

As the project transitioned into an open source project, the logo was stylized into the current stylized Daemon head silhouette logo that the project is using.

See also

Notes

  1. ^ GPL-2.0-or-later since 2001-08-28, version 1.5pre7

References

  1. ^ https://github.com/Netatalk/Netatalk/blob/master/COPYRIGHT
  2. ^ "Netatalk FAQ". Research Systems Unix Group. The University of Michigan. 19 February 1996. Archived from the original on 23 December 1996. Retrieved 11 January 2023. How do I pronouce netatalk? Ah, good question! The unenlightened often mis-pronounce this word \'net-'a-to.k\. The correct pronouciation is \'ned-*-to.k\ (the 't' is soft, like d, and the first 'a' is a schwa).
  3. ^ "Netatalk-devel Mailing List". SourceForge. SourceForge. 28 August 2001. Retrieved 11 January 2023. As of 1.5pre7, netatalk is now being distributed under the GNU Public License (GPL). Versions up to 1.5pre7 can still be modified under the BSD License, and all terms of the BSD License that do not conflict with the GPL are still in force.
  4. ^ "Mac Time Client/Server". The University of Melbourne. The University of Melbourne. 19 February 1996. Archived from the original on 14 February 1997. Retrieved 12 January 2023. The tardis/Timelord package allows the Macintosh time to be set over an AppleTalk network from a Macintosh or UNIX/CAP based time server. {{cite web}}: |archive-date= / |archive-url= timestamp mismatch; 3 March 2001 suggested (help)
  5. ^ "NetAFP Netatalk Support". NetAFP. NetAFP. 15 August 2010. Archived from the original on 15 August 2010. Retrieved 11 January 2023.
  6. ^ Ralph Böhme (11 December 2013). "SerNet expands Apple Support – NetAFP joins SerNet". SerNet. SerNet Service Network GmbH. Retrieved 11 January 2023. SerNet is joined by Ralph Böhme from NetAFP to further strengthen the SAMBA team. Böhme is the main developer of Netatalk, a free AFP implementation for Linux servers. [...] "Many users and manufacturers use Netatalk as Linux servers for Apple clients. Over the next two years, they need to migrate to SMB," says Ralph Böhme.