From owner-freebsd-current@FreeBSD.ORG Thu Jun 30 00:43:01 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4371316A41C for ; Thu, 30 Jun 2005 00:43:01 +0000 (GMT) (envelope-from rsh.lists@comcast.net) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [204.127.202.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0500643D48 for ; Thu, 30 Jun 2005 00:43:00 +0000 (GMT) (envelope-from rsh.lists@comcast.net) Received: from [192.168.1.11] (tardiss.hsd1.ma.comcast.net[66.30.82.93]) by comcast.net (sccrmhc14) with ESMTP id <20050630004300014004i0ele>; Thu, 30 Jun 2005 00:43:00 +0000 Message-ID: <42C34012.9060208@comcast.net> Date: Wed, 29 Jun 2005 20:42:58 -0400 From: Sean User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050330) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adam K Kirchhoff References: <42C098B0.5060004@voicenet.com> <42C119FE.7020809@comcast.net> <42C1381B.9000901@voicenet.com> <42C31D30.3000009@comcast.net> <42C3266A.3000901@voicenet.com> In-Reply-To: <42C3266A.3000901@voicenet.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Portupgrade, -CURRENT & SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rsh.lists@comcast.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 00:43:01 -0000 Adam K Kirchhoff wrote: > > > I think you mean '...we have to rebuild the kernel to go UP, > portupgrade..." > > Which, yes, is quite annoying and, IMHO, is a pretty critical bug that > needs fixing. It makes SMP on -CURRENT nearly unusable if you want to > regularly update your ports. > > Adam > > That was what I meant. Oh well. I looked at your problem report earlier today. If I recall your are running i386, I am amd64, so at least the problem does not discriminate. Sean