Re: cross-buildworld from i386 to alpha b rked...

In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes: > >I tried "make buildworld TARGET_ARCH=alpha" and it croaked. Is this >expected breakage for a cross-build or genuine breakage ? >/flat/src/usr.sbin/pstat/pstat.c:546: `NLOCKED' undeclared (first use in this >fu >nction) It's genuine b

Re: df

In message <[EMAIL PROTECTED]>, Ian writes: >Actually, I now think a more-correct fix would be to have no if statement at >all, and just always recalculate the field widths after calling the routine >to re-get the stats. Yes, I agree. Committed, thanks! Ian To Unsubscribe: send mail to [EMAIL P

Re: df

In message <[EMAIL PROTECTED]>, Terry Lambert writes: >I think the reason for the "if" is to keep the df from hanging >indefinitely, particularly when you give it an explicit list. No, I believe the "if (vfslist != NULL)" code was there to reduce the maximum column widths to those necessary for a

Typo in uma_core.c causing panics after uma_zdestroy()

The logic for testing UMA_ZFLAG_INTERNAL in zone_dtor() is reversed. I was able to reliably reproduce crashes with: mdconfig -a -t malloc -s 10m mdconfig -d -u 0 mdconfig -a -t malloc -s 10m mdconfig -d -u 0 Ian Index: uma_core.c

<    1   2