All of lore.kernel.org
 help / color / mirror / Atom feed
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

             reply	other threads:[~2004-05-27 13:12 UTC|newest]

Thread overview: 50+ 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
  -- strict thread matches above, loose matches on Subject: below --
2020-06-06 17:09 Documentation G.W. Haywood
2020-06-07 21:23 ` Documentation Pablo Neira Ayuso
2020-06-10 12:55   ` Documentation G.W. Haywood
2017-03-27  5:53 documentation Julia Lawall
2011-04-13 23:33 Documentation Eugene Shatsky
2011-04-14  4:44 ` Documentation Jonáš Vidra
2011-04-14 13:54 ` Documentation Edward Shishkin
2011-01-31 21:39 documentation Roberto Spadim
2011-01-31 21:43 ` documentation Mathias Burén
2011-01-31 21:58 ` documentation NeilBrown
2011-01-31 22:14   ` documentation Roberto Spadim
2011-02-01  9:37     ` documentation hansbkk
2011-02-01 13:49       ` documentation Roberto Spadim
2010-12-01 18:00 Documentation David Lambert
2010-12-01 18:06 ` Documentation Stefan Schmidt
2010-12-01 18:39   ` Documentation David Lambert
2010-12-01 18:54     ` Documentation Stefan Schmidt
2010-12-01 22:46       ` Documentation Robert Foerster
2010-12-02 20:37         ` Documentation David Lambert
2010-12-02 20:52           ` Documentation Robert Foerster
2010-12-03  7:35             ` Documentation Christophe Aeschlimann
2010-03-14  0:17 Documentation Giuseppe Macrì
2006-02-10  8:20 Documentation Nico -telmich- Schottelius
2005-10-24 19:05 Documentation Vagin Andrey S.
2004-06-24 17:10 Documentation Tomas Ebenlendr
2004-06-24 22:03 ` Documentation Yoshinori K. Okuji
2004-06-25 13:17   ` Documentation Jeroen Dekkers
2004-06-26 15:05     ` Documentation Yoshinori K. Okuji
2004-05-15 14:28 Documentation Jody
2004-05-17 13:35 ` Documentation Andrey Romanenko
2004-05-17 13:40 ` Documentation Miguel Bolanos
2003-06-06 13:20 Documentation Matthew Wilcox
2002-08-29  9:39 documentation vandana  mehtani
2002-08-29 15:46 ` documentation Dave Wilhardt
2002-04-24 14:26 documentation Guilhem Tardy
2002-04-24 16:58 ` documentation Takashi Iwai
2002-04-24 19:32   ` documentation Guilhem Tardy
2002-04-26 17:54     ` documentation Takashi Iwai
2002-05-03 16:11       ` documentation Guilhem Tardy
2002-05-03 16:22         ` documentation Paul Davis
2002-05-03 16:28         ` documentation Takashi Iwai
2002-03-22 15:32 Documentation Gopakumar.C.E
2002-03-30  7:42 ` Documentation Ralf Baechle
2002-02-02  9:18 Documentation Guillaume Chamberland-Larose
2002-02-02 10:39 ` Documentation Yven J. Leist
2002-02-05 18:18   ` Documentation Randy.Dunlap
2001-11-15 18:03 Documentation war

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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.