| Click here to select a new forum. |
| Netatalk 2.2.8 Released |
Posted by: slipperygrey on 2023-03-04 22:56:54
@CTB Great! It's expected that guest access is read only. Since a2boot and timelord are working, it means that atalkd is working perfectly. The only problem is that afpd isn't being registered with atalkd as an AppleTalk service. Try using systemctl to stop afpd, wait a few seconds, then start it again. Usually takes care of the problem. |
Posted by: CTB on 2023-03-05 05:11:25
I know how to start afpd with systemctl. How do I stop afpd with systemctl? |
Posted by: slipperygrey on 2023-03-05 10:08:17
I know how to start afpd with systemctl. How do I stop afpd with systemctl? You replace 'start' with 'stop' in the command that you use.
sudo systemctl stop afpd |
Posted by: CTB on 2023-03-05 13:19:52
Well that seems pretty simple. I have been using 'sudo systemctl start afpd.service'. Is the .service necessary? |
Posted by: CTB on 2023-03-05 13:26:12
It worked a treat. Thanks for all your help and also your work on resurrecting Netatalk 2.2.x for the community.
pi@retropi:~/netatalk-2.2.8 $nbplkup
retropi:AFPServer 65280.201:129
retropi😛roDOS16 Image 65280.201:3
retropi:Apple //e Boot 65280.201:3
retropi:Apple //gs 65280.201:3
retropi:TimeLord 65280.201:128 |
Posted by: slipperygrey on 2023-03-05 16:12:14
Well done! You're welcome, thanks for using it. And no, ".service" is optional when using systemctl. |
Posted by: CTB on 2023-03-05 16:47:56
Can nbplkup be used to see if atalkd is running similar to what you see with afpd (pi:AFPServer 65280.201:129)? |
Posted by: slipperygrey on 2023-03-05 17:16:04
That you're getting the above output from nbplkup is exactly evidence that atalkd is running. It is atalkd that manages those servers registered with NBP running on your RPi that you see there. If atalkd wasn't working correctly nbplkup wouldn't see anything running on the Pi (although it can see servers running on Macs or other netatalk instances on the network.) |
Posted by: CTB on 2023-03-05 21:05:24
Thanks for clarifying. I will test the server via DDP with my SE/30 running system 7.1 in a few days. The server shows up fine on Basilisk II via AFP. |
Posted by: slipperygrey on 2023-03-05 21:51:34
It should work, as long as they sit on the same ethernet network!
Just to be pedantic again: the file sharing protocol is AFP regardless of whether it's over IP or DDP. What you wanted to say was "AFP over IP", as opposed to "AFP over DDP". In fact, an early product name Apple used when selling it as a commercial product for enterprises was "AppleShare IP".
e.g. https://macintoshgarden.org/apps/appleshare-ip-502 |
Posted by: CTB on 2023-03-05 22:01:07
Got it. My server works on AFP over IP. I am going to test AFP over DDP when I get to a machine that can see it. That would be my SE/30 with an ethernet card running System 7.1.
I have a question regarding the installation instructions. You mention in the "AppleTalk Support in Kernel" section
"to check if your kernel has AppleTalk support, first start the atalkd daemon, then issue this command and inspect the output:
$ lsmod | grep appletalk"
What output is expected if the AppleTalk support is indeed present? |
Posted by: CTB on 2023-03-05 22:41:20
It should work, as long as they sit on the same ethernet network!
Just to be pedantic again: the file sharing protocol is AFP regardless of whether it's over IP or DDP. What you wanted to say was "AFP over IP", as opposed to "AFP over DDP". In fact, an early product name Apple used when selling it as a commercial product for enterprises was "AppleShare IP".
e.g. https://macintoshgarden.org/apps/appleshare-ip-502 I worked for Apple for 25 years (recently retired) and I remember the launch of AppleShare IP and the confusion it caused. This was because AppleShare was always the product name for the serve software. At the time we were told to express the various versions/combinations as AppleTalk over LocalTalk, AppleTalk over Ethernet and AppleTalk via IP. AFP at the time was interchangeable with AppleTalk even though technically not correct 😉 |
Posted by: slipperygrey on 2023-03-05 23:00:36
Got it. My server works on AFP over IP. I am going to test AFP over DDP when I get to a machine that can see it. That would be my SE/30 with an ethernet card running System 7.1.
I have a question regarding the installation instructions. You mention in the "AppleTalk Support in Kernel" section
"to check if your kernel has AppleTalk support, first start the atalkd daemon, then issue this command and inspect the output:
$ lsmod | grep appletalk"
What output is expected if the AppleTalk support is indeed present? The output should be something like this, indicating that the appletalk module is indeed loaded:
$ lsmod | grep appletalk
appletalk 36864 24
The reason my guide says to run atalkd first, is because I have observed on Debian that the module is dynamically loaded only when atalkd starts up. I can't say whether this will always be the case or not.
If you're able to run atalkd and nbplkup without error you should be golden. |
Posted by: slipperygrey on 2023-03-05 23:04:48
I worked for Apple for 25 years (recently retired) and I remember the launch of AppleShare IP and the confusion it caused. This was because AppleShare was always the product name for the serve software. At the time we were told to express the various versions/combinations as AppleTalk over LocalTalk, AppleTalk over Ethernet and AppleTalk via IP. AFP at the time was interchangeable with AppleTalk even though technically not correct 😉 Thanks for sharing your insights! If folks internally at Apple at the time also got the terminology "wrong" that would suggest a marketing / education challenge for sure. 😉
What notable products / parts of the company did you work with over the years? |
Posted by: CTB on 2023-03-05 23:10:21
The output should be something like this, indicating that the appletalk module is indeed loaded:
$ lsmod | grep appletalk
appletalk 36864 24
The reason my guide says to run atalkd first, is because I have observed on Debian that the module is dynamically loaded only when atalkd starts up. I can't say whether this will always be the case or not.
If you're able to run atalkd and nbplkup without error you should be golden. This was my result.
pi@retropi:~ $ lsmod | grep appletalk
appletalk 36864 24
psnap 16384 1 appletalk |
Posted by: CTB on 2023-03-05 23:14:23
Thanks for sharing your insights! If folks internally at Apple at the time also got the terminology "wrong" that would suggest a marketing / education challenge for sure. 😉
What notable products / parts of the company did you work with over the years? 1996-1999 I managed Apple Australia's K-12 Eduction business
1999-2021 I managed Apple Inc's Worldwide Developer Relations group in Asia Pacific |
Posted by: CTB on 2023-03-09 01:51:20
I am pleased to report that my SE/30 running System 7.1 sees the 2.2.8 server in the Chooser. |
Posted by: slipperygrey on 2023-03-09 11:30:02
Right on! Enjoy vintage Mac file sharing. 🙂 |
Posted by: CTB on 2023-03-13 13:24:31
Dumb question but how do I get atalkd.service, afpd.service, timelord.service and a2boot.service to all launch automatically at startup of the pi? |
Posted by: slipperygrey on 2023-03-13 15:41:37
Dumb question but how do I get atalkd.service, afpd.service, timelord.service and a2boot.service to all launch automatically at startup of the pi? For starters, you have to make sure you enable the services with systemctl. That's one of the steps in my guide so I assume you did this already.
An issue that has recently been identified is that atalkd will fail to start up if it takes too long to bring up the network interface and establish a network connection. This is particularly common with wifi only RPis (e.g. Zero W). You can edit the service files as per the linked PR and see if that helps. |
| < 2 > |