From owner-freebsd-current Sat Jan 30 09:39:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15674 for freebsd-current-outgoing; Sat, 30 Jan 1999 09:39:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15646 for ; Sat, 30 Jan 1999 09:39:35 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.2/8.8.5) with SMTP id RAA00753; Sat, 30 Jan 1999 17:39:19 GMT Date: Sat, 30 Jan 1999 17:39:13 +0000 (GMT) From: Doug Rabson To: Daren Sefcik cc: current@FreeBSD.ORG Subject: Re: lkm not working In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 Jan 1999, Daren Sefcik wrote: > I am now up to 4.0 and lkm is not working... > > rover# modstat > modstat: /dev/lkm: Device not configured > > I have not used it much but I know it worked with > my 3.0 system...any pointers would be great. The lkm system has been superceded by a new kernel linker system called KLD. The lkm support is still available by adding 'options LKM' to your kernel configuration but since all standard lkms have been converted to the new system, there should be no need. To find the list of loaded modules in the new system, use kldstat. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message