John Baldwin wrote:
[ Trimming cc's a bit ]
On Wednesday, September 08, 2010 10:01:22 am Vadim Goncharov wrote:
Big thanks for your work, but unfortunately, the problem itself is not ISDN or
network stack, it is deeper. It is the policy or may be style of thought,
discourse. Something like:
progress dictates we need fix/maintainership to feature X
& we have no resources to maintain feature X
-> we announce theis need, but only to _limited_ audience, not wide circles
-> nobody responds
-> the X code is removed
AND we think this logic chain is correct, thought we did not things this way
even 5 years ago.
Actually, things have worked this way far longer than 5 years ago. For
example, we lost a few SCSI HBA drivers during the transition to CAM (e.g.
wds(4) was not present in 4.x but was eventually CAM-ified and reappeared
in 5.0). I suspect there was far less notice given for those drivers
than for ISDN (multiple notices to arch@ and current@ spread out across
many months).
On top of which, I'd say that the general philosopy is always that
you stick with the release that works for you. Surely the people who
"need" those ISDN drivers, simply stay with the release that works for
them. If they need new features as well as ISDN, they do a cost-benefit
analysis on writing drivers to fit the new framework.
- Mark
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[email protected]"
