On 1/13/2011 5:46 AM, Tapio Rantala wrote:
to, 2011-01-13 kello 21:25 +0800, ext Zhu, Peter J kirjoitti:
Why run both sysvinit and upstart in image ?
That is not possible, the thought was to leave a choice for the person
who creates the image, so that images could have been created with
sysvinit if upstart was not functioning for some reason.
That's my understanding as well.
Then what do you mean by " patch sysvinit and fastinit packages so that they require
upstart to function "?
Package sysvinit will not include actual sysvinit daemon anymore. Init
scripts within fastinit will no longer be functional with original
sysvinit as they are modified for upstart.
I don't like that at all...
why would upstart package just not provide a complete replacement??????
this upstart migration is starting to sound like a bigger and bigger
deal that is visible to applications etc...
... not a good idea since upstart is only for one release.
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
