From owner-freebsd-questions Tue Jul 8 16:11:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA15238 for questions-outgoing; Tue, 8 Jul 1997 16:11:00 -0700 (PDT) Received: from train.tgci.com (train.tgci.com [205.185.169.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA15213 for ; Tue, 8 Jul 1997 16:10:45 -0700 (PDT) Received: from belana (belana.tgci.com [205.185.169.100]) by train.tgci.com (8.6.12/8.6.9) with SMTP id QAA14509; Tue, 8 Jul 1997 16:16:51 -0700 Message-Id: <199707082316.QAA14509@train.tgci.com> Comments: Authenticated sender is From: "Riley J. McIntire" To: dmaddox@scsn.net (Donald J. Maddox) Date: Tue, 8 Jul 1997 16:18:38 +0000 Subject: Re: (Fwd) garbage from syslogd after compiling new kernel Reply-to: chaos@tgci.com CC: freebsd-questions@FreeBSD.ORG Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Riley J. McIntire wrote: > > > > Hi, > > > > Could the disabling KTRACE cause the syslog output I got below? snip > > \^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[2;1H\^[[m\^[[7m\^[[m\ > wdc0: > > disabled, not probed. > ccd0-3: Concatenated disk drivers > > This looks like the kind of stuff (cursor control sequences, etc.) > that > doing a visual userconfig might leave in your logs... > That's most likely it--I used it right after rebuilding this kernel. I was kinda concerned about disabling KTRACE but couldn't find a reason not to. Is there any reason to enable it for "normal" use? It *is* enable by default, as are a number off other required "options". Thanks for you help, Riley