[2478] in SIPB_Linux_Development
Re: Kernel interface changes (was Re: cdrecord problems on
daemon@ATHENA.MIT.EDU (Kev)
Thu Feb 4 09:11:25 1999
To: yodaiken@chelm.cs.nmt.edu
Cc: efoo@MIT.EDU (Edwin Foo), alan@lxorguk.ukuu.org.uk, warlord@MIT.EDU,
xiphmont@MIT.EDU, linux-kernel@vger.rutgers.edu, linux-dev@MIT.EDU,
jered@MIT.EDU, nemo@MIT.EDU, linux-scsi@vger.rutgers.edu,
cox@idecnet.com
In-Reply-To: Your message of "Thu, 04 Feb 1999 09:07:27 MST."
<199902041607.JAA18863@chelm.cs.nmt.edu>
Date: Thu, 04 Feb 1999 09:11:04 EST
From: Kev <klmitch@MIT.EDU>
> > Unfortunately, I think it is a problem you have to take up and deal with.
> > Recompiling sources for entire server setups in a live production
>
> So you use the 2.0 version until a 2.2 version stabilizes. The problem
> really is that the Linux unreliable development kernel is so good that
> people actually want to run production systems on it, and then complain when
> it does not stay stable.
we're not talking about going from 2.0 to 2.2; we're talking about going
from 2.0.33 to 2.0.34. In the past, many changes have been made which
have broken binary compatibility without warning and without good reason.
*THIS MUST NOT CONTINUE HAPPENING* if Linux expects to get anywhere.
--
Kevin L. Mitchell <klmitch@mit.edu>
------------------------- -. .---- --.. ..- -..- --------------------------
http://web.mit.edu/klmitch/www/ (PGP keys availiable from here)
RSA AE87D37D/1024: DE EA 1E 99 3F 2B F9 23 A0 D8 05 E0 6F BA B9 D2
DSS ED0DB34E/1024: D9BF 0E74 FDCB 43F5 C597 878F 9455 EC24 ED0D B34E
DH 2A2C31D4/2048: 1A77 4BA5 9E32 14AE 87DA 9FEC 7106 FC62 2A2C 31D4
