linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nkwebi Peace" <motlogel@webmail.co.za>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev plus keyboard and mouse (fedora core 5)
Date: Tue, 09 May 2006 06:53:05 +0000	[thread overview]
Message-ID: <web-21354797@cgp8.sentechsa.net> (raw)
In-Reply-To: <web-20955891@cgp8.sentechsa.net>

Greg, It seems when I am not in X, but I an using the
keyboard and mouse, the /sys/class/input/mouseX and
/sys/class/input/eventX files do not get updated.. So I was
thinking the solution will be to check the console as well,
and that brings me back to the first question of locating
the device file names for console..

regards..

On Mon, 8 May 2006 11:24:49 -0700
 Greg KH <greg@kroah.com> wrote:
>On Mon, May 08, 2006 at 06:03:36PM +0200, Nkwebi Peace
>wrote:
>> 
>> Hello everyone.. I need help with identifying device
>files
>> for my keyboard and mouse..I am trying to write a c
>program
>> to retrieve access times for my keyboard and mouse and
>> wanted to do it using the stat() system call which
>require
>> the file name for each devive file...If they is a better
>> way to do it please help with that..The reason I am
>asking
>> is because the /dev drive seems to be populated with
>many
>> ttyXXX files and I can't identify which is which..
>
>Why do you care about the tty files for keyboards?
>
>> The /dev/input directory also has many files and I can't
>seem to
>> locate the correct one..
>
>One of them points back to your keyboard, if you have the
>event driver
>loaded.  Look in /sys/class/input/ to try to figure it
>out.
>
>> I am running fedora core 5, which I understand uses udev
>for handling
>> device files and their naming..
>> 
>> The other question I wanted to ask is whether the
>dynamic
>> naming of device files also applies to the keyboard and
>> mouse, and can one handle that in a program if device
>file
>> names are not kept static using the udev rules..
>
>You can have persistant names for input devices, as I
>think Debian has
>done that.  Not sure if Fedora has or not, but if not, a
>few simple rule
>additions would do it for you.
>
>good luck,
>
>greg k-h

___________________________________________________________________
For super low premiums, click here http://www.webmail.co.za/dd.pwm

http://www.webmail.co.za the South African FREE email service


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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

  parent reply	other threads:[~2006-05-09  6:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08 16:03 Udev plus keyboard and mouse (fedora core 5) Nkwebi Peace
2006-05-08 18:24 ` Greg KH
2006-05-09  6:53 ` Nkwebi Peace [this message]
2006-05-09 16:50 ` Darren Salt
2006-05-09 20:14 ` Greg KH

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=web-21354797@cgp8.sentechsa.net \
    --to=motlogel@webmail.co.za \
    --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).