==== INFO on Bugs READ BUGS section just before the download ====
I am please to announce the availability of Entware-ng a COMPLETE substitute for Optware (abandoned not maintained) and Astware (specific to the platform)
Next NO NEEDED with 0.97
====== DUE TO recent update[/size] ... please just after installation do : open a console, then opkg update ; opkg upgrade ========
Entware-ng is 100% on line with Openwrt version available on multiple plateform ... mipsel, armel, armhf, x86, x86_64
Entware-ng is maintained ... and updated frequently and on bug report ...
Entware-ng use UP TO DATE libraries ex. libc is 2.23 compare to version provide by Asustor
... from Optware NOT really ... get the list of installed software, save your config file (to be adapted) and uninstall it MANDATORY
... from astware it's possible
... ... get the list of installed software and depends :
... ... /opt/bin/opkg list_installed | grep -v ^opkg | cut -d ' ' -f 1 > /share/Public/my_applist
... ... save configuration file
... ... then reinstall using the list (ex. using a while read line ; do /opt/bin/opkg install $line ; done < /share/Public/my_applist
... then uninstall astware ...
[size=150]FOR SECURITY REASON PLEASE UN-INSTALL Optware and / or Astware before installing Entware-ng
Entware-ng use /opt ...
... to manage folder or file install in opt during installation or after at boot ... a move mechanism is use to keep the correct path ...
... ex. /opt/google/chrome/chrome-sandbox
... if exist at install it is move to the new /opt, if (even normally not) it exist when Entware-ng start at boot (or be disable at boot and started later) ... it is moved also ...
... correct a problem of not changing opt_(arch) to opt ... so link broken
... include Patch for coexisting with Virtualbox
... Upgrade possible ... you keep previous install ALL YOUR program and configuration
0.96 corrected for previous firmware (AS_NAS_ARCH not filled for x86 32 bits models before 2.5.1 Beta) ... use uname to select the good one (Thanks to Ekilor that report the bug)
[Upgrade from 0.96 to 0.97]
... NO need if you have already apply the patch
... If you upgrade ... YOUR opkg programs, start_up and configuration are keep AS IS ... only an opkg update and opkg upgrade is done
ALL with an automatic selection of version (uname -m)
x86 with 32 bits firmware (32 bits x86 version installed)
x86 with 64 bits firmware (64 bits version is installed)
Optware and Astware must be uninstalled BEFORE ... (even an option exist to keep astware on x86 model ... even risky)
1600+ ... list : http://entware.wl500g.info/binaries/ent ... kages.html Packages are updated one per month
changelog (version updated) : https://github.com/Entware/entware/wiki/Changelog
Specific packages from Zyxmon exist like Deluge 1.3.12 + addons, iotop, etc. exist also
Wiki : https://github.com/Entware/entware/wiki (adapt to Asustor implementation)
Issues and bugs report : https://github.com/Entware/entware/issues (only issue for Entware packages)
One command compatible with old ipkg one : opkg
An auto start services mechanism exist to start background process (all is provide to run your own)
BASIC FIRST usage :
ALL PREVIOUS requirement are NOT yet needed
open a console and do :
if you start using it from an existing open console add before using :
... this source add /opt/bin and /opt/sbin in the PATH (way to search executable program)
... NOW 0.97
... opkg update and opkg upgrade will be done after install (first start of Entware-ng)
... only "source /opt/etc/profile" is need if you DON'T close and re-open the console
list packages available :
or better try to select part of the name
opkg list | grep xxx (xxx is apart of the name ex. netstat ... )
If the output is too large cut the first words (here output field 1 to 10 of the response separator is space " "
opkg list | cut -f 1-10 -d " "
You can combine all of them ...
Detail of opkg options :
- Code: Select all
opkg must have one sub-command argument
usage: opkg [options...] sub-command [arguments...]
where sub-command is one of:
update Update list of available packages
upgrade Upgrade installed packages
install <pkgs> Install package(s)
configure <pkgs> Configure unpacked package(s)
remove <pkgs|regexp> Remove package(s)
flag <flag> <pkgs> Flag package(s)
<flag>=hold|noprune|user|ok|installed|unpacked (one per invocation)
list List available packages
list-installed List installed packages
list-upgradable List installed and upgradable packages
list-changed-conffiles List user modified configuration files
files <pkg> List files belonging to <pkg>
search <file|regexp> List package providing <file>
find <regexp> List packages whose name or description matches <regexp>
info [pkg|regexp] Display all info for <pkg>
status [pkg|regexp] Display all status for <pkg>
download <pkg> Download <pkg> to current directory
compare-versions <v1> <op> <v2>
compare versions using <= < > >= = << >>
print-architecture List installable package architectures
depends [-A] [pkgname|pat]+
whatdepends [-A] [pkgname|pat]+
whatdependsrec [-A] [pkgname|pat]+
whatprovides [-A] [pkgname|pat]+
whatconflicts [-A] [pkgname|pat]+
whatreplaces [-A] [pkgname|pat]+
-A Query all packages not just those installed
-V[<level>] Set verbosity level to <level>.
--verbosity[=<level>] Verbosity levels:
0 errors only
1 normal messages (default)
2 informative messages
4 debug level 2
-f <conf_file> Use <conf_file> as the opkg configuration file
--cache <directory> Use a package cache
-d <dest_name> Use <dest_name> as the the root directory for
--dest <dest_name> package installation, removal, upgrading.
<dest_name> should be a defined dest name from
the configuration file, (but can also be a
directory name in a pinch).
-o <dir> Use <dir> as the root directory for
--offline-root <dir> offline installation of packages.
--add-arch <arch>:<prio> Register architecture with given priority
--add-dest <name>:<path> Register destination with given path
--force-depends Install/remove despite failed dependencies
--force-maintainer Overwrite preexisting config files
--force-reinstall Reinstall package(s)
--force-overwrite Overwrite files from other package(s)
--force-downgrade Allow opkg to downgrade packages
--force-space Disable free space checks
--force-postinstall Run postinstall scripts even in offline mode
--force-remove Remove package even if prerm script fails
--force-checksum Don't fail on checksum mismatches
--noaction No action -- test only
--download-only No action -- download only
--nodeps Do not follow dependencies
--nocase Perform case insensitive pattern matching
Remove package and all dependencies
--autoremove Remove packages that were installed
automatically to satisfy dependencies
-t Specify tmp-dir.
--tmp-dir Specify tmp-dir.
regexp could be something like 'pkgname*' '*file*' or similar
e.g. opkg info 'libstd*' or opkg search '*libop*' or opkg remove 'libncur*'
Opkg documentation : https://wiki.openwrt.org/doc/techref/opkg
Version APKG : 0.97 (current)
In x86 (32 bits models) and perhaps on Arm (T.B.C.)
... some package refuse to install due to space not avaialble in /opt
... ... ex. for gcc : "verify_pkg_installable: Only have 0kb available on filesystem /opt, pkg gcc needs 28646"
... This is due to Asustor choice ... to have /opt in romfs
... this error is only for "big" packages (BUT big is relative to space available in a router (opkg come from OpenWRT) , on this "big" package a stat of file-system is done and return free space = 0 on /opt (normal for a romfs) ...
... SOLUTION : use --force-space in command line : ex. "opkg --force-space install <package>"
ADD THIS permanently (no more in command line)
... add line :
in /opt/etc/opkg.conf ... so this will be added transparently to all opkg command ...
PATCH MUST BE APPLY on v0.96 BUT ONLY on 0.96 NOT with 0.97 to solve conflict with VirtualBox
POST : viewtopic.php?f=42&t=7695
APPLY to ALL NAS model is possible (for the future) ... to be compatible with version 0.97 and more ...
APKG 0.97.2 : https://mega.nz/#!lx0mRb5K!CCOmg26FMa_b ... K7PCcPlU-0