--- bluez-utils-2.25.orig/debian/pinwrapper +++ bluez-utils-2.25/debian/pinwrapper @@ -0,0 +1,8 @@ +#/bin/sh + +if [ -x /usr/bin/bluez-pin ] +then + /usr/bin/bluez-pin "$@" +else + /usr/lib/kdebluetooth/kbluepin "$@" +fi \ No newline at end of file --- bluez-utils-2.25.orig/debian/control +++ bluez-utils-2.25/debian/control @@ -0,0 +1,60 @@ +Source: bluez-utils +Section: admin +Priority: optional +Maintainer: Debian Bluetooth Maintainers +Uploaders: Edd Dumbill , Filippo Giunchedi +Build-Depends: bison, debhelper (>> 4.1.0), flex, libbluetooth2-dev, autotools-dev, cdbs, libdbus-1-dev, libusb-dev +Standards-Version: 3.6.2 + +Package: bluez-utils +Architecture: any +Depends: ${shlibs:Depends}, sysvinit (>= 2.80-1), module-init-tools | modutils, makedev (<< 3.3.8.2-0), lsb-base (>= 3.0-3) +Suggests: python-gtk2, python (>= 1.5), bluez-firmware +Conflicts: bluez-sdp (<= 1.5-2), bluez-pan +Replaces: bluez-sdp (<= 1.5-2), bluez-pan +Description: Bluetooth tools and daemons + This package contains tools and system daemons for using Bluetooth devices. + . + BlueZ is the official Linux Bluetooth protocol stack. It is an Open Source + project distributed under GNU General Public License (GPL). + . + More information is available at http://bluez.sourceforge.net/ + +Package: bluez-pcmcia-support +Architecture: alpha arm i386 ia64 powerpc hppa m68k mips mipsel sparc sh3 sh4 sh3eb sh4eb amd64 +Priority: extra +Depends: bluez-utils (= ${Source-Version}), pcmcia-cs (>= 3.2.2) +Description: PCMCIA support files for BlueZ 2.0 Bluetooth tools + This package contains files to enable PCMCIA card services to recognise + and initialise PCMCIA Bluetooth devices. + . + BlueZ is the official Linux Bluetooth protocol stack. It is an Open Source + project distributed under GNU General Public License (GPL). + . + More information is available at http://bluez.sourceforge.net/ + +Package: bluez-cups +Architecture: any +Depends: ${shlibs:Depends}, cupsys +Description: Bluetooth printer driver for CUPS + This package contains a driver to let CUPS print to Bluetooth-connected + printers. It is part of the BlueZ project. + . + BlueZ is the official Linux Bluetooth protocol stack. It is an Open Source + project distributed under GNU General Public License (GPL). + . + More information is available at http://bluez.sourceforge.net/ + +Package: bluetooth +Architecture: all +Depends: bluez-utils, bluez-noninteractive-pin | bluez-pin +Description: Bluetooth stack utilities + This metapackage provides the bluez utilities for managing the linux bluetooth + stack for kernels 2.4 and 2.6. + +Package: bluetooth-desktop +Architecture: all +Depends: bluetooth, bluez-pin +Description: Bluetooth stack utilities + This metapackage provides the same utilities as the bluetooth package plus the + graphical pin helper --- bluez-utils-2.25.orig/debian/patches/008_unsafe_pand_option.patch +++ bluez-utils-2.25/debian/patches/008_unsafe_pand_option.patch @@ -0,0 +1,58 @@ +--- bluez-utils/pand/bnep.c ++++ bluez-utils/pand/bnep.c +@@ -184,12 +184,12 @@ + { + struct bnep_connadd_req req; + +- strcpy(req.device, dev); ++ strncpy(req.device, dev, 16); + req.sock = sk; + req.role = role; + if (ioctl(ctl, bnepconnadd, &req)) + return -1; +- strcpy(dev, req.device); ++ strncpy(dev, req.device, 16); + return 0; + } + + +=== modified file 'bluez-utils/pand/main.c' +--- bluez-utils/pand/main.c ++++ bluez-utils/pand/main.c +@@ -182,6 +182,8 @@ + while (!terminate) { + socklen_t alen = sizeof(l2a); + int nsk; ++ char this_netdev[16]; ++ + nsk = accept(sk, (struct sockaddr *) &l2a, &alen); + if (nsk < 0) { + syslog(LOG_ERR, "Accept failed. %s(%d)", strerror(errno), errno); +@@ -197,14 +199,14 @@ + close(nsk); + continue; + } +- +- if (!bnep_accept_connection(nsk, role, netdev)) { ++ strncpy(this_netdev, netdev, 16); ++ if (!bnep_accept_connection(nsk, role, this_netdev)) { + char str[40]; + ba2str(&l2a.l2_bdaddr, str); + + syslog(LOG_INFO, "New connection from %s %s", str, netdev); + +- run_devup(netdev, str, sk, nsk); ++ run_devup(this_netdev, str, sk, nsk); + } else { + syslog(LOG_ERR, "Connection failed. %s(%d)", + strerror(errno), errno); +@@ -608,7 +610,7 @@ + break; + + case 'e': +- strcpy(netdev, optarg); ++ strncpy(netdev, optarg, 16); + break; + + case 'n': + --- bluez-utils-2.25.orig/debian/patches/000_rfcomm_conf_example.patch +++ bluez-utils-2.25/debian/patches/000_rfcomm_conf_example.patch @@ -0,0 +1,25 @@ +--- rfcomm/rfcomm.conf.orig 2005-12-26 13:27:16.840000000 +0100 ++++ rfcomm/rfcomm.conf 2005-12-26 13:28:04.720000000 +0100 +@@ -2,16 +2,16 @@ + # RFCOMM configuration file. + # + +-rfcomm0 { ++#rfcomm0 { + # Automatically bind the device at startup +- bind no; ++# bind yes; + + # Bluetooth address of the device +- device 11:22:33:44:55:66; ++# device 11:22:33:44:55:66; + + # RFCOMM channel for the connection +- channel 1; ++# channel 1; + + # Description of the connection +- comment "Example Bluetooth device"; +-} ++# comment "Example Bluetooth device"; ++#} --- bluez-utils-2.25.orig/debian/patches/005_l2ping_section.patch +++ bluez-utils-2.25/debian/patches/005_l2ping_section.patch @@ -0,0 +1,8 @@ +--- bluez-utils-2.4.orig/tools/l2ping.1 2004-01-15 20:43:05.000000000 +0000 ++++ bluez-utils-2.4/tools/l2ping.1 2004-01-15 20:42:13.000000000 +0000 +@@ -1,4 +1,4 @@ +-.TH L2PING 1 "Jan 22 2002" BlueZ "Linux System Administration" ++.TH L2PING 8 "Jan 22 2002" BlueZ "Linux System Administration" + .SH NAME + l2ping \- Send L2CAP echo request and receive answer + .SH SYNOPSIS --- bluez-utils-2.25.orig/debian/patches/002_hcid_conf_defaults.patch +++ bluez-utils-2.25/debian/patches/002_hcid_conf_defaults.patch @@ -0,0 +1,20 @@ +--- hcid/hcid.conf.orig 2004-05-26 12:47:42.000000000 +0100 ++++ hcid/hcid.conf 2004-05-26 12:50:43.000000000 +0100 +@@ -23,7 +23,7 @@ + pairing multi; + + # PIN helper +- pin_helper /usr/bin/bluepin; ++ pin_helper /usr/bin/pinwrapper; + + # D-Bus PIN helper + #dbus_pin_helper; +@@ -34,7 +34,7 @@ + # Local device name + # %d - device id + # %h - host name +- name "BlueZ (%d)"; ++ name "%h-%d"; + + # Local device class + class 0x100; --- bluez-utils-2.25.orig/debian/patches/006_xsims.patch +++ bluez-utils-2.25/debian/patches/006_xsims.patch @@ -0,0 +1,45 @@ +--- bluez-utils-2.7-old/scripts/bluetooth.init 2004-05-09 13:39:43.000000000 +0300 ++++ bluez-utils-2.7/scripts/bluetooth.init 2004-07-16 23:45:58.000000000 +0300 +@@ -45,7 +45,7 @@ + case "$1" in + start) + echo -n "Starting $DESC:" +- if $HCID_ENABLE && [ -x "$HCID_EXEC" -a -f "$HCID_CONFIG" ] ; then ++ if $HCID_ENABLE && [ -x "$HCID_EXEC" ] && [ -f "$HCID_CONFIG" ] ; then + $HCID_EXEC -f $HCID_CONFIG + echo -n " $HCID_NAME" + fi +@@ -61,15 +61,15 @@ + $HID2HCI_EXEC --tohci > /dev/null 2>&1 || true + echo -n " $HID2HCI_NAME" + fi +- if $RFCOMM_ENABLE && [ -x "$RFCOMM_EXEC" -a -f "$RFCOMM_CONFIG" ] ; then ++ if $RFCOMM_ENABLE && [ -x "$RFCOMM_EXEC" ] && [ -f "$RFCOMM_CONFIG" ] ; then + $RFCOMM_EXEC -f $RFCOMM_CONFIG bind all || true + echo -n " $RFCOMM_NAME" + fi +- if $DUND_ENABLE && [ -x "$DUND_EXEC" -a -n "$DUND_OPTIONS" ] ; then ++ if $DUND_ENABLE && [ -x "$DUND_EXEC" ] && [ -n "$DUND_OPTIONS" ] ; then + $DUND_EXEC $DUND_OPTIONS + echo -n " $DUND_NAME" + fi +- if $PAND_ENABLE && [ -x "$PAND_EXEC" -a -n "$PAND_OPTIONS" ] ; then ++ if $PAND_ENABLE && [ -x "$PAND_EXEC" ] && [ -n "$PAND_OPTIONS" ] ; then + $PAND_EXEC $PAND_OPTIONS + echo -n " $PAND_NAME" + fi +diff -ur bluez-utils-2.7-old/test/hsplay bluez-utils-2.7/test/hsplay +--- bluez-utils-2.7-old/test/hsplay 2004-05-09 13:39:43.000000000 +0300 ++++ bluez-utils-2.7/test/hsplay 2004-07-16 23:44:59.000000000 +0300 +@@ -9,7 +9,7 @@ + HSTEST="./hstest" + fi + +-if [ -z "$1" -o -z "$2" ] ++if [ -z "$1" ] || [ -z "$2" ] + then + echo -e "Usage:\n\thsplay [channel]" + exit + + + --- bluez-utils-2.25.orig/debian/patches/007_hcid_typo.patch +++ bluez-utils-2.25/debian/patches/007_hcid_typo.patch @@ -0,0 +1,11 @@ +--- hcid/security.c.orig 2005-12-26 15:32:00.116000000 +0100 ++++ hcid/security.c 2005-12-26 15:32:11.096000000 +0100 +@@ -853,7 +853,7 @@ + if (!chan) + return; + +- syslog(LOG_INFO, "Stoping security manager %d", hdev); ++ syslog(LOG_INFO, "Stopping security manager %d", hdev); + + /* this is a bit sneaky. closing the fd will cause the event + loop to call us right back with G_IO_NVAL set, at which --- bluez-utils-2.25.orig/debian/patches/003_hcid_conf_addition.patch +++ bluez-utils-2.25/debian/patches/003_hcid_conf_addition.patch @@ -0,0 +1,14 @@ +Index: hcid/hcid.conf.5 +=================================================================== +--- hcid/hcid.conf.5 (revision 136) ++++ hcid/hcid.conf.5 (working copy) +@@ -49,6 +49,9 @@ + \fBpin_helper\fP "\fIfile\fP" + + The path to the PIN helper application. The default is "/bin/bluepin". ++The PIN helper is invoked with the direction of request (in/out), the bluetooth ++destination address and the device name as parameters. ++(e.g. /bin/bluepin out aa:bb:cc:dd:ee:ff "my device") + The following output is expected from the PIN helper: + + PIN:12345678 --- bluez-utils-2.25.orig/debian/patches/004_rfcomm_usage.patch +++ bluez-utils-2.25/debian/patches/004_rfcomm_usage.patch @@ -0,0 +1,11 @@ +--- bluez-utils-2.4.orig/rfcomm/main.c 2003-04-15 21:20:58.000000000 +0200 ++++ bluez-utils-2.4/rfcomm/main.c 2004-01-15 15:03:32.000000000 +0100 +@@ -532,6 +532,8 @@ + printf("Options:\n" + "\t-i [hciX|bdaddr] Local HCI device or BD Address\n" + "\t-h, --help Display help\n" ++ "\t-r, --raw Use tty RAW mode\n" ++ "\t-f, --config [file] Specify alternate config file\n" + "\t-a Show all devices (default)\n" + "\n"); + --- bluez-utils-2.25.orig/debian/patches/003_manpages.patch +++ bluez-utils-2.25/debian/patches/003_manpages.patch @@ -0,0 +1,462 @@ +--- tools/hciattach.8.orig 2005-12-20 14:13:27.952000000 +0100 ++++ tools/hciattach.8 2005-12-20 14:13:45.972000000 +0100 +@@ -3,44 +3,41 @@ + hciattach \- attach serial devices via UART HCI to BlueZ stack + .SH SYNOPSIS + .B hciattach +-[ -n ] [ -p ] [ -t timeout ] < ++.RB [\| \-n \|] ++.RB [\| \-p \|] ++.RB [\| \-t ++.IR timeout \|] + .I tty +-> < +-.I type +-| +-.I id +-> [ ++.IR type \||\| id + .I speed +-] [ + .I flow +-] + .SH DESCRIPTION + .LP + Hciattach is used to attach a serial UART to the Bluetooth stack as HCI + transport interface. + .SH OPTIONS + .TP +-.BI -n ++.B \-n + Don't detach from controlling terminal. + .TP +-.BI -p ++.B \-p + Print the PID when detaching. + .TP +-.BI -t timeout ++.BI \-t " timeout" + Specify an initialization timeout. (Default is 5 seconds.) + .TP +-.I ++.I tty + This specifies the serial device to attach. A leading + .B /dev + can be omitted. Examples: + .B /dev/ttyS1 + .B ttyS2 + .TP +-.I ++.IR type \||\| id + The +-.B type ++.I type + or +-.B id ++.I id + of the Bluetooth device that is to be attached, i.e. vendor or other device + specific identifier. Currently supported types are + .RS +@@ -48,45 +45,45 @@ + .B type + .B description + .TP +-any ++.B any + Unspecified HCI_UART interface, no vendor specific options + .TP +-ericsson ++.B ericsson + Ericsson based modules + .TP +-digi ++.B digi + Digianswer based cards + .TP +-xircom ++.B xircom + Xircom PCMCIA cards: Credit Card Adapter and Real Port Adapter + .TP +-csr ++.B csr + CSR Casira serial adapter or BrainBoxes serial dongle (BL642) + .TP +-bboxes ++.B bboxes + BrainBoxes PCMCIA card (BL620) + .TP +-swave ++.B swave + Silicon Wave kits + .TP +-bcsp ++.B bcsp + Serial adapters using CSR chips with BCSP serial protocol + .RE + + Supported IDs are (manufacturer id, product id) + .RS + .TP +-0x0105, 0x080a ++.B 0x0105, 0x080a + Xircom PCMCIA cards: Credit Card Adapter and Real Port Adapter + .TP +-0x0160, 0x0002 ++.B 0x0160, 0x0002 + BrainBoxes PCMCIA card (BL620) + .RE + + .TP +-.I ++.I speed + The +-.B speed ++.I speed + specifies the UART speed to use. Baudrates higher than 115.200bps require + vendor specific initializations that are not implemented for all types of + devices. In general the following speeds are supported: +@@ -96,9 +93,9 @@ + Supported vendor devices are automatically initialised to their respective + best settings. + .TP +-.I ++.I flow + If the keyword +-.B flow ++.I flow + is appended to the list of options then hardware flow control is forced on + the serial link ( + .B CRTSCTS +--- tools/hciconfig.8.orig 2005-11-06 23:44:47.859378000 +0100 ++++ tools/hciconfig.8 2005-12-20 14:13:45.976000000 +0100 +@@ -2,89 +2,95 @@ + .SH NAME + hciconfig \- configure Bluetooth devices + .SH SYNOPSIS +-.B hciconfig -h ++.B hciconfig ++.B \-h + .br +-.B hciconfig [-a] ++.B hciconfig ++.RB [\| \-a \|] + .br +-.B hciconfig [-a] [command [command parameters]] ++.B hciconfig ++.RB [\| \-a \|] ++.RI [\| command ++.RI [\| "command parameters" \|]\|] + + .SH DESCRIPTION + .LP +-.B +-hciconfig +-is used to configure Bluetooth devices. is the name of a Bluetooth +-device installed in the system. If is not given, +-.B +-hciconfig ++.B hciconfig ++is used to configure Bluetooth devices. ++.I hciX ++is the name of a Bluetooth device installed in the system. If ++.I hciX ++is not given, ++.B hciconfig + prints name and basic information about all the Bluetooth devices installed in +-the system. If is given but no command is given, +-it prints basic information on device only. Basic information is ++the system. If ++.I hciX ++is given but no command is given, it prints basic information on device ++.I hciX ++only. Basic information is + interface type, BD address, ACL MTU, SCO MTU, flags (up, init, running, raw, + page scan enabled, inquiry scan enabled, inquiry, authentication enabled, + encryption enabled). + .SH OPTIONS + .TP +-.BI -h ++.B \-h, \-\-help + Gives a list of possible commands. + .TP +-.BI -a ++.B \-a, \-\-all + Other than the basic info, print features, packet type, link policy, link mode, + name, class, version. + .SH COMMANDS + .TP +-.BI up ++.B up + Open and initialize HCI device. + .TP +-.BI down ++.B down + Close HCI device. + .TP +-.BI reset ++.B reset + Reset HCI device. + .TP +-.BI rstat ++.B rstat + Reset statistic counters. + .TP +-.BI auth ++.B auth + Enable authentication (sets device to security mode 3). + .TP +-.BI noauth ++.B noauth + Disable authentication. + .TP +-.BI encrypt ++.B encrypt + Enable encryption (sets device to security mode 3). + .TP +-.BI noencrypt ++.B noencrypt + Disable encryption. + .TP +-.BI secmgr ++.B secmgr + Enable security manager (current kernel support is limited). + .TP +-.BI nosecmgr ++.B nosecmgr + Disable security manager. + .TP +-.BI piscan ++.B piscan + Enable page and inquiry scan. + .TP +-.BI noscan ++.B noscan + Disable page and inquiry scan. + .TP +-.BI iscan ++.B iscan + Enable inquiry scan, disable page scan. + .TP +-.BI pscan ++.B pscan + Enable page scan, disable inquiry scan. + .TP +-.BI ptype " [type]" ++\fBptype\fP [\fItype\fP] + With no +-.I +-type ++.I type + , displays the current packet types. Otherwise, all the packet types specified + by +-.I +-type ++.I type + are set. +-.I +-type ++.I type + is a comma-separated list of packet types, where the possible packet types are + .BR DM1 , + .BR DM3 , +@@ -117,8 +123,7 @@ + .IR voice , + prints voice setting. Otherwise, sets voice setting to + .IR voice . +-.I +-voice ++.I voice + is a 16-bit hex number describing the voice setting. + .TP + .BI iac " [iac]" +@@ -145,9 +150,9 @@ + prints out the current inquiry scan type. Otherwise, sets inquiry scan type to + .IR type . + .TP +-.BI inqparms " [win:int]" ++\fBinqparams\fP [\fIwin\fP:\fIint\fP] + With no +-.IR win:int , ++.IR win : int , + prints inquiry scan window and interval. Otherwise, sets inquiry scan window + to + .I win +@@ -155,23 +160,20 @@ + .I int + slots. + .TP +-.BI pageparms " [win:int]" ++\fBpageparms\fP [\fIwin\fP:\fIint\fP] + With no +-.IR win:int , ++.IR win : int , + prints page scan window and interval. Otherwise, sets page scan window to +-.I +-win ++.I win + slots and page scan interval to +-.I +-int ++.I int + slots. + .TP + .BI pageto " [to]" + With no + .IR to , + prints page timeout. Otherwise, sets page timeout +-to +-.I ++to .I + to + slots. + .TP +@@ -181,19 +183,16 @@ + prints out the current AFH mode. Otherwise, sets AFH mode to + .IR mode . + .TP +-.BI aclmtu " " ++\fBaclmtu\fP \fImtu\fP:\fIpkt\fP + Sets ACL MTU to + to +-.I +-mtu ++.I mtu + bytes and ACL buffer size to +-.I +-pkt ++.I pkt + packets. + .TP +-.BI scomtu " " ++\fBscomtu\fP \fImtu\fP:\fIpkt\fP + Sets SCO MTU to +-to + .I mtu + bytes and SCO buffer size to + .I pkt +@@ -223,43 +222,34 @@ + .TP + .BI lm " [mode]" + With no +-.I +-mode ++.I mode + , prints link mode. +-.B +-MASTER ++.B MASTER + or +-.B +-SLAVE ++.B SLAVE + mean, respectively, to ask to become master or to remain slave when a + connection request comes in. The additional keyword +-.B +-ACCEPT ++.B ACCEPT + means that baseband connections will be accepted even if there are no + listening + .I AF_BLUETOOTH + sockets. + .I mode + is +-.B +-NONE ++.B NONE + or a comma-separated list of keywords, where possible keywords are +-.B +-MASTER ++.B MASTER + and + .B "ACCEPT" . +-.B +-NONE ++.B NONE + sets link policy to the default behaviour of remaining slave and not accepting + baseband connections when there are no listening + .I AF_BLUETOOTH + sockets. If +-.B +-MASTER ++.B MASTER + is present, the device will ask to become master if a connection request comes + in. If +-.B +-ACCEPT ++.B ACCEPT + is present, the device will accept baseband connections even when there are no + listening + .I AF_BLUETOOTH +--- tools/l2ping.1.orig 2005-12-20 14:13:39.272000000 +0100 ++++ tools/l2ping.1 2005-12-20 14:13:45.976000000 +0100 +@@ -3,50 +3,48 @@ + l2ping \- Send L2CAP echo request and receive answer + .SH SYNOPSIS + .B l2ping +-[ +-.I -i +-] [ +-.I -s size +-] [ +-.I -c count +-] [ +-.I -t timeout +-] [ +-.I -f +-] < ++.RB [\| \-i ++.IR \|] ++.RB [\| \-s ++.IR size \|] ++.RB [\| \-c ++.IR count \|] ++.RB [\| \-t ++.IR timeout \|] ++.RB [\| \-f \|] + .I bd_addr +-> ++ + .SH DESCRIPTION + .LP + L2ping sends a L2CAP echo request to the Bluetooth MAC address +-.B bd_addr ++.I bd_addr + given in dotted hex notation. + .SH OPTIONS + .TP +-.I -i " " ++.BI \-i " " + The command is applied to device +-.I ++.BI + hciX + , which must be the name of an installed Bluetooth device (X = 0, 1, 2, ...) + If not specified, the command will be sent to the first available Bluetooth + device. + .TP +-.I -s size ++.BI \-s " size" + The +-.B size ++.I size + of the data packets to be sent. + .TP +-.I -c count ++.BI \-c " count" + Send +-.B count ++.I count + number of packets then exit. + .TP +-.I -c \fBtimeout\fP ++.BI \-t " timeout" + Wait +-.B \fBtimeout\fP ++.I timeout + seconds for the response. + .TP +-.I -f ++.B \-f + Kind of flood ping. Use with care! It reduces the delay time between packets + to 0. + .TP --- bluez-utils-2.25.orig/debian/devfs-devices +++ bluez-utils-2.25/debian/devfs-devices @@ -0,0 +1,262 @@ +# devices file +# format: name [bc] major minor uid gid mode +# or: directory-name d "" "" uid gid mode +vhci c 10 250 root root 0660 +bluetooth d "" "" root dialout 0770 +bluetooth/rfcomm d "" "" root dialout 0770 +bluetooth/rfcomm/0 c 216 0 root dialout 0660 +bluetooth/rfcomm/1 c 216 1 root dialout 0660 +bluetooth/rfcomm/2 c 216 2 root dialout 0660 +bluetooth/rfcomm/3 c 216 3 root dialout 0660 +bluetooth/rfcomm/4 c 216 4 root dialout 0660 +bluetooth/rfcomm/5 c 216 5 root dialout 0660 +bluetooth/rfcomm/6 c 216 6 root dialout 0660 +bluetooth/rfcomm/7 c 216 7 root dialout 0660 +bluetooth/rfcomm/8 c 216 8 root dialout 0660 +bluetooth/rfcomm/9 c 216 9 root dialout 0660 +bluetooth/rfcomm/10 c 216 10 root dialout 0660 +bluetooth/rfcomm/11 c 216 11 root dialout 0660 +bluetooth/rfcomm/12 c 216 12 root dialout 0660 +bluetooth/rfcomm/13 c 216 13 root dialout 0660 +bluetooth/rfcomm/14 c 216 14 root dialout 0660 +bluetooth/rfcomm/15 c 216 15 root dialout 0660 +bluetooth/rfcomm/16 c 216 16 root dialout 0660 +bluetooth/rfcomm/17 c 216 17 root dialout 0660 +bluetooth/rfcomm/18 c 216 18 root dialout 0660 +bluetooth/rfcomm/19 c 216 19 root dialout 0660 +bluetooth/rfcomm/20 c 216 20 root dialout 0660 +bluetooth/rfcomm/21 c 216 21 root dialout 0660 +bluetooth/rfcomm/22 c 216 22 root dialout 0660 +bluetooth/rfcomm/23 c 216 23 root dialout 0660 +bluetooth/rfcomm/24 c 216 24 root dialout 0660 +bluetooth/rfcomm/25 c 216 25 root dialout 0660 +bluetooth/rfcomm/26 c 216 26 root dialout 0660 +bluetooth/rfcomm/27 c 216 27 root dialout 0660 +bluetooth/rfcomm/28 c 216 28 root dialout 0660 +bluetooth/rfcomm/29 c 216 29 root dialout 0660 +bluetooth/rfcomm/30 c 216 30 root dialout 0660 +bluetooth/rfcomm/31 c 216 31 root dialout 0660 +bluetooth/rfcomm/32 c 216 32 root dialout 0660 +bluetooth/rfcomm/33 c 216 33 root dialout 0660 +bluetooth/rfcomm/34 c 216 34 root dialout 0660 +bluetooth/rfcomm/35 c 216 35 root dialout 0660 +bluetooth/rfcomm/36 c 216 36 root dialout 0660 +bluetooth/rfcomm/37 c 216 37 root dialout 0660 +bluetooth/rfcomm/38 c 216 38 root dialout 0660 +bluetooth/rfcomm/39 c 216 39 root dialout 0660 +bluetooth/rfcomm/40 c 216 40 root dialout 0660 +bluetooth/rfcomm/41 c 216 41 root dialout 0660 +bluetooth/rfcomm/42 c 216 42 root dialout 0660 +bluetooth/rfcomm/43 c 216 43 root dialout 0660 +bluetooth/rfcomm/44 c 216 44 root dialout 0660 +bluetooth/rfcomm/45 c 216 45 root dialout 0660 +bluetooth/rfcomm/46 c 216 46 root dialout 0660 +bluetooth/rfcomm/47 c 216 47 root dialout 0660 +bluetooth/rfcomm/48 c 216 48 root dialout 0660 +bluetooth/rfcomm/49 c 216 49 root dialout 0660 +bluetooth/rfcomm/50 c 216 50 root dialout 0660 +bluetooth/rfcomm/51 c 216 51 root dialout 0660 +bluetooth/rfcomm/52 c 216 52 root dialout 0660 +bluetooth/rfcomm/53 c 216 53 root dialout 0660 +bluetooth/rfcomm/54 c 216 54 root dialout 0660 +bluetooth/rfcomm/55 c 216 55 root dialout 0660 +bluetooth/rfcomm/56 c 216 56 root dialout 0660 +bluetooth/rfcomm/57 c 216 57 root dialout 0660 +bluetooth/rfcomm/58 c 216 58 root dialout 0660 +bluetooth/rfcomm/59 c 216 59 root dialout 0660 +bluetooth/rfcomm/60 c 216 60 root dialout 0660 +bluetooth/rfcomm/61 c 216 61 root dialout 0660 +bluetooth/rfcomm/62 c 216 62 root dialout 0660 +bluetooth/rfcomm/63 c 216 63 root dialout 0660 +bluetooth/rfcomm/64 c 216 64 root dialout 0660 +bluetooth/rfcomm/65 c 216 65 root dialout 0660 +bluetooth/rfcomm/66 c 216 66 root dialout 0660 +bluetooth/rfcomm/67 c 216 67 root dialout 0660 +bluetooth/rfcomm/68 c 216 68 root dialout 0660 +bluetooth/rfcomm/69 c 216 69 root dialout 0660 +bluetooth/rfcomm/70 c 216 70 root dialout 0660 +bluetooth/rfcomm/71 c 216 71 root dialout 0660 +bluetooth/rfcomm/72 c 216 72 root dialout 0660 +bluetooth/rfcomm/73 c 216 73 root dialout 0660 +bluetooth/rfcomm/74 c 216 74 root dialout 0660 +bluetooth/rfcomm/75 c 216 75 root dialout 0660 +bluetooth/rfcomm/76 c 216 76 root dialout 0660 +bluetooth/rfcomm/77 c 216 77 root dialout 0660 +bluetooth/rfcomm/78 c 216 78 root dialout 0660 +bluetooth/rfcomm/79 c 216 79 root dialout 0660 +bluetooth/rfcomm/80 c 216 80 root dialout 0660 +bluetooth/rfcomm/81 c 216 81 root dialout 0660 +bluetooth/rfcomm/82 c 216 82 root dialout 0660 +bluetooth/rfcomm/83 c 216 83 root dialout 0660 +bluetooth/rfcomm/84 c 216 84 root dialout 0660 +bluetooth/rfcomm/85 c 216 85 root dialout 0660 +bluetooth/rfcomm/86 c 216 86 root dialout 0660 +bluetooth/rfcomm/87 c 216 87 root dialout 0660 +bluetooth/rfcomm/88 c 216 88 root dialout 0660 +bluetooth/rfcomm/89 c 216 89 root dialout 0660 +bluetooth/rfcomm/90 c 216 90 root dialout 0660 +bluetooth/rfcomm/91 c 216 91 root dialout 0660 +bluetooth/rfcomm/92 c 216 92 root dialout 0660 +bluetooth/rfcomm/93 c 216 93 root dialout 0660 +bluetooth/rfcomm/94 c 216 94 root dialout 0660 +bluetooth/rfcomm/95 c 216 95 root dialout 0660 +bluetooth/rfcomm/96 c 216 96 root dialout 0660 +bluetooth/rfcomm/97 c 216 97 root dialout 0660 +bluetooth/rfcomm/98 c 216 98 root dialout 0660 +bluetooth/rfcomm/99 c 216 99 root dialout 0660 +bluetooth/rfcomm/100 c 216 100 root dialout 0660 +bluetooth/rfcomm/101 c 216 101 root dialout 0660 +bluetooth/rfcomm/102 c 216 102 root dialout 0660 +bluetooth/rfcomm/103 c 216 103 root dialout 0660 +bluetooth/rfcomm/104 c 216 104 root dialout 0660 +bluetooth/rfcomm/105 c 216 105 root dialout 0660 +bluetooth/rfcomm/106 c 216 106 root dialout 0660 +bluetooth/rfcomm/107 c 216 107 root dialout 0660 +bluetooth/rfcomm/108 c 216 108 root dialout 0660 +bluetooth/rfcomm/109 c 216 109 root dialout 0660 +bluetooth/rfcomm/110 c 216 110 root dialout 0660 +bluetooth/rfcomm/111 c 216 111 root dialout 0660 +bluetooth/rfcomm/112 c 216 112 root dialout 0660 +bluetooth/rfcomm/113 c 216 113 root dialout 0660 +bluetooth/rfcomm/114 c 216 114 root dialout 0660 +bluetooth/rfcomm/115 c 216 115 root dialout 0660 +bluetooth/rfcomm/116 c 216 116 root dialout 0660 +bluetooth/rfcomm/117 c 216 117 root dialout 0660 +bluetooth/rfcomm/118 c 216 118 root dialout 0660 +bluetooth/rfcomm/119 c 216 119 root dialout 0660 +bluetooth/rfcomm/120 c 216 120 root dialout 0660 +bluetooth/rfcomm/121 c 216 121 root dialout 0660 +bluetooth/rfcomm/122 c 216 122 root dialout 0660 +bluetooth/rfcomm/123 c 216 123 root dialout 0660 +bluetooth/rfcomm/124 c 216 124 root dialout 0660 +bluetooth/rfcomm/125 c 216 125 root dialout 0660 +bluetooth/rfcomm/126 c 216 126 root dialout 0660 +bluetooth/rfcomm/127 c 216 127 root dialout 0660 +bluetooth/rfcomm/128 c 216 128 root dialout 0660 +bluetooth/rfcomm/129 c 216 129 root dialout 0660 +bluetooth/rfcomm/130 c 216 130 root dialout 0660 +bluetooth/rfcomm/131 c 216 131 root dialout 0660 +bluetooth/rfcomm/132 c 216 132 root dialout 0660 +bluetooth/rfcomm/133 c 216 133 root dialout 0660 +bluetooth/rfcomm/134 c 216 134 root dialout 0660 +bluetooth/rfcomm/135 c 216 135 root dialout 0660 +bluetooth/rfcomm/136 c 216 136 root dialout 0660 +bluetooth/rfcomm/137 c 216 137 root dialout 0660 +bluetooth/rfcomm/138 c 216 138 root dialout 0660 +bluetooth/rfcomm/139 c 216 139 root dialout 0660 +bluetooth/rfcomm/140 c 216 140 root dialout 0660 +bluetooth/rfcomm/141 c 216 141 root dialout 0660 +bluetooth/rfcomm/142 c 216 142 root dialout 0660 +bluetooth/rfcomm/143 c 216 143 root dialout 0660 +bluetooth/rfcomm/144 c 216 144 root dialout 0660 +bluetooth/rfcomm/145 c 216 145 root dialout 0660 +bluetooth/rfcomm/146 c 216 146 root dialout 0660 +bluetooth/rfcomm/147 c 216 147 root dialout 0660 +bluetooth/rfcomm/148 c 216 148 root dialout 0660 +bluetooth/rfcomm/149 c 216 149 root dialout 0660 +bluetooth/rfcomm/150 c 216 150 root dialout 0660 +bluetooth/rfcomm/151 c 216 151 root dialout 0660 +bluetooth/rfcomm/152 c 216 152 root dialout 0660 +bluetooth/rfcomm/153 c 216 153 root dialout 0660 +bluetooth/rfcomm/154 c 216 154 root dialout 0660 +bluetooth/rfcomm/155 c 216 155 root dialout 0660 +bluetooth/rfcomm/156 c 216 156 root dialout 0660 +bluetooth/rfcomm/157 c 216 157 root dialout 0660 +bluetooth/rfcomm/158 c 216 158 root dialout 0660 +bluetooth/rfcomm/159 c 216 159 root dialout 0660 +bluetooth/rfcomm/160 c 216 160 root dialout 0660 +bluetooth/rfcomm/161 c 216 161 root dialout 0660 +bluetooth/rfcomm/162 c 216 162 root dialout 0660 +bluetooth/rfcomm/163 c 216 163 root dialout 0660 +bluetooth/rfcomm/164 c 216 164 root dialout 0660 +bluetooth/rfcomm/165 c 216 165 root dialout 0660 +bluetooth/rfcomm/166 c 216 166 root dialout 0660 +bluetooth/rfcomm/167 c 216 167 root dialout 0660 +bluetooth/rfcomm/168 c 216 168 root dialout 0660 +bluetooth/rfcomm/169 c 216 169 root dialout 0660 +bluetooth/rfcomm/170 c 216 170 root dialout 0660 +bluetooth/rfcomm/171 c 216 171 root dialout 0660 +bluetooth/rfcomm/172 c 216 172 root dialout 0660 +bluetooth/rfcomm/173 c 216 173 root dialout 0660 +bluetooth/rfcomm/174 c 216 174 root dialout 0660 +bluetooth/rfcomm/175 c 216 175 root dialout 0660 +bluetooth/rfcomm/176 c 216 176 root dialout 0660 +bluetooth/rfcomm/177 c 216 177 root dialout 0660 +bluetooth/rfcomm/178 c 216 178 root dialout 0660 +bluetooth/rfcomm/179 c 216 179 root dialout 0660 +bluetooth/rfcomm/180 c 216 180 root dialout 0660 +bluetooth/rfcomm/181 c 216 181 root dialout 0660 +bluetooth/rfcomm/182 c 216 182 root dialout 0660 +bluetooth/rfcomm/183 c 216 183 root dialout 0660 +bluetooth/rfcomm/184 c 216 184 root dialout 0660 +bluetooth/rfcomm/185 c 216 185 root dialout 0660 +bluetooth/rfcomm/186 c 216 186 root dialout 0660 +bluetooth/rfcomm/187 c 216 187 root dialout 0660 +bluetooth/rfcomm/188 c 216 188 root dialout 0660 +bluetooth/rfcomm/189 c 216 189 root dialout 0660 +bluetooth/rfcomm/190 c 216 190 root dialout 0660 +bluetooth/rfcomm/191 c 216 191 root dialout 0660 +bluetooth/rfcomm/192 c 216 192 root dialout 0660 +bluetooth/rfcomm/193 c 216 193 root dialout 0660 +bluetooth/rfcomm/194 c 216 194 root dialout 0660 +bluetooth/rfcomm/195 c 216 195 root dialout 0660 +bluetooth/rfcomm/196 c 216 196 root dialout 0660 +bluetooth/rfcomm/197 c 216 197 root dialout 0660 +bluetooth/rfcomm/198 c 216 198 root dialout 0660 +bluetooth/rfcomm/199 c 216 199 root dialout 0660 +bluetooth/rfcomm/200 c 216 200 root dialout 0660 +bluetooth/rfcomm/201 c 216 201 root dialout 0660 +bluetooth/rfcomm/202 c 216 202 root dialout 0660 +bluetooth/rfcomm/203 c 216 203 root dialout 0660 +bluetooth/rfcomm/204 c 216 204 root dialout 0660 +bluetooth/rfcomm/205 c 216 205 root dialout 0660 +bluetooth/rfcomm/206 c 216 206 root dialout 0660 +bluetooth/rfcomm/207 c 216 207 root dialout 0660 +bluetooth/rfcomm/208 c 216 208 root dialout 0660 +bluetooth/rfcomm/209 c 216 209 root dialout 0660 +bluetooth/rfcomm/210 c 216 210 root dialout 0660 +bluetooth/rfcomm/211 c 216 211 root dialout 0660 +bluetooth/rfcomm/212 c 216 212 root dialout 0660 +bluetooth/rfcomm/213 c 216 213 root dialout 0660 +bluetooth/rfcomm/214 c 216 214 root dialout 0660 +bluetooth/rfcomm/215 c 216 215 root dialout 0660 +bluetooth/rfcomm/216 c 216 216 root dialout 0660 +bluetooth/rfcomm/217 c 216 217 root dialout 0660 +bluetooth/rfcomm/218 c 216 218 root dialout 0660 +bluetooth/rfcomm/219 c 216 219 root dialout 0660 +bluetooth/rfcomm/220 c 216 220 root dialout 0660 +bluetooth/rfcomm/221 c 216 221 root dialout 0660 +bluetooth/rfcomm/222 c 216 222 root dialout 0660 +bluetooth/rfcomm/223 c 216 223 root dialout 0660 +bluetooth/rfcomm/224 c 216 224 root dialout 0660 +bluetooth/rfcomm/225 c 216 225 root dialout 0660 +bluetooth/rfcomm/226 c 216 226 root dialout 0660 +bluetooth/rfcomm/227 c 216 227 root dialout 0660 +bluetooth/rfcomm/228 c 216 228 root dialout 0660 +bluetooth/rfcomm/229 c 216 229 root dialout 0660 +bluetooth/rfcomm/230 c 216 230 root dialout 0660 +bluetooth/rfcomm/231 c 216 231 root dialout 0660 +bluetooth/rfcomm/232 c 216 232 root dialout 0660 +bluetooth/rfcomm/233 c 216 233 root dialout 0660 +bluetooth/rfcomm/234 c 216 234 root dialout 0660 +bluetooth/rfcomm/235 c 216 235 root dialout 0660 +bluetooth/rfcomm/236 c 216 236 root dialout 0660 +bluetooth/rfcomm/237 c 216 237 root dialout 0660 +bluetooth/rfcomm/238 c 216 238 root dialout 0660 +bluetooth/rfcomm/239 c 216 239 root dialout 0660 +bluetooth/rfcomm/240 c 216 240 root dialout 0660 +bluetooth/rfcomm/241 c 216 241 root dialout 0660 +bluetooth/rfcomm/242 c 216 242 root dialout 0660 +bluetooth/rfcomm/243 c 216 243 root dialout 0660 +bluetooth/rfcomm/244 c 216 244 root dialout 0660 +bluetooth/rfcomm/245 c 216 245 root dialout 0660 +bluetooth/rfcomm/246 c 216 246 root dialout 0660 +bluetooth/rfcomm/247 c 216 247 root dialout 0660 +bluetooth/rfcomm/248 c 216 248 root dialout 0660 +bluetooth/rfcomm/249 c 216 249 root dialout 0660 +bluetooth/rfcomm/250 c 216 250 root dialout 0660 +bluetooth/rfcomm/251 c 216 251 root dialout 0660 +bluetooth/rfcomm/252 c 216 252 root dialout 0660 +bluetooth/rfcomm/253 c 216 253 root dialout 0660 +bluetooth/rfcomm/254 c 216 254 root dialout 0660 +bluetooth/rfcomm/255 c 216 255 root dialout 0660 --- bluez-utils-2.25.orig/debian/pand.8 +++ bluez-utils-2.25/debian/pand.8 @@ -0,0 +1,59 @@ +.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.29. +.TH BlueZ "1" "February 2003" "PAN daemon" "User Commands" +.SH NAME +pand \- BlueZ Bluetooth PAN daemon +.SH DESCRIPTION +The pand PAN daemon allows your computer to connect to ethernet +networks using Bluetooth. +.SH SYNPOSIS +pand +.SH OPTIONS +.TP +\fB\-\-show\fR \fB\-\-list\fR \fB\-l\fR +Show active PAN connections +.TP +\fB\-\-listen\fR \fB\-s\fR +Listen for PAN connections +.TP +\fB\-\-connect\fR \fB\-c\fR +Create PAN connection +.TP +\fB\-\-search\fR \fB\-Q[duration]\fR +Search and connect +.TP +\fB\-\-kill\fR \fB\-k\fR +Kill PAN connection +.TP +\fB\-\-killall\fR \fB\-K\fR +Kill all PAN connections +.TP +\fB\-\-role\fR \fB\-r\fR +Local PAN role (PANU, NAP, GN) +.TP +\fB\-\-service\fR \fB\-d\fR +Remote PAN service (PANU, NAP, GN) +.TP +\fB\-\-device\fR \fB\-i\fR +Network interface name +.TP +\fB\-\-source\fR \fB\-S\fR +Source bdaddr +.TP +\fB\-\-nosdp\fR \fB\-D\fR +Disable SDP +.TP +\fB\-\-encrypt\fR \fB\-E\fR +Enable encryption +.TP +\fB\-\-master\fR \fB\-M\fR +Become the master of a piconet +.TP +\fB\-\-nodetach\fR \fB\-n\fR +Do not become a daemon +.TP +\fB\-\-persist\fR \fB\-p[interval]\fR +Persist mode +.TP +\fB\-\-cache\fR \fB\-C[valid]\fR +Cache addresses + --- bluez-utils-2.25.orig/debian/bluez-pcmcia-support.install +++ bluez-utils-2.25/debian/bluez-pcmcia-support.install @@ -0,0 +1 @@ +debian/tmp/etc/pcmcia/* --- bluez-utils-2.25.orig/debian/bluepin.1 +++ bluez-utils-2.25/debian/bluepin.1 @@ -0,0 +1,16 @@ +.TH BLUEPIN "1" "April 2002" "bluepin - bluetooth PIN helper" "User Commands" + +.SH NAME +bluepin \- bluetooth PIN helper + +.SH DESCRIPTION +.B bluepin +is used by +.BR hcid (8) +to ask the user for a PIN code when +pairing is attempted. +.PP +It does not make sense to run this command yourself. + +.SH SEE ALSO +.BR hcid (8) --- bluez-utils-2.25.orig/debian/lintian-overrides +++ bluez-utils-2.25/debian/lintian-overrides @@ -0,0 +1,2 @@ +bluez-utils: mknod-in-maintainer-script +bluez-utils: python-script-but-no-python-dep --- bluez-utils-2.25.orig/debian/modutils +++ bluez-utils-2.25/debian/modutils @@ -0,0 +1,10 @@ +# BlueZ modules +alias net-pf-31 bluez +alias bt-proto-0 l2cap +alias bt-proto-2 sco +alias bt-proto-3 rfcomm +alias bt-proto-4 bnep +alias bt-proto-5 cmtp +alias bt-proto-6 hidp +alias tty-ldisc-15 hci_uart +alias char-major-10-250 hci_vhci --- bluez-utils-2.25.orig/debian/dund.8 +++ bluez-utils-2.25/debian/dund.8 @@ -0,0 +1,49 @@ +.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.29. +.TH BlueZ "1" "February 2003" "DUN daemon version 0.5" "User Commands" +.SH NAME +dund \- BlueZ Bluetooth dial-up networking daemon +.SH DESCRIPTION +DUN daemon version 0.5 +.SH SYNOPSIS +dund +.SH OPTIONS +.TP +\fB\-\-show\fR \fB\-\-list\fR \fB\-l\fR +Show active DUN connections +.TP +\fB\-\-listen\fR \fB\-s\fR +Listen for DUN connections +.TP +\fB\-\-connect\fR \fB\-c\fR +Create DUN connection +.TP +\fB\-\-search\fR \fB\-Q[duration]\fR +Search and connect +.TP +\fB\-\-kill\fR \fB\-k\fR +Kill DUN connection +.TP +\fB\-\-killall\fR \fB\-K\fR +Kill all DUN connections +.TP +\fB\-\-channel\fR \fB\-C\fR +RFCOMM channel +.TP +\fB\-\-source\fR \fB\-S\fR +Source bdaddr +.TP +\fB\-\-sdp\fR \fB\-D\fR +Enable SDP +.TP +\fB\-\-encrypt\fR \fB\-E\fR +Enable encryption +.TP +\fB\-\-master\fR \fB\-M\fR +Become the master of a piconet +.TP +\fB\-\-nodetach\fR \fB\-n\fR +Do not become a daemon +.TP +\fB\-\-persist\fR \fB\-p[interval]\fR +Persist mode + --- bluez-utils-2.25.orig/debian/bluez-utils.postinst +++ bluez-utils-2.25/debian/bluez-utils.postinst @@ -0,0 +1,105 @@ +#!/bin/sh + +# Move a conffile without triggering a dpkg question +mv_conffile() { + OLDCONFFILE="$1" + NEWCONFFILE="$2" + + if [ -e "$OLDCONFFILE" ]; then + echo "Preserving user changes to $NEWCONFFILE ..." + mv -f "$NEWCONFFILE" "$NEWCONFFILE".dpkg-new + mv -f "$OLDCONFFILE" "$NEWCONFFILE" + fi +} + +set -e +case "$1" in + configure) + # remove bluez-sdpd init, if present + if [ -f /etc/init.d/bluez-sdp ]; then + /usr/sbin/update-rc.d -f bluez-sdp remove + echo "To stop seeing this, remove the now redundant /etc/init.d/bluez-sdp script." + fi + # remove bluez-pan init, if present + if [ -f /etc/init.d/bluez-pan ]; then + /usr/sbin/update-rc.d -f bluez-pan remove + echo "To stop seeing this, remove the now redundant /etc/init.d/bluez-pan script." + echo "Also, bluez-pan is now part of bluez-utils. see /etc/default/bluez-utils for" + echo "more detail." + fi + + if [ -e /etc/init.d/bluez-utils ]; then + /usr/sbin/update-rc.d -f bluez-utils remove + # maybe a (medium/low debconf?) notice is best suited here + fi + + mv_conffile "/etc/init.d/bluez-utils" "/etc/init.d/bluetooth" + mv_conffile "/etc/default/bluez-utils" "/etc/default/bluetooth" + + + # update modules.conf + /sbin/update-modules >/dev/null 2>&1 + + # use MAKEDEV instead of the original bluez script below as per policy 10.6 + echo "Creating device nodes ..." + cd /dev && ./MAKEDEV bluetooth + + # Create BlueZ devices in /dev + # Originally by Marcel Holtmann + # Amended by Edd Dumbill for + # the Debian distribution and to support devfs +# +# VHCI_MAJOR=10 +# VHCI_MINOR=250 +# +# RFCOMM_MAJOR=216 +# +# # if devfs isn't mounted on /dev/ or we're not +# # using udev, then we need to create the device names +# +# if [ ! -e /dev/.devfsd -a ! -e /dev/.udevdb ]; then +# echo "Checking and creating device nodes ..." +# # +# # Create device for VHCI +# # +# if [ ! -c /dev/vhci ]; then +# mknod /dev/vhci c ${VHCI_MAJOR} ${VHCI_MINOR} +# chmod 660 /dev/vhci +# fi +# +# # +# # Create devices for RFCOMM +# # +# C=0; +# while [ $C -lt 256 ]; do +# if [ ! -c /dev/rfcomm$C ]; then +# mknod -m 660 /dev/rfcomm$C c ${RFCOMM_MAJOR} $C +# chgrp dialout /dev/rfcomm$C +# fi +# C=`expr $C + 1` +# done +# fi +# +# # handle the devfs case +# if [ -e /dev/.devfsd ]; then +# # tell devfs about the new files +# if [ -x /usr/sbin/update-devfsd ]; then +# echo "Updating devfsd configuration..." +# /usr/sbin/update-devfsd >/dev/null +# else +# echo "You have devfs enabled but no devfsd. This means that the" +# echo "RFCOMM device nodes cannot be checked and created if" +# echo "necessary. To make sure, please install the `devfsd'" +# echo "package and run `dpkg-reconfigure bluez-utils'." +# fi +# fi + + ;; + + *) + echo "postinst called with unknown argument \`$1'" >&2 + exit 0 + ;; +esac + +#DEBHELPER# --- bluez-utils-2.25.orig/debian/bluez-utils.bluetooth.default +++ bluez-utils-2.25/debian/bluez-utils.bluetooth.default @@ -0,0 +1,81 @@ +# Defaults for bluez-utils + +# This file supersedes /etc/default/bluez-pan. If +# that exists on your system, you should use this +# file instead and remove the old one. Until you +# do so, the contents of this file will be ignored. + +############ HIDD +# +# To have Bluetooth mouse and keyboard support, get the +# Linux 2.6.6 patch or better from bluez.org, and set +# HIDD_ENABLED to 1. +HIDD_ENABLED=0 +HIDD_OPTIONS="--master --server" +# to make hidd always use a particular interface, use something +# like this, substituting the bdaddr of the interface: +# HIDD_OPTIONS="-i AA:BB:CC:DD:EE:FF --server" +# +# remove '--master' if you're having trouble working with Ericsson +# T630 phones with hidd operational at the same time. + +############ COMPATIBILITY WITH OLD BLUEZ-PAN +# Compatibility: if old PAN config exists, use it +# rather than this file. +if test -f /etc/default/bluez-pan; then + . /etc/default/bluez-pan + return +fi +############ + +############ DUND +# +# Run dund -- this allows ppp logins. 1 for enabled, 0 for disabled. +DUND_ENABLED=0 + +# Arguments to dund: defaults to acting as a server +DUND_OPTIONS="--listen --persist" + +# Run dund --help to see the full array of options. +# Here are some examples: +# +# Connect to any nearby host offering access +# DUND_OPTIONS="--search" +# +# Connect to host 00:11:22:33:44:55 +# DUND_OPTIONS="--connect 00:11:22:33:44:55" +# +# Listen on channel 3 +# DUND_OPTIONS="--listen --channel 3" + +# Special consideration is needed for certain devices. Microsoft +# users see the --msdun option. Ericsson P800 users will need to +# listen on channel 3 and also run 'sdptool add --channel=3 SP' + +############ PAND +# +# Run pand -- ethernet: creates new network interfaces bnep +# that can be configured in /etc/network/interfaces +# set to 1 for enabled, 0 for disabled +PAND_ENABLED=0 + +# Arguments to pand +# Read the PAN howto for ways to set this up +# http://bluez.sourceforge.net/contrib/HOWTO-PAN +PAND_OPTIONS="" + +# example pand lines +# +# Act as the controller of an ad-hoc network +# PAND_OPTIONS="--listen --role GN" +# +# Act as a network access point: routes to other networks +# PAND_OPTIONS="--listen --role NAP" +# +# Act as a client of an ad-hoc controller with number 00:11:22:33:44:55 +# PAND_OPTIONS="--role PANU --connect 00:11:22:33:44:55" +# +# Connect to any nearby network controller (access point or ad-hoc) +# PAND_OPTIONS="--role PANU --search" + + --- bluez-utils-2.25.orig/debian/bluez-utils.manpages +++ bluez-utils-2.25/debian/bluez-utils.manpages @@ -0,0 +1,5 @@ +debian/hcid.8 +debian/hidd.1 +debian/bluepin.1 +debian/dund.8 +debian/pand.8 --- bluez-utils-2.25.orig/debian/NEWS +++ bluez-utils-2.25/debian/NEWS @@ -0,0 +1,106 @@ +bluez-utils (2.24-1) unstable; urgency=low + + this version moves /etc/{init.d,default}/bluez-utils to + /etc/{init.d,default}/bluetooth for LSB compilance. + If local modifications are detected the new files will be installed with + the ".dpkg-new" suffix + + -- Filippo Giunchedi Mon, 9 Jan 2006 14:33:48 +0100 + +bluez-utils (2.19-1) unstable; urgency=high + + * Includes new D-BUS support: sends signals for inquiry results and + remote name resolves. + + * Also adds support for device-specific SDP records. + + -- Edd Dumbill Fri, 19 Aug 2005 01:12:02 +0100 + +bluez-utils (2.9-1) unstable; urgency=low + + * This release improves input device support: EPoX keyboards and + their new HID presenters should now work correctly in report + protocol mode. + + -- Edd Dumbill Sun, 8 Aug 2004 15:19:24 +0100 + +bluez-utils (2.8-1) unstable; urgency=low + + * Users of dongles with HID proxy capability (this is where the dongle + pretends to be a keyboard and mouse until it is switched into Bluetooth + mode, allowing Bluetooth input devices to be used in BIOS etc.) are + now supported. The switch is made as part of the bluez-utils init + script. + + -- Edd Dumbill Mon, 14 Jun 2004 14:24:12 +0100 + +bluez-utils (2.7-1) experimental; urgency=low + + * Upstream has merged bluez-pan with this package. You should + remove the /etc/init.d/bluez-pan script, and use + /etc/default/bluez-utils to configure dund and pand, although + for the moment the old /etc/default/bluez-pan is also read. + + * This source package now has Bluetooth printing support, which + is built into the bluez-cups binary package. + + * DBUS support has been enabled in this build. To use it, add + 'dbus_pin_helper' into the options section, and comment out + the pin_helper. DBUS-aware pin helpers such as that in + bluez-pin will now be used. + + * Bluetooth HID devices (eg, mouse, keyboard) are now supported + for Linux 2.6.6 or better running the hidp patch from bluez.org. + If running these, set HIDD_ENABLED to 1 in /etc/default/bluez-utils + to enable support, then run hidd --connect to connect + to your keyboard or mouse. + + -- Edd Dumbill Wed, 26 May 2004 12:43:08 +0100 + +bluez-utils (2.6-1) experimental; urgency=low + + * Upstream has merged bluez-sdp with this package. The sdp tools + are now in this package. You should remove the /etc/init.d/bluez-sdp + script. + + * All tools from /sbin now live in /usr/sbin: hciattach hciconfig + hcid l2ping. + + -- Edd Dumbill Thu, 6 May 2004 11:58:16 +0100 + +bluez-utils (2.4-4) unstable; urgency=high + + * If you still use the old 'bluepin' PIN assistant: note it has moved + from /bin/ to /usr/bin/. You will need to update your hcid.conf + accordingly. Even better, install bluez-pin and use the helper from + there instead. + * hcitool has also moved to /usr/bin, and l2ping to /sbin. + + -- Edd Dumbill Wed, 15 Jan 2004 18:37:32 +0000 + +bluez-utils (2.4-3) unstable; urgency=low + + * If you're using devfsd and a recent Linux kernel (2.4.22 or later, or + 2.6.x), remove the file /etc/devfs/devices.d/bluez and run update-devfsd. + This will stop your system complaining when devfsd is started. This + package no longer installs that file, but you must remove it yourself. + If you need it in future, you can find it in /usr/share/doc/bluez-utils. + + -- Edd Dumbill Wed, 14 Jan 2004 21:14:35 +0000 + +bluez-utils (2.4-1) unstable; urgency=low + + * The rfcomm program has changed slightly: you now need a "bind yes" + in each entry in /etc/bluetooth/rfcomm.conf to ensure they are bound + at startup time. See man rfcomm for more details. + + -- Edd Dumbill Thu, 1 Jan 2004 18:38:35 +0100 + +bluez-utils (2.3-2) unstable; urgency=low + + * This package now depends on a new PIN helper bluez-pin. If you are + upgrading this package and want to use the new helper instead of the + default one (highly recommended) then alter your pin_helper line in + /etc/bluetooth/hcid.conf to specify /usr/bin/bluez-pin. + + -- Edd Dumbill Thu, 28 Aug 2003 12:38:35 +0100 --- bluez-utils-2.25.orig/debian/hcid.8 +++ bluez-utils-2.25/debian/hcid.8 @@ -0,0 +1,33 @@ +.\" This file was originally generated by help2man 1.27. +.TH HCID 8 "April 2002" "hcid - HCI daemon ver 1.0" "System management commands" + +.SH NAME +hcid \- Bluetooth Host Controller Interface Daemon + +.SH SYNOPSIS +.B hcid +[ +.B \-n +] [ +.B \-f +.I config-file +] + +.SH DESCRIPTION +This manual page documents briefly the +.B hcid +daemon, which manages all the Bluetooth devices. +.TP +.B \-n +Don't fork to run daemon in background. +.TP +.BI \-f\ config-file +Use alternate configuration file instead of + +.SH FILES +.TP +.I /etc/bluetooth/hcid.conf +Default location of the global configuration file. + +.SH AUTHOR +This manual page was written by Philipp Matthias Hahn for the Debian project (but may be used by others). --- bluez-utils-2.25.orig/debian/bluez-utils.dirs +++ bluez-utils-2.25/debian/bluez-utils.dirs @@ -0,0 +1 @@ +usr/bin --- bluez-utils-2.25.orig/debian/compat +++ bluez-utils-2.25/debian/compat @@ -0,0 +1 @@ +4 --- bluez-utils-2.25.orig/debian/bluez-utils.install +++ bluez-utils-2.25/debian/bluez-utils.install @@ -0,0 +1,13 @@ +debian/tmp/etc/bluetooth/hcid.conf +debian/tmp/etc/bluetooth/pin +debian/tmp/etc/bluetooth/rfcomm.conf +debian/tmp/etc/modutils/* +debian/tmp/etc/modprobe.d/* +debian/tmp/etc/devfs/* +debian/tmp/etc/dbus*/* +debian/tmp/usr/bin/* +debian/tmp/usr/sbin/* +debian/tmp/usr/share/man/man1/* +debian/tmp/usr/share/man/man5/* +debian/tmp/usr/share/man/man8/* +debian/tmp/usr/share/lintian/overrides/* --- bluez-utils-2.25.orig/debian/bluez-utils.bluetooth.init +++ bluez-utils-2.25/debian/bluez-utils.bluetooth.init @@ -0,0 +1,257 @@ +#! /bin/sh +### BEGIN INIT INFO +# Provides: bluetooth +# Short-Description: Start bluez bluetooth userspace daemons +### END INIT INFO +# +# bluez-utils Bluetooth subsystem starting and stopping +# +# originally from bluez's scripts/bluetooth.init +# +# Edd Dumbill +# LSB 3.0 compilance by Filippo Giunchedi +# +# startup control over dund and pand can be changed by +# editing /etc/default/bluez-utils + +PATH=/sbin:/bin:/usr/sbin:/usr/bin +DESC="Bluetooth services" + +HCID=/usr/sbin/hcid +HCIATTACH=/usr/sbin/hciattach +HCID_NAME=hcid + +HID2HCI=/usr/sbin/hid2hci + +UART_CONF=/etc/bluetooth/uart + +RFCOMM=/usr/bin/rfcomm +RFCOMM_NAME=rfcomm +RFCOMM_CONF=/etc/bluetooth/rfcomm.conf + +SDPD=/usr/sbin/sdpd +SDPD_NAME=sdpd + +DUND_DAEMON=/usr/bin/dund +DUND_NAME=dund +PAND_DAEMON=/usr/bin/pand +PAND_NAME=pand +HIDD_DAEMON=/usr/bin/hidd +HIDD_NAME=hidd + +DUND_ENABLED=0 +PAND_ENABLED=0 +HIDD_ENABLED=0 +DUND_OPTIONS="" +PAND_OPTIONS="" +HIDD_OPTIONS="--master --server" + +test -f /etc/default/bluetooth && . /etc/default/bluetooth +test -f /etc/default/rcS && . /etc/default/rcS + +. /lib/lsb/init-functions + +# test for essential daemons +test -x $HCID || exit 0 +test -x $HCIATTACH || exit 0 +test -x $RFCOMM || exit 0 +test -x $SDPD || exit 0 + +# disable nonessential daemons if not present +if test "$DUND_ENABLED" != "0"; then + if ! test -f $DUND_DAEMON; then + DUND_ENABLED=0 + fi +fi + +if test "$PAND_ENABLED" != "0"; then + if ! test -f $PAND_DAEMON; then + PAND_ENABLED=0 + fi +fi + +if test "$HIDD_ENABLED" != "0"; then + if ! test -f $HIDD_DAEMON; then + HIDD_ENABLED=0 + fi +fi + +set -e + +enable_hci_input() +{ + if [ "$VERBOSE" != no ]; then + log_success_msg "Switching on Bluetooth input devices..." + $HID2HCI --tohci + else + $HID2HCI --tohci >/dev/null 2>&1 + fi +} + +disable_hci_input() +{ + if [ "$VERBOSE" != no ]; then + log_success_msg "Switching Bluetooth input devices back to HID mode..." + $HID2HCI --tohid + else + $HID2HCI --tohid >/dev/null 2>&1 + fi +} + +start_pan() +{ + if test "$DUND_ENABLED" != "0"; then + start-stop-daemon --start --quiet --exec $DUND_DAEMON -- $DUND_OPTIONS + [ "$VERBOSE" != no ] && log_success_msg "Starting $DUND_NAME..." + + fi + if test "$PAND_ENABLED" != "0"; then + start-stop-daemon --start --quiet --exec $PAND_DAEMON -- $PAND_OPTIONS + [ "$VERBOSE" != no ] && log_success_msg "Starting $PAND_NAME..." + fi +} + + +stop_pan() +{ + if test "$DUND_ENABLED" != "0"; then + start-stop-daemon --stop --quiet --exec $DUND_DAEMON || true + [ "$VERBOSE" != no ] && log_success_msg "Stopping $DUND_NAME..." + fi + if test "$PAND_ENABLED" != "0"; then + start-stop-daemon --stop --quiet --exec $PAND_DAEMON || true + [ "$VERBOSE" != no ] && log_success_msg "Stopping $PAND_NAME..." + fi +} + +start_hid() +{ + if test "$HIDD_ENABLED" != "0"; then + start-stop-daemon --start --quiet --exec $HIDD_DAEMON -- $HIDD_OPTIONS + [ "$VERBOSE" != no ] && log_success_msg "Starting $HIDD_NAME..." + fi +} + +stop_hid() +{ + if test "$HIDD_ENABLED" != "0"; then + $HIDD_DAEMON --killall + start-stop-daemon --stop --quiet --exec $HIDD_DAEMON || true + [ "$VERBOSE" != no ] && log_success_msg "Stopping $HIDD_NAME..." + fi +} + +start_uarts() +{ + [ -f $HCIATTACH ] && [ -f $UART_CONF ] || return + grep -v '^#' $UART_CONF | while read i; do + if [ "$VERBOSE" != no ]; then + $HCIATTACH $i + else + $HCIATTACH $i >/dev/null 2>&1 + fi + done +} + +stop_uarts() +{ + killall hciattach > /dev/null 2>&1 || true +} + +start_rfcomm() +{ + if [ -x $RFCOMM ] && [ -f $RFCOMM_CONF ] ; then + # rfcomm must always succeed for now: users + # may not yet have an rfcomm-enabled kernel + if [ "$VERBOSE" != no ]; then + log_success_msg "Starting $RFCOMM_NAME..." + $RFCOMM -f $RFCOMM_CONF bind all || true + else + $RFCOMM -f $RFCOMM_CONF bind all >/dev/null 2>&1 || true + fi + fi +} + +stop_rfcomm() +{ + if [ -x $RFCOMM ] ; then + if [ "$VERBOSE" != no ]; then + log_success_msg "Stopping $RFCOMM_NAME..." + $RFCOMM unbind all || true + else + $RFCOMM unbind all >/dev/null 2>&1 || true + fi + fi +} + +restart_rfcomm() +{ + if [ -x $RFCOMM ] && [ -f $RFCOMM_CONF ] ; then + if [ "$VERBOSE" != no ]; then + log_success_msg "Restarting $RFCOMM_NAME..." + $RFCOMM unbind all || true + $RFCOMM -f $RFCOMM_CONF bind all || true + else + $RFCOMM unbind all >/dev/null 2>&1|| true + $RFCOMM -f $RFCOMM_CONF bind all >/dev/null 2>&1 || true + fi + fi +} + +case "$1" in + start) + log_daemon_msg "Starting $DESC" + + start-stop-daemon --start --quiet --exec $HCID || true + log_progress_msg "hcid" + start_uarts || true + + start-stop-daemon --start --quiet --exec $SDPD || true + log_progress_msg "sdpd" + + start_hid || true + enable_hci_input || true + start_rfcomm || true + start_pan || true + log_end_msg 0 + ;; + stop) + log_daemon_msg "Stopping $DESC" + stop_pan || true + stop_rfcomm || true + disable_hci_input || true + stop_hid || true + start-stop-daemon --stop --quiet --exec $SDPD || true + log_progress_msg "$SDPD_NAME" + start-stop-daemon --stop --quiet --exec $HCID || true + log_progress_msg "$HCID_NAME" + stop_uarts || true + log_end_msg 0 + ;; + restart|force-reload) + log_daemon_msg "Restarting $DESC" + stop_hid || true + stop_pan || true + start-stop-daemon --stop --quiet --exec $SDPD || true + start-stop-daemon --stop --quiet --exec $HCID || true + sleep 1 + start-stop-daemon --start --quiet --exec $HCID || true + start-stop-daemon --start --quiet --exec $SDPD || true + log_progress_msg "$HCID_NAME" + log_progress_msg "$SDPD_NAME" + start_pan || true + start_hid || true + restart_rfcomm + log_end_msg 0 + ;; + *) + N=/etc/init.d/bluetooth + # echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2 + echo "Usage: $N {start|stop|restart|force-reload}" >&2 + exit 1 + ;; +esac + +exit 0 + +# vim:noet --- bluez-utils-2.25.orig/debian/rules +++ bluez-utils-2.25/debian/rules @@ -0,0 +1,42 @@ +#!/usr/bin/make -f +# build rules for bluez-utils + +include /usr/share/cdbs/1/rules/buildcore.mk +include /usr/share/cdbs/1/rules/debhelper.mk +include /usr/share/cdbs/1/rules/simple-patchsys.mk +include /usr/share/cdbs/1/class/autotools.mk + +DEB_UPDATE_RCD_PARAMS = "start 25 2 3 4 5 . stop 74 0 1 6 ." +DEB_DH_INSTALLINIT_ARGS = "--name=bluetooth" + +DEB_CONFIGURE_EXTRA_FLAGS := --enable-pcmcia --enable-dbus --enable-cups --enable-hid2hci + +install/bluez-utils:: + # modutils config file + install -D -m 0644 debian/modutils \ + $(DEB_DESTDIR)/etc/modutils/bluez + install -D -m 0644 debian/modprobe.conf \ + $(DEB_DESTDIR)/etc/modprobe.d/bluez + + mv $(DEB_DESTDIR)/usr/share/man/man1/l2ping.1 \ + $(DEB_DESTDIR)/usr/share/man/man8/l2ping.8 + + # devfsd support + install -D -m 0644 debian/devfs-conf \ + $(DEB_DESTDIR)/etc/devfs/conf.d/bluez + + # lintian override + install -D -m 0644 debian/lintian-overrides \ + $(DEB_DESTDIR)/usr/share/lintian/overrides/bluez-utils + + # pinwrapper installation + install -D -m 0755 debian/pinwrapper \ + $(DEB_DESTDIR)/usr/bin/pinwrapper + + # have a sensible pin default, the upstream one 'BlueZ' + # cannot be typed on a phone keypad! + echo "1234" > $(DEB_DESTDIR)/etc/bluetooth/pin + +install/bluez-pcmcia-support:: + chmod a+x $(DEB_DESTDIR)/etc/pcmcia/bluetooth + --- bluez-utils-2.25.orig/debian/changelog +++ bluez-utils-2.25/debian/changelog @@ -0,0 +1,643 @@ +bluez-utils (2.25-1ubuntu1) edgy; urgency=low + + * merged from debian/unstable: + - updated debian/bluez-utils.bluetooth.init with our verbose + handling + - debian/patches/008_unsafe_pand_option.patch: re-added + - patches/002_hcid_conf_defaults.patch: use pinwrapper instead of bluez-pin + - don't build bluez-bcm203x + - build-dep on libbluetooth2-dev + + -- Michael Vogt Fri, 30 Jun 2006 15:46:52 +0200 + +bluez-utils (2.25-1) unstable; urgency=low + + * new upstream version + * install anything from /etc/dbus*/, thanks to Hendrik Sattler + (Closes: #284745) + * first remove dangling init.d links, then move /etc/init.d/bluez-utils to + bluetooth (Closes: #351330) + + -- Filippo Giunchedi Mon, 13 Feb 2006 22:31:26 +0100 + +bluez-utils (2.24-2) unstable; urgency=high + + * tight the dependency on lsb-base (>= 3.0-3) since we are using + log_daemon_msg (Closes: #350876) + * change dependency on makedev as suggested by Steve Langasek + (Closes: #350591) + * expand on hcid.conf(5) about pin helper parameters (Closes: #297566) + + -- Filippo Giunchedi Sun, 5 Feb 2006 21:52:39 +0100 + +bluez-utils (2.24-1) unstable; urgency=low + + * upload to unstable, rebuilding against dbus 0.60 + (Closes: #337988, #338794) + * make use of makedev in bluez-utils.postinst and conflict with + experimental's makedev (Closes: #338743) + + -- Filippo Giunchedi Mon, 9 Jan 2006 14:04:55 +0100 + +bluez-utils (2.24-0exp1) experimental; urgency=low + + * New upstream christmas release, really bugfix only + * rebuild against dbus (closes: #338794) + * fix hcid/security.c typo (closes: #339413) + * reworked bluetooth init script + + -- Filippo Giunchedi Mon, 26 Dec 2005 11:51:03 +0100 + +bluez-utils (2.24-0ubuntu6) dapper; urgency=low + + * Fix the 'install' call harder, to deal with every possible mangling + of coreutils semantics we've seen over the last 6 months, really. + + -- Adam Conrad Mon, 20 Mar 2006 12:39:11 +1100 + +bluez-utils (2.24-0ubuntu5) dapper; urgency=low + + * Use POSIX-compliant syntax with 'install' in debian/rules, so it + doesn't accuse us of overwriting directories with files. + + -- Adam Conrad Sun, 19 Mar 2006 22:30:51 +1100 + +bluez-utils (2.24-0ubuntu4) dapper; urgency=low + + * Enable hid2hci by default and start hidd with the --search option + * Apply unsafe handling of pand -e option patch (LP #6714) + + -- Charles Majola Wed, 15 Feb 2006 03:00:24 +0000 + +bluez-utils (2.24-0ubuntu3) dapper; urgency=low + + * pinwrapper script added and 002_hcid_conf_defaults.patch modified + to use it for kubuntu compatibility + https://launchpad.net/distros/ubuntu/+source/kdebluetooth/+bug/30889 + * Fix by Anthony Mercatante + + -- Jonathan Riddell Sun, 02 Feb 2006 00:59:16 +0100 + +bluez-utils (2.24-0ubuntu2) dapper; urgency=low + + * Prefer module-init-tools over modutils + + -- Matt Zimmerman Mon, 30 Jan 2006 07:14:21 -0800 + +bluez-utils (2.24-0ubuntu1) dapper; urgency=low + + * New upstream version + + -- Charles Majola Tue, 17 Jan 2006 10:57:52 +0200 + +bluez-utils (2.23-0exp1) experimental; urgency=low + + * New upstream release, Closes: #338260 + * suggest: python (>=1.5) this closes: #328410 + * dbus_pin_helper is now documented in hcid.conf manpage (Closes: #295742) + * added bluetooth and bluetooth-desktop metapackages for LSB 3.0 compilance + * updated 003_manpages.patch + + -- Filippo Giunchedi Tue, 20 Dec 2005 14:15:37 +0100 + +bluez-utils (2.22-0ubuntu3) dapper; urgency=low + + * debian/patches/007_dbus-0.60-api: + - fix a FTBFS because of dbus api changes + + -- Michael Vogt Tue, 20 Dec 2005 21:44:22 +0100 + +bluez-utils (2.22-0ubuntu2) dapper; urgency=low + + * rebuild for latest dbus, changed dependencies accordingly + + -- Michael Vogt Tue, 20 Dec 2005 20:41:48 +0100 + +bluez-utils (2.22-0ubuntu1) dapper; urgency=low + + * New upstream version + + -- Charles Majola Tue, 1 Nov 2005 22:08:47 +0000 + +bluez-utils (2.20-0ubuntu3) breezy; urgency=low + + * bluez-utils.init + - don't start hid2hci by default + + -- Charles Majola Fri, 30 Sep 2005 09:33:00 +0200 + +bluez-utils (2.20-0ubuntu2) breezy; urgency=low + + * Remove depends on bluez-pin for bluez-utils + + -- Jonathan Riddell Mon, 12 Sep 2005 14:12:16 +0100 + +bluez-utils (2.20-0ubuntu1) breezy; urgency=low + + * New upstream release + * Retire patches merged upstream + - debian/patches/009_escape_pinhelper_quotes.patch + - debian/patches/008_let_bluepin_check_for_Xorg.patch + + -- Charles Majola Wed, 7 Sep 2005 11:04:01 +0200 + +bluez-utils (2.19-1) unstable; urgency=high + + * New upstream release. + * Urgency high as fixes hcid pin helper vulnerability (CAN-2005-2547) + (Closes: #323365) + * Bump libbluetooth1-dev build dependency to 2.19 + * Add note about new features in debian/NEWS + + -- Edd Dumbill Fri, 19 Aug 2005 01:12:02 +0100 + +bluez-utils (2.18-1) unstable; urgency=low + + * New upstream version (Closes: #311743) + * Add amd64 to archs for bluez-pcmcia-support (Closes: #294489) + * bluez-utils.init: use -q option to hid2hci, remove /dev/null + redirection. + + -- Edd Dumbill Sat, 16 Jul 2005 14:15:37 +0100 + +bluez-utils (2.18-0ubuntu4) breezy; urgency=low + + * Remove "PIN" prefix, only pin helpers use it, security is set to auto + * CAN Entry + + -- Charles Majola Mon, 29 Aug 2005 10:06:31 +0200 + +bluez-utils (2.18-0ubuntu3) breezy; urgency=low + + * Change maintainer + * Bump Standards Version + * Remove package bcm203x, doesn't work with 2.6 kernels + * Fix pairing failure due to wrong default pin "1234" -> "PIN:1234" + + -- Charles Majola Mon, 15 Aug 2005 11:32:49 +0200 + +bluez-utils (2.18-0ubuntu2) breezy; urgency=low + + * debian/patches/009_escape_pinhelper_quotes.patch + - possible security valnerability (CAN-2005-2547) + + -- Charles Majola Wed, 10 Aug 2005 12:49:39 +0200 + +bluez-utils (2.18-0ubuntu1) breezy; urgency=low + + * New upstream release + - retire dbus patch, included upstream + + -- Charles Majola Wed, 13 Jul 2005 15:30:40 +0200 + +bluez-utils (2.15-2) unstable; urgency=low + + * Don't make device nodes if using udev (Closes: #283866) + + -- Edd Dumbill Sun, 6 Feb 2005 15:55:45 +0000 + +bluez-utils (2.15-1ubuntu2) breezy; urgency=low + + * debian/patches/001_dbus.patch: + - updated for the new dbus. + * debian/control.in: + - updated the Build-Depends on dbus. + + -- Sebastien Bacher Thu, 26 May 2005 23:03:03 +0200 + +bluez-utils (2.15-1ubuntu1) breezy; urgency=low + + * Resynchronise with Debian. + + -- Jeff Bailey Wed, 20 Apr 2005 10:59:58 -0400 + +bluez-utils (2.15-1) unstable; urgency=low + + * New upstream release. + * debian/control: require libbluetooth1-dev 2.15 or better to build. + * Update 003_manpages.patch. + * Retire 007_hidd_role_switch.patch as now in upstream. + + -- Edd Dumbill Sat, 5 Feb 2005 18:09:24 +0000 + +bluez-utils (2.10-6) unstable; urgency=low + + * Move the bluez-bcm203x package to contrib and make it depend on the + non-free firmware. + + -- Edd Dumbill Wed, 1 Dec 2004 14:53:30 +0000 + +bluez-utils (2.10-5ubuntu3) hoary; urgency=low + + * Let bluez-pin also check for Xorg server. + + -- Matthias Urlichs Thu, 3 Mar 2005 21:29:06 +0100 + +bluez-utils (2.10-5ubuntu2) hoary; urgency=low + + * Suggest python instead of python2.2. + + -- Matthias Klose Thu, 13 Jan 2005 00:31:50 +0100 + +bluez-utils (2.10-5ubuntu1) hoary; urgency=low + + * Resynchronise with Debian. + + -- Scott James Remnant Thu, 02 Dec 2004 12:46:42 +0000 + +bluez-utils (2.10-5) unstable; urgency=high + + * Build depend on libbluetooth1 >= 2.10-2, to get HID fix in for + big endian PowerPC machines and fix possible buffer overflow + vulnerability. See bug 281090 for more information. + + -- Edd Dumbill Mon, 29 Nov 2004 16:48:39 +0000 + +bluez-utils (2.10-4ubuntu1) hoary; urgency=low + + * Nathaniel McCallum + - debian/init.d: pretty initscript + - debian/control: versioned depend on lsb-base + + -- Thom May Mon, 29 Nov 2004 11:06:57 +0000 + +bluez-utils (2.10-4) unstable; urgency=low + + * Reflect rename of bluez-bcm203x-firmware to bluez-firmware. + * Update README.Debian to reference use of firmware packages. + + -- Edd Dumbill Fri, 12 Nov 2004 14:13:30 +0000 + +bluez-utils (2.10-3) unstable; urgency=low + + * New package: bluez-bcm203x for Broadcom firmware loading on 2.4 series + kernels. + * bluez-utils now suggests the firmware package; many dongles require + it to work. + + -- Edd Dumbill Fri, 12 Nov 2004 14:00:59 +0000 + +bluez-utils (2.10-2) unstable; urgency=high + + * rules, bluez-pcmcia-support.postinst: ensure /etc/pcmcia/bluetooth is + executable. + + -- Edd Dumbill Fri, 12 Nov 2004 10:55:41 +0000 + +bluez-utils (2.10-1) unstable; urgency=medium + + * New upstream release. Contains bugfixes useful for sarge. + * Retire 007_pcmcia_conf.patch. + * Add 007_hidd_role_switch.patch, which stops hidd forcing role switch. + Added --master to HIDD_OPTIONS to ensure that Apple Bluetooth Keyboards + reconnect automatically. (Closes: #274495) + + -- Edd Dumbill Thu, 14 Oct 2004 15:03:06 +0100 + +bluez-utils (2.9-4) unstable; urgency=high + + * Added patch 007_pcmcia_conf.patch, to fix breakage with PCMCIA startup. + Thanks Zoltan Ivanfi. (Closes: #271622) + + -- Edd Dumbill Wed, 15 Sep 2004 12:26:47 +0100 + +bluez-utils (2.9-3) unstable; urgency=high + + * debian/bluez-utils.init: Kill HCI connection on stop/start. Avoids need + for taking batteries out of Microsoft Bluetooth mouse on restart. + * debian/bluez-utils.init: Silence hid2hci output, it's noisy and shouldn't + complain if no hid dongles found. + * Fix a path in README.Debian (Closes: #266041) + + -- Edd Dumbill Sun, 29 Aug 2004 18:21:22 +0100 + +bluez-utils (2.9-2) unstable; urgency=low + + * Add in libusb-dev dependency so hid2hci is built. + + -- Edd Dumbill Sun, 8 Aug 2004 16:58:39 +0100 + +bluez-utils (2.9-1) unstable; urgency=low + + * New upstream release. + * Remove "XSI-isms" from init script, thanks David Weinehall + (Closes: #259837) + * Update configure flags. + * Update Debian NEWS file. + * Depend on libbluetooth1-dev >= 2.9-1. + + -- Edd Dumbill Sun, 8 Aug 2004 15:44:08 +0100 + +bluez-utils (2.8-1) unstable; urgency=low + + * New upstream release. + - Fixes initialisation of bnep interfaces (Closes: #256436) + * Remove everything in the 2.6 modprobe conf that's in the default + installation anyway. This basically leaves hidp protocol. + * Move dbus1-dev builddep to right place in control file (Closes: #257055) + * Don't install unrequired printers.conf. + * Amend README.Debian.bluez-cups to reflect no printers.conf. + * Retire hidd patch. + * Make hid startup happen before PAN startup (Closes: #258835) + * Include hcid.conf man page (Closes: #257041) + * Depend on libbluetooth1-dev >= 2.8-1 + + -- Edd Dumbill Fri, 16 Jul 2004 21:08:55 +0100 + +bluez-utils (2.7-5) unstable; urgency=low + + * Add separate modprobe config for kernel 2.6 (Closes: #255188) + + -- Edd Dumbill Sat, 19 Jun 2004 20:37:40 +0100 + +bluez-utils (2.7-4) unstable; urgency=low + + * Add support for HID proxy dongles in the init script. These + will now be switched on after hidd starts. + * Don't scribble permissions for /dev/rfcomm* on each install + (Closes: #231510) + + -- Edd Dumbill Mon, 14 Jun 2004 14:24:12 +0100 + +bluez-utils (2.7-3) unstable; urgency=low + + * Upload to unstable. + + -- Edd Dumbill Wed, 9 Jun 2004 23:25:51 +0100 + +bluez-utils (2.7-2) experimental; urgency=low + + * Add fix from Marcel Holtmann for hidd killall command + + -- Edd Dumbill Wed, 26 May 2004 19:43:04 +0100 + +bluez-utils (2.7-1) experimental; urgency=low + + * New upstream. + * Further large changes: this package now incorporates dund and pand. + * Updated man page patches. + * Updated hcid.conf patch. + * Enable building with D-BUS support. + * Enable building of CUPS backend: goes in new package bluez-cups. + Added printers.conf file and CUPS readme file. + * Integrated pand and dund startup stuff into the init script. + * Updated README.Debian. + * Now Conflicts, Replaces bluez-pan. + * Install module aliases in /etc/modprobe.d. + + -- Edd Dumbill Wed, 26 May 2004 12:43:08 +0100 + +bluez-utils (2.6-1) experimental; urgency=low + + * New upstream. In experimental as big changes. + * Build for all except s390. + * Conflicts with old bluez-sdp: this functionality is now in + the bluez-utils package. + * Merged startup from bluez-sdp into bluez-utils startup. + postinst now removes rc.d links for bluez-sdp. + + -- Edd Dumbill Thu, 6 May 2004 11:58:16 +0100 + +bluez-utils (2.4-6) unstable; urgency=high + + * Remove others-readable permissions from devfs configuration of + rfcomm devices. Do the same for the non-devfs versions. + (Closes: #229782) + + -- Edd Dumbill Mon, 26 Jan 2004 15:55:52 +0000 + +bluez-utils (2.4-5) unstable; urgency=low + + * Use $(DEB_DESTDIR) in rules, don't assume debian/tmp. This should + fix build failures on some of the buildds. + + -- Edd Dumbill Thu, 15 Jan 2004 23:22:56 +0000 + +bluez-utils (2.4-4) unstable; urgency=low + + * Practically all of the work for this upload done by Philipp Matthias Hahn + -- thanks Philipp! + * bluez-pcmcia-support is Arch: alpha,arm,i386,ia64,powerpc only, because + hppa,m68k,mips,mipsel,s390,sparc don't have pcmcia-cs. (Closes: #227925) + * Improve all manual pages. (patch 003_manpages.patch) + * Update rfcomm/main.h:usage() and rfcomm/rfcomm.1 (Closes: #227069) + (patch 004_rfcomm_usage.patch) + * Move bluepin and hcitool to /usr/bin (Closes: #226876) + * Moved l2ping to /sbin. + + -- Edd Dumbill Thu, 15 Jan 2004 18:22:20 +0000 + +bluez-utils (2.4-3) unstable; urgency=low + + * Don't install devfsd devices file, really (Closes: #220146) + * Add corresponding note about older kernels and devfs. + * Ensure NEWS.Debian is distributed (Closes: #227390) + + -- Edd Dumbill Wed, 14 Jan 2004 11:47:19 +0000 + +bluez-utils (2.4-2) unstable; urgency=low + + * Depend on modutils or module-init-tools (Closes: #226366) + * Maybe bluez-pcmcia-support be extra in priority, like pcmcia-cs + + -- Edd Dumbill Tue, 6 Jan 2004 10:41:31 +0000 + +bluez-utils (2.4-1) unstable; urgency=low + + * New upstream. + * Fix restart order (Closes: #224199) + * Use mksymlink in devfsd conf file (Closes: #220146) + * Add cmtp alias to the modutils file + * Updated NEWS.Debian to note rfcomm config file change, + update sample rfcomm config file + + -- Edd Dumbill Thu, 1 Jan 2004 20:19:09 +0000 + +bluez-utils (2.3-4) unstable; urgency=low + + * Restart rfcomm in init script restart (Closes: #216907) + + -- Edd Dumbill Sat, 25 Oct 2003 22:30:39 +0100 + +bluez-utils (2.3-3) unstable; urgency=low + + * Change python-gtk suggests to python-gtk-1.2 (Closes: #208119) + + -- Edd Dumbill Wed, 24 Sep 2003 13:21:58 +0100 + +bluez-utils (2.3-2) unstable; urgency=low + + * Fix net-pf-31 alias to 'bluez' not 'hci_usb' + * Move to cdbs + * Change priority to 'optional' + * Bump standards version to 3.5.9 + * Depend on the DBUS bluez-pin helper, and deprecate use of the + buggy Python pin helper as a default. (Closes: #196092, #191444) + * Move Python deps to Suggests. + * Add explanation to README.Debian that headset utils are very + experimental and not for installation (Closes: #196225) + * Use start-stop-daemon in init file. + * Change default PIN to '1234' as 'BlueZ' can't be used with most cellphone + PIN requests. + * Change default hcid.conf to include hostname in interface ID. + + -- Edd Dumbill Thu, 28 Aug 2003 12:38:35 +0100 + +bluez-utils (2.3-1) unstable; urgency=low + + * New upstream release + - hciconfig: CSR firmware revision support, voice commands now + working on big endian machines + - hciattach: support Texas Bluetooth modules, high UART rates on + Ericsson modules, BCSP initialisation fixes + - hcitool: support role switch command + - removes glib dependency + * Remove rfcomm lexing patch, now incorporated upstream + + -- Edd Dumbill Sat, 22 Mar 2003 13:53:09 +0000 + +bluez-utils (2.2-4) unstable; urgency=low + + * Moved to Colin's Build System. + + -- Edd Dumbill Sat, 22 Mar 2003 12:27:26 +0000 + +bluez-utils (2.2-3) unstable; urgency=low + + * Added versioned pcmcia-cs dependency for bluez-pcmcia-support, + needs pcmcia-cs 3.2 or better. (Closes: #181685) + * Amended bluepin to explictly require gtk 1.2 in anticipation + of the change of python-gtk to default to gtk 2.0. + * Fixed spelling mistake in bluepin. + + -- Edd Dumbill Sat, 22 Feb 2003 11:54:32 +0000 + +bluez-utils (2.2-2) unstable; urgency=low + + * Fixed permissions of /dev/bluetooth and /dev/bluetooth/rfcomm. + Thanks Gerd Flaig. (Closes: #181428) + * Added rfcomm initialisation into init file, commented out example + entry in rfcomm.conf so it doesn't get set up on init + * Fixed a bug in rfcomm which meant an empty config file would + generate a syntax error. + + -- Edd Dumbill Tue, 18 Feb 2003 00:32:26 +0000 + +bluez-utils (2.2-1) unstable; urgency=low + + * New upstream release + - support for voice settings in hciconfig + - updated man pages + - bug fixes to hcitool + * Updated standards version to 3.5.8 + + -- Edd Dumbill Wed, 1 Jan 2003 14:28:29 +0000 + +bluez-utils (2.1-3) unstable; urgency=low + + * /dev/rfcomm* now chgrp to 'dialout', thanks to Joey Hess for + pointing this out + * README.Debian updated to reflect status quo of kernel modules + + -- Edd Dumbill Mon, 2 Dec 2002 20:03:42 +0000 + +bluez-utils (2.1-2) unstable; urgency=low + + * Added directory creation to devfs devices file (thanks Zdzislaw + A.Kaleta) + * Fixed chgrp of /dev/rfcomm* to group 'bluetooth' + + -- Edd Dumbill Thu, 31 Oct 2002 07:47:44 +0000 + +bluez-utils (2.1-1) unstable; urgency=low + + * New upstream release + - adds kernel support for rfcomm + * Made postinst create correct rfcomm* and vhci devices + and add a system group 'bluetooth' + + -- Edd Dumbill Tue, 8 Oct 2002 17:01:35 +0100 + +bluez-utils (2.0-release-2) unstable; urgency=low + + * Added modutils alias entries for bnep and rfcomm, which will be + available in the latest releases of the kernel modules. + + -- Edd Dumbill Tue, 08 Oct 2002 16:59:57 +0100 + +bluez-utils (2.0-release-1) unstable; urgency=low + + * New upstream release + * Updated maintainer address to my Debian address + * Updated standards version to 3.5.6 + * Package now updates /etc/modutils/bluez for the BlueZ modules + * hcid is now stopped and started on an upgrade + + -- Edd Dumbill Sat, 31 Aug 2002 20:27:43 +0100 + +bluez-utils (2.0-pre12-2) unstable; urgency=low + + * Added AM_MAINTAINER_MODE to configure.in (Closes: #154929) + For more info on why I did this, see + http://lists.debian.org/debian-devel/2001/debian-devel-200111/msg01422.html + + -- Edd Dumbill Wed, 31 Jul 2002 11:28:30 +0100 + +bluez-utils (2.0-pre12-1) unstable; urgency=low + + * New upstream release + * Added TODO list, removed redundant upstream README + + -- Edd Dumbill Wed, 26 Jun 2002 12:37:26 +0100 + +bluez-utils (2.0-pre9-5) unstable; urgency=low + + * Added missing build-depends on bison and flex + + -- Edd Dumbill Sat, 15 Jun 2002 20:19:05 +0100 + +bluez-utils (2.0-pre9-4) unstable; urgency=low + + * Added build-depends on libglib1.2-dev + + -- Edd Dumbill Tue, 11 Jun 2002 21:57:00 +0100 + +bluez-utils (2.0-pre9-3) unstable; urgency=low + + * Moved startup priority to 25, so as to be after pcmcia. + + -- Edd Dumbill Sun, 5 May 2002 18:33:00 +0100 + +bluez-utils (2.0-pre9-2) unstable; urgency=low + + * Fixed bluepin to find the running X server properly under Debian. + + -- Edd Dumbill Sun, 5 May 2002 15:32:00 +0100 + +bluez-utils (2.0-pre9-1) unstable; urgency=low + + * New upstream version. + * Follow upstream's versioning conventions. + + -- Edd Dumbill Thu, 2 May 2002 16:24:00 +0100 + +bluez-utils (1.99.8-3) unstable; urgency=low + + * Separated out PCMCIA support files into bluez-pcmcia-support. + * Added --always-pcmcia option to configure script so we can force + PCMCIA support scripts install. + + -- Edd Dumbill Fri, 19 Apr 2002 11:36:00 +0100 + +bluez-utils (1.99.8-2) unstable; urgency=low + + * Fixed killall returning error in init script. + + -- Edd Dumbill Wed, 17 Apr 2002 01:00:00 +0100 + +bluez-utils (1.99.8-1) unstable; urgency=low + + * Initial Release. + + -- Edd Dumbill Wed, 17 Apr 2002 01:00:00 +0100 + --- bluez-utils-2.25.orig/debian/devfs-conf +++ bluez-utils-2.25/debian/devfs-conf @@ -0,0 +1,3 @@ +REGISTER ^bluetooth/rfcomm/([0-9]+) CFUNCTION GLOBAL mksymlink $devname rfcomm\1 +REGISTER ^bluetooth/rfcomm/([0-9]+) PERMISSIONS root.dialout 0660 +UNREGISTER ^bluetooth/rfcomm/([0-9]+) CFUNCTION GLOBAL unlink rfcomm\1 --- bluez-utils-2.25.orig/debian/modprobe.conf +++ bluez-utils-2.25/debian/modprobe.conf @@ -0,0 +1,18 @@ +# BlueZ modules + +# These are all in the default aliases file. Uncomment them only +# if for some reason you need them. +#alias net-pf-31 bluetooth +#alias bt-proto-0 l2cap +#alias bt-proto-2 sco +#alias bt-proto-3 rfcomm +#alias bt-proto-4 bnep +#alias bt-proto-5 cmtp +#alias tty-ldisc-15 hci_uart + +# HIDP is not yet in the standard aliases file. +alias bt-proto-6 hidp + +# Uncomment this if you wish to use VHCI +# Unfortunately no minor has been assigned. +# alias char-major-10-250 hci_vhci --- bluez-utils-2.25.orig/debian/bcm203x-wrapper +++ bluez-utils-2.25/debian/bcm203x-wrapper @@ -0,0 +1,2 @@ +#!/bin/sh +exec /usr/lib/bluez-bcm203x/bcm203x "$@" --- bluez-utils-2.25.orig/debian/bluez-cups.install +++ bluez-utils-2.25/debian/bluez-cups.install @@ -0,0 +1 @@ +debian/tmp/usr/lib/cups/backend/* --- bluez-utils-2.25.orig/debian/bluez-utils.preinst +++ bluez-utils-2.25/debian/bluez-utils.preinst @@ -0,0 +1,25 @@ +#!/bin/sh + +# snip from http://www.dpkg.org/ConffileHandling + +# Prepare to move a conffile without triggering a dpkg question +prep_mv_conffile() { + CONFFILE="$1" + + if [ -e "$CONFFILE" ]; then + md5sum="`md5sum \"$CONFFILE\" | sed -e \"s/ .*//\"`" + old_md5sum="`sed -n -e \"/^Conffiles:/,/^[^ ]/{\\\\' $CONFFILE'{s/.* //;p}}\" /var/lib/dpkg/status`" + if [ "$md5sum" = "$old_md5sum" ]; then + rm -f "$CONFFILE" + fi + fi +} + +case "$1" in +install|upgrade) + if dpkg --compare-versions "$2" le "2.19-1"; then + prep_mv_conffile "/etc/init.d/bluez-utils" + prep_mv_conffile "/etc/default/bluez-utils" + fi +esac + --- bluez-utils-2.25.orig/debian/bluez-bcm203x.install +++ bluez-utils-2.25/debian/bluez-bcm203x.install @@ -0,0 +1,2 @@ +debian/tmp/etc/hotplug/usb/* +debian/tmp/usr/lib/bluez-bcm203x/* --- bluez-utils-2.25.orig/debian/TODO +++ bluez-utils-2.25/debian/TODO @@ -0,0 +1,6 @@ +TODO for bluez-utils + +Last updated 2002/10/08 +Edd Dumbill + +* Improve manual pages --- bluez-utils-2.25.orig/debian/bluez-utils.docs +++ bluez-utils-2.25/debian/bluez-utils.docs @@ -0,0 +1,2 @@ +debian/devfs-devices +debian/FAQ --- bluez-utils-2.25.orig/debian/bluez-cups.README.Debian +++ bluez-utils-2.25/debian/bluez-cups.README.Debian @@ -0,0 +1,11 @@ +bluez-cups + +To configure a Bluetooth printer, set it up in CUPS like it was connected to +your parallel or USB port. Then edit your /etc/cups/printers.conf and replace +the device URI with a bluetooth one. + +The printer's URI will look something like this: bluetooth://00408C5E5DA4/spp +If your printer uses HCRP (hardcopy cable replacement protocol) then remove +the "/spp" from the end. SPP is serial port protocol. + + -- Edd Dumbill , Fri Jul 16 19:25:21 BST 2004 --- bluez-utils-2.25.orig/debian/hidd.1 +++ bluez-utils-2.25/debian/hidd.1 @@ -0,0 +1,41 @@ +.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.33. +.TH HIDD "1" "May 2004" "hidd - Bluetooth HID daemon" "User Commands" +.SH NAME +hidd \- manual page for hidd - Bluetooth HID daemon +.SH DESCRIPTION +hidd - Bluetooth HID daemon +.SS "Usage:" +.IP +hidd [options] [commands] +.SH OPTIONS +.TP +\fB\-i\fR +Local HCI device or BD Address +.TP +\fB\-t\fR +Set idle timeout (in minutes) +.TP +\fB\-n\fR, \fB\-\-nodaemon\fR +Don't fork daemon to background +.TP +\fB\-h\fR, \fB\-\-help\fR +Display help +.SS "Commands:" +.TP +\fB\-\-server\fR +Start HID server +.TP +\fB\-\-search\fR +Search for HID devices +.TP +\fB\-\-connect\fR +Connect remote HID device +.TP +\fB\-\-kill\fR +Terminate HID connection +.TP +\fB\-\-killall\fR +Terminate all connections +.TP +\fB\-\-show\fR +List current HID connections --- bluez-utils-2.25.orig/debian/bluez-pcmcia-support.postinst +++ bluez-utils-2.25/debian/bluez-pcmcia-support.postinst @@ -0,0 +1,14 @@ +#!/bin/sh + +set -e +case "$1" in + configure) + chmod a+x /etc/pcmcia/bluetooth + ;; + + *) + exit 0 + ;; +esac + +#DEBHELPER# --- bluez-utils-2.25.orig/debian/FAQ +++ bluez-utils-2.25/debian/FAQ @@ -0,0 +1,123 @@ +Fri Dec 16 21:13:10 CET 2005 + + [1]Home [2]Documentation [3]Download [4]Development [5]Links [6]Contact + [7][IMG] + BlueZ Official Linux Bluetooth protocol stack + [8]Documentation o[9]FAQ o[10]Protocols o[11]Profiles o[12]Drivers + o[13]Hardware + +Frequently asked questions + +general questions + + 1. What is BlueZ? + BlueZ is official Linux Bluetooth protocol stack. It is an Open + Source project distributed under GNU General Public License (GPL). + BlueZ kernel is part of the official Linux kernel since version + 2.4.6. + + 2. Where can I download BlueZ packages? + You can download all BlueZ packages from [14]this page. + + 3. Whom do I contact for support? + Please send your suggestions, questions and problem descriptions + to the [15]users mailing list. + + 4. Who is developing BlueZ? + BlueZ was originally developed by Qualcomm Incorporated. It is now + an Open Source project with many contributors through out the + world. Look at the [16]credits for more details. + + 5. What platforms are supported? + Most platforms supported by 2.4.x and newer Linux kernels. Please + click [17]here for a complete list of supported platforms and + hardware. + + 6. What do I need to use Bluetooth on Linux? + You need Linux system with 2.4.x or newer kernel, BlueZ user space + packages and a Bluetooth device. If you do not have actual + Bluetooth device you could use HCI Emulation daemon provided in + BlueZ-HCIEmu package. + + 7. What Bluetooth protocol and layers are supported by Linux? + Linux kernel supports all core Bluetooth protocols and layers. + Look at the [18]feature list or read the [19]protocols + descriptions. + + 8. What interfaces are available for Bluetooth applications? + Linux provides standard Berkeley socket interface to all Bluetooth + layers. The RFCOMM layer also provides a TTY interface. + + 9. Does Linux provide interface to the L2CAP layer? + Yes. L2CAP layer provides Berkeley socket interface. + + 10. Does Linux support multiple Bluetooth devices? + Yes. You can have several Bluetooth devices connected to one + computer. + + 11. Does Linux support multiple Bluetooth connections? + Yes. All Linux Bluetooth layers support multiple connections. + + 12. Does Linux have kernel support for RFCOMM protocol? + Yes. Both RFCOMM socket and TTY interfaces are supported. + + 13. Does Linux support Bluetooth security? + Yes. Connection and Service (PSM) level security are supported. + + 14. What Bluetooth hardware is supported by Linux? + Please visit the [20]hardware list. + + 15. Do I still need BlueZ-Kernel package? + No. You should upgrade to the latest 2.4.x or 2.6.x Linux kernel. + + 16. What if I don't want to upgrade but I do want latest Bluetooth + features? + We have patches for all Linux kernel's from 2.4.18 onwards. You + can find them [21]here. + + 17. What is 'rfcommd'? + RFCOMMd (or rfcommd) is the user space implementation of the + RFCOMM protocol. It was replaced by RFCOMM kernel module and + shouldn't be used anymore. + + 18. RFCOMM connection using minicom or other tool fails? + In case you have created the RFCOMM link using the "rfcomm bind" + function this can be caused by application timeouts. This is not a + problem of BlueZ or the RFCOMM implementation but rather a problem + with the different nature of a RFCOMM virtual TTY and a physical + serial TTY device which is normally used by those applications. + Some applications implement a timeout protection function while + opening the port. If opening the port takes longer than a certain + amount of time then the application fails. A serial TTY will + usually only take several microseconds to open while the RFCOMM + virtual TTY can take several seconds. Try to create the connection + before starting your application. This can be done by the "rfcomm + connect" function. The Bluetooth connection will then remain until + the rfcomm utility is stopped. + + Copyright © 2000-2005 BlueZ Project. All Rights Reserved. + +References + + Visible links + 1. http://www.bluez.org/ + 2. http://www.bluez.org/documentation.html + 3. http://www.bluez.org/download.html + 4. http://www.bluez.org/development.html + 5. http://www.bluez.org/links.html + 6. http://www.bluez.org/contact.html + 7. http://sourceforge.net/projects/bluez + 8. http://www.bluez.org/documentation.html + 9. http://www.bluez.org/faq.html + 10. http://www.bluez.org/protocols.html + 11. http://www.bluez.org/profiles.html + 12. http://www.bluez.org/drivers.html + 13. http://www.bluez.org/hardware.html + 14. http://www.bluez.org/download.html + 15. http://www.bluez.org/lists.html + 16. http://www.bluez.org/credits.html + 17. http://www.bluez.org/about.html + 18. http://www.bluez.org/about.html + 19. http://www.bluez.org/protocols.html + 20. http://www.bluez.org/hardware.html + 21. http://www.bluez.org/patches.html --- bluez-utils-2.25.orig/debian/copyright +++ bluez-utils-2.25/debian/copyright @@ -0,0 +1,32 @@ +This package was debianized by Edd Dumbill on +Sat, 13 Apr 2002 16:09:02 +0100. + +It was downloaded from http://bluez.sf.net/ + +Upstream Author: Maksim Krasnyanskiy + +Copyright: + + BlueZ - Bluetooth protocol stack for Linux + Copyright (C) 2000-2001 Qualcomm Incorporated + + Written 2000,2001 by Maxim Krasnyansky + + This package is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; version 2 dated June, 1991. + +On Debian GNU/Linux systems, the complete text of the GNU General +Public License can be found in `/usr/share/common-licenses/GPL'. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS +OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. +IN NO EVENT SHALL THE COPYRIGHT HOLDER(S) AND AUTHOR(S) BE LIABLE FOR ANY CLAIM, +OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER +RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, +NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE +USE OR PERFORMANCE OF THIS SOFTWARE. + +ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF ANY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS, RELATING TO USE OF THIS SOFTWARE IS DISCLAIMED. + --- bluez-utils-2.25.orig/debian/bluez-bcm203x.README.Debian +++ bluez-utils-2.25/debian/bluez-bcm203x.README.Debian @@ -0,0 +1,9 @@ +bluez-bcm203x + +Do not install this package if you're running a 2.6 series kernel. + +To use Broadcom devices with kernel 2.4, you will need to install the +bluez-bcm203x-firmware package too. This is available from the Debian +repository on www.bluez.org. + +-- Edd Dumbill --- bluez-utils-2.25.orig/debian/README.Debian +++ bluez-utils-2.25/debian/README.Debian @@ -0,0 +1,144 @@ +bluez-utils for Debian +---------------------- + +In order to use BlueZ you need the BlueZ kernel modules installed. +These are part of modern Linux kernels, 2.4.21 or better, and 2.6 +series kernels. Patches for earlier kernels are available from +http://bluez.sourceforge.net/. + +This package updates /etc/modules.conf for the BlueZ modules. + +It also automatically creates the /dev/rfcomm* serial devices for using +RFCOMM with legacy applications -- see rfcomm(8). Users must be in group +'dialout' to have privileges to use these devices. + +You can edit /etc/bluetooth/rfcomm.conf to have some rfcomm devices bound +automatically at boot time. + +This package contains also the dund and pand daemons for enabling +dial-up and ethernet networking over bluetooth. Edit the +/etc/default/bluez-utils file in order to enable these services. See +below for more details on their configuration. + +The manual pages in this package are mostly very rudimentary. Further +documentation for BlueZ 2.0 can be found at http://bluez.sf.net/ + +If you run devfsd and an older kernel (2.4.21 or younger) you may find +that the /dev/bluetooth/rfcomm* devices are not created for you. To fix +this run: + +# gzip -dc /usr/share/doc/bluez-utils/devfs-devices.gz \ + >/etc/devfs/devices.d/bluez +# /usr/sbin/update-devfsd + +If you wish to install PCMCIA card services support for your Bluetooth +devices you should install the bluez-pcmcia-support package. + +Some USB dongles require firmware to make them work: if 2.4 kernel, +install bluez-bcm203x and bluez-firmware. If 2.6 kernel, just install +bluez-firmware. The bluez-firmware package is available in Debian's +"non-free" section and also online at +http://bluez.sourceforge.net/download/debian/ + +Additional Documentation +------------------------ + +See http://www.bluez.org/documentation.html for BlueZ documentation +and http://www.holtmann.org/linux/bluetooth/ for a collection of +linux bluetooth related HOWTOs. + +Keyboard and mouse support +-------------------------- + +The hidd daemon allows keyboards and mice to be connected to your +system. Ensure you have the hidp patch for Linux 2.6.6 or better +from http://www.bluez.org/patches.html. + +Then change HIDD_ENABLED in /etc/default/bluez-utils to 1 and restart +bluez-utils. That enables the hidd server. You must then connect to +your keyboard or mouse using hidd --connect . On first +connection, pairing is likely. Mice normally have a preset PIN which +should be in the manufacturer's documentation, try 0000. For keyboards, +type the PIN on the Bluetooth keyboard and hit enter, and then type it +in on a cable-attached keyboard to pair. In future your keyboard or +mouse should reconnect to your computer automatically. You must invoke +hidd as root. + +Kernel 2.4.26 users may find experimental patches at +http://www.nenie.org/misc/bluetooth/ + +Security +-------- + +The configuration as shipped is insecure. on your Bluetooth +connections. You should change /etc/bluetooth/pin to your desired PIN. + +Headset support +--------------- + +These tools now include some support for headsets. There are two +test programs 'hsmicro' and 'hsplay' that aren't installed by default; +you'll need too get the source and compile these yourself as upstream +doesn't want them installed. This is because these tools are highly +experimental and unstable, and shouldn't be depended on in any way. + +PIN helper +---------- + +This package uses the PIN helper from the bluez-pin package, which is +much better than the ropey Python one shipped by upstream. Should you +wish to use the upstream helper, install the suggested python-gtk package +and python, and change the pin_helper line in /etc/bluetooth/hcid.conf +to read /usr/bin/bluepin. Alternatively, if you wish to use D-BUS +notification for PIN requests, uncomment the dbus line in the hcid.conf. + + +Bluetooth Networking Quickstart +------------------------------- + +In the future this package will contain better documentation. In the +meantime, here's a quick primer: + +1. Starting dund and pand at boot time + +See /etc/default/bluez-utils for how to configure these two daemons to +run at boot-time. Read below also. + + +2. PPP over RFCOMM + +This is what most devices call "LAN Access" or "Serial Access". It +uses normal PPP over a serial connection. Most PDAs will be able to +connect using this method. + +Use the 'dund' tool to accept incoming connections. Configure pppd +as per the instructions in the ppp package. Then run: + + dund --listen --sdp --nodetach + +Try and connect your device and you'll see something like: + +dund[9801]: DUN daemon ver 1.1pre4 +dund[9811]: New connection from 00:02:31:24:17:6A + +The --sdp option causes the DUN access to be advertised to other +devices via the SDP protocol. Most devices need this in order to be +able to connect. + +Run dund --help to see the various other options available to you. + +If you want to make an outgoing connection using PPP, for instance to +a mobile phone, use the 'rfcomm' program from bluez-utils to bind a +/dev/rfcommX serial port to the phone, and then then use pppd as you +would with a normal modem. + +3. PAN + +The 'pand' tool allows you to use ethernet style networking over +Bluetooth. It creates a network interface on your machine that can be +configured in the same way normal network devices are. + +For full details see the PAN HOWTO at + + + -- Edd Dumbill , Fri Nov 12 14:12:46 GMT 2004