• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

Yet Another Netatalk 2.2 Fork

Mk.558

Well-known member
Thank you for the feedback.

What I'll probably end up doing is making a separate subheading that points to your site/references this Netatalk 2.2 fork, along with the advantages of doing so. Netatalk 2.1.6 doesn't really do anything your fork doesn't already do, the work on it just makes it better, and it's not like Netatalk is a drag on system resources these days anyways.

Some time ago I found about the tinymacipgw project, and I liked it, but felt it was too limited. Some day I'll have to find out a limited GUI (I played with Linux mostly around 2010, and while I maintain it as a backup OS on all my systems, I really don't use it) system like Lubuntu was back in the day that ideally takes up less than 500MB but is otherwise fully functional and has the full Netatalk 2.2 + macipgw integration that I can run in a VM. Console-only VMs with very little extendability/no GUI tend to make my head hurt -- not to mention, I find it easier to pull up gedit or whatever and edit the .conf files rather than using vi or vim.

About your neat little tutorial:

A) Generally if it's Netatalk 2.1/2.2, anything all the way back to a 512K with System 3.3/Finder 5.4 using AppleShare WS 1.1 can connect to it see here. That's a 512Ke but a 512K will work the same
B) I was never really able to get 7.1 working with OT 1.3/AppleShare Client 3.7.4 to work with Tiger but maybe one day I'll buckle down again and try to figure out how to do it. Copying extensions over manually without using the Installer is a good way to get reliable system bombs
C) I've got a question -- in the Guide, I reference to make a temporary share in /media/ (it's referenced in the Guest client connection): my Linux techspeak is a bit weak. I don't think that's a good place to put a temporary share, and I honestly have no idea where you'd put a folder accessible by every user (think of sharing the Programs folder of your vintage mac's hard drive) on a *NIX box. I don't think that's a thing, most of the time you share a folder in the user home directory or something? I don't know. Put it in /var/? I asked this before like 10 years ago and nobody could give me a concrete answer
D) Lot of good stuff, nice job

reminder to self: 512K/512Ke to phonenet RXD/TXD wiring
 
Last edited:

slipperygrey

Well-known member
C) I've got a question -- in the Guide, I reference to make a temporary share in /media/ (it's referenced in the Guest client connection): my Linux techspeak is a bit weak. I don't think that's a good place to put a temporary share, and I honestly have no idea where you'd put a folder accessible by every user (think of sharing the Programs folder of your vintage mac's hard drive) on a *NIX box. I don't think that's a thing, most of the time you share a folder in the user home directory or something? I don't know. Put it in /var/? I asked this before like 10 years ago and nobody could give me a concrete answer
This is for read-only access for Guest users, right? I would recommend either /srv or somewhere in /home. On the other hand, /var is supposed to be used for volatile data I think, not really long-term file storage. See also: https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

D) Lot of good stuff, nice job
Thank you!
 

gsteemso

Well-known member
This is for read-only access for Guest users, right? I would recommend either /srv or somewhere in /home. On the other hand, /var is supposed to be used for volatile data I think, not really long-term file storage. See also: https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard


Thank you!
Reading the Wikipedia summary of that, it's pretty clear that /srv is the correct place - it's for files and other data that the machine serves.

If the shared file store was to be externally writeable, well, that would run counter to the stated semantics of the /srv directory - but it would nevertheless be in keeping with the actual purpose, so I personally would just keep it there anyway.
 

Mk.558

Well-known member
My Linux skills are not in shape recently.

I'd like a tarball archive of the 2.2.10 fork. I have no idea how Github works so when I don't see a download link that I need to shuffle around disks I get confused. Is there one?
 

Arbee

Well-known member
Thanks for all your work on this, @slipperygrey ! I was able to get 2.2.10 up and running on my home server (running Fedora 38) with relatively little drama, and I'm able to connect equally well from emulated System 7 in MAME all the way up to the just-released macOS 14.1 Sonoma developer beta. I do have to manually modprobe appletalk before atalkd will start, maybe future systemd scripts can do that?
 

slipperygrey

Well-known member
Thanks for all your work on this, @slipperygrey ! I was able to get 2.2.10 up and running on my home server (running Fedora 38) with relatively little drama, and I'm able to connect equally well from emulated System 7 in MAME all the way up to the just-released macOS 14.1 Sonoma developer beta. I do have to manually modprobe appletalk before atalkd will start, maybe future systemd scripts can do that?
You're welcome, happy that it's useful to you!

I'm a Debian user where the appletalk module is loaded automatically, as NJRoadfan says.

Getting a more seamless experience on Fedora would definitely be nice. First question: Do you have to compile the module yourself or is it included with Fedora 38 by default?

If you have a Github account it would be great if you could create a ticket for this so that we can figure out the best solutions: https://github.com/Netatalk/netatalk/issues
 

Arbee

Well-known member
The module's included (it's in the kernel-modules-extra package, which usually isn't installed by default, but has a lot of useful things in it). I have a GH account, I'lll go ahead and create a ticket.
 
Top