On Tue, 1 Nov 2005 23:15:23 +0100 "Holger Bauer" <[EMAIL PROTECTED]> wrote:
> Well, I haven't tried that yet, but I would think that should work just > fine. If not just set the file back to the original state, reboot (so it > runs as rw filesystem again), upload firmware, set file back tp wrap and > reboot to make it ro again. But I would first try under labcondition if > it works with ro filesystem. If the file isn't accepted in ro state > (reporting a platform error) try renaming the firmwarefile so it has > "-wrap-" in the filename. > > And of course, share your knowledge if you find out anything ;-) > > Holger > I didn't try it for a long time because until V 0.95.4 there were other (DynDNS bugs) which kept me from doing this. Now, I have tried the upgrade from 0.95.4 to 0.96.4 and it went fine after reverting the platform to "pfSense". Without that, when the platform was "wrap", the upgrade process didn't even start. I didn't try yet the second solution ie. renaming the firmware file. Maybe next time. When the platform is faked to "wrap", it will expect the filename to be xxx-wrap-xxx or xxx-Embedded-xxx? Any hint? Best regards Imre -- This is Linux Land. In silent nights you can hear the windows machines rebooting
signature.asc
Description: PGP signature
