From owner-freebsd-current Thu Aug 31 18:13:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id SAA04208 for current-outgoing; Thu, 31 Aug 1995 18:13:50 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id SAA04200 for ; Thu, 31 Aug 1995 18:13:48 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id SAA12864; Thu, 31 Aug 1995 18:10:52 -0700 To: Terry Lambert cc: bde@zeta.org.au (Bruce Evans), wollman@lcs.mit.edu, freebsd-current@FreeBSD.org, jhay@mikom.csir.co.za Subject: Re: pseudo device lkm's broken In-reply-to: Your message of "Thu, 31 Aug 1995 17:49:29 PDT." <199509010049.RAA23766@phaeton.artisoft.com> Date: Thu, 31 Aug 1995 18:10:51 -0700 Message-ID: <12861.809917851@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Yes, this is a pardigm shift. It means that drivers and file systems > and anything else that is expected to be loadable or linkable as an > option to the kernel build must have a single entry/multiple consumer > interface with callback registration. Anything that places itself I'm no kernel hacker, but this seems like a serious win even to me. So, given that the interdependency set between LKM and kernel is even smaller with this, do you think there's any chance of us being able to remove ld from the equation at some point? It would be nice if the kernel could load them directly, without requiring a user mode program to run interferance first. Jordan