From: Gregory Nowak <greg@romuald.net.eu.org>
To: speakup@braille.uwo.ca
Subject: loading modules under 2.6.x
Date: Thu, 29 Dec 2005 11:59:13 -0700 [thread overview]
Message-ID: <20051229185913.GA4054@localhost.localdomain> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all.
Under the 2.6.x series of kernels, most of my modules get loaded
automagically either during hardware detection, or as they are
needed. However, I have 2 modules, ip_nat_ftp and pcspkr, that don't
load automatically. I realize that I can create a script under
/etc/init.d/ that would modprobe them, but using /etc/modprobe.conf
looks like a much more elegant, and more proper solution. The problem
is, that having read the modprobe.conf man page, I see how to create
aliases, how to pass options to a module, and how to install/remove
modules using custom commands. I don't see a way to simply modprobe
for a module. The 2 things that I have tried, using alias, and the
install command, ended up either not working, or putting modprobe in a
loop.
So, would someone please be kind enough to tell me what I'm missing,
and what's the proper way to simply modprobe a module using 2.6.x
kernels and module init tools? BTW, I'm running debian if that makes a
difference. Thanks in advance for any help.
Greg
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDtDIB7s9z/XlyUyARAoeRAJ9IadSTHC+puBx7GvvFSWIBUutycACgrKkA
0cUPIKfnBe42AULqnTG2Kew=
=vLwy
-----END PGP SIGNATURE-----
next reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak [this message]
` Charles Hallenbeck
` Luke Yelavich
` John G. Heim
` Sean McMahon
` Lorenzo Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051229185913.GA4054@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).