Package: bluez-utils
Version: 3.7-1

The manual page for pand says:

  pand will execute /etc/bluetooth/pan/dev-up device destination when the
  interface becomes available.

This vas true for some old versions, but it is no longer true: in
pand/main.c, devupcmd is initialized to NULL, and the script is indeed not
executed. The behavior can be restored using a --devup option, but this
option is not present in the default init script.

I think the paragraph about dev-up should be removed from the manual page,
and the change underlined in the changelog.

Regards,

-- 
  Nicolas George

Attachment: signature.asc
Description: Digital signature

Reply via email to