From owner-freebsd-questions Sun Nov 3 18:44:37 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA00466 for questions-outgoing; Sun, 3 Nov 1996 18:44:37 -0800 (PST) Received: from Rigel.orionsys.com (root@rigel.orionsys.com [205.148.224.9]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA00415; Sun, 3 Nov 1996 18:44:21 -0800 (PST) Received: from localhost (dbabler@localhost) by Rigel.orionsys.com (8.7.6/8.6.9) with SMTP id SAA00256; Sun, 3 Nov 1996 18:44:12 -0800 (PST) Date: Sun, 3 Nov 1996 18:44:12 -0800 (PST) From: Dave Babler To: "Jordan K. Hubbard" cc: questions@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: Kernel tty problem In-Reply-To: <7208.847061472@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 3 Nov 1996, Jordan K. Hubbard wrote: > > I'm running 2.1.5-STABLE here; originally made from the CD-ROM sources. > > I'm using CTM, subscribed to the -STABLE branch. Everything was running > > just fine until I decided to recompile the kernel to add ipfw. After > > You have to have spammed something in your kernel config file, there's > no other practical explanation. > > Start again with the GENERIC file. If it works, carefully turn it > into something more closely approximating your file, one line at a > time, until it stops working. Done, you know now that the line you > just removed should have stayed. :-) > > If GENERIC doesn't work then talk to us again because you've found a > real problem. > Thank you for getting back to me. I started over with GENERIC and recreated my custom kernel config file... with one minor exception: my previous version, I'd been paring down things I didn't think I needed and optimizing. One of the options I took out was COMPAT_43. The new version from scratch includes it and it all works. I was under the impression that COMPAT_43 was only required for *some* older programs... apparently that was what was breaking quite a few of them, however. I suppose it could also be some of the things added to GENERIC since the 2.1.5 release, but at this point, COMPAT_43 seems to be the culprit. -Dave