IvanExpert
commented
8 years ago I hadn't heard of ciopfs before, but it sounded like a potentially good solution. I tried it out, and in Linux, it performed as hoped, where the mountpoint is the visible front end to another directory that is supposed to remain unaccessed, in which all the mixed case filenames in the front end directory are stored as lowercase. Cool.
UPDATE: it works. Skip a couple comments down.
Unfortunately, when I tried to get Netatalk to share the ciopfs mountpoint, even over plain old AFP-over-TCP to my Mac, it simply didn't show up among the list of available volumes. If I then unmounted the mountpoint, the folder being used for the mountpoint appeared as a shared volume as expected, so I don't think it's a Netatalk configuration issue. I'm assuming that Netatalk just decides that that mountpoint is unsuitable for use as a share for some reason, but I was unable to find any output or log files to offer any clues (doesn't mean they're not around, somewhere, though). For reference, I added user1 (or "pi" on the Pi) to the "fuse" group, so that I could use ciopfs without needing to be root, and I moved the shares from /media/A2SHARED/A2FILES to /home/user1/A2FILES.
I think it's still worth pursuing trying to get ciopfs to work; Netatalk's got to be not sharing that mountpoint for some reason, so if that were understood maybe it could be modified or coaxed into doing so.
It also might be worth experimenting with mounting an HFS+ or NTFS disk image and using that for a share point. In an early incarnation of A2SERVER I actually was using NTFS and it may have even been working (can't remember), but Steven Hirsch talked me out of it on the grounds that it certainly would hever have been tested with Netatalk and is very different than native Unix filesystems.
Another solution might be modifying Netatalk to, if the options:prodos attribute is set, to somehow crossreference an all-caps version of the filename to the mixed case version on the actual host filesystem. This would be beyond my skill set, but not Steven Hirsch's.
knghtbrd
The problem
While GS/OS works just fine with mixed case files, ProDOS 8 and the //e does not. If files on AppleTalk are not all in uppercase (or not all accessible in uppercase), it can't handle them.
The solution
Run your netatalk shares on a case-insensitive filesystem. Any time ProDOS 8 tries to access a file, it'll do so in uppercase. And it will succeed because case-insensitive! If you have a case-insensitive filesystem, just let netatalk know and happiness ensues!
Why the solution won't work
Linux is not case-insensitive. There's a case-insensitive version of ext3 and possibly ext4, but who knows how current it is, and then you have to patch in weird 3rd party driver mods to a critical system driver on a production system. This isn't 1998 here!
The potential solution to the problem with the solution
http://www.brain-dump.org/projects/ciopfs/
FUSE driver that makes things look case-insensitive, even though the underlying filesystem actually isn't. I dunno if this is packaged in Jessie, it almost certainly isn't in Wheezy. But if it's not too complex, it might be really worth looking into.
@IvanExpert have you heard of this one before?