From owner-freebsd-smp Mon Feb 14 12:44:30 2000 Delivered-To: freebsd-smp@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by builder.freebsd.org (Postfix) with ESMTP id 96C663F4D for ; Mon, 14 Feb 2000 12:44:28 -0800 (PST) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA48374; Mon, 14 Feb 2000 12:43:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: sthaug@nethelp.no Cc: marc@oldserver.demon.nl, diskiller@cnbinc.com, neil@synthcom.com, freebsd-smp@FreeBSD.ORG Subject: Re: 4.0 SMP Problem? In-reply-to: Your message of "Mon, 14 Feb 2000 18:42:18 +0100." <28104.950550138@verdi.nethelp.no> Date: Mon, 14 Feb 2000 12:43:09 -0800 Message-ID: <48371.950560989@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have to echo these sentiments; I've been running softupdates on my SMP box and building frequent releases on it, among other disk-intensive exercises, and it works flawlessly. Has for months, in fact, despite known-bugs getting fixed in soft updates during that time. - Jordan > > > SMP alone, and softupdate alone, and everything else, is broken on 4.0. > > > I cvsup'd a few days ago, so it was a recent current. > > > > I don't know about softupdates, which I do not use. SMP alone is *not* > > broken on 4.0. It never was, not even during the recent (x)install > > and lib problems. > > I'm using SMP *and* softupdates on a system here. It survives multiple > buildworlds just fine - so I'd say things are working pretty well. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message