Перейти к содержанию

QNAP NAS:Entware: различия между версиями

нет описания правки
Нет описания правки
 
(не показаны 3 промежуточные версии этого же участника)
Строка 15: Строка 15:
== Using repo ==
== Using repo ==
Entware uses OPKG package manager, detailed help can be found here. Lets find transmission packages and install it's Web UI with dependencies, just for example:
Entware uses OPKG package manager, detailed help can be found here. Lets find transmission packages and install it's Web UI with dependencies, just for example:
<source lang="php">
 
  # opkg update
<syntaxhighlight lang="bash">
  $> opkg update
  Downloading http://bin.entware.net/mipselsf-k3.4/Packages.gz.
  Downloading http://bin.entware.net/mipselsf-k3.4/Packages.gz.
  Updated list of available packages in /opt/var/opkg-lists/entware.
  Updated list of available packages in /opt/var/opkg-lists/entware.
</source>
</syntaxhighlight>
<pre>
 
  # opkg list transmission*
<syntaxhighlight lang="bash">
  $> opkg list transmission*
  transmission-cli - 2.84-4 - CLI utilities for transmission.
  transmission-cli - 2.84-4 - CLI utilities for transmission.
  transmission-daemon - 2.84-4 - Transmission is a simple BitTorrent client.
  transmission-daemon - 2.84-4 - Transmission is a simple BitTorrent client.
Строка 29: Строка 31:
  transmission-remote - 2.84-4 - CLI remote interface for transmission.
  transmission-remote - 2.84-4 - CLI remote interface for transmission.
  transmission-web - 2.84-4 - Webinterface resources for transmission.
  transmission-web - 2.84-4 - Webinterface resources for transmission.
</pre>
</syntaxhighlight>
<pre>
 
  # opkg install transmission-web
<syntaxhighlight lang="bash">
  $> opkg install transmission-web
  Installing transmission-web (2.84-4) to root...
  Installing transmission-web (2.84-4) to root...
  Downloading http://bin.entware.net/mipselsf-k3.4/transmission-web_2.84-4_mipselsf.ipk.
  Downloading http://bin.entware.net/mipselsf-k3.4/transmission-web_2.84-4_mipselsf.ipk.
Строка 38: Строка 41:
  ...
  ...
  See Using... articles from right column to find out some use cases.
  See Using... articles from right column to find out some use cases.
</pre>
</syntaxhighlight>


== Note about packages upgrade ==
== Note about packages upgrade ==
In some rare cases you can fall into issue when new package wont start:
In some rare cases you can fall into issue when new package wont start:
<pre>
 
  # opkg update
<syntaxhighlight lang="bash">
  # opkg upgrade
  $> opkg update
  # minidlna
  $> opkg upgrade
  $> minidlna
  minidlna: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
  minidlna: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
</pre>
</syntaxhighlight>
 
Unfortunately, **''%%opkg%%''** is too simple to track down **''%%minidlna%%''** dependencies has been changed and **''%%minidlna%%''** should be re-installed too. So, you have to do that manually:
Unfortunately, **''%%opkg%%''** is too simple to track down **''%%minidlna%%''** dependencies has been changed and **''%%minidlna%%''** should be re-installed too. So, you have to do that manually:
<pre>
 
  # opkg --autoremove remove minidlna
<syntaxhighlight lang="bash">
  # opkg install minidlna
  $> opkg --autoremove remove minidlna
  $> opkg install minidlna
Internals
Internals
</pre>
</syntaxhighlight>
 
Entware uses OpenWrt buildroot to compile packages. Some of packages came from OpenWrt, others are unique. We sync our sources with OpenWrt feeds and update our own packages approx. once per month, catching bugs and adding some enhancements all other time.
Entware uses OpenWrt buildroot to compile packages. Some of packages came from OpenWrt, others are unique. We sync our sources with OpenWrt feeds and update our own packages approx. once per month, catching bugs and adding some enhancements all other time.
See how to Compile packages from sources if you wish to edit or add packages.
See how to Compile packages from sources if you wish to edit or add packages.
Every binary from the repo uses no library from outside the /opt folder. No kernel modules are provided as long as they may be (and will be!) incompatible with current firmware.
Every binary from the repo uses no library from outside the /opt folder. No kernel modules are provided as long as they may be (and will be!) incompatible with current firmware.