Recent content by slipperygrey

Check the INSTALL.md file for the requirements. afpfs-ng can work with most AFP servers including netatalk but there’s no direct dependency between the two.

@mactjaap I'm pleased to announce a massively improved version of my afpfs-ng fork, v0.9.2 https://github.com/Netatalk/afpfs-ng/releases/tag/0.9.2 The FUSE client has been completely overhauled and should work reliably now on any supported OS (Linux, FreeBSD, macOS), to mount multiple volumes...

The key is to get AppleTalk network routing between your netatalk host and the old Mac working. AppleTalk does automatic service discovery so once the routing is working, the CUPS printer should be populated in the LaserWriter Chooser extension's list of printers. If you haven't done so...

I responded to the TLS 1.0 situation over at the corresponding TD thread, but in short I don't think it can be easily overcome unless the website owner updates their cryptography. In fact, I can't load this website even with Python 3.9 on Raspbian Bullseye. Regarding npr.org, Macproxy Plus...

It's not a bad idea to have something like podman running on a proxmox hypervisor, and then container based deployments of all relevant software components. Gives you a nice abstraction layer with automation for configuration and deployment of individual components. Netatalk is obviously...

As a concrete example, OpenBSD has chosen not to provide EA capabilities in their default file systems (FFS, FFS2) and probably never will. I don't have any intention to remove AppleDouble v2 from netatalk.

I have observed that certain AppleShare Client versions ignore the server supplied icon and always uses the default one from the client’s resource fork. Haven’t mapped out exactly which ones behave like this though.

@NJRoadfan what would you say is the expected behavior for resource fork EAs when running a non-Solaris OS with ZFS, say FreeBSD? Is the org.netatalk.ResourceFork EA a Solaris extension?

You're welcome! Please let me know if you have any suggestions how to improve the docs or the software. I had the same thought at first! Unfortunately if you don't pass an icon to the AFP client you get exactly that: A volume without an icon. Just the volume name text on the desktop. What was...

@pl212 It's a great blog post, thanks for sharing! I read it a a while ago. :) The change in Netatalk v4 is that I removed the two leftmost icons from icon.h, and added these two that I drew. The top one is the new default, and the bottom can be activated with "legacy icon = sdcard". The rest...

I can address both of these. The volume name has an easy solution: Put a "volume name = My Volume" line in the volume definition to get case sensitive volume names. The netatalk 4.2.0 release notes talks about the reason for this change. Regarding the volume icon: In previous versions, the...

@saybur The ad toolsuite is meant to solve this exact problem, but as you've noticed it's terribly buggy. The one known workaround is to carry out the commands with the exact user that owns the shared volume root dir on the host. You can try chowning it to your main user and try again. I tried...

Good stuff, thanks for reporting back. A stable release will follow shortly. There are no other functional changes in this intermediate version apart from the Docker parameters.

The PRs have been merged! These changes will be included in the next stable release (aiming for some time next week.)

Thank you for the feedback! You're absolutely right, I accidentally caused a breakage while refactoring the container entrypoint script. This should bring back RandNum auth without using INSECURE_AUTH: https://github.com/Netatalk/netatalk/pull/2338 Would it be sufficient to have a login...