Re: Feature Removals for 2.6.25

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Stephen Hemminger <shemminger@...>
Cc: Harvey Harrison <harvey.harrison@...>, Andrew Morton <akpm@...>, David Miller <davem@...>, Jiri Slaby <jirislaby@...>, Pavel Machek <pavel@...>, Christoph Hellwig <hch@...>, Dominik Brodowski <linux@...>, Andi Kleen <ak@...>, Adrian Bunk <bunk@...>, Arjan van de Ven <arjan@...>, Greg Kroah-Hartman <gregkh@...>, Nick Piggin <npiggin@...>, LKML <linux-kernel@...>, Randy Dunlap <randy.dunlap@...>, Len Brown <len.brown@...>
Date: Thursday, February 14, 2008 - 2:16 pm

Stephen Hemminger wrote:

And those of us who are using it *have* old hardware. Old hardware that 
perhaps the people forcing other driver on us don't have.

I guess I have a real problem with the "make die hard users report 
problems" thing, because it assumes that there is nothing wrong with 
*causing* us problems. Understand, this is not "change is bad" but 
"change is expensive." Because it means a change in kernel config, 
modules.conf, and possibly rc.local or initrd or similar. A per-machine 
effort which is small in ones, and large in sum.
If this were a case of the sk98lin driver needing work, I wouldn't be 
making the argument. But to make work for users in a case where there is 
no saving in effort for developers, sounds as if the developers place no 
value at all on the time of the people who build their own kernels, and 
if the vendors are good with it, that's all that matters.

Note that because the hardware is old, it's highly likely that most of 
it will be retired before that sk98lin driver needs a change. I can't 
see anyone using sk98lin on a new system, so it would be less 
contentious to let the hardware (or users) die of natural causes if you can.

-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 


--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Feature Removals for 2.6.25, Harvey Harrison, (Thu Jan 31, 9:38 pm)
Re: Feature Removals for 2.6.25, Bill Davidsen, (Wed Feb 13, 10:49 pm)
Re: Feature Removals for 2.6.25, Stephen Hemminger, (Wed Feb 13, 10:55 pm)
Re: Feature Removals for 2.6.25, Bill Davidsen, (Thu Feb 14, 2:16 pm)
Re: Feature Removals for 2.6.25, Arjan van de Ven, (Thu Feb 14, 2:24 pm)
Re: Feature Removals for 2.6.25, David Newall, (Thu Feb 14, 7:20 pm)
Re: Feature Removals for 2.6.25, Rene Herman, (Thu Feb 14, 11:27 pm)
Re: Feature Removals for 2.6.25, Christoph Hellwig, (Thu Feb 14, 2:26 pm)
Re: Feature Removals for 2.6.25 - old NCR53C9x driver, Boaz Harrosh, (Sun Feb 3, 6:44 am)
Re: Feature Removals for 2.6.25, Nick Piggin, (Fri Feb 1, 9:29 pm)
Re: Feature Removals for 2.6.25, Stephen Hemminger, (Fri Feb 1, 3:08 am)
Re: Feature Removals for 2.6.25, Arjan van de Ven, (Fri Feb 1, 12:53 am)
Re: Feature Removals for 2.6.25, Harvey Harrison, (Fri Feb 1, 1:18 am)
Re: Feature Removals for 2.6.25, Arjan van de Ven, (Fri Feb 1, 2:33 am)
Re: Feature Removals for 2.6.25, Harvey Harrison, (Fri Feb 1, 3:04 am)