On 9/21/2010 3:28 PM, Auke Kok wrote: > > 1) elimination of endless shell scripts: > > init calls /etc/rc.d/rc calls /bin/bash calls /lib/lsb/init-functions > calls /sbin/service calls /etc/init.d/$servicename calls > a-bunch-of-nonsense-checks calls way-too-much-bash-code calls... etc. > > All of these are a waste of time. ... > > 3) it scales. We're not talking about a server withy 60-70 services > running. It's a mobile device with very limited services (and we want > to keep it that way) This argument seems to negate your argument about too many shell scripts. If there are only a hand full of services then you only have a handful of scripts. With the scripts broken up you can manage them independently instead as a monolithic block that all services must coordinate. No these really aren't a waste of time. They are there so that the system can be brought up in different states. It sounds like your proposing that meego will run one way, and one way only across all variants of hardware and flavors of device. ...
> > Do you have a concrete issue where something "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." ? Yes. Plugins for things running in sysinit will have dependencies on 3rd party software that must start before stuff in sysinit. Specifically we have an ofono plugin that needs to talk to a communication link multiplexing daemon that is specific to a piece of 3rd party hardware. With ofono launching out of rc.sysinit there is nowhere to start the multiplexing daemon other than hacking on rc.sysinit. Regards, -p.j. > > Auke > >> >> regards, >> Anubhav > > (please don't top-post) (amen) -- P.J. Bostley [email protected] Qualcomm Innovation Center Inc. is a member of the Code Aurora Forum _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
