All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hcid.conf seemingly ignored
Date: Wed, 20 Dec 2006 12:04:57 +0100	[thread overview]
Message-ID: <20061220110457.GC20278@suse.de> (raw)
In-Reply-To: <458904A1.5090508@glidos.net>

On Wed, Dec 20, 2006 at 09:38:41AM +0000, Paul Gardiner wrote:
 =

> 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.

In this case, it is easy to script all this with dbus-send or apitest.
Just a script that sets up the machine and verifies the configuration
afterwards. Keep this script under version control and everything will
be fine :-)

> > If the procedure explained in /usr/share/doc/packages/bluez-utils/READM=
E.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.

If it does not work, let me know so that i can fix the documentation.

Have fun,

    Stefan

-- =

Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg  | "Well, surrounding them's out." =


-------------------------------------------------------------------------
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=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-12-20 11:04 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
2006-12-20 11:04             ` Stefan Seyfried [this message]
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=20061220110457.GC20278@suse.de \
    --to=seife@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.