From owner-freebsd-hackers Tue Jun 6 7:10:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69]) by hub.freebsd.org (Postfix) with ESMTP id DBBC337BD7F for ; Tue, 6 Jun 2000 07:10:15 -0700 (PDT) (envelope-from myevmenkin@att.com) Received: from gab200r1.ems.att.com ([135.37.94.32]) by almso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id KAA05442 for ; Tue, 6 Jun 2000 10:10:13 -0400 (EDT) Received: from njb140bh2.ems.att.com by gab200r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id KAA20707; Tue, 6 Jun 2000 10:11:43 -0400 (EDT) Received: by njb140bh2.ems.att.com with Internet Mail Service (5.5.2650.21) id ; Tue, 6 Jun 2000 10:10:13 -0400 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'hackers@freebsd.org'" Subject: RE: kerneld for FreeBSD Date: Tue, 6 Jun 2000 10:10:05 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="koi8-r" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [...] > > > This is, IMO, a good idea. I certainly don't want some > > > smartass daemon > > > unloading a module just because it thinks it should. 8) > > > > another option in config file? something like ``do_not_unload''? > > No. Modules shouldn't be unloaded automatically. but why? :-) what is wrong with that? it would be so nice to have small GENERIC kernel and bunch of modules. kernel will start, identify all hardware (pci/pnp) and than load appropriate modules. the only problem here is old hardware :( [...] > > i do not agree :-) code wants device > driver/interface/filesystem/????. > > code should not care about module name. of course it is > better to have > > name convension, but i think this is not the case. :-) > > This is debatable; mount, for example, knows the name of its > plugins. So > does PAM. Kernel modules are just plugins that go somewhere else. let say i'm a third party vendor. i developed new hardware and driver for FreeBSD (of course KLD module). i do not want to give my source code to anybody. so you have the following options: 1) go ahead and try to convince me to use the same name convention 2) just ignore this hardware/driver/vendor 3) wait until somebody writes an ``open source'' driver 4) try do something to make in work (could be as easy as rename) 5) ??? thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message