public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gardiner <osronline@glidos.net>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hcid.conf seemingly ignored
Date: Wed, 20 Dec 2006 09:38:41 +0000	[thread overview]
Message-ID: <458904A1.5090508@glidos.net> (raw)
In-Reply-To: <20061220085414.GA18455@suse.de>

Stefan Seyfried wrote:
> On Tue, Dec 19, 2006 at 08:23:37PM +0000, Paul Gardiner wrote:
>  
>> Ok, that works. It gives me a way, other than hciconfig, to make the 
>> device discoverable. Still a pity that hcid.conf isn't obeyed as in
>> opensuse 10.1. That was simpler for my set up.
> 
> Well, that's the price we are paying for progress.
> (and it escapes me how editing hcid.conf is easier than using
> bluetooth-applet once to set up the system :-))

The machine in question is a headless server. Also I keep all my
config changes under CVS, and use CVS to do most of the work
of configing a new machine (or upgrading a machine to a new
version of opensuse).  I often use the GUI interfaces when first
setting up something I've never used before, but once I
have a reasonable set up, I like to break it down to config
file changes so that I can reuse the settings easily. Admittedly
this may not be common usage.

>> The real problem now though, is whatever I do I can't get dund to
>> respond.  Its a shame this was all working reliable back with 10.1.
>> Now it looks like I'm not going to be able to get it going.
> 
> If the procedure explained in /usr/share/doc/packages/bluez-utils/README.dund
> does not work, please file a bugreport at bugzilla.novell.com so i can update
> the documentation.

Ok thanks. I'm not sure I have read that before. That may help a lot.

Cheers,
	Paul.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-12-20  9:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 10:12 [Bluez-users] hcid.conf seemingly ignored Paul Gardiner
2006-12-19 10:20 ` Marcel Holtmann
2006-12-19 12:28   ` Paul Gardiner
2006-12-19 15:36     ` Stefan Seyfried
2006-12-19 15:49       ` Paul Gardiner
2006-12-19 16:31         ` Stefan Seyfried
2006-12-19 17:23           ` Paul Gardiner
2006-12-19 17:37             ` Ulisses Furquim
2006-12-19 17:42             ` Stefan Seyfried
2006-12-19 17:51               ` Marcel Holtmann
2006-12-19 20:23       ` Paul Gardiner
2006-12-20  8:54         ` Stefan Seyfried
2006-12-20  9:38           ` Paul Gardiner [this message]
2006-12-20 11:04             ` Stefan Seyfried
2006-12-20 22:40               ` Paul Gardiner
2006-12-21 23:13                 ` Paul Gardiner
2006-12-22 11:06                   ` Stefan Seyfried
2006-12-22 11:18                     ` Paul Gardiner

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=458904A1.5090508@glidos.net \
    --to=osronline@glidos.net \
    --cc=bluez-users@lists.sourceforge.net \
    /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