From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: Strange parport detection
Date: Sun, 15 May 2005 04:31:19 +0000 [thread overview]
Message-ID: <4286D097.1060203@ums.usu.ru> (raw)
In-Reply-To: <4286617B.8070000@tiscali.it>
Sandro Latini wrote to linux-hotplug-devel:
>Hi,
>i'm using a LFS linux with udev version 0.57.
>
linux-hotplug-devel@lists.sourceforge.net is a wrong list, please use
lfs-dev@linuxfromscratch.org for LFS-specific questions. LFS uses its
own version of udev rules, see
http://downloads.linuxfromscratch.org/udev-config-3.rules
BTW if you upgrade package versions, it's recommended that you follow
the development version of the book. Most of time, that's the only
difference between stable and development books. Also, bugs in the
stable book, if any, will never be fixed.
>All works fine except for
>the parport device that is not correctly rappresented in /dev.
>I have just looked in dmesg for the right assignament of the parallel
>port and all seems fine. In sysfs there is a "parport0" too.
>Then i have looked udev rules file and found this:
>
>"KERNEL="parport[0-9]*", NAME="%k", GROUP="lp"
>
>
Works perfectly here with:
KERNEL="parport[0-9]*", GROUP="lp"
So the problem is definitely already resolved in the development version
of the book. If that does not work for you, please mail to
lfs-dev@linuxfromscratch.org .
--
Alexander E. Patrakov
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id\x16281&op=click
_______________________________________________
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
prev parent reply other threads:[~2005-05-15 4:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 20:37 Strange parport detection Sandro Latini
2005-05-15 4:31 ` Alexander E. Patrakov [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=4286D097.1060203@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--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).