I took the liberty of uploading the later version, and updated the description a bit for clarity.That's a great find, well done.
Do you feel like uploading that to the Garden or shall I? (https://macintoshgarden.org/apps/tardis-and-timelord)
Can anyone walk me through the process of installing this onto an existing A2SERVER on a Raspberry Pi?
You could SSH into my Pi if you wanna give it a shot.
Thanks for the suggestion, but as usual Linux hates me and I get all sorts of errors when I try to compile. I'll hit up @mactjaap for the binary.@Byte Knight One trick that you can try, is to go through the steps to check out Netatalk code (e.g. Netatalk 2.2.x) then configure it with --enable-timelord and compile it. This will give you the compiled timelord binary for your platform in the contrib/timelord/ subdir.
At that point, you can either run the binary from that location whenever you need it, or manually copy the binary to whatever location Netatalk binaries are currently installed (and optionally, update the startup script to append '-l' to the shell command that starts timelord if it is localtime that you want.)
Or, lobby @NJRoadfan to have A2SERVER get a new release.
I feel bad for barging in here
These are very good points -- upstream Netatalk as it exists today is at its core a tool for corporate deployments and large sprawling multi-zone networks with thousands of users and complex access control and authentication needs. The project also has been less than effective at deprecating old platforms and features that are no longer relevant or plain broken. Dead platforms such as Ultrix, SunOS4, IRIX, HP/UX, BSD 4.4, Mac OS X Server, etc? Check! Kerberos 4 and 5 authentication? Yes sir! Features that either don't compile, or noone uses anymore such as Dropbox Kludge, Linux/Solaris ACLs, Quota, SRVLOC, etc? Yep, they're all there for your consideration.In the really long term, I'm not convinced that netatalk2 is the right codebase to be building on. netatalk2 is a tool for big networks with complicated requirements, which is why its configuration has lots of switches and options, and why it needs finesseing on networks without a router. It's also fairly dense, fairly old-school C that is written to perform, rather than to be comprehensible or maintainable. So, while it was a good tool for corporate/largeish-network AppleTalk, it isn't really suitable for home use with a small handful of machines. That's not meant of course to argue that people who are doing logistics on keeping netatalk2 building and working are wasting their time, they're doing good work that I couldn't, and I appreciate them. But it'd also be nice to have a simpler, easier to maintain appletalk stack that perhaps didn't have all the features and performance for hobbyist use.
That was basically my primary concern, In that Reddit thread there were several folks saying that they made patches and I did not want this to end up as a situation where there were several Netatalk 2 forks and I would have to figure out which one to use. So I am glad that there is some effort a consolidation. I just hope that everyone in that thread knows about your repo and your efforts. I think there was actually one other reply in addition to yourself and @NJRoadfan who mentioned they were making patches.@sailingdarter Hi there, I'm the person you spoke to most recently on that Reddit thread, so you certainly came to the right place. There's a parallel thread here for discussion around the Netatalk 2.x fork that I made, which is where I'm aiming to collect and merge all community patches including the Timelord improvements from this one. Please don't hesitate to use it and contribute your own improvements!
The vast majority of the community patches have been merged, and the head of branch-netatatalk-2-2 is indeed more or less at par with Netatalk 2.x v220101. The only one patch that was rejected was the one for preventing timestamps to be updated when copying folders on GS/OS. Apparently that patch broke conformance with the AFP3 spec. I guess some sacrifices have to be made when you try to support everything from Apple II clients all the way up to macOS Monterey.Along with a lot of other good stuff, by the look of it! Is that most of the patches you'd collected? Very good work, I'm really pleased.