Re: A Framework to automatically configure a Kernel

From: Ahmad Reza Cheraghi (a_r_cheraghi_at_yahoo.com)
Date: 09/05/05

  • Next message: Catalin Toda: "promisc mode question"
    Date:	Mon, 5 Sep 2005 07:50:30 -0700 (PDT)
    To: linux-kernel@vger.kernel.org
    
    

    --- Emmanuel Fleury <fleury@cs.aau.dk> wrote:

    > Hi,
    >
    > Ahmad Reza Cheraghi wrote:
    > >
    > > I install right now a gcc 4.0 debian-packege on my
    > > system and it still works. But I attached another
    > > patch(I thik I did a mistake in the patch;-)).
    >
    > Might be as well ! :)
    >
    > But, I'll give it a try when you'll get this fixed !
    >
    > >>2) Why is the target called "auconfig" and not
    > >>"autoconfig" (just like
    > >>we have a "menuconfig") ?
    > >
    > > I thought that autoconfig will be to large for
    > that
    > > reaseon i called it auconfig.
    >
    > Well, "menuconfig" is not that small either ! :)
    > More explicit you are, better it is (within some
    > reasonable limit).
    >
    > > If you mean with your question that, why there are
    > > less rules and why they don't get its information
    > from
    > > /sys or /proc etc. The answer will be:
    > >
    > > Not that much. Most of the information will be
    > > obtained from lspci and dmesg. The only one that
    > gets
    > > its inforamation directly from the I/O of the
    > Hardware
    > > is lspci. The other one like dmesg, /proc... anre
    > > based on the Kernel installation and on drivers
    > > installation. And it might happened that you won't
    > > find Hardware that are on your system but aren't
    > > installed from your Kernel.
    >
    > It was what I meant (sorry to have been unclear).
    >
    > > But if you mean with your question, that why it
    > dosn't
    > > first of all create list of all of the information
    > > given from /proc, ...? The answer is:
    > >
    > > That the basic Idea of the framework is to extend
    > it
    > > easily. And the rules can be changed they way
    > someody
    > > knew its right and ok.
    >
    > Ok.
    >
    > Regards
    > --
    > Emmanuel Fleury
    >
    > Assistant Professor | Office: B1-201
    > Computer Science Department, | Phone: +45 96 35 72
    > 23
    > Aalborg University, | Mobile: +45 26 22 98
    > 03
    > Fredriks Bajersvej 7E, | E-mail:
    > fleury@cs.aau.dk
    > 9220 Aalborg East, Denmark | URL:
    > www.cs.aau.dk/~fleury
    >

    __________________________________________________
    Do You Yahoo!?
    Tired of spam? Yahoo! Mail has the best spam protection around
    http://mail.yahoo.com
    -
    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: Catalin Toda: "promisc mode question"

    Relevant Pages

    • Re: Why most run Microsoft, not RedHat
      ... When it crashes, you insert the software CD, and ... I suggest that the installation WILL have an OPTION ... Do You Yahoo!? ... Mail has the best spam protection around ...
      (Fedora)
    • Re: 2.6.12 Performance problems
      ... to tell me what was wrong with my setup, ... Do You Yahoo!? ... Mail has the best spam protection around ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Why most run Microsoft, not RedHat
      ... When it crashes, you insert the software CD, and ... I suggest that the installation WILL have an OPTION ... Do You Yahoo!? ... Mail has the best spam protection around ...
      (Fedora)
    • Re: Help by KConfig expansion
      ... zconf.tab.c_shipped as well but it still dont work. ... Do You Yahoo!? ... Mail has the best spam protection around ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: ext3 journal commit performance
      ... _together_ after issuing both of them to disk, ... Do You Yahoo!? ... Mail has the best spam protection around ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)