From owner-cvs-src@FreeBSD.ORG  Fri May  9 11:27:46 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 F078A37B401; Fri,  9 May 2003 11:27:45 -0700 (PDT)
Received: from mail.imp.ch (mail.imp.ch [157.161.1.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 44AD743F75; Fri,  9 May 2003 11:27:42 -0700 (PDT)
	(envelope-from mb@imp.ch)
Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9])
	by mail.imp.ch (8.12.6p2/8.12.3) with ESMTP id h49IRWPq019342;
	Fri, 9 May 2003 20:27:32 +0200 (CEST)
	(envelope-from Martin.Blapp@imp.ch)
Date: Fri, 9 May 2003 20:27:32 +0200 (CEST)
From: Martin Blapp <mb@imp.ch>
To: John Baldwin <jhb@FreeBSD.org>
In-Reply-To: <XFMail.20030509134912.jhb@FreeBSD.org>
Message-ID: <20030509202516.J23311@cvs.imp.ch>
References: <XFMail.20030509134912.jhb@FreeBSD.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Paul Richards <paul@freebsd-services.com>
cc: cvs-src@FreeBSD.org
cc: src-committers@FreeBSD.org
cc: cvs-all@FreeBSD.org
cc: Peter Wemm <peter@wemm.org>
Subject: Re: cvs commit: src/sys/boot/i386/libi386 i386_module.c
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, 09 May 2003 18:27:46 -0000


Hi,

> Trying to kldload something that is already present in the kernel
> either fails or results in a kernel panic.  If you are already
> rebooting to test it, then you might as well build a new kernel
> as a new module each time.

I thought there were patches posted to CURRENT to address this
issue ? Nobody seems to have them comitted, unfortunatly.

Martin