From owner-freebsd-hackers Tue Dec 9 18:50:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA04480 for hackers-outgoing; Tue, 9 Dec 1997 18:50:57 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from acroal.com (firewall0.acroal.com [209.24.61.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA04470 for ; Tue, 9 Dec 1997 18:50:47 -0800 (PST) (envelope-from jamil@acroal.com) Received: from localhost (jamil@localhost) by acroal.com (8.8.8/8.8.7) with SMTP id SAA15133; Tue, 9 Dec 1997 18:48:04 -0800 (PST) (envelope-from jamil@acroal.com) Date: Tue, 9 Dec 1997 18:48:04 -0800 (PST) From: "J. Weatherbee - Senior Systems Architect" To: David Kelly cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Why so many steps to build new kernel? In-Reply-To: <199712100124.TAA26461@nospam.hiwaay.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On this topic. I don't care for Linux (Too Unreliable), but theyv'e had a curses based configuration tool as part of the sources since v 2.0. It is kind of nice since it lets you choose what hardware support you want to compile in and even some port variables etc. > As for the config step, it could be worse, it could be Linux. :-) > Actually its been so long since I built a Linux kernel that I forgot how > it was done. Hasn't been long enough for me to forget that one *had* to > build a custom Linux kernel in order to get a functional mix of the > right device drivers for your system. Hopefully (for Linux) that has > changed by now.