Yesterday I tried to update busybox. However the result is quite negative.
The original busybox v1.1.1 (2009.09.11-06:18+0000) executable is located in /bin. Using ipkg (Optware) I downloaded and installed the latest available busybox package v1.10.3 (2010-05-17 05:57:25 UTC) which consists of two packages: busybox-base (executable itself) and busybox-links (for each command) to /opt/bin.
Then I replaced /bin/busybox with /opt/bin/busybox and immediately the ShareSpace began to show odd behaviour. Busybox version has changed to v1.10.3 as expected, but I couldn’t even reboot or shutdown either through power button or web interface. After I disconnected the unit from mains the ShareSpace turned into the bricked state. Fortunately I’d backed up my /dev/md0 before experimenting.
For me it seems that the original busybox v1.1.1 (2009.09.11-06:18+0000) executable contains something (instructions) specific for ShareSpace hardware. So it acts like a part of the internal Linux OS. If one replaces it with different version, the device cannot even be rebooted and shut down.
Now I’m thinking of a way of using both versions: the original busybox v1.1.1 (2009.09.11-06:18+0000) for systems to operate correctly and busybox v1.10.3 (2010-05-17 05:57:25 UTC) for all or most of commands. Any ideas or input would be very much appreciated.