Recent content by slipperygrey

Major netatalk news: we now support SQLite as the CNID database backend for the AFP file server, in the main development branch. Why is this big news you ask? Thank you for the great question! For the last two decades (since at least v1.5 in 2002) netatalk has been using Berkeley DB as the...

@opualuan not to hijack the thread, but we're a friendly community that can help with netatalk compilation problems too. One option is to head over to the netatalk project GitHub Discussions section and start a new Q&A thread. The netatalk wiki has a range of OS specific guides as well that...

So does this mean you're connecting only one of these machines at a time to the AsanteTalk? And you're using a non-twisted serial cable, and not something like PhoneNet with termination on both ends, for instance?

That sounds quite useful, nicely done!

You're probably thinking of MacProxy Plus. https://github.com/hunterirving/macproxy_plus The fork of my fork of the original macproxy python flask script. :)

@mactjaap Just in case you didn't notice: a new feature as of netatalk v4.2.1 is the bundling of Thomas Kaiser's pap backend for CUPS. You can enable it with "-Dwith-cups-pap-backend=true" in the build system. I believe you're currently bundling the same backend script yourself, so up to you...

To make a long story short, we all moved on to other projects. One of the former devs (Uwe) is now maintaining his own fork called scsi2pi (which doesn't come with its own GUI but rather is compatible with, and rely on the piscsi Web UI. So packaging scsi2pi with the piscsi Web UI could actually...

@mactjaap On this topic, have you considered bundling piscsi (or scsi2pi) and the piscsi Web UI with your distribution? The piscsi app itself is very light-weight so it shouldn't be much of an overhead for the RPi on top of the other software that you're bundling. Particularly relevant...

Speaking about hostname, once you upgrade to netatalk 4.2 you get access to the new "server name" option that allows you to set the name of the AFP server independent of hostname. (This was a feature of netatalk 2.x but fell off in 3.x...) May come in handy for you all.

In addition to the containerized webmin discussed in the netatalk 2.4 thread, I also got the mysql CNID backend up and running in containers a few days ago. The original intention was for testing purposes: to test the mysql backend in continuous integration and stop me from breaking it (again.)...

A solution to this issue has been merged into the main branch now. I introduced a dynamic module option that hides away the "service actions" that expect the netatalk daemons to be locally available. This option gets enabled by default when building the webmin module via the Dockerfile. So now...

Being stuck at home over the Easter weekend fighting off a cold, I had the inspiration/time to work on this. Over at the feature request ticket that you raised, I have explained the solution at a high level. In the end, I settled on the config file polling option. Hopefully it won't have too...

@Mk.558 at risk of going off topic, have you by any chance serviced the floppy drive in your SE/30 in recent years? In my experience from refurbishing dozens of Mac floppy drives, more than 90% of drives of that era that I worked on were restored to full functionality after being stripped down...

My macproxy fork has been effectively obsoleted by macproxy plus: https://github.com/hunterirving/macproxy_plus You may want to use this one instead!

In my experience it's surprisingly consistent. I test nonstop on 12 different platforms. :)