This forum is no longer active. Please post your questions to our new community site
Can't install on x86 Synology NAS
|
|
I selected all the default options on the latest release (1.1.2-1 linux) on my Intel Atom-based Synology DS710+ (running DSM 3.0), under BusyBox. This is what I get:
if I try to run ctlscript.sh status, I get this:
Anyone have any ideas? |
|
|
Sorry but it seems BusyBox does not support some commands and in this case it seems that does not fully support perl. |
|
|
So is that it? I can’t do anything? Or can I alter the scripts to suit the reduced BusyBox functionality? Where do I look? Thanks. |
|
|
It looks like this failure is simply because BusyBox stat doesn’t support the —format switch rather than Perl as a whole. Presumably this is where the script stops and there’s a whole bunch of stuff it’s supposed to do afterwards but isn’t. Surely this is something I can easily fix if I know where to look? Or is this just the start of a mountain of trouble? Perl is formally included with Synology so the support should be pretty comprehensive. |
|
|
Hi, You can create a small fix as a workaround: 1. Create a “stat” script whith the following:
2. Change permissions: chmod 755 stat Then run the installer again and the stat action should not fail. Once the stack was installed you can remove this script. |
|
|
Hmmm, it appears BusyBox always uses built-ins over what’s in the path. The only way I could get a fake “stat” to work was by putting alias stat=“echo” in the system-wide profile. Whilst that works from the command line, the BitNami Redmine installer falls back to the built-in stat and I get the same error :( |
|
|
OK you replace it the system “stat” comand with a fake script? |
|
|
Well, stat is part of BusyBox, so I can’t actually replace that individual command with a fake script. And having a fake script in my path doesn’t work, because BusyBox will always execute an internal command instead of what is in the path. And even using an alias to redirect stat doesn’t work (although as I say, this final method DOES work from the command line but not with the installer). |
|
|
Sorry in this case it seems it is not possible to run the installer on top of BusyBox. |
|
|
That’s a real shame. I think you’d get quite a lot of interest if there was a modified stack suitable for BusyBox as it’s in a LOT of embedded devices, stripped-down systems and NAS boxes! |

