From owner-freebsd-current  Sat Sep  9 13:27:49 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA28041
          for current-outgoing; Sat, 9 Sep 1995 13:27:49 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA28033
          for <current@freebsd.org>; Sat, 9 Sep 1995 13:27:47 -0700
Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id NAA01250; Sat, 9 Sep 1995 13:26:39 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id NAA00222; Sat, 9 Sep 1995 13:28:50 -0700
Message-Id: <199509092028.NAA00222@corbin.Root.COM>
To: Julian Howard Stacey <jhs@vector.eikon.e-technik.tu-muenchen.de>
cc: current@freebsd.org
Subject: Re: SIGUSR 10 & 11 on kernel from src-cur.0965 
In-reply-to: Your message of "Sat, 09 Sep 95 18:56:04 +0200."
             <199509091656.SAA00513@vector.eikon.e-technik.tu-muenchen.de> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sat, 09 Sep 1995 13:28:49 -0700
Sender: current-owner@freebsd.org
Precedence: bulk

>My 24x80 style tty login is still getting SIGUSR 10 & 11 on a kernel from
>the 69K src-cur.0965.gz (latest i've got)

   This is another reminder to people: There were changes that were made to
-current in the area of the VOP/VFS layering. This REQUIRES that all of your
LKMs be rebuilt or else you WILL have sig 10/11/?? and panics caused by this.
Also, the sources for SUP/CTM weren't automatically updated until just very
recently - the cron entry was missing after freefall's upgrade. PLEASE re-SUP
and/or whatever CTM people do and make sure that your source tree is up to
date.

-DG