KM Shortcut on boot

[aditya3098]

I know this might be on like a gazillion different places, but can anyone point out how I can run the shortcut.sh script from kindlemenu (and a few others) on boot? I tried /etc/upstart/pillow.conf, hooking it on to NiLuJe's SS hack, etc.

[NiLuJe]

Doesn't dos1 event thingy have a hook on framework start?

[aditya3098]

Originally Posted by NiLuJe

Doesn't dos1 event thingy have a hook on framework start?

Ill look. But I need pillow load, not framework start. Are they the same?

[eureka]

Originally Posted by eureka

[...] However, it should possible to add new Upstart job definition (into /etc/init) for running that shell script right after (re)starting pillow. Something like /etc/init/pillow_local_mod.conf (not tested at all!!): [...]

[aditya3098]

I managed to get it to hook on to the screensaver stuff. Turns out I put my code after the return 0.

[brianinmaine]

Curious - what do you have to run at screensaver? an Xscreensaver module?

[aditya3098]

Originally Posted by brianinmaine

Curious - what do you have to run at screensaver? an Xscreensaver module?

The kindlemenu stuff, and some other pillow hacks. By ss, I mean the screensaver hack.

[Aeris]

Aditya: unless you check manually software updates codes every time, I don't recommend you to add an upstart job... if any script loaded from it got seriously bugged, maybe you could risk to brick your device. Moreover, when the framework restarts you will lose again some mods, so this wouldn't solve all the problems in any case. In my opinion, the best thing is to create a comprehensive, simple bash script to launch from kual when needed, that initializes all the stuff you need

[aditya3098]

Originally Posted by Aeris

Aditya: unless you check manually software updates codes every time, I don't recommend you to add an upstart job... if any script loaded from it got seriously bugged, maybe you could risk to brick your device. Moreover, when the framework restarts you will lose again some mods, so this wouldn't solve all the problems in any case. In my opinion, the best thing is to create a comprehensive, simple bash script to launch from kual when needed, that initializes all the stuff you need

I didnt add an upstart job. And yes, I mannually check EVERY update. Since 5.1.0. That was the first blast of DESTRUCTIVE.

[eureka]

Originally Posted by Aeris

Aditya: unless you check manually software updates codes every time, I don't recommend you to add an upstart job... if any script loaded from it got seriously bugged, maybe you could risk to brick your device.

Note, however, that aditya3098 has KT, so he's possibly know about Kubrick.

[aditya3098]

Originally Posted by eureka

Note, however, that aditya3098 has KT, so he's possibly know about Kubrick.

Kubrick? What's that? I just have a shell script that automatically blasts the storage, and then installs a recent backup, and restores all my kual stuff, books (they are these thing that have text in them, kind of like documentation), and other misc stuff.

[twobob]

I used kubrick just yesterday, Utterly frozen device. Fix in 5 or 6 mins.
rmmod -f fundamental modules and switching in the wrong one. Bad idea. :P

[Aeris]

Originally Posted by eureka

Note, however, that aditya3098 has KT, so he's possibly know about Kubrick.

Ah yes you are right

Kubrick? What's that? I just have a shell script that automatically blasts the storage, and then installs a recent backup, and restores all my kual stuff, books (they are these thing that have text in them, kind of like documentation), and other misc stuff.

You could safely try with Eureka method then!