From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Documentation
Date: Thu, 27 May 2004 13:12:23 +0000 [thread overview]
Message-ID: <40B5E937.4000601@ums.usu.ru> (raw)
In the Linux From Scratch (LFS) support mailing list a question has been
asked: why can't hotplug load the "snd-pcm-oss" module automatically
despite the fact that the Creative Live! soundcard is found and the
"snd-emu10k1" module is loaded automatically for it. I answered this
question, but another point has been raised there that should be really
discussed here.
Namely, the problem is that the recommendations on building Linux kernel
and writing /etc/modules.conf (or modprobe.conf) file that predate
adoption of Hotplug are now wrong, invalid and even harmful. Since
Hotplug and Udev will be probably included in the next version of LFS,
and even experienced developers cannot build a trouble-free kernel for
use with Hotplug and Udev on their first attempt, we expect a sharp
increase of support questions per day in our list.
I could not find any up-to-date "good practice" documents upon building
the kernel that work well with Hotplug and Udev. E.g., it is mentioned
nowhere that if a character or block device driver is built as a module,
then it will not be loaded automatically. Yes, that is in the Udev FAQ,
but in the wrong form: you state that it is not the task of Udev to load
modules (it is a negative statement), and I need an URL with some
positive recommendations how to load modules and to avoid various
chicken-and-egg problems. The snd-pcm-oss problem is also documented
nowhere. (is there any comprehensive list of such undetectable modules?)
Could you please post link here to some good (possibly even "official")
up-to-date and newbie-proof list of good kernel building practices? The
discussion of modprobe.conf will be also very nice. I will be glad to
put that link into the LFS book, thus avoiding repeated support questions.
If such document is not written yet, we should collaborate and write it.
--
Alexander E. Patrakov
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_idÅ66&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-05-27 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 13:12 Alexander E. Patrakov [this message]
2004-05-28 23:25 ` Documentation Greg KH
2004-06-02 6:11 ` Documentation Niko Sauer
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=40B5E937.4000601@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--cc=linux-hotplug@vger.kernel.org \
/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 NNTP newsgroup(s).