I agree that each product might have different connectivity and different
configuration needs on the rootfs.
However current thoughts are based on
1) Some of the common configurations of YP are currently at build time in yocto
project, but appying them doesnot require a rebuild. Such
Ramana,
Maybe I do not understand what exactly you are looking for. Maybe you have
some concrete examples.
Anything that somehow changes the configuration of the target has to go
into the root file system one way or the other. You can easily include
packages into the root file system by adding
On Thu, Apr 4, 2013 at 6:42 PM, Sean Liming sean.lim...@annabooks.com wrote:
Why post-build instead of pre-build?
The idea is that you have one build, and you are manufacturing 5000 devices.
So you take this one build and load it on each of your identical
devices which you then sell to your
-Original Message-
From: Trevor Woerner [mailto:twoer...@gmail.com]
Sent: Monday, April 08, 2013 1:28 PM
To: Sean Liming
Cc: Venkata ramana gollamudi; yocto@yoctoproject.org; Sanil kumar
Subject: Re: [yocto] RFC: Post build configuration
On Thu, Apr 4, 2013 at 6:42 PM, Sean Liming
On Mon, Apr 8, 2013 at 5:49 PM, Sean Liming sean.lim...@annabooks.com wrote:
Is this post-build utility an active
project for the Yocto Project or is it just getting started?
It's only in the discussion phase right now, hence the RFC in the
subject line.
The process that you are describing is commonly called device
provisioning. I have experienced this process from different angles:
working for a company making functional test equipment for electronics
production lines and working for a company providing software for set-top
boxes.
From this
This is in reference to my previous post regarding post build configuration,
with few points re-iterating to set the ground.
https://lists.yoctoproject.org/pipermail/yocto/2012-November/012867.html
Post build configuration and need for configuration platform/model:
There have been
