From owner-freebsd-hackers  Mon Apr 28 22:47:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id WAA27188
          for hackers-outgoing; Mon, 28 Apr 1997 22:47:44 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA27182
          for <freebsd-hackers@FreeBSD.org>; Mon, 28 Apr 1997 22:47:42 -0700 (PDT)
Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA05306; Mon, 28 Apr 1997 22:47:50 -0700 (PDT)
To: Simon Shapiro <Shimon@i-Connect.Net>
cc: Julian Elischer <julian@whistle.com>, freebsd-hackers@FreeBSD.org
Subject: Re: A Desparate Plea for Help... 
In-reply-to: Your message of "Mon, 28 Apr 1997 18:44:43 PDT."
             <XFMail.970428191646.Shimon@i-Connect.Net> 
Date: Mon, 28 Apr 1997 22:47:50 -0700
Message-ID: <5304.862292870@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> BTW, I have disabled ALL LKM's in the system and it appears to hold
> together!

<USUAL-OBLIGATORY-POINT TRIGGERED-BY="LKM-KEYWORD">
If your installed LKMs are not in sync with your kernel, e.g. you're
actively using LKMs and you haven't gone into /usr/src/lkm and done a
"make depend all install" to correspond to the kernel you just
config'd, built and installed, well, then you're taking your life into
your own hands and you should, at the minimum, probably be spanked.

Various schemes, ranging from the semi-sane to the outright crackpot,
have been advanced for adding LKM versioning and fancy dependency
checking but nothing workable (and inoffensive to the smell) has been
implemented yet, so, for now this is what you have to do.  Again:
MAKE SURE YOUR LKMS ARE IN SYNC WITH YOUR KERNEL!

Thank you.
</USUAL-OBLIGATORY-POINT>

In this particular case, however, I think I blame the OSS LKM
specifically and if the linux & screen saver lkms are sure to be in
sync with their kernel then they can probably be brought back safely.

I should also point out that if this turns out to be an instance of
someone using a driver which is *openly acknowledged to be BETA
software* on a production machine, and crashing that machine from said
use, then I shall most definitely recommend that this particular
someone do at least 10 hours of penance in recompense, perhaps by
helping out at the local homeless shelter or giving blood.
Foolishness of such magnitude demands some form of restitution. ;-)

					Jordan