On Sat, Sep 18, 2010 at 5:53 PM, Arjan van de Ven <[email protected]> wrote: > On 9/18/2010 7:23 AM, Felipe Contreras wrote: >> 2010/9/17 Greg KH<[email protected]>: >>> On Fri, Sep 17, 2010 at 03:19:05PM +0300, Pertti Kellomäki wrote: >>>> Are there any plans re upstart in MeeGo? I'm asking because we have >>>> test scripts that use initctl to control daemons, so the scripts >>>> need to be modified if there is no upstart. >>> >>> I would hope it would be on the roadmap for future releases. >> >> Huh? I think nowadays upstart can be considered deprecated: >> http://0pointer.de/blog/projects/systemd.html > > just because someone is doing an experiment doesn't mean other things are > deprecated....
Ok, I thought that was obvious, but I guess time will tell. > systemd has design issues which have to be hashed out obviously (Fedora is > punting on it for F14 for a reason) > upstart has license/contribution issues which are not pretty Fedora is putting it on F14 because F13 was practically out when systemd was announced. > MeeGo currently has a highly customized boot process, optimized for speed. > At this point, if we were to switch, > upstart matches that closer than systemd does.... so upstart would be a more > logical change if we were to change. If you want speed, you need a customized boot process in traditional init systems (sysvinit, upstart), because everything gets started, so then you need to pick and choose what really gets started, and when. But systemd turns the problem around; nothing gets started, unless it's really used, so there's less need to customize (if any). > It's ok to have multiple competing technologies; that's one of the ways > innovation happens in open source.. competition. Sure, but we are not using any, so I don't see why we should assume that upstart will be used. I think both approaches need to be carefully and equally considered. -- Felipe Contreras _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
