| /src/usr.bin/diff3/tests/ |
| H A D | long-o.txt | 2 These lines are the same in all three files
3 These lines are the same in all three files
5 These lines are the same in all three files
6 These lines are the same in all three files
7 These lines are the same in all three files
9 These lines are the same in all three files
10 These lines are the same in all three files
12 These lines are the same in all three files
13 These lines are the same in all three files
14 These lines are the same in all three files
[all …]
|
| H A D | long-y.txt | 2 These lines are the same in all three files
3 These lines are the same in all three files
5 These lines are the same in all three files
6 These lines are the same in all three files
7 These lines are the same in all three files
9 These lines are the same in all three files
10 These lines are the same in all three files
12 These lines are the same in all three files
13 These lines are the same in all three files
14 These lines are the same in all three files
[all …]
|
| H A D | long-m.txt | 2 These lines are the same in all three files
3 These lines are the same in all three files
5 These lines are the same in all three files
6 These lines are the same in all three files
7 These lines are the same in all three files
9 These lines are the same in all three files
10 These lines are the same in all three files
12 These lines are the same in all three files
13 These lines are the same in all three files
14 These lines are the same in all three files
[all …]
|
| H A D | long-merge.out | 2 These lines are the same in all three files
3 These lines are the same in all three files
5 These lines are the same in all three files
6 These lines are the same in all three files
7 These lines are the same in all three files
9 These lines are the same in all three files
10 These lines are the same in all three files
16 These lines are the same in all three files
17 These lines are the same in all three files
18 These lines are the same in all three files
[all …]
|
| /src/secure/lib/libcrypto/man/man3/ |
| H A D | SSL_CTX_new.3 | 140 These are later inherited by the \fBSSL\fR object representing an active session.
161 provide serialization of access for these cases.
183 These are the general\-purpose \fIversion\-flexible\fR SSL/TLS methods.
187 Applications should use these methods, and avoid the version\-specific
191 These functions do not exist anymore, they have been renamed to
199 A TLS/SSL connection established with these methods will only understand the
200 TLSv1.2 protocol. These methods are deprecated.
203 A TLS/SSL connection established with these methods will only understand the
204 TLSv1.1 protocol. These methods are deprecated.
207 A TLS/SSL connection established with these methods will only understand the
[all …]
|
| /src/share/man/man5/ |
| H A D | src.conf.5 | 120 When set, it enforces these options:
181 When set, these options are also in effect:
229 When set, it enforces these options:
236 When set, these options are also in effect:
251 When set, it enforces these options:
262 When set, these options are also in effect:
291 These can be used to help mitigate some exploit techniques.
306 When set, these options are also in effect:
376 When set, it enforces these options:
392 When set, it enforces these options:
[all …]
|
| /src/crypto/openssl/doc/man3/ |
| H A D | SSL_CTX_new.pod | 78 These are later inherited by the B<SSL> object representing an active session.
99 provide serialization of access for these cases.
125 These are the general-purpose I<version-flexible> SSL/TLS methods.
129 Applications should use these methods, and avoid the version-specific
134 These functions do not exist anymore, they have been renamed to
143 A TLS/SSL connection established with these methods will only understand the
144 TLSv1.2 protocol. These methods are deprecated.
148 A TLS/SSL connection established with these methods will only understand the
149 TLSv1.1 protocol. These methods are deprecated.
153 A TLS/SSL connection established with these methods will only understand the
[all …]
|
| H A D | OPENSSL_fork_prepare.pod | 24 These methods are currently unused, and as such, no replacement methods are
33 Platforms without fork(2) will probably not need to use these functions.
36 such as Linux that have both functions will normally not need to call these
39 L<OPENSSL_init_crypto(3)> will register these functions with the appropriate
41 applications, these functions can be called directly. They should be used
59 These functions were added in OpenSSL 1.1.1.
|
| /src/sys/dev/isci/scil/ |
| H A D | scif_sas_design.h | 99 Some of the SAS framework objects contain sub-state machines. These
137 the overall architecture of the component will also be defined in these
155 and one direct header file. These files delineate the methods, members, etc.
156 associated with this object. Please reference these files directly for
170 and one direct header file. These files delineate the methods, members, etc.
171 associated with this object. Please reference these files directly for
187 source files and one direct header file. These files delineate the
189 these files directly for
205 and one direct header file. These files delineate the methods, members, etc.
209 classes (common files). Please reference these files directly for further
[all …]
|
| /src/sys/contrib/openzfs/tests/zfs-tests/tests/functional/cli_user/misc/ |
| H A D | misc.cfg | 33 # these are the set of settable ZFS properties
41 # these are a set of values we apply, for use when testing the
51 # these are an alternate set of property values
66 # these are a set of values we apply, for use when testing the
76 # these are an alternate set of property values
85 # these are the set of settable ZFS properties
93 # these are a set of values we apply, for use when testing the
103 # these are an alternate set of property values
|
| /src/contrib/ncurses/man/ |
| H A D | curs_get_wstr.3x | 161 \fB\%ncurses\fP(3X) describes the variants of these functions.
163 These functions return
171 these functions fail if
195 All of these functions except
212 These functions cannot store a
221 While these functions conceptually implement
241 these functions do not return
264 X/Open Curses Issue\ 4 describes these functions.
267 Issue\ 4 documented these functions as passing an array of
290 All of the vendors implement these functions using
[all …]
|
| H A D | curs_inchstr.3x | 98 \fB\%ncurses\fP(3X) describes the variants of these functions.
100 These functions return
108 these functions fail if
130 All of these functions except
162 X/Open Curses Issue\ 4 describes these functions.
164 It characterizes the strings stored by these functions as containing
170 but does not specify whether the string stored by these functions is
189 introduced these functions.
|
| H A D | curs_add_wchstr.3x | 92 \fB\%ncurses\fP(3X) describes the variants of these functions.
94 Because these functions do not call \fB\%wadd_wch\fP(3X) internally,
111 These functions return
119 these functions fail if
141 All of these functions except
145 X/Open Curses Issue\ 4 describes these functions.
148 X/Open Curses Issue\ 4 (1995) initially specified these functions.
157 These were later additions to
|
| H A D | curs_addchstr.3x | 93 \fB\%ncurses\fP(3X) describes the variants of these functions.
95 Because these functions do not call \fB\%waddch\fP(3X) internally,
112 These functions return
120 these functions fail if
142 All of these functions except
146 X/Open Curses Issue\ 4 describes these functions.
154 introduced these functions.
|
| H A D | curs_addwstr.3x | 103 \fB\%ncurses\fP(3X) describes the variants of these functions.
105 These functions return
113 these functions fail if
138 All of these functions except
142 X/Open Curses Issue\ 4 describes these functions.
148 X/Open Curses Issue\ 4 (1995) initially specified these functions.
157 These were later additions to
|
| /src/lib/libc/posix1e/ |
| H A D | acl.3 | 42 provides a library for userland access to and manipulation of these ACLs.
57 all of these support routines are implemented in
93 These functions are described in
103 These functions are described in
148 These functions are described in
189 These functions are described in
220 These functions are described in
229 These functions are described in
235 Documentation of the internal kernel interfaces backing these calls may
282 These additional labels provide fine-grained discretionary access control,
[all …]
|
| /src/lib/libc/locale/ |
| H A D | DESIGN.xlocale | 11 This document describes the implementation of these APIs for FreeBSD.
25 variants of these functions, to make it harder for accidental uses of the
42 supported by `setlocale()`. These are likewise immutable after creation. This
46 The exception to these mutability rules is a set of `mbstate_t` flags stored
47 with each locale. These are used by various functions that previously had a
76 None of these were thread safe. Caching is only really of use for supporting
114 APIs, but also simplifies the modifications to these functions. The
119 The ctype.h functions are a little different. These are not implemented in
120 terms of their locale-aware versions, for performance reasons. Each of these
126 `strtoq_l()` and `strtouq_l() `are not provided. These are extensions to
[all …]
|
| /src/crypto/openssl/include/openssl/ |
| H A D | engine.h | 42 * These flags are used to control combinations of algorithm (methods) by
73 * these control commands on behalf of the ENGINE using their "cmd_defns"
99 * ENGINEs can support their own command types, and these flags are used in
130 * NB: These 3 control commands are deprecated and should not be used.
131 * ENGINEs relying on these commands should compile conditional support for
132 * compatibility (eg. if these symbols are defined) but should also migrate
134 * can be "discovered" by calling applications. The fact these control
141 * These flags are used to tell the ctrl function what should be done. All
165 * These control commands allow an application to deal with an arbitrary
167 * THESE COMMANDS because zero is used to indicate 'end-of-list'. Other
[all …]
|
| /src/contrib/ntp/scripts/stats/ |
| H A D | README.stats | 6 this feature. Since these files can become rather large and cumbersome,
67 by these radios.
90 refclock_as2201.c source module for a list of the commands used. These
101 These data determine the deviations of external time/frequency inputs
118 These data show the receiver model number and option configuration.
134 These data determine the deviations of the receiver oscillator with
150 These data determine the deviations and weights to calculate ensemble
166 These data determine which stations of the LORAN chain are being
187 These data determine the receiver oscillator type, mode, status and
200 These data determine the receiver position and elevation, together with
[all …]
|
| /src/share/man/man3/ |
| H A D | ATOMIC_VAR_INIT.3 | 104 These variables are not type-compatible with their non-atomic
236 parameter of these
261 These atomic operations are typically implemented by the compiler, as
266 header implements these macros on top of existing compiler intrinsics to
279 To prevent unintended non-atomic access to these variables, this header
284 atomic intrinsics, these macros may emit function calls to fallback
286 These fallback routines are only implemented for 32-bits and 64-bits
292 These macros attempt to conform to
295 These macros appeared in
|
| /src/etc/mtree/ |
| H A D | README | 1 Note: If you modify these files, please keep hier(7) updated!
3 These files are used to create empty file hierarchies for building the
10 of levels in these files can become quite deep causing the line to
20 d) Sanity checking changes to these files can be done by following
34 mechanism for making better selections for these as it
43 are more complicated, but can often catch missing entries in these
|
| /src/crypto/openssl/doc/designs/quic-design/ |
| H A D | dgram-api.md | 38 these new APIs to define a fallback code path.
56 The motivation for this is that these functions are intended to support
80 structures (as discussed above) and also intend these functions to be
145 are defined and all of these fields are set to zero on call and on return.
148 which the remote and local addresses are to be filled. If either of these
208 - We would need to include the OS headers which provide these
211 - If we choose to support these functions when OS support is not available
217 - We would need to translate these structures during every call.
221 these allocations probably will need to be on the stack, and therefore
255 Obviously these quantities of iovecs are unrealistically large.
[all …]
|
| /src/crypto/openssl/doc/man7/ |
| H A D | OSSL_PROVIDER-base.pod | 38 These may be used in a property query string with fetching functions to select
52 These may be used in a property query string with fetching functions to select
58 The OpenSSL base provider supports these operations and algorithms:
137 In addition to this provider, all of these encoding algorithms are also
138 available in the default provider. Some of these algorithms may be used in
207 In addition to this provider, all of these decoding algorithms are also
208 available in the default provider. Some of these algorithms may be used in
221 In addition to this provider, all of these store algorithms are also
|
| /src/contrib/xz/src/liblzma/api/lzma/ |
| H A D | delta.h | 31 * these are not currently planned since byte-wise delta is almost as good.
41 * These options are needed by both encoder and decoder.
71 * breaking the ABI. You should not touch these, because the names
72 * of these variables may change. These are and will never be used
73 * when type is LZMA_DELTA_TYPE_BYTE, so it is safe to leave these
|
| /src/sys/contrib/dev/acpica/ |
| H A D | changes.txt | 203 is updated with new nodes. Add compile and dump functionality for these
513 A warning will be issued for each of these cases.
514 Note: For existing ASL/projects, these warnings may be disabled by
660 These included a few casts, as well as a null pointer check.
750 for these macros to a simple string literal - thus disallowing the use
758 Note: The MS compiler requires the use of string literals for these
972 parameters. This change swaps these parameter requirements. Now it is
1191 errors are directed to the console instead. These error messages
1221 buffers with no initializer list (these buffers will be filled with
1287 pointer" warnings, but these have been found to be false positive
[all …]
|