From: Daniel M. <da...@mi...> - 2025-04-02 05:07:01
|
Hi Michael, I agree that there are valid reasons for wanting case-sensitive volume names. Therefore we have introduced the "volume name" option in this version. If you set "volume name" to the string that was previously the section ID, you will get the same behavior as previously. For example: [my volume] path = /my/path volume name = My AFP Volume The full release notes has some more details and discussion on this, as well. Cheers, Daniel On Tuesday, April 1st, 2025 at 11:27 AM, Michael Grundmann <mi...@li...> wrote: > > > Am 31.03.25 um 23:41 schrieb Daniel Markstedt: > > > > So far, Netatalk has relied on ini section names for volume names. > However, upstream iniparser treats section names as case insensitive, > and will force them to lowercase internally. Hence, you will see that by > default, your volumes are now named in all lowercase. For instance, if > your volume section is defined as [My AFP Volume] it will be mounted as > my afp volume on a Mac. > > > Hi - I don't know, but I think thats not a good idear - what is whit the > pathnames of pictures in Indesign-Documents > > /Volumes/My AFP Volume/pictures/1.jpg ≠ /Volumes/my afp > volume/pictures/1.jpg > > > So - I don't know > > > > The Netatalk dev team is proud to present the first version in the 4.2 release series. > > > > Find the release notes and tarballs at: > > https://github.com/Netatalk/netatalk/releases/tag/netatalk-4-2-0 > > > > The theme for this release series is security and reliability. > > > > We are now more aggressively controlling and validating the size of buffers, check for NULL pointers, free dynamically allocated memory, initialize variables before use, control filesystem access with file handlers to avoid race conditions, and so on. > > > > For the first time ever, we pass our own Quality Gate on SonarQube. > > https://sonarcloud.io/summary/overall?id=Netatalk_netatalk&branch=main > > > > While we haven't seen any side effects in our testing, there is a small chance that edge cases are seeing different behavior now, for instance due to C strings being truncated instead of allowed to overflow. If you find new bugs, please report them to us! > > > > There are also two notable dependency changes: > > > > We now depend on a shared iniparser library, rather than the bundled one used since v3.0. > > This leads to some marginal changes in ini parser behavor, since our local library was heavily modified. > > However we believe this is a beneficial move in the long run, since iniparser is an actively developed library. > > > > Secondly, we have converted all documentation from XML to Markdown. > > This removes the dependency on the XML stack and DocBook XSL stylesheets. > > Rather, we now use cmark to generate man pages from Markdown sources. > > > > Beyond this, there are a large number of quality-of-life improvements and bugfixes in this release. > > > > A big thanks to all contributors! > > > > We are looking forward to your feedback. > > > > Sincerely, > > > > Daniel > > > > _______________________________________________ > > Netatalk-admins mailing list > > Net...@li... > > https://lists.sourceforge.net/lists/listinfo/netatalk-admins > > > > -- > Gruß Michael > > Wenn du verstehst, was du tust, wirst du nichts lernen > > > _______________________________________________ > Netatalk-admins mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/netatalk-admins |