Startup script execution order?

[bmarkus]

What is the actual startup script execution order? Are these executed in alphabetic order one by one when all extensions loaded or parallel? Is there a difference in 2.5 and 2.6?

[^thehatsrule^]

iirc, they are in alphabetical order, and are executed one-by-one as part of each extension's loading

[bmarkus]

iirc, they are in alphabetical order, and are executed one-by-one as part of each extension's loading

Are you saying script is executed immediately after the extension is loaded and not after all extensions loaded?

[^thehatsrule^]

Yes

[Jason W]

Actually, it has been recently changed to where during boot if an extension has a startup script, that startup script name is echoed to a file and the order of extensions is loaded alphabetically, but with dependencies loaded first if a dep file exists for the extension.  At the end of boot, the name of the startup scripts exist in the file in the order that the extensions were loaded.  Then at the end of boot after depmod and ldconfig are run, the startup scripts are executed from that list.

In other words, if dbus has expat listed as a dependency, then expat gets loaded and it's startup script is run before dbus's both during boot as well as with appbrowser use.

[bmarkus]

Jason, thanks for the explanation, it is clear. Only one question. In which version is it introduced? Is 2.5 and 2.6x behaves on the same way or is it new in 2.6?

[Jason W]

Introduced in 2.5, but functionally it has the same effect on extensions as the previous manner of running the scripts upon each extension load during boot, deps first.