[DEV] How Enabled Archos Gen9 To Run Scripts Into init.d

---

HI !

As you noticed , Archos didn't enabled run scripts into init.d directory !

Of course, there init.d directory into /system/etc/init.d with two scripts , but unfortunately never runs !

I found a way can be activated init.d directory allows scripts to automatically .

I know there are other ways for do this , but I really kept to run all script into init.d directory , and not elsewhere.

For this mechanism to work , device need to be rooted and busybox to be installed.

Now is very simple to add the following command :

> /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d , that will allow scripts to run in directory init.d !

This command must be placed in your system initialization file !

regard,
surdu_petru

Originally Posted by surdu_petru

Now is very simple to add the following command :

> /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d , that will allow scripts to run in directory init.d !

Better way would be to enable init.d in kernel- sources are available- but I don't know if init.d also needs in-system support (sorry, I don't have time to play with sources, even no time to fix modded Desire kernel).

Originally Posted by surdu_petru

This command must be placed in your system initialization file !

regard,
surdu_petru

In init.rc to be exact, putting it in initramfs won't do anything.

EDIT:
So only "standard" recovery and update.zip flashing is missing?

Originally Posted by gen_scheisskopf

Better way would be to enable init.d in kernel- sources are available- but I don't know if init.d also needs in-system support (sorry, I don't have time to play with sources, even no time to fix modded Desire kernel).


In init.rc to be exact, putting it in initramfs won't do anything.

EDIT:
So only "standard" recovery and update.zip flashing is missing?

Hi!

For edit kernel work is almost "crazy"....have to be calm and have more free time.....it is not so easy .. many errors can occur during the process
I tried some time ago....but device just boot with custom boot animation , but that and nothing more !!!
I'll try in the future but I expect kernel version 3.x.y.z ICS....

Them as well so you say....we need just standard CWM Recovery for our devices !

Otherwise it looks good and beautiful !

Good Luck !

Is it just a case of adding that line to the end of the Init.RC rile?

Originally Posted by theguy

Is it just a case of adding that line to the end of the Init.RC rile?

If you add this line as in init.rc, than the scripts in init.d will never run !!!

If you do not know how to use this command....then I think you don't need.....

Remember, this tutorial is the inscription [DEV] from developers !!!

Good luck !

Hi !

To help you, let me just say the next thing :

- putting this command in init.rc ( exec /system/bin/logrwapper /system/xbin/busybox run-parts /system/etc/init.d ) , normally expected to work ! , but unfortunately for me did not work. Well, now you must look for another initialization file system !!!

( Normally this command is part of a script recovery system and it was into

recovery.sh
.................................................. .................................................. ...........
#!/system/bin/sh
..........
..........
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
.........
.........
.................................................. .................................................. ...........
@theguy.... I think you're happy now ....

I've just took a closer look into ICS, it seems that init.d is enabled (take a look at /etc/init.d/rcS).
A little edit should enable all scripts to be used:

#!/bin/sh


# Start all init scripts in /etc/init.d
# executing them in numerical order.
#
for i in /etc/init.d/* ;do /* was:  /etc/init.d/S??* */

     # Ignore dangling symlinks (if any).
     [ ! -f "$i" ] && continue

     case "$i" in
	*.sh)
	    # Source shell script for speed.
	    (
		trap - INT QUIT TSTP
		set start
		. $i
	    )
	    ;;
	*)
	    # No sh extension, so fork subprocess.
	    $i start
	    ;;
    esac
done