Bug #792
closedNuke Arcnet and Token Ring support from kernel
0%
Description
Unless no one objects with good enough arguments, I'd like to commit
these patches in Monday:
http://leaf.dragonflybsd.org/~hasso/nuke-arcnet.patch
http://leaf.dragonflybsd.org/~hasso/nuke-token-ring.patch
There have been opinions to do the same with FDDI, but I'm not so sure.
Unlike Arcnet and Token Ring I know FDDI still be used in some networks
(although in the old ones nobody touches any more, but still). Opinions?
Updated by dillon over 17 years ago
:Unless no one objects with good enough arguments, I'd like to commit
:these patches in Monday:
:
:http://leaf.dragonflybsd.org/~hasso/nuke-arcnet.patch
:http://leaf.dragonflybsd.org/~hasso/nuke-token-ring.patch
:
:There have been opinions to do the same with FDDI, but I'm not so sure.
:Unlike Arcnet and Token Ring I know FDDI still be used in some networks
:(although in the old ones nobody touches any more, but still). Opinions?
:
:--
:Hasso Tepper
I think we can safely nuke it.
-Matt
Matthew Dillon
<dillon@backplane.com>
Updated by tuxillo over 17 years ago
On Sat, 25 Aug 2007 03:22:14 +0300, Hasso Tepper wrote:
I'm not absolutely expert in anything but I would like to know why this
drivers are nuked instead converted into modules. thanks
Updated by erik-wikstrom over 17 years ago
It's a question about code maintenance, changes to other subsystems
might require changes to the code for Token Ring and such, and if none
uses them you can't be sure that those changes really work, only that
they compile. And if none uses them then making the changes is just
unnecessary work, so it's easier to just remove them.
Making them modules would not solve this problem, just add the extra
work of modulising the code that none will use anyway. And once again
you have none testing to see if the module-versions really work.