On Wed, Jun 11, 2008 at 4:31 PM, Michael Biebl [EMAIL PROTECTED] wrote:
2008/6/12 Saravanan Shanmugham (sarvi) [EMAIL PROTECTED]:
Hi,
As Garret Cooper mentioned earlier, my team at Cisco is thinking of
working with Upstart as a process manager.
One of the questions that have come up
This sounds like Upstart is proposing a hard dependendency on D-Bus. Is
this really necessary. Has the impact on small/embedded platforms been
considered.
Communication infrastructure is a key design choice for any embedded
platform, hence it is important that a platform developer have the
Hi Sarvi,
This sounds like Upstart is proposing a hard dependendency on D-Bus. Is
this really necessary. Has the impact on small/embedded platforms been
considered.
please lets not have this discussion again. D-Bus is perfectly fine for
embedded systems. Actually having more than one IPC is
Matthias Urlichs wrote:
Hi,
Saravanan Shanmugham (sarvi):
This sounds like Upstart is proposing a hard dependendency on D-Bus.
It proposes a hard dependency on the d-bus library and protocol.
(There needs to be *some* way of talking to init ... and the d-bus
protocol seems to be reasonably
Hi Matthias,
This sounds like Upstart is proposing a hard dependendency on D-Bus.
It proposes a hard dependency on the d-bus library and protocol.
(There needs to be *some* way of talking to init ... and the d-bus
protocol seems to be reasonably sane for doing this kind of thing)
this
