Navy at Philadelphia, Pa., on 21 March 1918, and commissioned the same day, Lt. No.) 1407, El Capitan was transferred from the USSB to the U.S. Shipping Board (USSB) under a bare boat charter for the War Department Account. Renamed El Capitan and completed under the aegis of the Emergency Fleet Corporation, the ship - slated for possible employment as a service collier if converted to a coal-burner - was acquired by the U.S. Olson, was launched on 18 August 1917 at Newport News, Va., by the Newport News Shipbuilding & Dry Dock Co., for the Southern Pacific Steamship Co. My Time Machine example is different due to the way that clients claim their own unique directories, but for general file sharing (say, like documents and images), you really don't want more than 10-15 people on an AFP share, otherwise things get very slow.The steamship California, later renamed Oliver J. It's worth noting that file sharing over AFP is certainly doable, however the protocol is quite poor compared to SMB for complex, busy shares. Where I work, I build a large multi-terabyte store on a Linux VM running Netatalk 3.1, and via Puppet run commands on every Mac in our offices (about 250 of them all up) to keep them all backed up with Time Machine. In fact, if you want to set up a Time Machine backup share, AFP is the only supported protocol (due to how Apple deal with sparse bundles and metadata and a few other complex bits that Time Machine needs). You can run the open source software Netatalk on any *nix system, and share files with an Apple client using AFP. It was also renamed "Apple File Protocol" to drop the association with AppleTalk, and try not to confuse people. They also modified AFP so that it could use TCP/IP as it's transport, and that is still alive in OSX today. Many years later, Apple dropped support for both AppleTalk and IPX, and standardised on TCP/IP like everyone else. It also contained a file sharing protocol with it, which was called the "Appletalk Filing Protocol", or AFP. AppleTalk was a collection of things, including a communication protocol down at the layer2/3 in the OSI model, that was more akin to IPX (compare and contrast to TCP/IP). All the same, it's worth knowing if you need to test an older version of the protocol for some reason (which does perform differently under OSX in certain circumstances, again mostly due to Apple's stupidity).Ĭlick to expand.More clarification: Appletalk and AFP are somewhat related, but ultimately two different things. Apple's insistence on using them to differentiate between versions of the protocols is not only confusing, but also inaccurate. Both are just marketing names for the same concepts (CIFS in particular was chosen to try and lure people away from NFS, and is entirely a marketing jargon thing). There are really no differences between SMB and CIFS at the technology level. Samba is an open source implementation of the SMB/CIFS protcols, as well as a very large volume of surrounding technologies that manage authentication and authorization of users (mostly emulating both a WindowsNT4 domain controller, as well as an Active Directory 2000 through 2008 domain controller). There is no such thing as "The Samba Protocol". If you specify the URI with "smb://", you will connect at the highest common SMB protocol available at both ends (from 1.0 up to and including SMB protocol 3.0, under 10.11 El Capitan). Specifically under MacOSX and Apple's lingo, "cifs://" forces a share to connect using SMB protocol 1.0. Vendors (not any one in particular - Sun/Oracle, IBM, Microsoft and Apple all have a hand in SMB/CIFS) try to confuse the issue with different names for different things, but they are the same.
0 Comments
Leave a Reply. |