From: "Georg Nikodym" <georgn@somanetworks.com>
To: John Jasen <jjasen@datafoundation.com>
Cc: William Knop <w_knop@hotmail.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Modules and DevFS
Date: Thu, 1 Feb 2001 11:13:12 -0500 (EST) [thread overview]
Message-ID: <14969.35608.472226.83936@somanetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0102011021520.31149-100000@flash.datafoundation.com>
In-Reply-To: <F204tAEHLB8TrBHxvZ900001de6@hotmail.com> <Pine.LNX.4.30.0102011021520.31149-100000@flash.datafoundation.com>
>>>>> "JJ" == John Jasen <jjasen@datafoundation.com> writes:
JJ> On Thu, 1 Feb 2001, William Knop wrote:
>> >One thing that I've noticed with devfs is that all the old-style
>> >names are symlinks.
>>
>> Hmm... I have no symlinks until the module loads. Therefore X sees
>> no /dev/input/mouse, doesn't ask the kernel for it, the kernel
>> doesn't load the module, and DevFS doesn't add the /dev
>> entry. There's got to be an easy way around this. Perhaps it has
>> already been implimented, but I haven't been able to get anything
>> to work well (manual loading for me).
JJ> change your XF86Config file to point to /dev/psaux
Or /dev/input/mice if you use a USB thang.
-
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-02-01 16:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 21:34 William Knop
2001-01-30 22:20 ` Michael B. Trausch
2001-01-31 22:05 ` Brian May
2001-02-01 10:31 ` Helge Hafting
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=14969.35608.472226.83936@somanetworks.com \
--to=georgn@somanetworks.com \
--cc=jjasen@datafoundation.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w_knop@hotmail.com \
/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®