From owner-freebsd-smp Tue Jun 20 12:36:12 2000 Delivered-To: freebsd-smp@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id C707437BC13 for ; Tue, 20 Jun 2000 12:36:06 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA55238; Tue, 20 Jun 2000 21:34:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Cc: Warner Losh , mjacob@feral.com, Matthew Dillon , freebsd-smp@FreeBSD.ORG Subject: Re: SMP discussion moving to freebsd-smp In-reply-to: Your message of "Tue, 20 Jun 2000 21:30:04 +0200." <55142.961529404@critter.freebsd.dk> Date: Tue, 20 Jun 2000 21:34:51 +0200 Message-ID: <55236.961529691@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <55142.961529404@critter.freebsd.dk>, Poul-Henning Kamp writes: >I don't agree with your rather rabid "current must always work" >attitude, having been one of the primary people through the >1.0 to 2.0 transition I know how many developers that cost us. Damn, sign bug! Should have read: I don't agree with your rather rabid "current must always work" attitude, but having been one of the primary people through the 1.0 to 2.0 transition I know how many developers the opposite cost us. The meaning here is: No, it can't be basically useless for months on end, but yes, it may be dead for days or maybe even a week. I think I will agree that requiring UP to compile and work (for the regular -current definition of "work") for at leat 80-90% of the days is not an unreasonable requirement. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message