Breaking system configuration in stable kernels

[Bill Davidsen]

  I've beaten this dead horse before, but Linux will not look to
management like a viable candidate for default o/s until whoever releases
new versions of *stable* kernel series with cosmetic changes which break
existing systems running earlier releases of the same stable kernel
series.

  The last time I complained, it was about changing the name of a module
itself, this time the names of the parameters of modules have been
changed. Couldn't that have waited for 2.5, or for-bloody-ever? The names
of the parameters to the cmpci module were changed, for example from
"fm_io" to "fmio" which prevents the module from loading with a newer
kernel. And if the "options" line in modules.conf is changed, then it
won't load with older kernels. Maybe I'm to only one who has to roll back
out of a new release?

  This is serious, because the module can't be loaded by hand if
modules.conf has invalid parameters. So loading would have to be moved to
rc.local, and done with correct parameters, which eliminates demand
loading of the module. PITA when sound is only loaded to play a message to
the operator to change the backup media.

  I love getting problems like this on my vacation, I'm pissed, and I
really think it indicates a lack of attention to detail. I think I saw
this in another module while doing a quick diff and grep, but it should be
in any modules. Cosmetic changes which impact users can wait, even
including fixes in spelling in error messages, since people *do* grep logs
for them. Grrr!

-- 
bill davidsen <[e-mail]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.