Linux kernel drops AppleTalk Networking

in the same news, the code will be moved to github.com/linux-netdev/mod-orphan

Based on this, I understand it should be possible to build an external module.

Also, while looking for an alternative, I stumbled upon this project

It aims to create a userspace implementation of AppleTalk
 
My understanding is maintaining an out-of-tree module can be challenging: the whole "we don't break userspace" mantra doesn't apply to the kernel's internal interfaces which can rapidly change without much warning.

I think TaliTalk is being done by @Bolacore here?Absolutely no disrespect to what they're doing, it's quite interesting, but Netatalk has been around for a long time (I mean, I've been a user for like 20+ years). There's something to be said for codebases that have decades of testing and bugfixes applied. I personally won't be looking for an alternative unless the devs decide they don't want to continue work on the project.
 
That’s me yes, but it targets a very different purpose than Netatalk. TailTalk is a really primitive stack by comparison as we don’t do any packet routing, zones, or things like that as I figured if you needed those you’d use the battle tested software made for that purpose (I.e Netatalk). Maybe that will change in the future, I just didn’t want to bite off more than I could handle at this point.

Quite a shame to see it dropped, but I can’t say I’m surprised either. Just hoping the out of tree sources now won’t be too hard to keep updated against the newer kernels.
 
So an exaflop datacenter burned 18 tons of coal and its conclusion was to delete 512kB of perfectly functioning code? bravo.
 
If there is enough feedback the removal will be postponed. That is the most straightforward approach now. If nobody complains, then the kernel networking folks will be justified.

They need an active maintainer who can chug through the AI generated bug reports.
 
very disappointing but not surprising given the real AI chaos around the kernel right now, appletalk in the kernel has been in danger for a while

I haven't looked closely at the code, but (hubris incoming) it's only a few thousand lines, I wonder how difficult a small interface would be (especially considering netatalk is more or less the only user of the kernel appletalk stack).
 

Thanks AI....

Can't say I'm surprised given the slop of AI bug reports flooding everything. Overall it seems to be driving maintainers of open source software to the point of quitting at an alarming rate. Hopefully it won't be too hard to compile out-of-tree or be replaced with something user space. Really puts a damper on work I did for Netatalk and A2SERVER.
I thought the kernel gurus had agreed to back off on this due to community pushback?
 
Back
Top