OK. So it looks like to upgrade my existing Kamikaze installation, I'm going to need to flash a new firmware onto it with mtd.
But I am sure this will not be the last time I want to do this and I really want to avoid having reconfigure from scratch every time. So, I understand that for the new firmware I'm going to build, I can add packages (i.e. to the firmware so that I don't have to use ipkg to add them after I flash the new firmware) that I had installed since my last firmware build/install simply by changing them from "m" to "y" when I "make config". Am I correct, so far? Now, there is the issue of all of the configuration I have done since I did my last firmware installation. A very nice, typical example is say /etc/config/network. Of course, that is custom to my installation but I'd like to avoid having to reconfigure that every time I install a new firmware. So I see that in package/base-files/files/etc/config/network is the basic network config. Should I modify that for my local installation, so that the firmware I create will have it's network already configured for my use? This seems a bit un-portable though, and what of other files from other packages? Running around making these "per installation specific" changes seems like a bad idea. Any way to avoid? Any way to build custom firmwares without using these kinds of "source hacks"? Indeed, I could simply backup and then restore /etc/config after I have done my reflashing, but even then, I'm monkeying around with that 192.168.1.1 address again. Is there any way for me to see what the filesystem will look like on my router after I've reflashed, prior to reflashing? I want to be able to inspect it and make tweaks to my build tree, rebuild the firmware image and check again, etc. Can I easily mount the firmware's filesystem for examination on my build host, or is there a copy of what's in the firmware's filesystem in a directory in the build tree somewhere? i.e. staged before building the firmware image. Thanx for any questions you would care to answer, b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ openwrt-devel mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
