On 9/29/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > On Fri, 29 Sep 2006 23:49:28 +0200, Carlo Calica <[EMAIL PROTECTED]> wrote: > > > > Big issue with bootstrap (of init process, not the kernel) is the > > entire base should use the new system. This way all the events are > > properly triggered. For instance, if the network is started with the > > old scripts upstart will never use the "network up" event trigger. > > Same with mounting partitions, starting syslog, etc. > > > I don't really follow you, but I'm guessing that you mean that if we stick > with our scripts the events wont be used/work. If we want to use upstart > I'm guessing we have to live with that during the transition. > If it gets as popular as Scott says it will be this is good news to me as > startup is one of the things that are most distro specific. >
Don't feel bad, I explained it backwards. The events need to be triggered from upstart tasks. Standard init tasks can't trigger events. For instance the "network up" event is triggered by the network task completeing. If the network task is old style it can't trigger the event. It wouldn't take much to decide on a few events and implement the tasks to complete them. I'm still hoping the library of tasks will grow so we don't have to write them. If we start too early our events might (will) differ. Having someone coordinate with the ubuntu folks would be a good idea if we decide to use it. -- Carlo J. Calica _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
