From owner-freebsd-stable Thu Dec 5 14:22:36 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6844C37B401 for ; Thu, 5 Dec 2002 14:22:34 -0800 (PST) Received: from fubar.adept.org (fubar.adept.org [63.147.172.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12B4343EC2 for ; Thu, 5 Dec 2002 14:22:34 -0800 (PST) (envelope-from mike@adept.org) Received: by fubar.adept.org (Postfix, from userid 1001) id 266F715247; Thu, 5 Dec 2002 14:19:54 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by fubar.adept.org (Postfix) with ESMTP id 2599815213 for ; Thu, 5 Dec 2002 14:19:54 -0800 (PST) Date: Thu, 5 Dec 2002 14:19:54 -0800 (PST) From: Mike Hoskins To: freebsd-stable@freebsd.org Subject: Re: Problems with make buildkernel In-Reply-To: <000f01c29c84$a3b21b90$0300a8c0@HYRULE> Message-ID: <20021205140237.H96241-100000@fubar.adept.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 5 Dec 2002, Scott Anderson wrote: > I habitually strip my kernel. I know that config works, because a buddy of > mine used the exact same config on his box and it worked fine. My cvsupfile > does include the crypto stuff too. I have a /usr/src/crypto folder. I'm > just thinking about putting Debian GNU/Linux 3.0 on the box :( If you can't figure out how to configure a BSD kernel, go with Red Hat or Windows XP. Nothing personal, but I doubt Debian's for you either. That said, I have many boxes with many kernels... What works on one does not necessarily work on the other. You say you "habitually strip [your] kernel" -- does that mean you've built this kernel or others before? If so, you must ask what you are doing differently now... If you can verify that you are in fact not doing things differently from a time when the _current_ config worked on the _current_ system, then it is time to provide some additional debug information. Statements like "I know that config works because it worked on another box" does not make it sound like you know what you're talking about. That's not a bad thing, since we all have a lot to learn, but does imply you should spend some time reading LINT and building a local kernel config file _specific to your machine_ that you fully understand. As suggested, the typical procedure is to cd /sys/i386/conf, cp GENERIC YOURKERNEL, vi LINT in a terminal, vi YOURKERNEL in another terminal, read LINT from top to bottom figuring out what you do or don't need, then comment/add/edit what you don't need in YOURKERNEL... So you essentially end up with a copy of GENERIC with a lot of comments. That makes it easy for people to see what you've changed, etc. Just commenting an option will "strip" it from the resultant binary kernel, so having comments around isn't a "bad thing" unless, perhaps, you're storing a very large config in the kernel and have very few resources. If you have additional questions about building a kernel, the handbook has specific examples. If you are beyond that point, and your kernel just won't build after verifying options against LINT, your local system, etc... Cvsuping again (after some amount of time so changes can actually be committed if something was in a "half-way" state during your initial checkout), watching the checkout and attempting to verify if the observed checkouts relate to where you see "breakage" is a good way to figure out what step to take next. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message