From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and parallel port support
Date: Tue, 04 Oct 2005 21:57:59 +0000 [thread overview]
Message-ID: <20051004215759.GA14122@vrfy.org> (raw)
In-Reply-To: <000101c5c83f$4c7184d0$3502a8c0@cisit.local>
On Tue, Oct 04, 2005 at 04:48:43PM -0500, Jason Dravet wrote:
> > -----Original Message-----
> > From: Greg KH [mailto:greg@kroah.com]
> > Sent: Tuesday, October 04, 2005 4:31 PM
> > To: Jason Dravet
> > Cc: linux-hotplug-devel@lists.sourceforge.net
> > Subject: Re: udev and parallel port support
> >
> > On Mon, Oct 03, 2005 at 12:24:24PM -0500, Jason Dravet wrote:
> > > Hello,
> > >
> > > I opened bugzilla bug 145148
> > > (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id\x145148) at the
> > > beginning of this year. Udev was creating a bunch of unnecessary items
> > in
> > > /dev. The parallel ports were mentioned specifically along with a large
> > > number of ttyS and tty nodes. When redhat responded to the bug I found
> > out
> > > that udev had to create the parallel port nodes itself using a rule
> > because
> > > the parallel port module was not loading at boot time. I opened the bug
> > to
> > > get the parallel port module to load at boot time so udev could
> > dynamically
> > > create the nodes instead of creating 4 parallel ports when most people
> > have
> > > (use) one.
> > >
> > > I received an email asking me to try the new fedora core 4 kernel. I
> > have
> > > installed it and it works fine for me. The issue is udev is still
> > creating
> > > the parallel port statically instead of dynamically. When will udev be
> > able
> > > to dynamically create the nodes for parallel ports?
> >
> > It does so today just fine, the last time I looked. It's a kernel
> > issue, not a udev issue.
> >
> > How could udev be creating devices "statically"? It's up to the kernel
> > to export what it has availble, and right now, it just exports them all.
> > Is that what bothers you? If so, feel free to change the kernel code to
> > work better if you wish.
> >
> > But again, it's a kernel issue, not a udev issue.
> >
> > thanks,
> >
> > greg k-h
>
> 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. At least that is
> what happens in version 0.58. Does it make sense now?
/etc/udev/makedev.d/ exists only on Red Hat. Every distro has it's own
way to create the "static" nodes.
Kay
-------------------------------------------------------
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:57 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
2005-10-04 21:57 ` Kay Sievers [this message]
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=20051004215759.GA14122@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 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).