for all:
root @ XiaoQiang: ~ # opkg install libgcc
Package libgcc (4.8-linaro-1) installed in root is up to date.
Configuring libgcc.
/data//usr/lib/opkg/info/libgcc.postinst: line 4: default_postinst: not found
Collected errors:
* pkg_run_script: package "libgcc" postinst script returned status 127.
* opkg_configure: libgcc.postinst returned 127.


I looked in other konfs and lately a bunch of people have a problem and no answer.
as a result of recommendations from the topicDiscussion: OpenWRT on ZyXEL Keenetic series routers in /data//usr/lib/opkg/info/libgcc.postinst commented out line number 4 default_postinst $ 0 $ @ and everything seemed to be delivered.
The solution is, of course, clumsy, it would be better if the default_postinst script worked, but it doesn’t exist and there’s not enough imagination ;-)

I'll try what happened - I’ll add in this message

Post has been editedcrass1968 - 22.09.14, 18:01

not. DE is definitely not needed in the router. but owncloud is the same - it will already be very, very nice. yes and webmin for example

Post has been editedlightvik - 22.09.14, 14:45

Trackscream ,


lua.tar.gz(569.89 KB)
www.tar.gz(7.57 MB)

>debian is not native to ordinary luce

To avoid strong confusion:
UCI are just unified configs for everything, which all have a single simple format and lie in a single place (/ etc / config). Well, the support system - scripts for convenient parsing of these configs. daemon init scripts parse uci configs and if necessary convert them to traditional software configs (or convert to command line parameters, it doesn't matter).
However, absolutely no one bothers to use traditional configs. It’s just that uci is more convenient, as long as you don’t need to remember where and what is configured.
debian-based is a system where software lies in turnips in the form of .deb files and is controlled by utilities like dpkg, aptitude, apt-get, etc. Unlike openwrt (opkg) and optware (ipkg) packages.
Accordingly, writing a program that will be deployed via .deb and at the same time configuring with uci does not present any special difficulties!

klirichek luci works not only through uci. In the openwrt trunk, part of the work of the guides is through ubus, the dbus clone for embedded systems. Moreover, as far as I remember, their interface is not too compatible. At least for this reason, I was not able to secure a lucy in the stock on the stock firmware. Rather, it was possible, but it worked through crutches and very crookedly.
P.S. You can certainly build ubus for debian and tweak the overall compatibility, but is the game worth the candle?
P.P.S.heremore details on this subject.


Post has been editedTrackscream - 22.09.14, 18:47

damn, it turned out that there is no mc (GNU Midnight Commander) in the openwrt repository for bcm53xx - if anyone knows where to find it, please share it!

crass1968, just build it yourself, on the mc network under openwrt there is no processor for our architecture yet. Perhaps they will add in the future, but for now, "spin as you like." The existing branch for architecture is in active development, so something may be missing, and everything in general may not work. This is normal at the moment.

And try to assemble it yourself!
In openwrt, this is usually more than simple (simpler than in dd-wrt).
In most cases, the differences between similar architectures are trivial (i.e. new packages are not added trite due to lack of free time, but not because of critical differences)

Sergiys2009, according to comrade klirichek self-assembled core does not want to work with stock firmware, i.e. while deaf. We will dig further.

I seem to have gathered mc here, please check if someone is working or not. The bcm47xx architecture for compatibility with stock unmodified firmware, the real ARM architecture with optimizations for the Cortex A8 (the same bcm53xx).

If it requires some dependencies, let me know which ones - I will give ipk for them.
May require libglib or ncurses, but both of them I think are in stock

Rename the file extension to .ipk, the forum does not allow you to upload files with this extension, I had to cheat :)
mc_4.7.5.3-2_brcm47xx.zip(314.62 KB)


Post has been editedTrackscream - 23.09.14, 08:29

TrackScream, jarvis (jarvis - from github) comes with firmware. And on that firmware the same web face as on stock. Those. "outside" you can’t tell what exactly is running. (By the way, who wanted iptv here - there is the necessary flag in the kernel config; it is possible to try)
But to make a "Frankenstein" from the core of the jarvis and the root of the runoff did not work out of the blue. Downloading when switching from the kernel to the root is severely slowed down (the startup took about 2 minutes), and upon completion, a reboot occurs.
There are fewer modules in the config on the jarvis; probably it makes sense to go through the contents of / lib / modules runoff and try to get the same thing in the jarvis (oh, if there was a stock kernel config - it would be even easier).
(personally, I am much more inclined towards a full-fledged openwrt than to finishing the Frankenstein)

.-------. ---------.---------.---------.-------.--------.
| || | _ | | | | |
| || _ | __| | | | ---|
| || | | | | |-- |
| ||____|____|____|____|_________|_______|________|
| ________ | S M A R T H O M E F R E E D O M
------------------------------------------------------------
Welcome to Jarvis!
------------------------------------------------------------
* Free your mind
* Your private cloud

Powered by Jack's Lab<http://jackslab.org>
------------------------------------------------------------

Isn't the BCM4709 a Cortex-A9?http: //www.broadcom.co...ions/BCM4707-4708-4709
and bcm53xx is generally mips, not arm if I'm not mistaken ...



there is one in the repositoryhttp://www.emuf.cz/dow...47xx/packages/Packages, only the Czechs have a thicker binary. in the evening I’ll check which one will work

By the way, I have long wanted to ask - why are libraries and repositories used for bcm53xx, and not for bcm47xx?

Post has been editedcrass1968 - 23.09.14, 05:59

crass1968, yes, overlooked, A9. But if it does not start then I will rebuild. Everything is complicated with chips: among bcm47xx and bcm53xx, some of the models are built on ARM, some on MIPS. OpenWRT developers decided not to bother and allocated the branch bcm47xx for mips processors, and bcm53xx for ARM, which introduces some confusion. I, at first, did not understand why packets from the 47xx branch on the router did not start, then I only realized that they were built for MIPS. The Czechs have a mirror of the official repository, where packages for 47xx are assembled with mips architecture. I found one more cant: I accidentally showed the package architecture bcm47xx instead of brcm47xx yesterday, the package manager will swear :( Later I will reload the corrected version.
Perezal.

Post has been editedTrackscream - 23.09.14, 08:31

Hmm, really some kind of porridge



in the official mc there is no, and it doesn’t look like a mirror - there are not enough packages, some stub



ok, wait

Here isthat openwrt branch and the package repository on which the firmware for the device is built, mc is in it, but of a "foreign" architecture. Support for Broadcom ARMs at the time of the release of Attitude Adjustment was not in the distribution.

Post has been editedTrackscream - 23.09.14, 08:36

I'm only in / snapshots / trunk / rummaged;)

I think it's worth



this is an extension of the capabilities of the installed firmware: yes2: although if you consider any changes in the / section to be a firmware change, then you are probably right

you don’t need to collect it, it is a set of php scripts.
but to make it work you need a web server with php and a DBMS

pkg_hash_fetch_best_installation_candidate: Packages for mc found, but incompatible with the architectures configured

crass1968, in opkg.conf what architectures and repositories are registered? The package is compatible only with the default config (attitude_adjustment / 12.09 repository and brcm47xx architecture).