[lkml]   [2005]   [Nov]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: New Linux Development Model
    On Saturday 05 November 2005 13:19, Edgar Hucek wrote:
    > Hi.
    > Sorry for not posting my Name.
    > Maybe you don't understand what i wanted to say or it's my bad english.
    > The ipw2200 driver was only an example. I had also problems with, vmware,
    > unionfs...

    Read the document linked to by Jean. It explains why a volatile API is
    ultimately beneficial to the Linux development process.

    It's frustrating for vendors and maintainers to keep their code up to date
    with the latest kernel, but if it's done incrementally after Linus releases
    (or during the very lengthy RC process), it's usually very easy.

    Also, you're gelling together many projects which have completely different
    reasons for breaking across kernel revisions.

    ipw2200 "works" in 2.6.14, it's just the maintainer has opted to use a "stable
    version" which lacks experimental features while ieee80211 gets up to

    OTOH, unionfs is poorly maintained and is a particularly sore example of how
    the linux development model is detrimental to external module development.

    There are people constantly working to make binary modules like VMWare, NVIDIA
    and ATI work under the newest kernels. Just google it. Ultimately we can't
    allow ourselves to be held down by slow-moving binary vendors. It's too
    inefficient (not to mention of questionable ethics).


    'No sense being pessimistic, it probably wouldn't work anyway.'
    Third year Computer Science undergraduate.
    1F2 55 South Clerk Street, Edinburgh, UK.
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-11-05 14:50    [W:0.020 / U:53.612 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site