Unless I'm missing something, it's an easy change because that's exactly what I did tinkering with it last night. I copied /usr/sbin/entware-setup.sh to jffs and adjusted the install url for arm7Thanks. @john9527 , you want to take a shot at updating entware-setup.sh with these? I'm still stuck in 384 debugging Hell here these days...
INST_URL='http://pkg.entware.net/binaries/armv7/installer/entware_install.sh'
INST_URL='http://bin.entware.net/armv7sf-k2.6/installer/generic.sh'
Probably an automated filter blocking it for code usages.AB-solution thread vanished?
Will the thread be back? I don't understand. I was just posting a reply and the whole thread disappeared!Probably an automated filter blocking it for code usages.
It's happened before where the thread got locked/hidden for some reason. I've messaged moderators so hopefully it'll be back soon.Will the thread be back? I don't understand. I was just posting a reply and the whole thread disappeared!
Yep...turned out to be an easy changeUnless I'm missing something, it's an easy change because that's exactly what I did tinkering with it last night. I copied /usr/sbin/entware-setup.sh to jffs and adjusted the install url for arm7
I put mine in post-mount ages ago and haven't looked back. A loop made no sense when there was an event-driven script call for the entware device!Yep...turned out to be an easy change
But while looking at it, someone remind me again why the entware start is in services-start with a retry loop instead of in post-mount? I seem to remember some discussion on this in the past.
Looks like it, the thread is marked as "moderated" to me.AB-solution thread vanished?
It's all that expletive language you use ;-)Looks like it, the thread is marked as "moderated" to me.
But I would not know why.
I could have used such language this morning when I realized what's really up with the Entware changes.It's all that expletive language you use ;-)
Me too...first thing I did after installing. Maybe we're missing something?I put mine in post-mount ages ago and haven't looked back. A loop made no sense when there was an event-driven script call for the entware device!
Everything seems to work fine so I must be really missing something!Me too...first thing I did after installing. Maybe we're missing something?
Yeah it's great fun when something gets pushed from upstream that blindsides you and next thing you know users are flooding your support channels asking why it's brokenI could have used such language this morning when I realized what's really up with the Entware changes.
All good now but I really would liked to have known beforehand to be prepared. @RMerlin and other coders around here usually have the foresight to warn me and let me have a go at the changes before it's published.
Ah, well, can't have it all.
MIPS does not need a change in the URL, it's the same as before. Only ARMv7 and aarch64 have changed.Smooth sailing, from what I can tell. I assume you can do the same with mips, but I can't test it.
I changed the case statement to this in AB-Solution, using 64-bit for the 86U. The MIPS url is the same as before:I still want to keep the setup script in the firmware. Don't forget that it's actually just a bootstrap, not the actual installer. What it does (if my memory's right):
1) Check for supported partition
2) Check the router's platform
3) download and execute the appropriate Entware installer
So I assume we'll just need to update the location of the new installer(s), and possibly add a code path for the aarch64 platform so it uses the 3x repo (I'm assuming the busybox and default path issues have been resolved since last time I looked at it).
case $(uname -m) in
armv7l) PART_TYPES='ext2|ext3|ext4'
INST_URL='http://bin.entware.net/armv7sf-k2.6/installer/generic.sh';;
mips) PART_TYPES='ext2|ext3'
INST_URL='http://pkg.entware.net/binaries/mipsel/installer/installer.sh';;
aarch64) PART_TYPES='ext2|ext3|ext4'
INST_URL='http://bin.entware.net/aarch64-k3.10/installer/generic.sh';;
*) lastError=" $(uname -m) is an unsupported platform to install\n Entware on."
reload_menu;;
esac
I'm already running OpenVPN 2.4.5 on my router....no problems there. I didn't see the Dropbear update, but given the history with Dropbear, we probably need to wring that out a bit before releasing it.
Unless I'm missing something, it's an easy change because that's exactly what I did tinkering with it last night. I copied /usr/sbin/entware-setup.sh to jffs and adjusted the install url for arm7
It's happened before where the thread got locked/hidden for some reason. I've messaged moderators so hopefully it'll be back soon.
I'm willing to apply to help out on some of the Europe side of things, if it would help?When a post awaits moderator review, the forum mods already receive notifications about it. Just have to be patient, only three of us to cover the forums, and I know at least two of us are in North America, so we're typically asleep during Euro/Asian mornings.
The entware change was so easy, I pulled in dropbear as well and made the changes for the localoptions.h support. Running now.One of the changes mentioned in the changelog is how you customize options.h, so it will take a few minor adjustments on top of the merge.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!