Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
A (now) well know side effect of the USB automount stuff used on the DNS is the setting of access to wide open. This is not a good idea.
It can be circumvented by either modifying the offending code (usb_disk, in /usr/sbin, linked to /usr/local/modules/sbin/usb_disk), or putting a script round chmod to reject "chmod -R 777 /mnt/USB/HD_c".
In order to boot from USB, this needs to be done in the start up sequence, and rc.init.sh is the earliest possible location.
Following advice (KyleK et al) I changed chmod to be a link to /usr/local/config/chmod_fix.sh, which checks the parameters to see if it is the usb stick and do nothing, otherwise call busybox chmod (params). This is usually fine, except if a parameter (filename say) contains a space. The command line needs this bracketing, but the brackets are stripped by the shell, and presented to the command as separate params.
This resolves the boot up symptoms. However, to avoid the above side effect, I editted the usb_disk binary to call '#hmod -R 777 ....' ie do nothing.
This also works, but there is a chmod call made before the modified version of usb_disk is in place, even though the substitution is made at the same point as the swapping of chmod link.
I know this is a bit rambly, but can anyone comment of the fine details of linux operation during processing rc.init.sh?
The only other course would be to edit the usb_disk in /usr/local/modules/sbin, but that is a read only partition, and I am not clear (yet) how to make it writable, so save the modified binary.
So any thoughts or other help please?
Offline