From: Marcel Holtmann <marcel@holtmann.org>
To: Andrej Rosano <andrejro@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Renaming hci interfaces with udev
Date: Tue, 28 Jul 2009 13:31:35 +0200 [thread overview]
Message-ID: <1248780695.28545.224.camel@violet> (raw)
In-Reply-To: <20090728083755.GA3292@stjenka>
Hi Andrej,
> I would like to change the default name of bluetooth interfaces (hci0, hci1, ...)
> using udev rules.
>
> While with wlan usb dongles it works with the line:
> KERNEL=="wlan*", NAME="foo0"
> the analogous for the bt:
> KERNEL=="hci*", NAME="foo0"
> doesn't work, while
> KERNEL=="hci*", RUN+="/usr/bin/touch /tmp/foo"
> works.
>
> I'm using kernel 2.6.30.1, udev 125 and bluez 4.46.
we don't support renaming HCI devices. However feel free to send a
kernel patch to enable it.
Regards
Marcel
next prev parent reply other threads:[~2009-07-28 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 8:37 Renaming hci interfaces with udev Andrej Rosano
2009-07-28 11:31 ` Marcel Holtmann [this message]
2009-07-28 11:34 ` Bastien Nocera
2009-07-28 12:05 ` Andrej Rosano
2009-07-28 12:22 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1248780695.28545.224.camel@violet \
--to=marcel@holtmann.org \
--cc=andrejro@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox