From owner-freebsd-current  Fri Mar  8 04:27:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id DAA01338
          for current-outgoing; Fri, 8 Mar 1996 03:18:20 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [192.216.222.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA01289
          for <current@FreeBSD.ORG>; Fri, 8 Mar 1996 03:18:08 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by who.cdrom.com (8.6.12/8.6.11) with ESMTP id XAA22194
          for <current@freebsd.org>; Thu, 7 Mar 1996 23:22:49 -0800
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id XAA16814; Thu, 7 Mar 1996 23:22:35 -0800 (PST)
To: Ken Lam <klam@awod.com>
cc: current@FreeBSD.ORG
Subject: Re: New kernel option proposed.. 
In-reply-to: Your message of "Thu, 07 Mar 1996 22:24:38 EST."
             <1.5.4b11.32.19960308032438.006be60c@awod.com> 
Date: Thu, 07 Mar 1996 23:22:35 -0800
Message-ID: <16812.826269755@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: owner-current@FreeBSD.ORG
Precedence: bulk

> Hmmm.. seems more obvious, but then won't that kind of mean that we 
> can't say RTFM?  After all, the standard 4.4bsd manuals, Unix System 
> Administrator Handbook, etc.. all refer to GENERIC in their kernel 
> configuration sections.  

I'm not proposing to remove the generic kernel, simply the magic
meaning of the keyword "GENERIC" in our kernel sources.  What if you
wanted to compile a non-GENERIC kernel with safety belts still intact?

						Jordan