From: Barrie Stott <G.B.Stott@bolton.ac.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: Help wanted with parallel port rule
Date: Thu, 29 Nov 2007 21:06:38 +0000 [thread overview]
Message-ID: <20071129210638.GA4043@etch1> (raw)
In-Reply-To: <20071129084807.GA3912@etch1>
I'm very grateful for your reply. There's a lot here to get to grips
with as there is with Kay's email. The main thing for me at present
is the following:
On Thu, Nov 29, 2007 at 01:18:04PM -0500, Bryan Kadzban wrote:
> The lp0 device file should show up when you load the lp module (I
> think), although you'll need the parport and parport_pc modules as well.
> You may want to try loading all of them if you don't have the file,
> though I think lp depends on both parport* modules.
I've never come across the lp module before. `modprobe lp' brought me
/dev/lp0 that I didn't have before without using links.conf. A lot of
other things are dropping into place and I want to play with these a
bit before getting to some of the other things you said.
> What I think Kay meant is that udev should be creating /dev/lp0 without
> any help from rules at all. If it doesn't do that, then there's some
> other kind of problem here; perhaps not all the modules are loaded or
> something?
How's that (not all modules loaded) for hitting the nail on the head?
I didn't have /dev/lp0 and couldn't find a good way to get it. Now it
comes by using `modprobe lp' and vanishes again with `rmmod lp'. And I
can use udev info with /dev/lp0 now as well. Things are looking up.
Thanks again; you've made me very happy.
Barrie.
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
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:[~2007-11-29 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 8:48 Help wanted with parallel port rule Barrie Stott
2007-11-29 11:09 ` Kay Sievers
2007-11-29 14:49 ` Barrie Stott
2007-11-29 18:18 ` Bryan Kadzban
2007-11-29 21:06 ` Barrie Stott [this message]
2007-11-29 23:32 ` Bryan Kadzban
2007-11-30 4:45 ` Alexander E. Patrakov
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=20071129210638.GA4043@etch1 \
--to=g.b.stott@bolton.ac.uk \
--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.