Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758595AbYHGV0b (ORCPT ); Thu, 7 Aug 2008 17:26:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755816AbYHGV0S (ORCPT ); Thu, 7 Aug 2008 17:26:18 -0400 Received: from 166-70-238-42.ip.xmission.com ([166.70.238.42]:43917 "EHLO ns1.wolfmountaingroup.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753072AbYHGV0S (ORCPT ); Thu, 7 Aug 2008 17:26:18 -0400 Message-ID: <1166.69.2.248.210.1218143094.squirrel@webmail.wolfmountaingroup.com> In-Reply-To: <2832.69.2.248.210.1218142926.squirrel@webmail.wolfmountaingroup.com> References: <17494.166.70.238.46.1217784156.squirrel@webmail.wolfmountaingroup.com> <33030.166.70.238.45.1217948565.squirrel@webmail.wolfmountaingroup.com> <200808060133.10457.nickpiggin@yahoo.com.au> <44919.166.70.238.45.1217949560.squirrel@webmail.wolfmountaingroup.com> <48987A24.3060000@nortel.com> <2364.69.2.248.210.1217954354.squirrel@webmail.wolfmountaingroup.com> <2832.69.2.248.210.1218142926.squirrel@webmail.wolfmountaingroup.com> Date: Thu, 7 Aug 2008 15:04:54 -0600 (MDT) Subject: Re: [ANNOUNCE] Merkey's Kernel Debugger From: jmerkey@wolfmountaingroup.com To: jmerkey@wolfmountaingroup.com Cc: "Daniel Barkalow" , jmerkey@wolfmountaingroup.com, "Chris Friesen" , "Nick Piggin" , "Geert Uytterhoeven" , "Stefan Richter" , "Josh Boyer" , linux-kernel@vger.kernel.org User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1259 Lines: 39 >> On Tue, 5 Aug 2008, jmerkey@wolfmountaingroup.com wrote: >> >>> Read it already. Quite a few large companies are using it at present >>> and >>> have been since 2000, BTW. >> >> The criterion for kernel inclusion isn't really whether it works, >> however. >> It's whether other people would be able to understand it well enough to >> support it if you disappear (or if somebody else has changes that >> require >> changes to it). If it works well but isn't nice code, nobody really >> benefits from having it in the kernel distribution rather than external >> (like it's been for the past 8 years). If it is nice code (somewhat >> regardless of whether it happens to work right now), people can work on >> it >> and keep it in sync with the kernel as they change things. >> >> -Daniel >> *This .sig left intentionally blank* >> > > It both works and is nice code. But I may not be impartial. > > Jeff > > You activate it from the keyboard the same way as kdb -- pause/break or int X or exceptions. Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/