Hi,
FreeWRT configuration filesystem is not intended to solve every
problem with configuration management on an embedded device. Fwcf is
designed to exactly solve following problem:
Somebody created a VPN appliance with FreeWRT. It is a monolothic
firmware for a specific device, with a specific functionality.
This appliance is used world-wide with more than 10 devices.
The device is remotely only accessible when the VPN tunnel is active.
After a while, some bugs are found, f.e. the Samba package is broken
and you can not create files with spaces, so you need to update 10
or more devices remotely via secure shell, without loosing the
configuration, otherwise the VPN tunnel does not come up again.
Here comes the reason why fwcf is developed. And it works exactly
like it should.
The above example is a reallife example ;)
I see no chance to get it working with the workflow Markus is
describing, because this would strongly depend on the filesystem
which is used. If you need to reset a device, just flash your new
image via:
mtd -e fwcf -r write image.bin linux
If you have an idea how to implement the functions you need, feel
free to add it as a new package ;)
bye
Waldemar
--
don't open your wrt, free it
http://www.freewrt.org
_______________________________________________
freewrt-developers mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-developers
