2.0.3 Image Testing
-
I am currently using the nanobsd 2.0.2 4G version. Can I use the upgrade file to only update one of the two slices?
-
I am currently using the nanobsd 2.0.2 4G version. Can I use the upgrade file to only update one of the two slices?
Update files only update one NanoBSD slice. That's how they've always worked. You can boot back to the other slice if needed.
-
great, I didn't know that. Not a whole lot of commits to the 2.0 release branch for some time now.
when I install a prerelease - how would i update to 2.0.3 once it's released? would I have to reinstall? Thx -
Regular firmware update like any other. If your auto update url is pointed to the 'stable' updates, you'll get it when it's released.
-
I've updated! The only issue for me was a long delay at boottime because my packages didn't reinstall. Or did they? Directly after the update i accidently loaded my old slice and all my packages got reinstalled into that one. Then, next reboot, i booted into the "new" slice and the firewall took ages to load and all packages were missing. I manually the packages and all is good now. It seems strange though that the package update was triggered when I was booting the old slice (I have updated running from slice number two, maybe thats related).
just to clarify, here are my messy upgrade steps:
i was running slice 2 when i started the update.
on reboot i chose to boot slice 2 ouch* and it reinstalled all packages
reboot into slice1: no packages -
FWIW, I upgraded to the latest image (13 Feb 1243), but I'm still having the problem that I initially reported here:
http://forum.pfsense.org/index.php/topic,57258.0.html
That thread eventually got hijacked to be a different issue (but also related to DHCP), but the original problem still remains. This is a regression since pfsense 2.0.1.
-
That thread didn't get hijacked, it was the main issue. The interface going down/up wasn't properly relaunching dhclient, and that should be fixed now. Several others with that same issue confirmed it was fixed for them. If there is a separate issue, then you can keep posting in that thread to continue investigating, or start a new one. The symptoms will be (at least slightly) different now, and it warrants further diagnosis.
-
php: /system_advanced_sysctl.php: The command '/sbin/sysctl hw.syscons.kbd_reboot="0"' returned exit code '1', the output was 'sysctl: unknown oid 'hw.syscons.kbd_reboot''
smallish glitch in current 2.0.3 pre. That variable is gone I guess?
-
That tunable is only valid on a full install w/vga, or nano+vga
It wouldn't be present on an embedded kernel or regular nanobsd.
-
Proxy Squid: Realtime stat (sqstat) doesn't auto refresh.
-
Packages are not relevant to 2.0.x image testing. That would be a subject for the packages board.
-
Planning to upgrade from 2.0.1 to try and improve MTU control on PPP.
Is it worth going to 2.0.2 or straight to 2.0.3? I guess second question is how close is 2.0.3 to being finalized - days/weeks/months?
Thanks
-
2.0.3 is better than 2.0.2 at the moment.
It would be out already, but we're waiting on FreeBSD to release a security announcement on OpenSSL that we need to account for. -
2.0.3 is better than 2.0.2 at the moment.
It would be out already, but we're waiting on FreeBSD to release a security announcement on OpenSSL that we need to account for.You guys ROCK!
-
What happened to the 2.0.3 download folders? Nothing there anymore.
-
Snapshot pruning probably caught them, I hadn't made a new one in a week. I'll run another off, check back late tonight.
-
I'm currently running this (below) version, would it be useful to grab the new snapshot you are creating tonight?
2.0.3-PRERELEASE (amd64) built on Wed Feb 13 12:44:38 EST 2013 FreeBSD 8.1-RELEASE-p13 -
There are some minor, but beneficial fixes. May as well get it. We're still in a holding pattern waiting on FreeBSD to release the OpenSSL SA, but we've found a couple little things here and there.
-
Any estimated time given by FreeBSD on the OpenSSL SA release?
-
None that I've seen. Last I saw was this on Feb 7 saying that the patches are in review… http://lists.freebsd.org/pipermail/freebsd-security/2013-February/006945.html
