sysvinit backward compatibility in upstart .5

[Saravanan Shanmugham (sarvi)]

Is it possible to implement SysV compatibility without using D-Bus
messaging? 
Meaning basically using the starting/started/stopping/stopped events of
a set of SysV compatibility jobs themselves.

Does it really require events to come from outside the Upstart Init
process.

Sarvi

>-----Original Message-----
>From: upstart-devel-bounces at lists.ubuntu.com 
>[mailto:upstart-devel-bounces at lists.ubuntu.com] On Behalf Of 
>Casey Dahlin
>Sent: Thursday, July 24, 2008 11:13 AM
>To: Sandeep Puddupakkam (spuddupa)
>Cc: upstart-devel at lists.ubuntu.com
>Subject: Re: sysvinit backward compatibility in upstart .5
>
>Sandeep Puddupakkam (spuddupa) wrote:
>>
>> Hi,
>>
>> I downloaded the upstart (.5) code from trunk. I was able to get the 
>> sysvinit backward compatibility going with upstart (.3.9). I 
>am trying 
>> to do the same with the code in trunk.
>>
>> I notice that runlevel, telinit etc are not yet implemented. 
>Are there 
>> plans of implementing them? If they will be implemented, is the plan 
>> to use the existing socket interface for telinit to talk to 
>upstart or 
>> will that be replaced by dbus. In which case, dbus should be started 
>> pretty early in the startup sequence.
>>
>> In the mean time, what are the alternatives I have to achieve the 
>> backward compatibility with sysvint?
>>
>>  
>>
>> Any suggestions are welcome.
>>
>>  
>>
>> Thanks and Regards,
>>
>>  
>>
>> Sandeep
>>
>They will be implemented, and in fact are. They currently 
>reside in the "dbus-userspace" branch on launchpad, but 
>merging is imminent. There should be a release soon with all 
>of this in place.
>
>--CJD
>
>--
>upstart-devel mailing list
>upstart-devel at lists.ubuntu.com
>Modify settings or unsubscribe at: 
>https://lists.ubuntu.com/mailman/listinfo/upstart-devel
>