Upstart on an embedded target
Scott James Remnant
scott at netsplit.com
Mon Feb 5 16:23:37 GMT 2007
On Mon, 2007-02-05 at 09:58 -0600, Chemparathy, Cyril wrote:
> > It all depends on the level of embeddedness, and
> > customisability you intend to have. If the set of tasks and
> > services can be changed, and varies depending on
> > configuration (e.g. OpenWRT) I'd recommend upstart.
> > If the services and tasks are fixed in stone, and resources
> > are a priority, eINIT may be better for you.
> The system in question is quite similar to WRT, with a great
> degree of configurable flexibility.
> Another question I have relates to the presence of __thread
> in libnih. The cross toolchain that we have unfortunately
> croaks when it encounters this. What are your thoughts on the
> right way to fix this?
You should be able to define that out -- just set the cache value
nih_cv_c_thread to "no" and it'll be expanded to nothing.
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20070205/5e1f215e/attachment.pgp
More information about the upstart-devel