AFP 3.x clients always use UTF8-MAC, AFP 2. FreeBSD is running ZFS as a backend filesystem, Ubuntu is running ext4. The AFP spec says the client is supposed to store the offset between the client's time and the server's time and adjust things accordingly. To support new AFP 3.x and older AFP 2.x clients at the same time, afpd needs to be able to convert between the various charsets used. I recently installed netatalk 3.1.0 on a FreeBSD 9.1 machine (port is not out yet, patched according to patches in 3.0.5), and I also have netatalk 3.0.5 running on ubuntu on another machine. NETATALK 3.X UBUNTU MACI need to test a AFP2.x Mac client with an unpatched netatalk build and see how it handles the dates. That being said, copying files from a OS X client to a netatalk server does NOT change the copied files "date modified" datestamp to the server's current time. This should automatically configure Netatalk for your operating system. The documented modification date logic hasn't changed between 2.x and 3.x, just that netatalk never implemented it correctly before! The only change is server time is UTC on 3.x and local time in 2.x. To build the binaries, first run the program. It essentially works but I want netatalk to use the default system users (passwd / shadow files) for authentication. NETATALK 3.X UBUNTU PDFI found the AFP3.0 PDF file referenced and compared what was in there vs. Now I installed netatalk (via apt-get) to use AFP to connect my Mac to the VM. The old file's timestamp is going to be off by your timezone offset on the new client!īasically its the same problem timelord has with local vs. The problem is when you copy a file over with an old client and then use a AFP3 client. Older clients like the IIgs have no concept of timezones, so they just store the timestamp to whatever local time is. For an explanation of all that -device stuff on the end, read the net0 section below. Proxmox’s configuration format doesn’t natively support setting a thread count, so I had to add my topology manually here by adding -smp 32,sockets2,cores8,threads2. This is great if you have a few Macs in your house and don’t want to buy a big enough Time Capsule to back them all up. AFP3 clients always assume the server stores files with UTC, so adjusts the timestamp on files accordingly based on what the client's timezone is set to. I’m passing through all 32 of my host threads to macOS. Netatalk is a daemon that runs an Apple File Protocol (AFP) service on a Linux or other nix machine that will allow Macs to use it as a file server and Time Machine backup target.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |