From owner-freebsd-questions Mon Apr 12 11:58:49 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 1001C15618 for ; Mon, 12 Apr 1999 11:58:42 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA05150; Mon, 12 Apr 1999 11:56:21 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 12 Apr 1999 11:56:20 -0700 (PDT) From: Doug White To: "Ben J. Cohen" Cc: questions@FreeBSD.ORG Subject: Re: Two questions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Apr 1999, Ben J. Cohen wrote: > I have two questions which should be straightforward to answer but I > couldn't find them in the mailing lists, etc. > > Firstly, when using some applications, particularly vi, in an xterm under > X the numeric keypad produces garbage like > y > x > w > v > u > this when I try to use it to get numbers. You _do_ have NumLock on, right? I've not had this problem since the 2.1.X days. > I have > > # Let the server do the NumLock processing. This should only be required > # when using pre-R6 clients > ServerNumLock > > in XF86Config. (This is necessary to make other applications work > properly.) > > Is there any way to stop this from happening? Take that directive out; it makes NumLock do nutty things. > Secondly, kernel messages go to the console. Is there any way of > redirecting the console to, say, /dev/ttyv2 so that when I log in on ttyv0 > I don't get lots of messages appearing on the screen? No, since /dev/console is glued to that vty. Just use a different vty; we do here. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message