lkml.org 
[lkml]   [1999]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: Kernel interface changes (was Re: cdrecord problems on
    Date
    From

    > > 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


    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:50    [W:0.019 / U:2.416 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site