Re: pfsync between 8.4 and 9.2
Warning: I don't know internals, I'm just a user. but one who reads the doucmebtation closer than I do apparently :-) According to pf(4), FreeBSD 9.2 matches OpenBSD 4.5. Specifically, pfsync(4) says: The pfsync protocol and kernel implementation were significantly modified between OpenBSD 4.4 and OpenBSD 4.5. The two protocols are incompatible and will not interoperate. So I think your experience was predictable, more or less :-) Maybe the information deserves a more prominent place than a man page. The detailed release notes of 9.0 did mention the upgrade pf but not consequences of pfsync. Thankyou! This completely passed me by. I will go ahead and upgrade the other machine today in that case, as it should then all work fine. Thanks very much for pointing this out, as it was worrying me somewhat! cheers, -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Clock not ticking during S3
On Tue, 1 Oct 2013 13:12:38 +0200, Dominic Fandrey wrote: The following is in my ntpd log. ... 27 Sep 23:06:40 ntpd[3045]: Listening on interface #67 wlan0, fe80::21c:bfff:fe58:3a87#123 Enabled 27 Sep 23:06:49 ntpd[3045]: Listening on interface #68 wlan0, 172.17.2.154#123 Enabled The system is sent to S3 at this point and woken 4 days later. This is how it comes up: 27 Sep 23:07:03 ntpd[3045]: no servers reachable 27 Sep 23:19:54 ntpd[3045]: synchronized to 83.170.1.225, stratum 2 27 Sep 23:19:54 ntpd[3045]: time correction of 306709 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time. Roughly 3 and a half days of time missing. I've never seen anything like it before. This is my system. FreeBSD mobileKamikaze.norad 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254957: Tue Aug 27 19:07:40 CEST 2013 root@mobileKamikaze.norad:/usr/obj/HP6510b-9/amd64/usr/src/sys/HP6510b-9 amd64 My 9.1 system is (physically) broken at the moment so I only have 8.2 sources to hand, but in any case it looks like the RTC - the only source of clock time available on resume, at least on i386 - was either stopped on suspend when the RTC was updated from system time, or - perhaps more likely? - couldn't be properly read back to restore time on resume. Is there logging of this suspend and resume cycle in /var/log/meesages ? ccing Alexander, resident master of clocks last time I tried following RTC suspend/resume with a view to maybe implementing resume-on-alarm. cheers, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: pfsync between 8.4 and 9.2
Just to follow this up for anyuone finding the thread, after upgrading the other firewall to 9.2 as well, pfsync works fine agai. The failover actually seems a lot faster in fact, so it looks like a big improvements. thanks, -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 9.2-PRE: switch off that stupid Nakatomi Socrates
According to Ullrich Franke on Tue, Oct 01, 2013 at 05:01:00PM +0200: We really should have a /bin/bikeshed. :-) /usr/bin/bikesched (now it begins anew :) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.net In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 9.2-PRE: switch off that stupid Nakatomi Socrates
On Wed, Oct 2, 2013 at 8:22 AM, Ollivier Robert robe...@keltia.freenix.frwrote: According to Ullrich Franke on Tue, Oct 01, 2013 at 05:01:00PM +0200: We really should have a /bin/bikeshed. :-) /usr/bin/bikesched Would schedulers get their own binary? Wouldn't it just be compiled into the kernel? Or are you proposing a modular scheduler using the bike algorithm? ;) -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ports binary upgrade question for 9.2
You don't have to recompile all ports when switching to a new _minor_ version. Minor versions are binary compatible. So in this case you don't have to do anything. Thanks for answer! I'm aware of compatibility. However, I'd like to have it all fresh, especially for luakit. I cannot find the server, to put the name in conf file for pkg. Txz packages are probably not ready yet. Further, reading manual, I assume portmaster to be happy to upgrade binary. I used it to install ports, recompiling it, due the lack of bin files for 9.1. -P should recompile only if it cannot find binary file. -PP would avoid any compiling whatever happens. To my understanding. Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Upgrade 9.1 - 9.2 Invalid format / BTX halted
Hi, I tried to upgrade one of my servers from FreeBSD 9.1 to 9.2 with freebsd-update upgrade -r 9.2-RELEASE after the first reboot the system hangs on boot with Invalid format ... BTX halted It's a Supermicro X9SCL-F mainboard. I upgraded FreeBSD from 9.0 to 9.1 REL sucessfull, when 9.1 was released. What happend with the upgrade to 9.2? Here is the screenshot http://212.78.99.130/btx.jpg Thanks for any help. Regards, Thomas. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
