Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 88802

Summary: /dev/rfcomm[01] missing
Product: [Fedora] Fedora Reporter: James Clark <jjc>
Component: MAKEDEVAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 2CC: bnocera, jukka, rpmuldoon
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 3.9-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-26 00:49:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 100644    
Attachments:
Description Flags
create rfcomm devices none

Description James Clark 2003-04-14 11:41:58 UTC 
/usr/bin/rfcomm and the rfcomm kernel module need /dev/rfcomm[01] to be useful,
but these don't get created automatically.  They are supposed to look like this:

crw-r--r--    1 root     root     216,   0 Apr 12 08:52 /dev/rfcomm0
crw-r--r--    1 root     root     216,   1 Apr 12 08:52 /dev/rfcomm1
Comment 1 Bastien Nocera 2003-08-26 23:56:27 UTC 
Created attachment 93968 [details]
create rfcomm devices
Comment 2 Bastien Nocera 2003-08-26 23:57:14 UTC 
This patch is necessary for the bluetooth packages to operate properly, please
apply.
Comment 3 Bastien Nocera 2003-10-21 22:04:53 UTC 
Reassigning to Fedora Core
Comment 5 Jukka Ketelaars 2004-06-01 08:39:15 UTC 
These are still not created in FC2 final. Also, I think bug 101075 is 
a duplicate of this one.
Comment 6 Bastien Nocera 2004-06-01 10:18:10 UTC 
*** Bug 101075 has been marked as a duplicate of this bug. ***
Comment 10 Alan Cox 2004-06-21 15:23:53 UTC 
The kernel, lanana and thus fhs/lsb say its "/dev/ttyUB*".  That
implies either there is a serious disconnect upstream (please resolve
upstream) or the bluetooth packages are the ones to correct
Comment 11 Bastien Nocera 2004-06-21 16:12:18 UTC 
"/dev/ttyUB*" are from the now defunct Axis Bluetooth stack, not the
currently used BlueZ stack.