public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Heikki Rantanen <hrantane@cc.hut.fi>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Re: Dund instructions?
Date: Tue, 01 Jun 2004 16:34:11 +0200	[thread overview]
Message-ID: <1086100451.4702.28.camel@pegasus> (raw)
In-Reply-To: <40BC910A.9030508@cc.hut.fi>

Hi Heikki,

> Ok. Apparently the bluez-pan-1.1-2mdk rpm package I found in rpmseek and 
> installed yesterday hasn't the newest version, since there is no manual 
> entry for dund. I think it would be nice if there was a list of 
> available commands with their man pages at the www-site. Now a question 
> as fundamental as "What commands/programs is available in Bluez?" is 
> actually very difficult to find answer to.

install bluez-libs-2.7 and bluez-utils-2.7 and you also get the manpages
for dund and pand. For the list of commands check the howtos and the
mailing list archives.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2004-06-01 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-31 22:06 [Bluez-users] Dund instructions? Heikki Rantanen
2004-05-31 22:16 ` Marcel Holtmann
2004-06-01 12:58   ` [Bluez-users] weird problem with rfcomm Jorge A. González
2004-06-01 14:22   ` [Bluez-users] Re: Dund instructions? Heikki Rantanen
2004-06-01 14:34     ` Marcel Holtmann [this message]

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=1086100451.4702.28.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=hrantane@cc.hut.fi \
    /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