Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I'm trying to use fonz' dns323/fsck/ with 0.7 but it keeps giving me this error when I run debug-reboot.sh or no-bash-reboot.sh:
insmod: error inserting '/mnt/HD_a2/ffp/fsck/reloaded-126.96.36.199-arm1.ko': -1 Unknown symbol in module
(if I try to run .reboot.sh it shuts down all my ssh and telnet but doesn't boot the alt kernel)
I've used this fsck method numerous times before and it has been fine. I am concerned I missed a step in the 0.7 install or something, or I have not linked (or unlinked) to/from busybox.
Is v frustrating.
I can also see:
reloaded: Unknown parameter `ip'
In dmesg. Dunno if it is related?
I usually run optware without ffp, but I needed to run fsck one day. I had left my ffp 0.5 install in /mnt/HD_a2/ffp and had saved a fun_plug script that would start ffp 0.5. So, all I had to do was rename my optware fun_plug to get it out of the way and put back the fun_plug that starts ffp 0.5. After rebooting into ffp, I could then do the normal restart to get the OS running without mounting the drives and then run fsck. When finished, I just put back my optware fun_plug and all was well.
You could do the same sort of thing, if you are sure of what you are doing and are careful. I'd probably rename fun_plug to fun_plug_0_7. Reboot to stop running ffp and access the drive from a network. Rename the ffp folder to ffp_0_7. Then install ffp 0.5 in the usual manner. You should then be able to boot to ffp 0.5. You may have to reinstall the fsck package to 0.5 at this point. Then do the usual restart to run fsck. When done with fsck, reboot into ffp 0.5, rename fun_plug to fun_plug_0_5. Reboot to stop running ffp, and access the drive from a network. Rename the ffp folder to ffp_0_5. Rename the ffp_0_7 folder to ffp. And rename the fun_plug_0_7 file to fun_plug. Reboot should bring ffp 0.7 back up.
This is a lot of steps and involves (re)installing ffp 0.5, which is a drag since you are on 0.7. But it is very likely to work.
The alternative is to figure out what it would take to fix the fsck package to work with 0.7. The fix may be very simple, or not.