From owner-freebsd-current  Sat Sep  9 13:48:23 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA29211
          for current-outgoing; Sat, 9 Sep 1995 13:48:23 -0700
Received: (from dyson@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA29202
          ; Sat, 9 Sep 1995 13:48:21 -0700
From: John Dyson <dyson>
Message-Id: <199509092048.NAA29202@freefall.freebsd.org>
Subject: Re: SIGUSR 10 & 11 on kernel from src-cur.0965
To: davidg@Root.COM
Date: Sat, 9 Sep 1995 13:48:21 -0700 (PDT)
Cc: jhs@vector.eikon.e-technik.tu-muenchen.de, current@freebsd.org
In-Reply-To: <199509092028.NAA00222@corbin.Root.COM> from "David Greenman" at Sep 9, 95 01:28:49 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 856       
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
> 
You are all going to be very unhappy with me :-(, but I am going to have
to change the VOP_GETPAGES/VOP_GETPAGES interface one more time.  I'll
make all kinds of noises when it happens (I am sure that others will
too :-)).

Sorry,
John