From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S263341AbTDGIry (for <rfc822;willy@w.ods.org>); Mon, 7 Apr 2003 04:47:54 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263343AbTDGIry (for <rfc822;linux-kernel-outgoing>); Mon, 7 Apr 2003 04:47:54 -0400
Received: from siaag2ab.compuserve.com ([149.174.40.132]:63631 "EHLO
	siaag2ab.compuserve.com") by vger.kernel.org with ESMTP
	id S263341AbTDGIrx (for <rfc822;linux-kernel@vger.kernel.org>); Mon, 7 Apr 2003 04:47:53 -0400
Date: Mon, 7 Apr 2003 04:55:27 -0400
From: Chuck Ebbert <76306.1226@compuserve.com>
Subject: Re: Wanted: a limit on kernel log buffer size
To: Robert Love <rml@tech9.net>, linux-kernel <linux-kernel@vger.kernel.org>
Message-ID: <200304070459_MC3-1-3358-A4AB@compuserve.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	 charset=us-ascii
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

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...)

--
 Chuck
 I am not a number!