Can someone help aficionado with making sure he has the right kernel installed that has the kernel panic fix in it? Once he does that, all this command line stuff will still be interesting but not essential.
aficionado, yes, I can think of a number of ways to try to make the loop work, but you might want to test them with a simple echo outside of the loop first. Until the "echo 3 > /proc/sys/vm/drop_caches" works without an error, no need to put it into a loop.
I cannot test this stuff without a Pi, but possible solutions without the new kernel would be to give yourself write permission to the drop_caches file with:
sudo chmod +w /proc/sys/vm/drop_caches
ls -l /proc/sys/vm/drop_caches
You would want the output of the ls -l to start with -rw-rw-rw-
If you change the permissions that way, the echo ought to work, but might not because you still would not have write permission to the /proc/sys/vm directories and I am not sure it would be possible or wise to make those writable by all.
The other theoretical way would be to use the sudo command. Again, I do not have a Pi so cannot test this now. Trying on my PDA does not work as I have not been able to get a drop_caches file onto it. Anyhow, to test permissions, just try
sudo echo 3 > /proc/sys/vm/drop_caches
If you do not get an error, then try the loop:
while true ; do sudo echo 3 > /proc/sys/vm/drop_caches ; sleep 1 ; done &
sudo while true ; do echo 3 > /proc/sys/vm/drop_caches ; sleep 1 ; done &
And post your results if it still is not working so forum members can help.
But if there is a kernel fix, getting that revised kernel working seems like a better way to go.
Lars, has ssh been disabled on all distributions or just Debian? That is not going to be fun for those of us needing ssh.
FORUM TIP: To view someone's posting history, sign in, click on their user name, then on "Search User's Posts." || Running ArchLinuxArm on Model 2B and 512MB Model B