Search results

@Mk.558 Thanks for the solid feedback, as always! I restructured the Quick Start page and put the list of requirements in the middle, as part of a more natural flow of operations. To your point, it might be worth experimenting with splitting the list so that only mandatory requirements come in...

I've been tinkering with the organization of the documentation lately, since I was able to lift it all into Markdown in the last release cycle which makes it much easier to work with. Right now my thinking is that the entry point is the documentation page on the website...

This is such an amazing reference resource. Thanks for your heroic push to overhaul it!

Do you already have a bridge between your LocalTalk and Ethernet networks (where the RPi sits)? If so, connecting your ImageWriter to the LocalTalk network should be enough to make it accessible from the RPi that's running netatalk / pap. Note that in general, you want to avoid routing...

Quick poll: of you netatalk users here, is anyone relying on the "include = /path/to/extra_afp.conf" directive in afp.conf? For context, this is a directive that allows you to dynamically load and nest a secondary afp.conf file. However this relied on local hacks to the iniparser library. I am...

This developer is I. Haha. @NJRoadfan and I discussed this topic a few months ago when working towards the v4 release. We didn’t have a concrete reason to change it at the time. But the use case at hand is a fair reason. No promises, but I’ll tinker with this and see how feasible it is to...

It's best to start the daemon directly rather than using systemd, to get more helpful output. I.e. run "papd -d" from the terminal.

Yep, "ad" is your friend. See the man page for usage notes: https://netatalk.io/stable/htmldocs/ad.1 Note that netatalk has to be running to use ad, because it relies on access to the CNID daemon to carry out the metadata update.

This might be the ideal stress test scenario for these code changes! To explain what I'm up to: I want to proactively shore up security and memory safety in 4.2, leveraging SonarQube static analysis. So far, I was able to resolve all security bugs – the outstanding ones had to do with PAM...

Are you using zones in your network by any chance? There is a small logic change here, where we break out of the inner while loop when we hit the end of the linked list containing routing information, and goes back to the outer while loop that iterates over zones. I *think* this is the correct...

That sounds promising. Would you be able to test this solution? https://github.com/Netatalk/netatalk/pull/1992 It should take care of the initial problem of accessing freed memory, while not introducing memory corruption. :)

And you're running the bleeding edge code, right? I might have caused the crash with this commit. Can you try reverting this and see if runs more stably then?

Excellent, I'm glad that it wasn't a new bug. We'll figure out how to implement NetBSD quota properly one of these days. Until then, I'm going to go ahead and hard code the build system to disable quota when building on NetBSD. This kind of insidious fail state is the worst. ;)

Can you please try building with "-Dwith-quota=false" and see if that makes a difference in behavior? We have had long-running trouble with the built-in libquota on NetBSD. See f.e. https://github.com/Netatalk/netatalk/issues/1900

@thecloud The fix for ASP connections has been merged. The new server name option should be ready to ship. :)

Yes, well spotted. After some testing I found that name was too ambiguous in certain contexts. Correct, hostname is now treated as a fallback when server name hasn't been defined. Now a friend has reported to me that there is missing code for registering server name for ASP connections...

@thecloud With this PR, I introduce a new Global option "server name" which should have the effect that you desire. https://github.com/Netatalk/netatalk/pull/1974 Please test it in your AppleTalk environment. I don't have any vintage Macs handy right now because of my current living...

Strike that. The hostname option is actually used in dsi_tcp_init() for an addrinfo() call. I can see the argument for introducing a new option that allows you to set the server name independent of the hostname.

This is an astute observation. Unless I'm overlooking something obvious reading the code, the documentation is plain wrong. The hostname option is used as server name and nothing else. The naming might come from the fact that if you don't explicitly set hostname, the server name is determined by...

PR merged to main! I also updated the afp.conf man page with descriptions and examples of the new behavior. This won't break anyone's existing configuration. Just that volume names will default to all lowercase, as observed by pl212. Here's a sample afp.conf that I added to the man page...