From: Brian May <bam@snoopy.apana.org.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Modules and DevFS
Date: 01 Feb 2001 09:05:58 +1100 [thread overview]
Message-ID: <84ofwnjs1l.fsf@snoopy.apana.org.au> (raw)
In-Reply-To: <F148MamEWkeMEwuwi7N000015ef@hotmail.com>
In-Reply-To: w_knop@hotmail.com's message of "31 Jan 01 21:34:53 GMT"
>>>>> "William" == William Knop <w_knop@hotmail.com> writes:
William> Correct me if I'm wrong, but DevFS only makes /dev
William> entries when a device is present, and the device is not
William> present until the module is loaded. So if I want to
William> access /dev/hda and the IDE module has not been loaded
William> yet, I will get a message telling me the device doesn't
William> exist or some such instead of autoloading the module and
William> being happy. Same goes for hotswap devices, right? I boot
William> directly into X and have to crash out (otherwise it
William> continually tries to unsuccessfully load X) so I could
William> enable my USB mouse and various other devices.
My /etc/modutils/devfsd has
probeall /dev/discs scsi-hosts sd_mod ide-probe-mod ide-disk DAC960
perhaps it should have something similar for /dev/hd*?
As a work around, put something like this:
alias /dev/hdd ide-cd
or (not tested; just guessing):
alias /dev/hd* /dev/ide
in /etc/modutils/aliases, and run update-modules.
William> I realize modularizing the entire IDE subsystem is not
William> really good anyway, because every time it reloads it will
William> rescan the bus... But what about USB? Suppose I don't
William> have any IDE or USB devices, but want support so I can
William> use them later. Especially in the case of USB,
William> plugability is a must for desktop "home" systems.
I am not really familiar with USB.
--
Brian May <bam@snoopy.apana.org.au>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-31 22:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 21:34 William Knop
2001-01-30 22:20 ` Michael B. Trausch
2001-01-31 22:05 ` Brian May [this message]
2001-02-01 10:31 ` Helge Hafting
2001-02-01 8:44 William Knop
2001-01-31 22:56 ` Michael B. Trausch
2001-02-02 10:35 ` Helge Hafting
2001-02-02 20:00 ` Michael B. Trausch
2001-02-05 10:36 ` Helge Hafting
2001-02-02 20:33 ` Georg Nikodym
2001-02-01 10:23 ` Peter Samuelson
2001-02-01 15:22 ` John Jasen
2001-02-01 16:13 ` Georg Nikodym
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=84ofwnjs1l.fsf@snoopy.apana.org.au \
--to=bam@snoopy.apana.org.au \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®