From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Andrew B. Cramer" Subject: Re: hi Date: Thu, 23 Jan 2003 18:19:43 -0600 Sender: linux-admin-owner@vger.kernel.org Message-ID: <3E30323F.18417.8647AC0@localhost> References: <20030123180540.GB2500@reivax.org> Reply-To: andrew.cramer@cramer-ts.com Mime-Version: 1.0 Content-Transfer-Encoding: 7BIT Return-path: In-reply-to: <15920.19286.239982.530912@cerise.nosuchdomain.co.uk> Content-description: Mail message body List-Id: Content-Type: text/plain; charset="us-ascii" To: Glynn Clements , linux-admin I think the file you are looking for is /etc/modules.conf in slackware. root@home:~# cd /etc root@home:/etc# ls modules.conf modules.conf root@home:/etc# cat modules.conf alias net-pf-4 off # we won't use PF IPX alias net-pf-5 off # we won't use PF AppleTalk root@home:/etc# That was created by default. I still running Slackware-3.x (4,5,6 I can't remember). Best - Andrew On 23 Jan 2003 at 20:06, Glynn Clements wrote: > > Xavier wrote: > > > > If your module doesn't fit any known type, or you specifically want it > > > to be loaded at boot rather than on demand, then the simplest solution > > > is probably to just add a modprobe command to the rc.local script. > > > > Or add the name of the module to /etc/modules which should contain "the > > names of kernel modules that are to be loaded at boot time" (at least in > > debian - don't remember if this is debian specific, > > I'm fairly sure that it is. At least, RedHat 6.2 doesn't have it, and > the last time that I used Slackware, that didn't have it (although it > did have rc.modules). > > In general, anything that relies upon the init configuration (i.e. > inittab, and scripts which are run from it) should be assumed to be > distribution-specific unless there is evidence to the contrary. > > OTOH, the use and semantics of modules.conf (aka conf.modules) is > built into modprobe, and so is likely to be applicable to all > distributions. > > -- > Glynn Clements > - > To unsubscribe from this list: send the line "unsubscribe linux-admin" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >