From owner-freebsd-current@FreeBSD.ORG Thu Aug 12 01:41:31 2004 Return-Path: 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 2730016A4CE; Thu, 12 Aug 2004 01:41:31 +0000 (GMT) Received: from lakermmtao06.cox.net (lakermmtao06.cox.net [68.230.240.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9468043D53; Thu, 12 Aug 2004 01:41:30 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao06.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040812014128.EFUA8791.lakermmtao06.cox.net@dolphin.local.net>; Wed, 11 Aug 2004 21:41:28 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id i7C1fTuc019706; Wed, 11 Aug 2004 20:41:29 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.13.1/8.13.1/Submit) id i7C1fOD4019705; Wed, 11 Aug 2004 20:41:24 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 11 Aug 2004 20:41:24 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: "Conrad J. Sabatier" cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: cvsup on amd64 just broke today X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.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, 12 Aug 2004 01:41:31 -0000 On 10-Aug-2004 Conrad J. Sabatier wrote: > > I hadn't noticed it before, but it does strike me as odd that the > binary package for amd64 would include a file with "i386" in the > name, and which is, in fact, an ELF 32 binary. Did something change > today that would effect the handling of such a file, perhaps? Just realized today while doing another system update that I had somehow deleted "options IA32" from my kernel config. Probably why cvsup suddenly stopped working. :-) My bad. -- Conrad J. Sabatier -- "In Unix veritas"