From owner-freebsd-security Fri Jul 30 6:36:52 1999 Delivered-To: freebsd-security@freebsd.org Received: from alfik.ms.mff.cuni.cz (alfik.ms.mff.cuni.cz [195.113.19.71]) by hub.freebsd.org (Postfix) with ESMTP id D28FC150D4; Fri, 30 Jul 1999 06:36:46 -0700 (PDT) (envelope-from mencl@nenya.ms.mff.cuni.cz) Received: from nenya.ms.mff.cuni.cz by alfik.ms.mff.cuni.cz; (8.8.8/v1.00/19990210.0854) id PAA15339; Fri, 30 Jul 1999 15:35:08 +0200 (MET DST) Received: from localhost (mencl@localhost) by nenya.ms.mff.cuni.cz (8.9.1b+Sun/8.9.1) with ESMTP id PAA13874; Fri, 30 Jul 1999 15:35:08 +0200 (MET DST) Date: Fri, 30 Jul 1999 15:35:08 +0200 (MET DST) From: "Vladimir Mencl, MK, susSED" To: Thomas Uhrfelt Cc: freebsd-net@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: your mail In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 30 Jul 1999, Thomas Uhrfelt wrote: > modstat: /dev/lkm: Device not configured > What is wrong, there is a /dev/lkm, so I have no idea what to do right now? > Anyone? Well, the special file does exist, but device is not configured. That's because in 3.2, LKMs were dropped to change to .ko - kernel objets. That's the new format of kernel modules. You can load a .ko kernel module for loading old LKM kernel modules. kldload /modules/lkm.ko Now, the lkm interface should be up, and you should be able to succeed with SKIP. I hope there's no collisinion between the two schemes of kernel modules. Vladimir Mencl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message