Just a question about the local.start- file. Has anyone actually managed to start a script or a command at bootup by using the local.start?
This is my local.start:
# This is a good place to load any misc programs
# on startup ( use 1>&2 to hide output)
echo "16:35 14:25 12:18 10:12 8:6 6:2" > /sys/devices/system/cpu/cpu0/cpufreq/phc_controls
But, when removing the splash, it just returns the message: No such file or directory.
The developers says that the local.start is run way up in the bootup- process, maybe even before some potentially needed modules is executed.
But if that is the fact, more people than just me should have noticed this.
EDIT: It might have something to do with the privileges of the directories and files (i e ~/cpufreq/phc_controls and ~/init.d/lm_sensors) but shouldn't the local.start have the privileges to execute any command included in the file?
If that is the problem, how do I give the local.start the privileges?