Post #1666075
2026-04-25 07:38 UTC
Replies (6)
-
@zhenech@chaos.social 2026-04-25 07:42
@kernellogger 3c509? Whoa. Used those in my first router box at home. That's probably 25 years ago now.
-
@klausman@mas.to 2026-04-25 08:15
@kernellogger One thing that bothers me about this (not that I think it's anyone's fault, or that I have an easy solution) is the people that have a genuine need for these old drivers (like the guy who spoke up about the 905), but that _don't_ follow LKML closely. They will likely only find out about this a year or more later when that kernel makes it to their distro, and then they are SOL and will have to ask someone to maintain the patch that keeps the driver around, likely for lots of cash.
-
@hackbyte@joinfriendica.de 2026-04-25 10:15
@kernellogger Heh .... ok ISDN and the 3c509 stuff is sad.. truly.. But at ax25 and amateur/ham-radio stuff, it may worth to wait a bit for their removal, as HAMs just recently start to discover linux for their needs.... Usually their stuff is always windows based because everyone has windows.. But they get tired of microslop too .... so still having native ax25 and others ham radio related stuff might be a good thing ... at least for a while still.
-
@mxk@hachyderm.io 2026-04-25 16:05
@kernellogger haven't checked, but can any of those thinks be used as part of the lib-target? That might be an okayish solution to keep networking code usable without needing to keep it in the Kernel. I am clearly pro cleanup. Things that nobody frequently tests and that are defacto unmaintained create a false sense of security and are better removed from the Kernel.
-
@penguin42@mastodon.org.uk 2026-04-25 17:48
@kernellogger I'd like some clarification over whether there are outstanding security reports against this pile; i.e. what's the situation on older stable kernels which still have these?
-
@florian@owo.ff15.eu 2026-04-26 20:25
@kernellogger ig @c3isdn does not count as a production environment 🙃