Re: FreeBSD 10 and zfsd

2013-12-19 Thread asomers
On Wed, Dec 18, 2013 at 2:40 PM, Outback Dingo wrote: > > > > On Wed, Dec 18, 2013 at 4:40 PM, Alan Somers wrote: >> >> On Wed, Dec 18, 2013 at 11:47 AM, Outback Dingo >> wrote: >> > >> > >> > On Wed, Dec 18, 2013 at 12:39 PM, Mark Felder wrote: >> >> >> >> On Thu, Oct 10, 2013, at 11:26, Alan

Re: Read-triggered corruption of swap backed MD devices

2013-05-24 Thread asomers
Fast work, Konstantin! This looks like it may be the solution to an intermittent and inexplicable bug we've been seeing that we feared may be data corruption in ZFS. On Fri, May 24, 2013 at 2:53 AM, Konstantin Belousov wrote: > On Fri, May 24, 2013 at 12:19:44PM +1000, Lawrence Stewart wrote: >>

Re: Can't compile lxpanel

2013-06-06 Thread asomers
Looks like a bug upstream. If this port worked in FreeBSD-9, then the difference might be the switch from gcc to clang. You could try compiling the port with gcc. Just add these lines to /etc/make.conf CC=gcc CXX=g++ CPP=gcpp Note: that will change the compiler used for ALL ports, as well as k

Re: CURRENT fails to build: usr/src/sbin/devd/devd.cc:1125:2: error: use of undeclared identifier 'va_end' va_end(argp);

2013-07-02 Thread asomers
And yet it's not producing any tinderbox errors. Perhaps stdarg.h is getting implicitly included by some other header in CURRENT, but not in whatever version of the code you have? For now, you can #include and I'll fix it when I get to the office this morning. On Tue, Jul 2, 2013 at 3:56 AM, O.