lib/libdhcputil/README.inittab

5 # Common Development and Distribution License, Version 1.0 only
12 # and limitations under the License.
15 # file and include the License file at usr/src/OPENSOLARIS.LICENSE.
25 Inittab Purpose, Goals, and Functionality
33 uses ad-hoc methods for learning and using them, ranging from using
38 options, not having a standard API for managing and parsing DHCP
40 in core Solaris (in.dhcpd, dhcpinfo, snoop, and dhcpmgr), the
48 customer and the application developer.  Its goal is to provide a
50 knowledge from and general routines for encoding and decoding DHCP
56 The inittab file contains information regarding the syntax and (to
58 read-only file (like /etc/termcap) and should not need to be changed
63 and describing a particular option.  The format is based heavily on
73       category unique and ideally should be unique across all categories.
74       Of particular note is that options names in the STANDARD, SITE, and
77    `category' is one of STANDARD, SITE, VENDOR, FIELD, or INTERNAL and
84       other purposes and thus may not be globally unique).  This field
85       should be per-category unique and the STANDARD and SITE fields
91       UNUMBER32, SNUMBER8, SNUMBER16, and SNUMBER32.  For numbers,
93       or signed, and the trailing number indicates the number of bits
106       (`i' for dhcpinfo, `s' for snoop, `d' for in.dhcpd, and
114 category (i.e., defined by the DHCP standard), and is option code
117 option are dhcpinfo, snoop, in.dhcpd and dhcpmgr.
119 Comments in the inittab file begin with `#', and end with a newline.
124 for all DHCP option consumers, with the following exceptions and notes:
126    o  The DHCP agent and DHCP server both have their core protocol-
148    o  Where a symbol is defined both in the inittab and in dhcptab(4),
155 Each inittab entry describes a specific DHCP option and is defined as
159 inittab_load(), inittab_getbyname(), or inittab_getbycode() and passed
186 and the `consumer' field consists of one of the following:
193 inittab_load() creates and returns an array of dhcp_symbol_t's made
196 the entries returned.  The array is dynamically allocated, and the
200 matching the given name or code for the provided category and the
215 if `inittab_ent' is incorrect, and ITAB_UNKNOWN if inittab_verify()
218 verified using the `ds_category' and `ds_code' fields from the
220 and the internal entry both must have the same ds_gran, ds_max, and
223 To perform encoding and decoding of DHCP options, the following
237 For inittab_encode(), `data' is an ASCII string to encode, and a
241 only the payload of the option is returned (i.e., the option code and
284 variables, DHCP_INITTAB_DEBUG, and DHCP_INITTAB_PATH, can be set