I would appreciate your input on this matter:

The Raspberry Pi can be used as an Apple IIGS boot device/file server with A2SERVER project. It is indicated that they use Netatalk 2.2.4 for this purpose, which was the last release of the version 2 binary until just about a week or two ago they released 2.2.5. Anyways, I couldn't get ddp to work with it. I used a ./configure string just like in the Guide and after following the same steps, still wouldn't work with Systems earlier than 7.5.3 & OT 1.3 OR MacTCP systems.

Could you possibly investigate why? The A2BOOT server uses DDP as well, no idea what's going on. I sent him an email and got zilch back.

RE: Guests -- ahh, you see, but it's a little more complicated than that. You can't share out the home directory to a Guest user because of permissions. Here's the section from the Guide:

To permit Guest access, run something like sudo mkdir /media/GuestF, then run sudo chmod 777 /media/GuestF so that the folder permissions (which will be owned by root) will permit read/write/execute operations for everybody, otherwise it won't work (user directories or any path of the File System cannot be shared without editing permissions, which is not advisable). Add the share path to /etc/netatalk/AppleVolumes.default like as shown earlier. Then edit the afpd.conf file so that the line at the bottom looks like the following (log feature not required, just for demonstration purposes) with the uams_guest.so, tacked on:

Code:

- -transall -uamlist uams_guest.so,uams_clrtxt.so,uams_dhx.so,uams_dhx2.so -nosavepassword -setuplog "default log_info /var/log/afpd.log"

Finally, restart the service with sudo /etc/init.d/netatalk restart to apply the changes, if it was already running. Note: Only use Guest accounts for special purposes because of the fairly serious security weakness. Logging is useful during troublesome times: look to sudo gedit /etc/netatalk/afpd.conf for two examples, one being the standard log and the much more verbose debug log. The log feature can also be enabled during the ./configure step.

Click to expand...

As I was wrangling with this issue, I found that using the -guestname flag didn't seem to make a difference. Maybe there is if you can use something like this, if the user is "floe": -guestname floe

I'm not sure if that would work, I doubt it. Maybe if you didn't allow the dhx and dhx2 uams, which is kind of stupid, but oh well. I also tried using the options: limitsize to limit the volume reporting to 2GB, didn't seem to work either.