Breaking system configuration in stable kernels
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines · Chris Siebenmann
You write:
| 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.[...]
| I love getting problems like this on my vacation, [...]
Quoted 6 lines
Although I sympathise, I have to ask: why are you rolling new kernels
(or new anythings) onto production servers without testing and a reversion plan? In years of experience with all sorts of vendors as well as Linux, I have yet to see *anyone* be reliable about this (the worst offender I've ever had to deal with was SGI, who would release 'urgent' kernel patches with crash bugs).
I certainly had a reversion plan and backups, but I don't have in-house hardware duplicating every client configuration. But there's only so much testing you can do before you put user load on the machine. Also, existing machines doesn't mean irreplacable mission critical machines, I don't upgrade unless I have a reason, and piss-poor VM performance certainly is a reason.
Quoted 7 lines
I strive to never put anything on our servers that I have not tested
on an expendable machine that is configured as closely as possible to the server. And I also try not to be anywhere near the leading edge on production servers, unless there is some strong benefit to it.The only time I roll something out 'right now stat!' is when it is
an urgent security fix.
I don't have that luxury. I can't afford to have a copy of most machines, and after load and stability testing I have to try on production machines. None of which addresses the issue that parameter name changes buy nothing functional, and can cause serious problems. If the module in question was needed for boot and in the initrd file the system wouldn't boot at all and there would be little to tell why.
I'd like Linux to be more widely used, and things like this are not invisible to the people who choose standards.
Signature · 3 lines
bill davidsen <[email protected]> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.
Quoted 5 lines · Bill Davidsen
Quoted 3 lines · Chris Siebenmann
You write:
| 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
Then educate "management". Have them use another Operating System. Try Microsoft Windows-2000/Professional. I've got it on my lap-top. It has never crashed so it's pretty good by Microsoft standards. However, I just finished downloading the latest Linux-kernel by using FTP on that machine. I didn't want to tie up this machine. I started the download at about 11:00 this morning. It finished around 3:00 this afternoon. We have a 1.3 GHz fiber link and the LAN is 100 MB/s. Pretty good for something that usually takes 5 minutes on Linux.
As I see it, you get the chance to complain about some poor performance because you don't have anything to compare present performance against. So, you upgrade to a minimally-tested kernel and complain that it's not a "viable candidate for default o/s..." -your words. Guess what, this complaint will always fall upon deaf ears.
What will help get your bleeding-edge kernel stable, is a bug report, a performance report, and sometimes even a "Hey... This one works great!".
Don't ever expect the kernel's internals to remain constant. This means that you will have to modify any of your custom modules for each and every kernel you download.
You can expect the API to remain constant. If it doesn't you have a valid beef. Otherwise, you will be talking to the forest.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
I was going to compile a list of innovations that could be attributed to Microsoft. Once I realized that Ctrl-Alt-Del was handled in the BIOS, I found that there aren't any.
In article <[email protected]>
[email protected] wrote:
| As I see it, you get the chance to complain about some poor performance | because you don't have anything to compare present performance against. | So, you upgrade to a minimally-tested kernel and complain that it's | not a "viable candidate for default o/s..." -your words. Guess what, | this complaint will always fall upon deaf ears. | | What will help get your bleeding-edge kernel stable, is a bug report, | a performance report, and sometimes even a "Hey... This one works great!". | | Don't ever expect the kernel's internals to remain constant. This means | that you will have to modify any of your custom modules for each and | every kernel you download. | | You can expect the API to remain constant. If it doesn't you have | a valid beef. Otherwise, you will be talking to the forest.
There seems to be confusion about the meaning of "stable." The stable
kernel series should be getting bug fixes, and the untested changes should go into the development (like 2.5) series where no one would expect it to be stable.
There should be no bleeding edge stable kernels, my point exactly. As
long as Linux behaves like a hacker's dream it will be perceived as such. When a stable kernel is released someone interested in reliable operation should take it over. We should not have "oh, shit, don't use" stable versions. For all the new features, the -ac kernels have consistently been more stable, because, as Alan says, "I run these kernels on my machines" and they behave like it.
| Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips). | | I was going to compile a list of innovations that could be | attributed to Microsoft. Once I realized that Ctrl-Alt-Del | was handled in the BIOS, I found that there aren't any.
Microsoft has actually had two good ideas; the software floating
point in the FORTRAN compiler for the 8080 CP/M system (one extra bit of precision) and MS-CHAP to prevent clear text passwords from passing on the net. Can't think of anything else which impressed me...
Signature · 4 lines
bill davidsen <[email protected]> "If I were a diplomat, in the best case I'd go hungry. In the worst case, people would die." -- Robert Lipe
Quoted 4 lines · [email protected] (bill davidsen) writes:
Microsoft has actually had two good ideas; the software floating
point in the FORTRAN compiler for the 8080 CP/M system (one extra bit of precision) and MS-CHAP to prevent clear text passwords from passing on the net.
Kerberos predates the latter by quite a bit.
-Doug
Signature · 2 lines
Let us cross over the river, and rest under the shade of the trees. --T. J. Jackson, 1863
Quoted 8 lines · Doug McNaught
Quoted 4 lines · [email protected] (bill davidsen) writes:
Microsoft has actually had two good ideas; the software floating
point in the FORTRAN compiler for the 8080 CP/M system (one extra bit of precision) and MS-CHAP to prevent clear text passwords from passing on the net.Kerberos predates the latter by quite a bit.
And numerical analysis types will tell you that extra precision in intermediate results is *EVIL* ;-)
Signature · 2 lines
Horst von Brand [email protected] Casilla 9G, Vin~a del Mar, Chile +56 32 672616