Run automaticaly a script just after plugin installation

[Mingyar]

Hi all,

I have a question I asked on another thread, but the object is on a different subject.
So, I try to have an answer with a new thread.

I make a plugin for wich the only thing I want is to run a script shell just after the installation.
This script self-destroy at the last instruction.

I looked at the nightmode plugin.
I see a file /root/autorun.sh
I made one for my plugin :
If my script is /mnt/onboard/.kobo/MyShell.sh,
/root/autorun.sh is :

/mnt/onboard/.kobo/MyShell.sh
rm /root/autorun.sh
sync
reboot

But, my script don't run after plugin installation.

Someone is able to help me please ?
Thanks.

EDIT : After a test with trace I can say that's /root/autorun.sh is not running after the plugin installation.

[Lucas Malor]

Have you edited and added also /etc/udev/rules.d/98-autorunHook.rules ?

Your autorun script have also to remove that file.

[Mingyar]

I forgot this.
I just made a test with, but nothing better.
I will work on this when at home.
Thanks.

[Mingyar]

So, I made new investigations :
the autorun.sh :

#!/bin/sh

echo "autorun" >/mnt/onboard/.kobo/autorun.log

echo "autorun" >/root/autorun.log

/mnt/onboard/.kobo/MyScript.sh

rm /etc/udev/rules.d/98-autorunHook.rules
rm /root/autorun.sh

sync
reboot

in MyScript.sh :

#!/bin/sh

...

cp /root/autorun.log /mnt/onboard/.kobo/autorun_from_root.log 1>/mnt/onboard/.kobo/a.log 2>&1

After copy of the KoboRoot.tgz in .kobo folder and unplug the Kobo, update phase is succedded by restart.

I plug the Kobo to the PC, the autorun.log doesn't exist in the .kobo folder.
I unplug then run MyScript.sh (user command in KoboTweaks plugin).
I plug again the Kobo.
I find the autorun_from_root.log in .kobo folder.

So, it seems that autorun.sh has been executed but was not able to access /mnt/onboard/.kobo folder.

Someone can confirm that ?
If I'm right, is there a way to execute automatically a script in /mnt/onboard/.kobo just after a plugin is installed ?
If not, I can put that script in the /root folder, but, this script has to work in the /mnt/onboard/.kobo/images ...

I hope my English is enough good to be explain my problem.

[xor_]

You could try to add a "sleep 60" (or so) line to your autorun script to wait until the sdcard stuff has been initialized.

Or you could add the invocation of your script to /etc/init.d/rcS, and then in the last line of your script restore the original /etc/init.d/rcS.

(The latter is problematic, though, in case the user has modified his rcS.)

[tshering]

Mingyar,

I am not sure whether I understand everything you are saying, and I am not a linux user. So chances are that I misunderstand the situation.
autorun.sh is run before rcS, right? At the point, when you call

echo "autorun" >/mnt/onboard/.kobo/autorun.log"

mnt/onboard is not yet mounted, therefore you cannot write to /mnt/onboard/.kobo/autorun.log.

[Mingyar]

Thanks for your answers

@tshering, you're probably right, it's my deduction too, by the events, not a certitude.
@xor_, good idea, I try this and reply here.

Thanks again.

[tshering]

Originally Posted by xor_

Or you could add the invocation of your script to /etc/init.d/rcS, and then in the last line of your script restore the original /etc/init.d/rcS.

(The latter is problematic, though, in case the user has modified his rcS.)

That is why Mingyar takes the nightmode hack as model. It should go somehow like this:
1) let 98-autorunHook.rules start autorun.sh
2) autorun.sh inserts into rcS at some point, after the line that mounts mnt/onboard a line that starts runonlyonce.sh. Then it deletes 98-autorunHook.rules and itself.
3) When rcS is run, runonlyonce.sh does whatever it should do and then deletes itself. Optionally it could in addition also remove the line that was added to rcS which invokes runonlyonce.sh.

[Mingyar]

That's right tshering.
After a first test with the delay, it doesn't work.
A second test, modifying /etc/init.d/rcS worked one time. My script in the .kobo directory has been launched.
But I did a mistake somewere, at the next test I bricked my Kobo
I'm restauring the SD before making other tests.

Just a question to be sure.
The call of my script in rcS should be in background (& at the end of the line, maybe nohup at the begin of line) ?
I suppose yes, because if I want to clean rcS in my script (called by rcS), it should be impossible if it's running ...

[Lucas Malor]

You can check if the device is mounted using:

mount | grep "/mnt/onboard"

inside a while loop with a sleep 1.

Source: http://usalug.com/phpBB3/viewtopic.php?p=110052#p110052

[Lucas Malor]

If I remember well, /etc/udev/rules.d scripts are launched at boot. You need to reboot the kobo to make it running. IMHO it's more simple to create a SSH connection.

[tshering]

@Lucas Malor

I thought Mingyar tries to make an install mechanism with KoboRoot.tgz. In this case the device will be rebooted after running the "if [ -e /mnt/onboard/.kobo/KoboRoot.tgz ]; then ..." part, and during the reboot the modified rcS will be run. If the call to runonlyonce.sh is inserted at the proper place, there should not be a doubt that mnt/onboard is already mounted.

@Mingyar
I don't think there is a problem modifying the file of the calling script, this doesn't influence the process. So nohub might not be necessary. However, I repeat that I have almost no knowledge about linux. So be warned.

[Mingyar]

Thanks all !

It works well now
My way to make it work is not perfect maybe, but it works.

autorun.sh :

#!/bin/sh

if [ `grep -c "MyScript" /etc/init.d/rcS` -eq 0 ]
then
   cp /etc/init.d/rcS /root/rcS
   chmod a+x /root/rcS
   echo "" >>/etc/init.d/rcS
   echo "nohup /mnt/onboard/.kobo/MyScript.sh &" >>/etc/init.d/rcS
   echo "sleep 5" >>/etc/init.d/rcS
   echo "if [ -s /root/rcS ]" >>/etc/init.d/rcS
   echo "then" >>/etc/init.d/rcS
   echo "   rm -rf /etc/init.d/rcS" >>/etc/init.d/rcS
   echo "   mv -f /root/rcS /etc/init.d/rcS" >>/etc/init.d/rcS
# for debug begin
   echo "else echo 'no /root/rcS' >/mnt/onboard/.kobo/NorcS.log 2>&1" >>/etc/init.d/rcS
# for debug end
   echo "fi" >>/etc/init.d/rcS
   echo "" >>/etc/init.d/rcS
fi

rm /etc/udev/rules.d/98-autorunHook.rules
rm /root/autorun.sh

sync
reboot

With your help, I progress

[Mingyar]

I don't want to open a new thread for my little question.

Is it possible in script shell to know the kobo model (Mini, Touch, Glo or Aura) ?

[KevinShort]

Originally Posted by Mingyar

I don't want to open a new thread for my little question.

Is it possible in script shell to know the kobo model (Mini, Touch, Glo or Aura) ?

You can use /bin/kobo_config.sh. It returns the codename of the device. Trilogy is Touch, kraken is Glo, pixie is Mini, and dragon is Aura.