From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and parallel port support
Date: Tue, 04 Oct 2005 21:56:14 +0000 [thread overview]
Message-ID: <20051004215614.GA17038@kroah.com> (raw)
In-Reply-To: <000101c5c83f$4c7184d0$3502a8c0@cisit.local>
On Tue, Oct 04, 2005 at 04:48:43PM -0500, Jason Dravet wrote:
>
> I am sorry I did not make my self clear. What I meant is that udev creates
> the /dev/lp0, /dev/parport0, /dev/lp1, ..., /dev/parport3 nodes by looking
> at /etc/udev/makedev.d/50-udev.nodes instead of actually detecting the
> ports. In the 50-udev.nodes file it says "These device have to be created
> manually" and proceeds to list several items include lp0.
That sounds like a redhat specific change to udev, please take it up
with them.
> At least that is what happens in version 0.58. Does it make sense
> now?
There is no such thing as a udev release numbered 0.58, sorry :)
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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
next prev parent reply other threads:[~2005-10-04 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 17:24 udev and parallel port support Jason Dravet
2005-10-04 21:31 ` Greg KH
2005-10-04 21:48 ` Jason Dravet
2005-10-04 21:56 ` Greg KH [this message]
2005-10-04 21:57 ` Kay Sievers
2005-10-04 22:12 ` Jason Dravet
2005-10-04 22:14 ` Jason Dravet
2005-10-04 22:26 ` Greg KH
2005-10-04 22:38 ` 'Kay Sievers'
2005-10-05 11:48 ` Sergey Vlasov
2005-10-05 14:05 ` Jason Dravet
2005-10-06 7:15 ` Marco d'Itri
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=20051004215614.GA17038@kroah.com \
--to=greg@kroah.com \
--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.