History log of /freebsd-current/usr.bin/bluetooth/rfcomm_sppd/rfcomm_sppd.c
Revision Date Author Comments
# 42b38843 16-Aug-2023 Warner Losh <imp@FreeBSD.org>

Remove $FreeBSD$: one-line .h pattern

Remove /^\s*\*+\s*\$FreeBSD\$.*$\n/


# 4d846d26 10-May-2023 Warner Losh <imp@FreeBSD.org>

spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD

The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.

Discussed with: pfg
MFC After: 3 days
Sponsored by: Netflix


# 1de7b4b8 27-Nov-2017 Pedro F. Giffuni <pfg@FreeBSD.org>

various: general adoption of SPDX licensing ID tags.

Mainly focus on files that use BSD 2-Clause license, however the tool I
was using misidentified many licenses so this was mostly a manual - error
prone - task.

The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.

No functional change intended.


# 8d6f425d 07-Apr-2015 Takanori Watanabe <takawata@FreeBSD.org>

Check l2cap socket initialisation and define L2CAP_SOCKET_CHECKED
This will fix build.


# dc7b2697 23-Oct-2014 Maksim Yevmenkin <emax@FreeBSD.org>

Change the code to use the openpty(3) API which uses the pts(4) driver
instead of the pty(4) driver.

PR: 184597
Submitted by: tobias.rehbein
MFC after: 2 weeks


# a7d5f7eb 19-Oct-2010 Jamie Gritton <jamie@FreeBSD.org>

A new jail(8) with a configuration file, to replace the work currently done
by /etc/rc.d/jail.


# fe0506d7 09-Mar-2010 Marcel Moolenaar <marcel@FreeBSD.org>

Create the altix project branch. The altix project will add support
for the SGI Altix 350 to FreeBSD/ia64. The hardware used for porting
is a two-module system, consisting of a base compute module and a
CPU expansion module. SGI's NUMAFlex architecture can be an excellent
platform to test CPU affinity and NUMA-aware features in FreeBSD.


# d37245a0 04-Feb-2009 Maksim Yevmenkin <emax@FreeBSD.org>

Clenup code a bit and do not call fork(2) before dameon(3) where not needed.

MFC after: 1 month


# d7f03759 19-Oct-2008 Ulf Lilleengen <lulf@FreeBSD.org>

- Import the HEAD csup code which is the basis for the cvsmode work.


# aa6985f4 14-May-2008 Maksim Yevmenkin <emax@FreeBSD.org>

Make -t <tty> optional in server mode. If not specified use stdin/stdout.
Document this. Do not require channel number in server mode. If not
specified - bind to ''wildcard'' channel zero. Real channel number will
be obtained automatically and registered with local sdpd(8). While I'm
here fix serial port service registration.

Submitted by: luigi
Tested by: Helge Oldach <freebsd-bluetooth at oldach dot net>
MFC after: 3 days


# 817e1ec9 10-Sep-2007 Kevin Lo <kevlo@FreeBSD.org>

Check return value of listen().

Reviewed by: emax
Approved by: re (kensmith)


# 0a314f7c 25-Jan-2007 Maksim Yevmenkin <emax@FreeBSD.org>

Add "server mode" to rfcomm_sppd(1).

Submitted by: Dave Eckhardt, bms
Tested by: Dave Eckhardt, Eric Anderson, bms


# a9412967 07-Dec-2005 Maksim Yevmenkin <emax@FreeBSD.org>

Teach rfcomm_sppd(8) to recognize "lan" (for LAN Access Using PPP) service
name in '-c' (RFCOMM channel) option.

MFC after: 3 days


# d47d4f47 22-Nov-2005 Maksim Yevmenkin <emax@FreeBSD.org>

Teach rfcomm_sppd(1) about service names, so it is possible to specify
service name instead of channel number with -c command option. Supported
service names are: DUN (Dial-Up Networking), FAX (Fax) and SP (Serial Port).

MFC after: 1 week


# 969fdab1 30-Sep-2004 Maksim Yevmenkin <emax@FreeBSD.org>

Make -t <tty> optional. If not specified use stdin/stdout.
Document this. These changes make it possible to write something like

set device "!/usr/bin/rfcomm_sppd -a BD_ADDR"

inside the /etc/ppp/ppp.conf file. Very convenient for the users :)

Submitted by: Konstantin Stepanenkov <kstepanenkov AT oilspace DOT com>
MFC after: 3 days


# 2aa65cf7 05-Aug-2004 Maksim Yevmenkin <emax@FreeBSD.org>

- One can use both BD_ADDR or name to specify address of the Bluetooth device.
Update man pages to document this fact.

- Update usage messages

- Change u_intXXX to uintXXX


# 263a3a25 22-Dec-2003 Maksim Yevmenkin <emax@FreeBSD.org>

Fix a couple of stylistic issues

Reviewed by: imp (mentor), ru
Approved by: imp (mentor)


# 4b1493e5 19-Dec-2003 Maksim Yevmenkin <emax@FreeBSD.org>

Fix uncontrolled access to the buffer in rfcomm_sppd(1).
Fix typo in hcsecd(8) man page.

Submitted by: Guido Falsi <mad@madpilot.net>
Reviewed by: imp (mentor)
Approved by: imp (mentor)


# 0986ab12 12-Oct-2003 Maksim Yevmenkin <emax@FreeBSD.org>

Update Bluetooth code.

Reviewed by: M. Warner Losh <imp@bsdimp.com>; John Hay <jhay@freebsd.org>
Approved by: M. Warner Losh <imp@bsdimp.com> (mentor)


# f2bb1cae 10-May-2003 Julian Elischer <julian@FreeBSD.org>

Part one of undating the bluetooth code to the newest version

Submitted by: Maksim Yevmenkin <m_evmenkin@yahoo.com>
Approved by: re@