XPost: comp.os.linux.development.system   
   From: user@example.net   
      
   phil-news-nospam@ipal.net wrote:   
   > In comp.os.linux.development.system J.O. Aho  wrote:   
   >   
   > |> However, someone building the firmware image for a cable TV set top box,   
   may   
   > |> have reason to make a more solid kernel image.   
   > |   
   > | In those cases you know the hardware and it will not change, in these   
   > | embedded environments you can build a monolithic/static kernel, which I   
   > | have pointed out earlier.   
   >   
   > Right.  But an automated builder script, intended for a variety of these   
   > environments, still needs to make a determination of what configuration is   
   > needed.  The assumption that an environment will not change is not the same   
   > as the assumption that all environments are the same.   
      
   The embedded Linux builds I have seen (not that many) has always been   
   quite dedicated, most SoC don't have much you can expand with, so if you   
   do a distro for a SoC, then you more or less know everything it will   
   have and can build in most of the things in the kernel, but some modular   
   parts of course for such things like usb, it the SoC supports it.   
      
   > | Being more clear what you wanted to do in first place would have been   
   > | better IMHO, you would have got a different kind of replies than you have.   
   > I like to be concise with things.  Obviously that has its problems with   
   people.   
   > Do I also need to explain I want to do this as a web form/app?   
      
   Of course the more you tell what you do, the easier it is to answer,   
   think of a car repairer who gets a customer who say "my car don't start,   
   what is wrong?" without showing the car, you will need to make a lot of   
   assumptions.   
      
      
   --   
      
     //Aho   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)