linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Jellinghaus <aj@ciphirelabs.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: 8/16bit usb minor device number problem
Date: Wed, 27 Sep 2006 16:03:32 +0000	[thread overview]
Message-ID: <451AA0D4.5090202@ciphirelabs.com> (raw)
In-Reply-To: <451A4559.80109@ciphirelabs.com>

Greg KH wrote:
> This is probably a glibc issue.  Can you manually create a device node
> with a minor of 257?
> 
> What version of glibc are you using?

ah, ok.

foo:~# mknod 002 c 189 257
foo:~# ls -l 002
crw-r--r--  1 root root 189, 1 Sep 27 16:01 002
foo:~# ldd /bin/mknod
         libc.so.6 => /lib/tls/libc.so.6 (0xa7e9f000)
         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xa7fda000)
foo:~# dpkg -s libc6
Package: libc6
Status: install ok installed
Priority: required
Section: base
Installed-Size: 15368
Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
Architecture: i386
Source: glibc
Version: 2.3.2.ds1-22sarge4


so latest udev (or at least /dev/bus/usb) and debian sarge is
not a good combination :(

Thanks for your help.

Regards, Andreas

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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

  parent reply	other threads:[~2006-09-27 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27  9:33 8/16bit usb minor device number problem Andreas Jellinghaus
2006-09-27 15:22 ` Greg KH
2006-09-27 16:03 ` Andreas Jellinghaus [this message]
2006-09-27 17:17 ` Greg KH

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=451AA0D4.5090202@ciphirelabs.com \
    --to=aj@ciphirelabs.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 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).