From owner-cvs-src@FreeBSD.ORG Mon Aug 2 18:28:37 2004 Return-Path: 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 8BE5A16A4CE; Mon, 2 Aug 2004 18:28:37 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 651B543D5D; Mon, 2 Aug 2004 18:28:37 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.13.1/8.12.11) with ESMTP id i72ISUr8001085; Mon, 2 Aug 2004 11:28:30 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i72IST9B001084; Mon, 2 Aug 2004 11:28:29 -0700 (PDT) (envelope-from obrien) Date: Mon, 2 Aug 2004 11:28:29 -0700 From: "David O'Brien" To: markm@freebsd.org Message-ID: <20040802182829.GA930@dragon.nuxi.com> References: <200408021814.i72IE6QJ030695@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408021814.i72IE6QJ030695@repoman.freebsd.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/modules Makefile X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Aug 2004 18:28:37 -0000 On Mon, Aug 02, 2004 at 06:14:06PM +0000, David E. O'Brien wrote: > obrien 2004-08-02 18:14:06 UTC > > FreeBSD src repository > > Modified files: > sys/modules Makefile > Log: > Don't build and install a mem.ko module. > Currently one cannot load the mem.ko module without panicing if mem is > compiled into the kernel and one cannot build a kernel w/o "device mem" > right now either. Thus it is too dangerous to install mem.ko right now > because if one puts 'mem_load="YES"' in /etc/loader.conf they cannot > boot an "old" kernel (at the time that a kernel doesn't have to be built > with "device mem). Please find a way for all your /dev KO's to detect if they are already active and not panic if loaded(initialized) twice. Many of the network and SCSI device KO's DTRT. Maybe you can copy their method of handling this. -- -- David (obrien@FreeBSD.org)