XPost: comp.os.linux.development.system   
      
   In comp.os.linux.development.system Mark Hobley  wrote:   
   | phil-news-nospam@ipal.net wrote:   
   |> Does it do all the configuration for you (aside from giving you the option   
   |> to do it your own way), such that the monolithic kernel would be the same   
   |> as you'd get running a modular kernel on that machine, in terms of what   
   |> drivers and other options are in effect?   
   |   
   | You build your own kernel from the command line as part of the   
   | installation process.   
      
   Build.  OK.  But what about configure.  Does it figure all that out for you   
   AND do it as correctly as it would load modules on a module based kernel?   
      
      
   |> I was hoping for a distribution that focus on this so that I can see how   
   they   
   |> address issues like how to configure the monolithic kernel correctly.   
   |   
   | There is a bug in the way that it builds, in that it currently does not   
   | let you use your own kernel-headers. This probably will not affect you   
   | because Gentoo installs a set of up to date headers anyway, and these   
   | are supposedly backwards compatible with all previos versions of the   
   | same 2.6 series kernel.   
   |   
   | However if you are maintaining a locally modified kernel fork, this can be a   
   | bit of a problem, if you want the headers from your local kernel to be   
   | used. I have been working around this for about three days solid now.   
   | I surrendered this afternoon, and this is now a bug.   
   |   
   | What you can do if you need your own kernel headers, is build with the   
   | Gentoo provided kernel headers, then mask out the kernel package and   
   | kernel headers from the package manager, then install your own, kernel and   
   | headers and rebuild the toolchain and glibc. However, I don't know how   
   | to do this yet, but I am working on it, and I am developing up to date   
   | documentation. There are some notes in the handbook.   
      
   I don't have any need to build with any headers other than what comes with   
   the kernel source code itself ... the same as the one being compiled (e.g.   
   2.6.28.2 headers used with a 2.6.28.2 kernel).   
      
   What I am looking for is how distributions go about presenting configuration   
   issues to the human doing the install.  The ideal distribution would be one   
   that BY DEFAULT builds a monolithic (no modules) kernel without any user   
   interaction needed at all (besides maybe an option screen to choose between   
   monolithic and modular).  One that requires the human to make all the same   
   configuration choices as they would have to do if independently building a   
   kernel from source is of no interest at all (because it adds nothing to the   
   kernel building process).   
      
   --   
   |WARNING: Due to extreme spam, googlegroups.com is blocked.  Due to ignorance |   
   |         by the abuse department, bellsouth.net is blocked.  If you post to  |   
   |         Usenet from these places, find another Usenet provider ASAP.        |   
   | Phil Howard KA9WGN (email for humans: first name in lower case at ipal.net) |   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)