<br><div><span class="gmail_quote">On 9/18/06, <b class="gmail_sendername">Kalle Vahlman</b> <<a href="mailto:kalle.vahlman@gmail.com">kalle.vahlman@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2006/9/18, <a href="mailto:tomas@oranginalab.com">tomas@oranginalab.com</a> <<a href="mailto:tomas@oranginalab.com">tomas@oranginalab.com</a>>:<br>> We are developing a Flash application to run on Nokia 770 devices and we
<br>> would like this application to be launched automatically when the device is<br>> switched on. How can we launch opera browser (in fullscreen mode) at<br>> startup? We've tried editing .profile and .ashrc but it does not work. Any
<br>> help would be appreciate. Thank you in advance. Tomà s<br><br>The usual (linux/debian) way of startup scripts are in /etc/init.d and<br>then a link to /etc/rc2.d (with name like "S99xx").</blockquote><div>
<br>Actually, that would be the place to put system-wide daemon/services startup scripts that have no UI. There should be a script in there that runs the desktop manager and within the desktop manager there should be mechanisms in place to start things up in a particular users session so that all the proper environment variables and user contexts are set. The rc startup scripts are a very wrong place to put a command to start up the browsers in a user's desktop.
<br><br>.ashrc is also not entirely proper either as that is the script that is fired when an ash shell is started up to get a virtual terminal, AFAIK. Not something that happens automatically at Maemo desktop startup.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">As you'll want it to run as "user" not root, you might want to add it<br>
to /etc/osso-af-init/ and edit real-af-base-apps to run the script so<br>you'll get the environment setup for free. You can look at the other<br>scripts there for examples.</blockquote><div><br>That seems to be the place but that script system sure is package manager unfriendly.
<br>Other distros typically have a script that will call any script placed in an /etc/something.d/ directory. That way a .deb (or rpm or whatever) can add or remove their hooks into the main startup sequence without having to parse (and possibly corrupt) the main start script.
<br><br>Are there other mechanisms around like this or maybe some gconf-2 variables that can be poked that act on the session level rather than system level?<br><br>/Mike<br></div><br></div>