Search results

  1. slipperygrey

    Netatalk 4.0 - Future-proofing Apple File Sharing

    It is wild that such a bug was not discovered for 13 years. By orphaned, you're saying that Netatalk won't read it again, or is it still read and processed on every access? At a related note, Netatalk has an option for automatically converting ADv2 metadata to EA metadata, called "convert...
  2. slipperygrey

    Netatalk 4.0 - Future-proofing Apple File Sharing

    You’re welcome! Naturally, a part of this alpha testing process is to ascertain in the field that we didn’t break things like this. ;)
  3. slipperygrey

    Netatalk 4.0 - Future-proofing Apple File Sharing

    There is a way, unchanged from netatalk 3.2: "appledouble = v2"
  4. slipperygrey

    Netatalk 4.0 - Future-proofing Apple File Sharing

    What NJRoadfan is saying in an indirect way here is that we're now looking for alpha testers of Netatalk 4.0.0. :) It's a one-way migration path from Netatalk 2.x, so please upgrade only on AFP volumes that have backups, or create fresh volumes for testing. 4.0.0 has a handful of new...
  5. slipperygrey

    Macproxy v24.8 release and Docker image

    Macproxy, the best* way to browse the modern web on ancient browsers, has a new release: v24.8 This is a maintenance release, since the Python dependencies were starting to age and accumulate security advisories. But, it also comes with a brand new "official" Docker image. Pull it from Docker...
  6. slipperygrey

    Netatalk 2.4.0 available

    These are good insights. I can see how this would be theoretically feasible. Do you have a particular mechanism in mind for monitoring changes to the config files (for option two)? The webmin module only writes to the config files when you hit the save button, so this won't be a problem.
  7. slipperygrey

    Netatalk 2.4.0 available

    The webmin module uses the standard webmin config scheme, so it can be set to look for netatalk binaries and config files at arbitrary locations. This should not be a problem. One correction to my previous post: we don’t actually use the init system but rather start afpd/netatalk (in...
  8. slipperygrey

    Netatalk 2.4.0 available

    @ironborn65 So if I understand your suggestion correctly, you would set up a separate Docker container that runs only webmin, which then mounts the file system of the netatalk container to access the netatalk config files? Two challenges to overcome for this to work, off the top of my head...
  9. slipperygrey

    Netatalk 2.4.0 available

    @ironborn65 You're welcome! Thank you for using netatalk. If I understand the question correctly, you're asking why I chose Docker bind mounts over Docker volumes in the docker-compose.yml example? If this is the question, the answer is: because bind mounts are self-managed and independent of a...
  10. slipperygrey

    Netatalk: changing “Workstation”

    Netatalk ships two tools - nbprgstr and nbpunrgstr - that registers and unregisters NBP names on the AppleTalk network, respectively. The technical reason you are seeing the "Workstation" NBP name for your server, is because the particular init script you're using runs nbprgstr after launching...
  11. slipperygrey

    Netatalk 2.4.0 available

    Correction: I couldn't get it to work properly with fuse 2.9.9 either.
  12. slipperygrey

    Netatalk 2.4.0 available

    +1 for afpfs-ng. Earlier this year I made a fork to modernize the code base, normalize the various abandoned forks and community patches, and get it compiling and running again. Alas, I was only able to get the interactive AFP client working reliably. The fuse file system layer isn’t working...
  13. slipperygrey

    The MacIPpi Rpi. The MacIPpi concept for Raspberry Pi.

    Nicely done! If you haven't done this already, I would recommend you also install and build with: libssl-dev (for DHX secure Classic Mac OS auth), libcups2-dev (for AppleTalk printing), libavahi-client-dev (for Zeroconf service discovery) and libpam0g-dev (for more secure auth.)
  14. slipperygrey

    The MacIPpi Rpi. The MacIPpi concept for Raspberry Pi.

    What version of the RPi OS are you running? As you can see in a subsequent post in that thread, Bullseye or older will require different steps to build netatalk.
  15. slipperygrey

    Netatalk 4.0 - Future-proofing Apple File Sharing

    Thanks to NJRoadfan's efforts, AppleTalk is now once more enabled in the main branch, almost 13 years after the previous maintainers started removing it! I just pushed another changeset that brings back all of the AppleTalk init scripts, so the low hanging fruit have all truly been picked at...
  16. slipperygrey

    Netatalk 4.0 - Future-proofing Apple File Sharing

    Awesome work so far! This is shaping up nicely. I'll keep an eye out for when you flag your PR as ready for review. My only requirement is that the codebase compiles in its default configuration, and that afpd can start up.
  17. slipperygrey

    Netatalk 4.0 - Future-proofing Apple File Sharing

    There is still a lot of work left to do, mind you! This was the easy part, I anticipate... In all honesty, we have been doing a lot of preparatory work over the last several months, in particular dgsga's hard work backporting the Meson build system to 2.x, plenty of modernization and removal of...
  18. slipperygrey

    Netatalk 4.0 - Future-proofing Apple File Sharing

    The PR that brings back all the AppleTalk code has been merged to main now, but disabled by default in the build system. This should allow us to tackle specific improvement areas one by one from now on. I started creating GitHub issue tickets for the known tasks. Please don't hesitate to add...
  19. slipperygrey

    Netatalk 4.0 - Future-proofing Apple File Sharing

    Cheers, this was helpful! I've been mostly noodling with the Meson build scripts lately, which consist of domain-specific pseudo-Python that takes a bit of getting used to. With the AppleTalk restoration project we will be heading into proper C coding shortly.
  20. slipperygrey

    Netatalk 4.0 - Future-proofing Apple File Sharing

    Cheers! Thanks for all your guidance in the past. When you get a chance to try again, I'd love to know if the BerkeleyDB lib dir error on NetBSD went away for you or not.
Back
Top