All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev: no /dev/input/mice made
Date: Fri, 11 Nov 2005 17:15:53 +0000	[thread overview]
Message-ID: <20051111171553.GA25883@vrfy.org> (raw)
In-Reply-To: <200511111647.jABGlcwv008824@orion.dwf.com>

On Fri, Nov 11, 2005 at 09:47:38AM -0700, Reg Clemens wrote:
> OK, something happened with my FC3 system, but now when
> I reboot, Windows won't come up.

What is "something"? What did you change?

> The problem is that /dev/input/mice is missing.
> If I make the directory and then the node, viz
> 
> 	mkdir /dev/input
> 	mknod /dev/input/mice c 13 63
> 
> then all is well.

What does:
  ls -l /sys/class/input/
print?

> I have to assume that udev is removing, and remaking this node
> each time I reboot.

Yes, that's intentional. /dev is on a tmpfs, its content does not
survive a reboot.

> What do I have to do to get it to do it right?
> As far as I can tell, the /etc/udev/rules.d/50-udev.rules file is untouched.

What kernel version?
What udev version?

Kay


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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:[~2005-11-11 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11 16:47 udev: no /dev/input/mice made Reg Clemens
2005-11-11 17:15 ` Kay Sievers [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=20051111171553.GA25883@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --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.