From owner-freebsd-current Sat Jun 15 13:39:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA15024 for current-outgoing; Sat, 15 Jun 1996 13:39:00 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA15013 for ; Sat, 15 Jun 1996 13:38:54 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id OAA25158; Sat, 15 Jun 1996 14:35:07 -0600 Date: Sat, 15 Jun 1996 14:35:07 -0600 From: Nate Williams Message-Id: <199606152035.OAA25158@rocky.sri.MT.net> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: ktrace [Was: 2.2-960612-SNAP resolver problems] In-Reply-To: <199606152005.WAA20827@uriah.heep.sax.de> References: <199606151633.KAA24752@rocky.sri.MT.net> <199606152005.WAA20827@uriah.heep.sax.de> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > I wonder whether we should turn on ktrace by default. > > > > Earlier on, people were having problems that were solved by removing > > KTRACE from their config file. > > Except of a recent brokeness in -current (that only affected people > actually using it), i cannot remember such problems. I used to have > it in my config file for several months if not years now. Actually, it affected people *NOT* using it. Even if you didn't use ktrace things were broken because of it. > gzip used to be absolutely broken for quite a longer period of time, > and nobody complained that it was still in the GENERIC config file. :) That's because it was required in GENERIC for the install utils. > Does anybody seriously object against putting it into GENERIC? Yes. It's un-necessary bloat that 95% of the users don't know how to use and the other 5% know how to add it. Nate