QNAP NAS:Entware: различия между версиями
8j0rn (обсуждение | вклад) (Новая страница: «Аналог QNAP_NAS:QNAPware, но с более большим списком пакетов. Список пакетов по адресу: bin.entware.net (armv5 (kernel 3.2 and higher), packages) Установщик: bin.entware.net Оригинал описания: forum.qnap.com https://...») |
8j0rn (обсуждение | вклад) Нет описания правки |
||
| Строка 1: | Строка 1: | ||
==Описание== | |||
Аналог [[QNAP_NAS:QNAPware]], но с более большим списком пакетов. | Аналог [[QNAP_NAS:QNAPware]], но с более большим списком пакетов. | ||
Список пакетов по адресу: [[http://bin.entware.net/armv5sf-k3.2/Packages.html bin.entware.net]] (armv5 (kernel 3.2 and higher), packages) | |||
Список пакетов по адресу: [[http://bin.entware.net/armv5sf-k3.2/Packages.html | Установщик: [[http://bin.entware.net/other/Entware_1.00std.qpkg bin.entware.net]] | ||
Оригинал описания: [[https://forum.qnap.com/viewtopic.php?f=351 forum.qnap.com]] | |||
Установщик: [[http://bin.entware.net/other/Entware_1.00std.qpkg | [[https://github.com/Entware/Entware/wiki#installation github.com]] | ||
== Installation == | |||
Оригинал описания: [[https://forum.qnap.com/viewtopic.php?f=351 | |||
[[https://github.com/Entware/Entware/wiki#installation | |||
See Install on... from right column to find out how to use Entware on your device. If you are using some unlisted device, make sure the few very basic requirements are met: | See Install on... from right column to find out how to use Entware on your device. If you are using some unlisted device, make sure the few very basic requirements are met: | ||
ARMv5, ARMv7, ARMv8(aarch64), MIPS, MIPSEL and x64 platform. | ARMv5, ARMv7, ARMv8(aarch64), MIPS, MIPSEL and x64 platform. | ||
rewritable **''%%/opt%%''** folder (as a part of rootfs or external drive). | rewritable **''%%/opt%%''** folder (as a part of rootfs or external drive). | ||
ability to run | ability to run <span style="color: green">/opt/etc/init.d/rc.unslung</span> start after boot and **''%%/opt/etc/init.d/rc.unslung%%''** stop before shutdown. | ||
(optional) ability to run **''%%/opt/etc/profile%%''** for interactive ssh/telnet session. | (optional) ability to run **''%%/opt/etc/profile%%''** for interactive ssh/telnet session. | ||
See Upgrade from... from right column if you've got working Entware-ng/-3x installation. | See Upgrade from... from right column if you've got working Entware-ng/-3x installation. | ||
== 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: | ||
<pre style="color: green"> | |||
< | # opkg update | ||
# 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. | </pre> | ||
</ | <pre style="color: green"> | ||
# opkg list transmission* | |||
< | transmission-cli - 2.84-4 - CLI utilities for transmission. | ||
# opkg list transmission* | transmission-daemon - 2.84-4 - Transmission is a simple BitTorrent client. | ||
transmission-cli - 2.84-4 - CLI utilities for transmission. | |||
transmission-daemon - 2.84-4 - Transmission is a simple BitTorrent client. | |||
It features a very simple, intuitive interface | It features a very simple, intuitive interface | ||
on top on an efficient, cross-platform back-end. | on top on an efficient, cross-platform back-end. | ||
This package contains the daemon itself. | This package contains the daemon itself. | ||
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> | ||
<pre style="color: green"> | |||
< | # opkg install transmission-web | ||
# 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. | Installing transmission-daemon (2.84-4) to root... | ||
Installing transmission-daemon (2.84-4) to root... | Downloading http://bin.entware.net/mipselsf-k3.4/transmission-daemon_2.84-4_mipselsf.ipk. | ||
Downloading http://bin.entware.net/mipselsf-k3.4/transmission-daemon_2.84-4_mipselsf.ipk. | ... | ||
... | 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> | ||
</ | == 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 style="color: green"> | |||
< | # opkg update | ||
# opkg update | # opkg upgrade | ||
# opkg upgrade | # minidlna | ||
# 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> | ||
</ | |||
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 style="color: green"> | |||
< | # opkg --autoremove remove minidlna | ||
# opkg --autoremove remove minidlna | # opkg install minidlna | ||
# opkg install minidlna | |||
Internals | Internals | ||
</ | </pre> | ||
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. | ||
Версия от 14:17, 3 февраля 2024
Описание
Аналог QNAP_NAS:QNAPware, но с более большим списком пакетов. Список пакетов по адресу: [bin.entware.net] (armv5 (kernel 3.2 and higher), packages) Установщик: [bin.entware.net] Оригинал описания: [forum.qnap.com] [github.com]
Installation
See Install on... from right column to find out how to use Entware on your device. If you are using some unlisted device, make sure the few very basic requirements are met: ARMv5, ARMv7, ARMv8(aarch64), MIPS, MIPSEL and x64 platform. rewritable **%%/opt%%** folder (as a part of rootfs or external drive). ability to run /opt/etc/init.d/rc.unslung start after boot and **%%/opt/etc/init.d/rc.unslung%%** stop before shutdown. (optional) ability to run **%%/opt/etc/profile%%** for interactive ssh/telnet session. See Upgrade from... from right column if you've got working Entware-ng/-3x installation.
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:
# opkg update Downloading http://bin.entware.net/mipselsf-k3.4/Packages.gz. Updated list of available packages in /opt/var/opkg-lists/entware.
# opkg list transmission* transmission-cli - 2.84-4 - CLI utilities for transmission. transmission-daemon - 2.84-4 - Transmission is a simple BitTorrent client. It features a very simple, intuitive interface on top on an efficient, cross-platform back-end. This package contains the daemon itself. transmission-remote - 2.84-4 - CLI remote interface for transmission. transmission-web - 2.84-4 - Webinterface resources for transmission.
# opkg install transmission-web Installing transmission-web (2.84-4) to root... Downloading http://bin.entware.net/mipselsf-k3.4/transmission-web_2.84-4_mipselsf.ipk. Installing transmission-daemon (2.84-4) to root... Downloading http://bin.entware.net/mipselsf-k3.4/transmission-daemon_2.84-4_mipselsf.ipk. ... See Using... articles from right column to find out some use cases.
Note about packages upgrade
In some rare cases you can fall into issue when new package wont start:
# opkg update # opkg upgrade # minidlna minidlna: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
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:
# opkg --autoremove remove minidlna # opkg install minidlna Internals
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. 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.