From: Hugh Esco <he@reclaimedcomputers.ca>
To: linux-hotplug@vger.kernel.org
Subject: udev install issues on Debian Sarge, missing device nodes
Date: Sun, 25 Jun 2006 17:01:29 +0000 [thread overview]
Message-ID: <20060625100129.0260ed48.he@reclaimedcomputers.ca> (raw)
Last week I built Debian Sarge on a Toshiba notebook. Only
when the client was picking up the machine did he mention
his USB printer and camera. Now I'm debugging an
incomplete installation of udev across a phone
conversation.
dpkg -l indicates that udev (and hotplug) are both
installed. But the /dev tree is empty and none of the
devices he needs to run his printer are available.
I'm thinking I must have missed an error along the way.
Why would udev install w/o building the device nodes?
And more importantly, what can I do to ask my client to
build these hopefully without him having to bring it back
in to my network for a re-install. Is there some
configuration script I missed running I can guide him
through?
All leads appreciated.
--
Hugh Esco
RCK Computer Services
http://reclaimedcomputers.ca/
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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 reply other threads:[~2006-06-25 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 17:01 Hugh Esco [this message]
2006-06-28 16:52 ` udev install issues on Debian Sarge, missing device nodes Hugh Esco
2006-06-28 17:09 ` 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=20060625100129.0260ed48.he@reclaimedcomputers.ca \
--to=he@reclaimedcomputers.ca \
--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).