How To Install Midnight Commander On Nas Setup

For a better experience, please enable JavaScript in your browser before proceeding.

The unofficial Synology forum for NAS owners and enthusiasts.

SynoForum.com is not owned by, or affiliated with Synology Inc.

This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.

By continuing to use this site, you are consenting to our use of cookies.

I follow the advice of Crest: crest wrote: 22 Aug 2017 05:44.

I have updated my nas (version 10.3.0.3 - Pilingitam (revision 4107) x64-embedded with OBI, and MC installed with OBI) to 11.1.0.4 - Atomics (revision 4528) embedded.

Then activate re-install in OBI and perform the installation of mc again.

After that log out from the CLI and login again, mc should start as expected.

Anyway, I have now updated the script for 11.1.0.4.

You can find it at the beginning of this thread.

If there is existing symlinks warnings, reboot the NAS and run the script again.

Also youll need to add mcommander.sh (with full path) in System Advanced Command Scripts (PostInit type) so itll automatically restore symlinks under usrlocal after NAS reboot.

I have poked around in the shell using information taken from the mcommander.sh script and I have found that libssl.so.7 referred to by the script does not exist.

Should I remove the symlink to libssl.so.7 and substitute it with libssl.so.111 for libssl.so.6 if I go Code: Select all ln -s usrliblibssl.so.111 libssl.so.6 the answer is: Code: Select all ln: libssl.so.6: File exists.

Alternatively, could I get a sure fire method of cleaning the slate to install mc from One Button Installer again Thanks, Luca.

How To Install Midnight Commander On Nas Setup