1 |
On Mon, 27 Mar 2017 13:31:56 -0400, |
2 |
Foster McLane wrote: |
3 |
> |
4 |
> On Mon, Mar 27, 2017 at 01:21:55PM -0400, John Covici wrote: |
5 |
> > On Mon, 27 Mar 2017 12:46:18 -0400, |
6 |
> > Foster McLane wrote: |
7 |
> > > |
8 |
> > > On Mon, Mar 27, 2017 at 12:28:11PM -0400, John Covici wrote: |
9 |
> > > > On Mon, 27 Mar 2017 08:44:59 -0400, |
10 |
> > > > Mick wrote: |
11 |
> > > > > |
12 |
> > > > > [1 <text/plain; us-ascii (quoted-printable)>] |
13 |
> > > > > On Monday 27 Mar 2017 13:45:08 Raffaele Belardi wrote: |
14 |
> > > > > > John Covici wrote: |
15 |
> > > > > > > Hi. After the last update of net-wireless/bluez hciconfig has |
16 |
> > > > > > > disappeared. Even downgrading did not bring it back, although it was |
17 |
> > > > > > > there in the previous release. How do I do hciconfig, scan and |
18 |
> > > > > > > friends now, or is there a way to get them back. |
19 |
> > > > > > > |
20 |
> > > > > > > As a workaround I put an old one back just copying the binary, so I |
21 |
> > > > > > > could proceed, but there has got to be a better way. |
22 |
> > > > > > > |
23 |
> > > > > > > Thanks in advance for any suggestions. |
24 |
> > > > > > |
25 |
> > > > > > https://wiki.archlinux.org/index.php/bluetooth#Deprecated_method_using_hcico |
26 |
> > > > > > nfig |
27 |
> > > > > > |
28 |
> > > > > > The ebuild lets you specify an extra-tools USE flag, maybe that one gets |
29 |
> > > > > > them back. |
30 |
> > > > > > |
31 |
> > > > > > raffaele |
32 |
> > > > > |
33 |
> > > > > |
34 |
> > > > > I'm on net-wireless/bluez-5.43-r1 with these USE flags: |
35 |
> > > > > |
36 |
> > > > > Installed versions: 5.43-r1(09:55:34 02/05/17)(cups obex readline udev - |
37 |
> > > > > debug -deprecated -doc -experimental -extra-tools -selinux -systemd -test - |
38 |
> > > > > test-programs -user-session ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" |
39 |
> > > > > ABI_S390="-32 -64" ABI_X86="64 -32 -x32" PYTHON_TARGETS="python2_7") |
40 |
> > > > > |
41 |
> > > > > I still have hciconfig, hcitools, et al. |
42 |
> > > > > |
43 |
> > > > |
44 |
> > > > I did as well, till I upgraded to 5.44 and then even downgrading did |
45 |
> > > > not bring back the tools. |
46 |
> > > > |
47 |
> > > > -- |
48 |
> > > > Your life is like a penny. You're going to lose it. The question is: |
49 |
> > > > How do |
50 |
> > > > you spend it? |
51 |
> > > > |
52 |
> > > > John Covici |
53 |
> > > > covici@××××××××××.com |
54 |
> > > > |
55 |
> > > |
56 |
> > > If you are just using the tools in your terminal, 'bluetoothctl' has replaced |
57 |
> > > those programs. If you are writing scripts with those commands, I do not |
58 |
> > > know of any worthy replacements besides using the DBus interface |
59 |
> > > manually. |
60 |
> > |
61 |
> > I need to make sure that hci0 is up before I start a program that |
62 |
> > wants to use it and when I start the bluetooth service, hci0 is down. |
63 |
> > How to put it up not using a terminal? Or how to get back those hci |
64 |
> > commands? |
65 |
> > |
66 |
> > -- |
67 |
> > Your life is like a penny. You're going to lose it. The question is: |
68 |
> > How do |
69 |
> > you spend it? |
70 |
> > |
71 |
> > John Covici |
72 |
> > covici@××××××××××.com |
73 |
> > |
74 |
> |
75 |
> You can set 'AutoEnable=true' in your '/etc/bluetooth/main.conf' file. |
76 |
> It should be commented at the bottom. |
77 |
|
78 |
OK, I will try that out, never heard of that parameter before. |
79 |
|
80 |
Thanks. |
81 |
|
82 |
-- |
83 |
Your life is like a penny. You're going to lose it. The question is: |
84 |
How do |
85 |
you spend it? |
86 |
|
87 |
John Covici |
88 |
covici@××××××××××.com |