Hi, I also had a similar question, with the following scenario in mind.
Starting a daemon from rc.sysinit also becomes a problem if there is a need to add new a daemon that has to be started *before* a daemon started by rc.sysinit. It will require developers to modify fastinit package and add a dependency to the fastinit package into their own. What is the reason that these daemons are started by rc.sysinit instead of individual init scripts ? This also is an interesting choice considering that rc.sysinit is not the traditional place to start system daemons. regards, Anubhav > Hi, > > I'm little bit confused regarding init scripts in Meego. What should be > the > preferred way of starting services/daemons in Meego? Should they be > started > from rc.sysinit (which many are in the current state) or should they be > started from init scripts? > > Will sysvinit be the official supported init or will it be superceded by > newer init-replacements such as upstart and systemd? > > Regards, > Mario > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
