From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sat, 09 Apr 2005 00:14:22 +0000 Subject: Re: device not part of a subsystem? Message-Id: <1113005662.4771.26.camel@localhost.localdomain> List-Id: References: <20050409000129.GA32481@wonderland.linux.it> In-Reply-To: <20050409000129.GA32481@wonderland.linux.it> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Sat, 2005-04-09 at 02:01 +0200, Marco d'Itri wrote: > Is this a bug? The rfcomm driver reports just this: > > $ udevinfo -a -p /class/tty/rfcomm0 > > [...] > > device '/sys/class/tty/rfcomm0' has major:minor 216:0 > looking at class device '/sys/class/tty/rfcomm0': > SYSFS{dev}="216:0" That looks bad. The subsystem is read from the device path. Don't know why this isn't working. What udev version is it? Do you use klibc? How does a "ls -l" in that directory look like? Is it a bluetooth device? > Should I change my rules files to not depend on the driver being part of > the tty subsystem or ask for the rfcomm driver to be fixed? Hmm, that device should probably have a "device" link? But let's find the SUBSYSTEM bug first. Kay ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&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