From owner-freebsd-current  Sat Dec  2 03:57:32 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id DAA07665
          for current-outgoing; Sat, 2 Dec 1995 03:57:32 -0800
Received: (from julian@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id DAA07652
          ; Sat, 2 Dec 1995 03:57:23 -0800
Date: Sat, 2 Dec 1995 03:57:23 -0800
From: Julian Elischer <julian>
Message-Id: <199512021157.DAA07652@freefall.freebsd.org>
To: hackers
Subject: OK EVERYONE, LISTEN UP..
Cc: current
Sender: owner-current@FreeBSD.ORG
Precedence: bulk


I've been testing my cdevsw and bdevsw changes
and I have two machines here that have been doing heavy work with them
and nothing's broken..

I'm going to make the changes to make it THE DEFAULT 
within 48 hours
so if you are a -current user, and haven't tried to see what
happens when you add 
options JREMOD
to your kernel, then you'd better check it now while it's still
just an option..

and yes, poul, with sources from this-evenning, I was unable to duplicate
your problem so I think it's something else.. :)

It's running reliably here and elsewhere so it shouldn't be too much
of a risk..

If you have problems and want this to not go ahead,
then get back to me in the next day or so..
because I'll be committing the next round, sunday night..
BTW if JREMOD fails. DO check if a kernel compiled out of the same
tree withut it also fails? I've chased 3 of those so far..

julian