From owner-freebsd-questions Sun Oct 20 18:45:45 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA10333 for questions-outgoing; Sun, 20 Oct 1996 18:45:45 -0700 (PDT) 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 SAA10328 for ; Sun, 20 Oct 1996 18:45:42 -0700 (PDT) Received: from localhost (dbabler@localhost) by Rigel.orionsys.com (8.7.6/8.6.9) with SMTP id SAA00231 for ; Sun, 20 Oct 1996 18:45:40 -0700 (PDT) Date: Sun, 20 Oct 1996 18:45:40 -0700 (PDT) From: Dave Babler Reply-To: Dave Babler To: questions@freebsd.org Subject: New kernel build weirdness Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just hasn't been my weekend. I'm running 2.1.5-STABLE and have been keeping up with the source changes using CTM. I've been running tc_wrappers for months and decided to rebuild the kernel to incorporate all the CTM changes and add ipfw. The only modification to my existing kernel configuration I did was to add option IPFIREWALL and IPFIREWALL_VERBOSE. After compiling, installing and rebooting, I started noticing some small and not-so-small problems. 1. the login from the console device now prints the user-ID following the prompt, such as: login: cosmo cosmo password: 2. Suddenly, cons25 doesn't understand control keys. In pine, for instance, arrow keys produce the equivalent ansi sequence printed to the screen and ^X (and others) are printed instead of being interpreted as control keys. Booting the old kernel works as it always has. Could I have screwed up the CTM updating process somehow, or missed compiling something that would do this? Any ideas where to start looking? -Dave