From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263503AbTDGQOr (for ); Mon, 7 Apr 2003 12:14:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263520AbTDGQOr (for ); Mon, 7 Apr 2003 12:14:47 -0400 Received: from air-2.osdl.org ([65.172.181.6]:9702 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S263503AbTDGQOp (for ); Mon, 7 Apr 2003 12:14:45 -0400 Date: Mon, 7 Apr 2003 09:24:10 -0700 From: "Randy.Dunlap" To: Chuck Ebbert <76306.1226@compuserve.com> Cc: rml@tech9.net, linux-kernel@vger.kernel.org Subject: Re: Wanted: a limit on kernel log buffer size Message-Id: <20030407092410.33ecddc1.rddunlap@osdl.org> In-Reply-To: <200304070459_MC3-1-3358-A4AB@compuserve.com> References: <200304070459_MC3-1-3358-A4AB@compuserve.com> Organization: OSDL X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 7 Apr 2003 04:55:27 -0400 Chuck Ebbert <76306.1226@compuserve.com> wrote: | Robert Love | | > I say if users cannot bother to read the documentation | >and understanding things, why are they compiling a kernel? | | | True, but then they'll come bleating to l-k when all they get is | a blank, black screen on boot. (At least _I_ figured out what | went wrong first...) Good that you figured it out. Just how far does boot get? What messages are printed before death? -- ~Randy