1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Nas200 Lampp

Discussion in 'Cisco/Linksys Network Storage Devices' started by Nymus, May 1, 2008.

  1. Nymus

    Nymus Addicted to LI Member

    Is there a way to download XAMPP for Linux and make it run straight out the box?
    Normally this is used to setup a WoS, but can it be used here?
    Just extract the tar file onto your harddisk and run a lampp start...
    As everything is included, nothing should be installed (I guess)?

    Someone has experience running this on a NAS200?
     
  2. jac_goudsmit

    jac_goudsmit Super Moderator Staff Member Member

    I haven't tried it and it looks pretty heavy (i.e. big) so don't expect much from performance if you can get it to run. In theory it may be possible to get it to work on my firmware, if it's compatible with the installed system libraries (there's currently no easy way to update the libraries).

    I'd say, just give it a try and let us know if you get it to work, or what problems you run into. Just copy the tar.gz file onto the harddisk over the network, then log in using SSH and follow the unpacking instructions. Note that the root filesystem on the NAS200 is read-only so you may have to do some (or a lot! as I said this looks like a big package) of tweaking to get everything to work.

    ===Jac
     
  3. Nymus

    Nymus Addicted to LI Member

    Jac,

    I gave it a try, but it expects to be installed in the /opt/lampp directory.
    And the current firmware has no opt directory nor lets me create one.
    File system is read-only...

    I used this as guide http://www.apachefriends.org/en/xampp-linux.html

    I then extracted it on my harddisk and did a batch replace of the /opt/lampp string in all scripts to /harddisk/volume_1/data/lampp

    No succes however as it returned:

    lampp: 20: Syntax error: "(" unexpected

    Then I removed my 'modified' version and tried the same without changing the paths in the scripts. Got the same error ...

    As there is no easy way of installing packages, I had hoped this to work as it contains 'all' packages necessary to run. (at least thats what I expect from a WoS).

    Any ideas?
     

Share This Page