[LEDE-DEV] restore or compile config backup from openwrt

Jochen Demmer jochen at winteltosh.de
Fri Aug 12 14:59:07 PDT 2016


There that script in ./scripts/env that let you handle more than one 
environment and that's why files actually reside in ./env/files rather 
than in ./files.
./files is only a symlink to ./env/files. Might this not be supported 
any more?

Jochen


Am 08.08.16 um 03:32 schrieb Yousong Zhou:
> On 7 August 2016 at 19:36, Jochen Demmer <jochen at winteltosh.de> wrote:
>> I'm sorry if my questions seems to stupid for you to answer, but I would
>> have to ask again.
>> I build with buildroot, flash to device, but everything I put in ./env/files
>> won't get to the devices filesystem where I expect it to be.
>> What I got is only default configuration files there.
>>
>> That procedure of putting files into ./env/files worked fine with openwrt's
>> buildroot. Did you change default behaviour?
>>
>> Jochen
>>
> I am only aware of path `files/` (in toplevel dir, not `env/`) for
> this purpose.  Does it work for you?
>
>                  yousong
>
>> Am 11.07.16 um 10:10 schrieb Jochen Demmer:
>>
>>> Hi,
>>>
>>> would I have to expect problems when restoring a configuration backup from
>>> a Chaos Calmer device?
>>> I plan to upgrade some devices to lede but don't want to reconfigure them
>>> manually.
>>>
>>> Also: What if I compile myself a lede firmware with buildroot and also use
>>> old configuration files (/etc/config) from a openwrt based system? I would
>>> put them into the corresponding files subdirectory of the buildroot path.
>>> I just tried it with a Archer C7 v2 and the vlan configuration doesn't
>>> seem to work.
>>>
>>> Thank you
>>>
>>> _______________________________________________
>>> Lede-dev mailing list
>>> Lede-dev at lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/lede-dev
>>
>> _______________________________________________
>> Lede-dev mailing list
>> Lede-dev at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/lede-dev



More information about the Lede-dev mailing list