title: In what circumstances 'Openwrt ' is preferred over 'Buildroot' frame work?
body: <p>I'm confused between Buildroot and OpenWrt. I mean in which scenario one will choose OpenWrt over Buildroot.</p>
  
  <p>As per my understanding, there are only 2 differences between Buildroot and OpenWrt</p>
  
  <ol>
  <li><p>OpenWrt provides package manager(opkg) which is not available for buildroot.</p></li>
  <li><p>OpenWrt provides the good number of packages support for most networking related devices (routers, switches etc).</p></li>
  </ol>
  
  <p>If I don’t need any package manager for a project and yet I want network support then I can choose Build root over OpenWrt, right? Is it not possible to build networking related packages in Buildroot itself?</p>
  
  <p>I mean if package manager is not a concern we can go ahead with buildroot itself right? there is no need to opt OpenWrt?</p>
  
  <p>If I'm wrong can anyone address the scenarios where buildroot fails and Openwrt wins?</p>
  
  <p>I mean is it possible to achieve what OpenWrt is doing(Building Firmware images for networking related hardware) with Buildroot itself. I observed that the init process (early userspace) behaviour is different for Buildroot and OpenWrt.</p>
  
  <ul>
  <li>In Buildroot init script will be read <code>etc/inittab</code> and the scripts under <code>init.d</code> will be executed.</li>
  <li>In Openwrt <code>procd</code> is the init script (<code>rc.common</code>)and will run the scripts listed under init.d as well as scripts under <code>rc.d</code>.</li>
  </ul>
  
  <p>Will this affect any way if I try to use Buildroot to generate an Image for the firmware which is supported by OpenWrt?</p>