Eugen Leitl wrote: > On Thu, Oct 15, 2009 at 11:40:50AM +0200, Eugen Leitl wrote: > >> Aargh -- you might have found the real culprit there. >> Unfortunately, meanwhile I figured out that the error >> message was due to a corrupt /etc/rc.upgrade (read error, >> I presume the flash is fried). I've copied it over from >> a known good 1.2.2 installation, and tried the console >> upgrade from URL. Watching bsdtar, and praying, here. >> >> Damn, bsdtar just died (or finished correctly), and the >> firewall is now rebooting. Wish me luck. > > The firewall did come up correctly, though of course I > have no way to tell whether the upgrade process checked the > integrity of the upgrade before rebooting. > > Given filesystem or flash corruption I should probably redo > everything with 1.2.3 final, using a fresh 4 GByte flash. > > How far from production is 2.0 meanwhile? I presume RC1 won't > come this year yet?
I have seen a similar problem when installing some packages. It seems to particularly dislike having system libraries overwritten underneath it. Installing the packages would cause the system to sig11 and lots of processes would die. The same task on a normal PC full install worked fine. In the end I ended up removing the system binaries from the .tgz files since they were already on the system and shouldn't have been overwritten anyhow, but I could see that being a problem when updating a full install. That's another advantage of the nanobsd methodology, the system slice is never overwritten, just the inactive alternate. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
