On Sun, Nov 28, 2010 at 1:26 AM, Peter Jeremy peterjer...@acm.org wrote:
Since all the boinc processes are running at i31, why are they impacting
a buildkernel that runs with 0 nicety?
Someone please enlighten me if I'm wrong, but I'll take a stab at it.
With the setup you presented you're
On 28/11/2010 01:24, Graham Menhennitt wrote:
Hi all,
I've found something that I think is a bug in ipfw. At the very least,
it contradicts the man page and a number of web sites. It's also
different behaviour from a few months ago.
I have a IPV6 tunnel connection to Hurricane Electric that I
At this moment I hiring a FreeBSD server running FreeBSD 7.2.
After running cvsup, updating sources and ports, compiling the complete
system, installing kernel and the new world, rebooting the system gives
the old sytem and not the freshly
compiled FreeBSD 7.4-PRERELASE.
What is wrong? Where
- Original Message -
From: Jack Raats j...@jarasoft.net
Subject: Old system keeps coming back
At this moment I hiring a FreeBSD server running FreeBSD 7.2.
After running cvsup, updating sources and ports, compiling the complete
system, installing kernel and the new world, rebooting
On Sun, Nov 28, 2010 at 03:04:31PM +0100, Jack Raats wrote:
- Original Message - From: Jack Raats j...@jarasoft.net
Subject: Old system keeps coming back
At this moment I hiring a FreeBSD server running FreeBSD 7.2.
After running cvsup, updating sources and ports, compiling the
Greetings.
I have cvs'd to the most current 7-stable source tree and have compiled
a kernel using these sources.
However, when I attempt to complete the buildworld process, I keep
getting failures in the below-listed areas.
Does anyone know of an issue with these sources? I see that this
Jack Raats j...@jarasoft.net writes:
- Original Message -
From: Jack Raats j...@jarasoft.net
Subject: Old system keeps coming back
At this moment I hiring a FreeBSD server running FreeBSD 7.2.
After running cvsup, updating sources and ports, compiling the complete
system,
TB --- 2010-11-28 14:27:52 - tinderbox 2.6 running on freebsd-legacy.sentex.ca
TB --- 2010-11-28 14:27:52 - starting RELENG_7 tinderbox run for amd64/amd64
TB --- 2010-11-28 14:27:52 - cleaning the object tree
TB --- 2010-11-28 14:28:13 - cvsupping the source tree
TB --- 2010-11-28 14:28:13 -
TB --- 2010-11-28 15:52:31 - tinderbox 2.6 running on freebsd-legacy.sentex.ca
TB --- 2010-11-28 15:52:31 - starting RELENG_7 tinderbox run for i386/i386
TB --- 2010-11-28 15:52:31 - cleaning the object tree
TB --- 2010-11-28 15:52:43 - cvsupping the source tree
TB --- 2010-11-28 15:52:43 -
TB --- 2010-11-28 16:26:12 - tinderbox 2.6 running on freebsd-legacy.sentex.ca
TB --- 2010-11-28 16:26:12 - starting RELENG_7 tinderbox run for i386/pc98
TB --- 2010-11-28 16:26:12 - cleaning the object tree
TB --- 2010-11-28 16:26:22 - cvsupping the source tree
TB --- 2010-11-28 16:26:22 -
Problem is watchdog timeouts with a Broadcom GigE interface on a Tyan
S4881 using 7.4-PRERELEASE as of 11/22 and 7.3-STABLE as of 11/11.
I've done the following, with no success:
(1) Tried the second port, bge1, in case the first had gone bad, and
(2) Recompiled samba34 (failure occurs when
On Sun, Nov 28, 2010 at 04:04:34PM -0500, Michael L. Squires wrote:
Problem is watchdog timeouts with a Broadcom GigE interface on a Tyan
S4881 using 7.4-PRERELEASE as of 11/22 and 7.3-STABLE as of 11/11.
I've done the following, with no success:
(1) Tried the second port, bge1, in case
12 matches
Mail list logo
