NASLite Network Attached Storage

hi,
i want to run a little application on the machine NL2 is on...is it possible ??
it will be great cause i can turn off an other system over night or when not neede...actually this system runs only, because the server app is on it...


thanks a lot
greets

Nope, there is no command line available on NL.

This is not an option with NL because it would bring with it possible instability or worse yet, the loss of data. To do what you are talking about you will need to go with something like Ubuntu server and set up SAMBA on it along with what ever app you are looking to run.

Mike

mhh thanks for answer....

is it possible to get an version where i can start one or two more processes? on my one risk!

i don´t wanna set up an extra machine... and it would be the greatest to combine this easy running fileserver and antoher service in background!

thanks for an answer..

If your looking to do this then why not just load Ubuntu on it instead and setup the processes you need. What you want to do is not what NL was designed to do.

It is a NAS utility, designed for speed and reliability. It is not designed as a server, which is what you are asking for at this point. You need console and NL has none available to the user.

PM Tony or Ralph, maybe they will, maybe they won't.

Mike

Regarding the inability of NASLite to run "apps" natively - there are very good reasons for why that is not possible and also not desirable. I'll try and explain as follows:

In terms of environment, the first thing to consider is that NASlite runs in a very tight RAM-disk where room is allocated to accommodate only the needs of the associated services. The second thing to consider are dependencies. NASlite uses minimalist libraries that include only functionality required by the associated services. It is highly unlikely that other apps will run unmodified. Point here is that NASLite contains only that which is necessary to run the associated services and is not designed to run other apps.

In terms of booting and configuration, NASLite boots each time with no idea what hardware it will have to render and what resources it will have to export. All of that is probed and set at boot time. The configuration contains only options that are not associated with low-level hardware services. The exception to that rule are the options one can set for each individual disk. In that case the options are saved on the disk in question, so those options will migrate with the disk. With that in mind, it is easy to understand why all services are configured on the fly based on what is available for export. That makes the execution of foreign apps virtually impossible within the NASLite environment.

And then, there is the question of stability, but that is a very subjective topic. We have done a good number of tests to determine the most-suitable approach for providing the core NASLite services in the most efficient, effective and stable manner. The M2 version is a perfect example of the above. In theory the task of adding UPnP and DAAP services to NASLite is rather trivial, but in practice, it was very time consuming and often frustrating.

Hope that answers some of the questions people may have on the topic.