From: Brad Hards <bhards@bigpond.net.au>
To: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.20-pre2 compile error
Date: Wed, 14 Aug 2002 08:05:02 +1000 [thread overview]
Message-ID: <200208140805.03039.bhards@bigpond.net.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0208131714360.19585-100000@sharra.ivimey.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 14 Aug 2002 02:21, Ruth Ivimey-Cook wrote:
<snip>
> For example, recently I wanted to find the combined mouse device on an RH3
> system that I haven't got around to switching to devfs; after a lot of
> searching, including in the kernel sources, I gave up. On defvs it's
> obvious: you have /dev/mouse/, and under that "mice", which, being the
> plural of "mouse", is pretty clear, IMO.
Note that this is partly an experience (maybe even cultural) issue.
Given the same problem, I'd think "ah, mouse. Now that is an input device, so
I'd expect it to be in /devin/input. Hmm - lots of mouse0, mouse1, etc type
entries, and a "mice" entry. That'll probably be the one..."
I personally wouldn't think to look in /dev/mouse. And remember that we speak
(mostly) the same language. Maus?
I guess it is just a matter of what you know.
Brad
- --
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9WYKPW6pHgIdAuOMRAlGyAJ9Oh18IJwOG16GhwqO/5Jl/sMRwcwCdFR53
ecU1Ko3Y/s6TOBSuo7aXmGg=
=URqj
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2002-08-13 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 5:31 Chad Young
2002-08-13 8:28 ` Adrian Bunk
2002-08-13 10:30 ` Stephane Wirtel
2002-08-13 10:38 ` Adrian Bunk
2002-08-13 11:01 ` Stephane Wirtel
2002-08-13 11:32 ` Christoph Hellwig
2002-08-13 16:21 ` Ruth Ivimey-Cook
2002-08-13 22:05 ` Brad Hards [this message]
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=200208140805.03039.bhards@bigpond.net.au \
--to=bhards@bigpond.net.au \
--cc=Ruth.Ivimey-Cook@ivimey.org \
--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®