From owner-freebsd-questions@FreeBSD.ORG Sat Dec 16 01:18:23 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1D22316A403 for ; Sat, 16 Dec 2006 01:18:23 +0000 (UTC) (envelope-from ranger@oldpathsbaptistchurch.org) Received: from trinity.vnet-inc.com (matrix.vnet-inc.com [216.129.224.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F8C743C9D for ; Sat, 16 Dec 2006 01:16:38 +0000 (GMT) (envelope-from ranger@oldpathsbaptistchurch.org) Received: from localhost (localhost.vnet-inc.com [127.0.0.1]) by trinity.vnet-inc.com (Postfix) with ESMTP id 365A35A43F64 for ; Fri, 15 Dec 2006 18:18:11 -0700 (MST) Received: from trinity.vnet-inc.com ([127.0.0.1]) by localhost (matrix.vnet-inc.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59360-04 for ; Fri, 15 Dec 2006 18:18:11 -0700 (MST) Received: from [192.168.139.205] (unknown [65.19.244.43]) by trinity.vnet-inc.com (Postfix) with ESMTP id CB2DD5A43C1D for ; Fri, 15 Dec 2006 18:18:10 -0700 (MST) From: Old Ranger Organization: OPBC To: freebsd-questions@freebsd.org Date: Fri, 15 Dec 2006 18:18:08 -0700 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612151818.08425.ranger@oldpathsbaptistchurch.org> X-Virus-Scanned: by amavisd-new at vnet-inc.com Subject: Re: cvsup and amd64 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Dec 2006 01:18:23 -0000 On Friday 15 December 2006 18:04, Schmehl, Paul L wrote: > Please tell me, did I need to specify anything specifically about the amd64 > architecture when running cvsup? Did I possibly get a GENERIC kernel file > through cvsup that is not compatible with amd? > > ********************************************************************** > > Sorry for the horrible formatting, but for reasons beyond my control, I > only have access to Microsoft Outlook right now. It appears no one has > answered you yet, so, to alleviate your fears, yes, unless you've changed > the kernel in any way (and it sounds like you haven't), a simple make > buildkernel and make installkernel should work just fine. Reboot > afterwards, and you should be running the new kernel. The only reason you > would *need* to make a change would be if you're running dual processors or > you need to customize the kernel for performance reasons. Otherwise the > GENERIC kernel will suffice. > > Paul Schmehl (pauls@utdallas.edu) > Senior Information Security Analyst > University of Texas at Dallas > http://www.utdallas.edu/ir/security/ **** Thank you! Somehow, I got through it today, with SMP working too! I had a little problem with mergemaster, after buildworld, which had a couple of problems that I got around with the make -k argument. Some things didn't get built. Mergemaster rejected some files - /var/tmp/temproot/etc/rc.d/jail /var/tmp/temproot/etc/ssh/ssh_config /var/tmp/temproot/etc/ssh/sshd.config /var/tmp/temproot/etc/motd I elected to "merge by hand", just to coplete the process. Now I'll have to learn what it means to "merge by hand." Thanks to all who responded with advice and insights. I have now a working amd64x2 kernel and a partially built, installed, and merged world. There are still some strange messages appearing at boot time. That's for another day. Z. Wade Hampton Twin Bridges, Montana