Bug 88802 - /dev/rfcomm[01] missing
Summary: /dev/rfcomm[01] missing
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: MAKEDEV
Version: 2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Brock Organ
URL:
Whiteboard:
: 101075 (view as bug list)
Depends On:
Blocks: CambridgeTarget
TreeView+ depends on / blocked
 
Reported: 2003-04-14 11:41 UTC by James Clark
Modified: 2007-11-30 22:10 UTC (History)
3 users (show)

Fixed In Version: 3.9-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-26 00:49:35 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
create rfcomm devices (436 bytes, patch)
2003-08-26 23:56 UTC, Bastien Nocera 		no flags Details | Diff
View All

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.
Note You need to log in before you can comment on or make changes to this bug.