From owner-cvs-src@FreeBSD.ORG  Fri Oct 24 16:12:58 2003
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A1D4516A4BF
	for <cvs-src@FreeBSD.org>; Fri, 24 Oct 2003 16:12:58 -0700 (PDT)
Received: from rootlabs.com (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id 7EBC443FDF
	for <cvs-src@FreeBSD.org>; Fri, 24 Oct 2003 16:12:56 -0700 (PDT)
	(envelope-from nate@rootlabs.com)
Received: (qmail 67238 invoked by uid 1000); 24 Oct 2003 23:12:57 -0000
Date: Fri, 24 Oct 2003 16:12:57 -0700 (PDT)
From: Nate Lawson <nate@root.org>
To: Scott Long <scottl@freebsd.org>
In-Reply-To: <20031024165549.C77416@pooker.samsco.home>
Message-ID: <20031024161208.Q67220@root.org>
References: <200310242202.h9OM2TWs026868@repoman.freebsd.org>
 <20031024165549.C77416@pooker.samsco.home>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: cvs-src@FreeBSD.org
cc: src-committers@FreeBSD.org
cc: Warner Losh <imp@FreeBSD.org>
cc: cvs-all@FreeBSD.org
Subject: 
	Re: cvs commit: src/sbin/devd devd.cc devd.h devd.hh parse.y token.l
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Oct 2003 23:12:58 -0000

On Fri, 24 Oct 2003, Scott Long wrote:
> On Fri, 24 Oct 2003, Warner Losh wrote:
> > imp         2003/10/24 15:02:29 PDT
> >
> >   FreeBSD src repository
> >
> >   Modified files:
> >     sbin/devd            devd.cc devd.h devd.hh parse.y token.l
> >   Log:
> >   Parse the ! lines that will soon be coming from the kernel.  These are
> >   a generalized notification mechanism for subsystems wishing to report
> >   events.
> >
> >   Revieded by: njl
> >
> >   # The kernel side seems like it might be causing panics for me, but should
> >   # be forthcoming shortly.
>
> Huh?  Is there a reason why we need even less stability right now?

I think the code is very simple and not likely to be causing the problem
he mentioned.  I think he was being overly cautious.  I've been using it
with no problems.

-Nate