RE: Driver Model 2 Proposal - Linux Kernel Performance v Usability

From: Chad Kitching (CKitching_at_powerlandcomputers.com)
Date: 09/05/03

  • Next message: Geert Uytterhoeven: "[PATCH] dmasound kill MOD_{IN,DE}C_USE_COUNT"
    Date:	Fri, 5 Sep 2003 15:53:27 -0500
    To: "Mike Fedyk" <mfedyk@matchmail.com>
    
    

    From: Mike Fedyk [mailto:mfedyk@matchmail.com]
    > Here is one thing we don't have standardized across the entire Linux
    > distribution landscape.
    >
    > What you need is a project that will take the top 10
    > distributions, and do
    > this however each distribution does their thing:
    >
    > o identify the current kernel running (you're going to use the kernel
    > you're running, right?)

    Not to mention on boot-up check to make sure the module still loads
    without warnings on the current kernel (or make sure the module exists
    in the current /lib/modules directory.
       
    > o download the kernel source for the running kernel

    Problem: Most distributors modify their kernel somewhat. Some enough
    to cause binary module incompatibility with the 'stock' kernel.
    Matching running kernel and source code kernel would be tricky, to
    say the least.
     
    > o install the source in some temporary location

    Why not just make the includes directory get installed somewhere.
    Somewhere like /lib/modules/`uname -r`/build/includes (especially since
    make install puts a symlink at /lib/modules/`uname -r`/build anyway)
    You also need to prep the extracted kernel with the proper .config, etc.
    which isn't always in the source package from some distributors.

    > o compile against the downloaded kernel source
    >
    > o install the module under /lib/modules
    >
    > o load the module (with the corect optional parameters)

    The biggest problem is people not having installed the C compiler, and
    related tools. Or having not installed the kernel headers matching
    their version of the kernel.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Geert Uytterhoeven: "[PATCH] dmasound kill MOD_{IN,DE}C_USE_COUNT"

    Relevant Pages

    • Re: [poll] Is the megafreeze development model broken?
      ... and for which it takes years to respond to bug reports in any case ... that problems with distribution packaged software should be reported ... Assuming your "stable base systems" contains the Linux kernel, ... Noone forces any users to install the software their distribution ...
      (Linux-Kernel)
    • 2.6.12-rc5-mm1: configuring vmware workstation modules
      ... problem occurs when I change kernel to linux-2.6.12-rc5-mm1 and try to ... In which directory do you want to install the application's icon? ... Trying to find a suitable vmmon module for your running kernel. ...
      (Linux-Kernel)
    • Re: ATI fglrx driver 3.7.6 on Suse 9.1
      ... I'm just happy to say that I did install the new fglrx ... Some pointers about the fglrx README (missing info...ish and really ... get this synchronized with the running kernel: ...
      (alt.os.linux.suse)
    • Re: thoughts on kernel security issues
      ... major security figure and/or haven't donated your life to security and ... the developer and more focus on the development. ... That's pretty complex in terms of kernel code, ... > most of the extra patches that distribution kernels apply are patches ...
      (Linux-Kernel)
    • Re: [poll] Is the megafreeze development model broken?
      ... that problems with distribution packaged software should be reported ... Assuming your "stable base systems" contains the Linux kernel, ... The Debian kernel packages ... Ion, they just go ahead and install it from the distro, because there's ...
      (Linux-Kernel)