source: rtems/cpukit/libnetworking/libc/linkaddr.3 @ 0e16fa45

5
Last change on this file since 0e16fa45 was 9b4422a2, checked in by Joel Sherrill <joel.sherrill@…>, on 05/03/12 at 15:09:24

Remove All CVS Id Strings Possible Using a Script

Script does what is expected and tries to do it as
smartly as possible.

+ remove occurrences of two blank comment lines

next to each other after Id string line removed.

+ remove entire comment blocks which only exited to

contain CVS Ids

+ If the processing left a blank line at the top of

a file, it was removed.

  • Property mode set to 100644
File size: 4.3 KB
Line 
1.\" Copyright (c) 1993
2.\"     The Regents of the University of California.  All rights reserved.
3.\"
4.\" This code is derived from software contributed to Berkeley by
5.\" Donn Seeley at BSDI.
6.\"
7.\" Redistribution and use in source and binary forms, with or without
8.\" modification, are permitted provided that the following conditions
9.\" are met:
10.\" 1. Redistributions of source code must retain the above copyright
11.\"    notice, this list of conditions and the following disclaimer.
12.\" 2. Redistributions in binary form must reproduce the above copyright
13.\"    notice, this list of conditions and the following disclaimer in the
14.\"    documentation and/or other materials provided with the distribution.
15.\" 3. All advertising materials mentioning features or use of this software
16.\"    must display the following acknowledgement:
17.\"     This product includes software developed by the University of
18.\"     California, Berkeley and its contributors.
19.\" 4. Neither the name of the University nor the names of its contributors
20.\"    may be used to endorse or promote products derived from this software
21.\"    without specific prior written permission.
22.\"
23.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
33.\" SUCH DAMAGE.
34.\"
35.\"     From: @(#)linkaddr.3    8.1 (Berkeley) 7/28/93
36.\"
37.Dd June 17, 1996
38.Dt LINK_ADDR 3
39.Os BSD 4.4
40.Sh NAME
41.Nm link_addr ,
42.Nm link_ntoa
43.Nd elementary address specification routines for link level access
44.Sh SYNOPSIS
45.Fd #include <sys/types.h>
46.Fd #include <sys/socket.h>
47.Fd #include <net/if_dl.h>
48.Ft void
49.Fn link_addr "const char *addr" "struct sockaddr_dl *sdl"
50.Ft char *
51.Fn link_ntoa "const struct sockaddr_dl *sdl"
52.Sh DESCRIPTION
53The routine
54.Fn link_addr
55interprets character strings representing
56link-level addresses, returning binary information suitable
57for use in system calls.
58The routine
59.Fn link_ntoa
60takes
61a link-level
62address and returns an
63.Tn ASCII
64string representing some of the information present,
65including the link level address itself, and the interface name
66or number, if present.
67This facility is experimental and is
68still subject to change.
69.Pp
70For
71.Fn link_addr ,
72the string
73.Fa addr
74may contain
75an optional network interface identifier of the form
76.Dq "name unit-number" ,
77suitable for the first argument to
78.Xr ifconfig 8 ,
79followed in all cases by a colon and
80an interface address in the form of
81groups of hexadecimal digits
82separated by periods.
83Each group represents a byte of address;
84address bytes are filled left to right from
85low order bytes through high order bytes.
86.Pp
87.\" A regular expression may make this format clearer:
88.\" .Bd -literal -offset indent
89.\" ([a-z]+[0-9]+:)?[0-9a-f]+(\e.[0-9a-f]+)*
90.\" .Ed
91.\" .Pp
92Thus
93.Li le0:8.0.9.13.d.30
94represents an ethernet address
95to be transmitted on the first Lance ethernet interface.
96.Pp
97The direct use of these functions is deprecated in favor of the
98.Xr addr2ascii 3
99interface; however, portable programs cannot rely on the latter as it is
100not yet widely implemented.
101.Sh RETURN VALUES
102.Fn link_ntoa
103always returns a null terminated string.
104.Fn link_addr
105has no return value.
106(See
107.Sx BUGS . )
108.Sh SEE ALSO
109.Xr addr2ascii 3
110.\" .Xr iso 4
111.Sh HISTORY
112The
113.Fn link_addr
114and
115.Fn link_ntoa
116functions appeared in
117.Bx 4.3 Reno  .
118.Sh BUGS
119The returned values for link_ntoa
120reside in a static memory area.
121.Pp
122The function
123.Fn link_addr
124should diagnose improperly formed input, and there should be an unambiguous
125way to recognize this.
126.Pp
127If the
128.Va sdl_len
129field of the link socket address
130.Fa sdl
131is 0,
132.Fn link_ntoa
133will not insert a colon before the interface address bytes.
134If this translated address is given to
135.Fn link_addr
136without inserting an initial colon,
137the latter will not interpret it correctly.
Note: See TracBrowser for help on using the repository browser.