11 Aug
2014
11 Aug
'14
7:50 p.m.
Yes, this is the same behavior I noticed. As lime-config is executed in
preinit (as a uci-defaults script), it may not configure properly some
things. And as the exceptions are not controlled in the code, once
something goes wrong the script stops its execution and everything
became not configured.
This is fixed in the branch "new_init" which right now is merged in the
branch "hardware-detection" which is probably the most advanced branch
of the current ones.
I'll compile right now for this branch and the binaries will be
available in the respo.
Cheers.
El lun 11 ago 2014 20:26:13 CEST, Gui Iribarren escribió:
Is there any chance that on firstboot you got a lot of
uncommited uci settings?
Check 'uci changes'
p4u spotted that bug a couple of days ago but i'm not sure he fixed it already
On August 11, 2014 1:43:13 PM GMT-03:00, Max Schmit <max.schmit(a)gmail.com> wrote:
--
./p4u
Hi,
I installed the new image from download.libre-mesh.org, for the 703n
issued on 5 August. The name of the image is sounding fine, however
once installed, the router seems to run a regular openwrt binary, no
LiMe flavour.
Seems that some things are missing or did I?
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev