| /netbsd-src/external/ibm-public/postfix/dist/src/util/ |
| H A D | dict_cidr.map | 12 1.2.3.3 1.2.3.3 can't happen
13 1.2.3.4 1.2.3.4 can happen
14 1.2.3.5 1.2.3.5 can happen
15 1.2.3.6 1.2.3.6 can happen
16 1.2.3.7 1.2.3.7 can happen
17 1.2.3.8 1.2.3.8 can't happen
21 1.2.3.3 1.2.3.3 can happen
22 1.2.3.8 1.2.3.8 can happen
25 ::f3 ::f3 can't happen
26 ::f4 ::f4 can happen
[all …]
|
| H A D | dict_cidr.ref | 41 1.2.3.3=1.2.3.3 can happen
43 1.2.3.4=1.2.3.4 can happen
45 1.2.3.5=1.2.3.5 can happen
47 1.2.3.6=1.2.3.6 can happen
49 1.2.3.7=1.2.3.7 can happen
51 1.2.3.8=1.2.3.8 can happen
53 ::f3=::f3 can happen
55 ::f4=::f4 can happen
57 ::f5=::f5 can happen
59 ::f6=::f6 can happen
[all …]
|
| /netbsd-src/crypto/external/bsd/heimdal/dist/tests/can/ |
| H A D | Makefile.am | 9 SCRIPT_TESTS = check-can
25 check-can: check-can.in Makefile
26 $(do_subst) < $(srcdir)/check-can.in > check-can.tmp
27 chmod +x check-can.tmp
28 mv check-can.tmp check-can
50 check-can.in \
|
| /netbsd-src/external/bsd/ipf/dist/ |
| H A D | WhatsNew50.txt | 6 * all of the tuneables can now be set at any time, not just whilst disabled
13 * tunables can now be set via ipf.conf;
17 * ipmon.conf can now be used to generate SNMPv1 and SNMPv2 traps using
22 * DNS proxy for the kernel that can block queries based on domain names;
24 * FTP proxy can be configured to limit data connections to one or many
32 * simple encapsulation can now be configured with ipnat.conf,
38 * acceptance of ICMP packets for "keep state" rules can be refined through
45 * comments can now be a part of a rule and loaded into the kernel and
51 * interface names, aside from that the packet is on, can be present in
57 * rules can now be added with an expiration time, allowing for their
[all …]
|
| /netbsd-src/sys/external/bsd/sljit/dist/doc/ |
| H A D | overview.txt | 3 with SLJIT. Further details can be found in sljitLir.h.
11 - can be easily ported to wide-spread CPU
17 - can be translated to machine code efficiently
33 - integer registers, which can store either an
35 - floating point registers, which can store either a
99 Floating point registers can either contain a single
114 values and can be set by certain instructions.
118 - Most instructions can freely modify these status
122 - The SLJIT_SET_E, SLJIT_SET_U, etc. options can
133 since no instruction can set both of these flags. When
[all …]
|
| /netbsd-src/external/bsd/openldap/dist/doc/guide/release/ |
| H A D | autoconf-install.txt | 11 you can run in the future to recreate the current configuration, a file
18 diffs or instructions to the address given in the `README' so they can
45 5. You can remove the program binaries and object files from the
47 files that `configure' created (so you can compile the package for
58 the `configure' script does not know about. You can give `configure'
60 a Bourne-compatible shell, you can do that on the command line like
64 Or on systems that have the `env' program, you can do it like this:
70 You can compile the package for more than one kind of computer at the
88 `/usr/local/bin', `/usr/local/man', etc. You can specify an
92 You can specify separate installation prefixes for
[all …]
|
| /netbsd-src/external/bsd/openldap/dist/doc/install/ |
| H A D | configure | 15 you can run in the future to recreate the current configuration, a file
22 diffs or instructions to the address given in the `README' so they can
49 5. You can remove the program binaries and object files from the
51 files that `configure' created (so you can compile the package for
62 the `configure' script does not know about. You can give `configure'
64 a Bourne-compatible shell, you can do that on the command line like
68 Or on systems that have the `env' program, you can do it like this:
74 You can compile the package for more than one kind of computer at the
92 `/usr/local/bin', `/usr/local/man', etc. You can specify an
96 You can specify separate installation prefixes for
[all …]
|
| /netbsd-src/external/gpl2/grep/dist/ |
| H A D | INSTALL | 11 you can run in the future to recreate the current configuration, a file
18 diffs or instructions to the address given in the `README' so they can
45 5. You can remove the program binaries and object files from the
47 files that `configure' created (so you can compile the package for
58 the `configure' script does not know about. You can give `configure'
60 a Bourne-compatible shell, you can do that on the command line like
64 Or on systems that have the `env' program, you can do it like this:
70 You can compile the package for more than one kind of computer at the
88 `/usr/local/bin', `/usr/local/man', etc. You can specify an
92 You can specify separate installation prefixes for
[all …]
|
| /netbsd-src/external/bsd/less/dist/ |
| H A D | INSTALL | 16 you can run in the future to recreate the current configuration, a file
23 diffs or instructions to the address given in the `README' so they can
50 5. You can remove the program binaries and object files from the
52 files that `configure' created (so you can compile the package for
63 the `configure' script does not know about. You can give `configure'
65 a Bourne-compatible shell, you can do that on the command line like
69 Or on systems that have the `env' program, you can do it like this:
75 You can compile the package for more than one kind of computer at the
93 `/usr/local/bin', `/usr/local/man', etc. You can specify an
97 You can specify separate installation prefixes for
[all …]
|
| /netbsd-src/external/bsd/ntp/dist/ |
| H A D | INSTALL | 13 you can run in the future to recreate the current configuration, a file
20 diffs or instructions to the address given in the `README' so they can
47 5. You can remove the program binaries and object files from the
49 files that `configure' created (so you can compile the package for
60 the `configure' script does not know about. You can give `configure'
62 a Bourne-compatible shell, you can do that on the command line like
66 Or on systems that have the `env' program, you can do it like this:
72 You can compile the package for more than one kind of computer at the
90 `/usr/local/bin', `/usr/local/man', etc. You can specify an
94 You can specify separate installation prefixes for
[all …]
|
| /netbsd-src/external/gpl2/rcs/dist/ |
| H A D | INSTALL | 11 you can run in the future to recreate the current configuration, a file
18 diffs or instructions to the address given in the `README' so they can
45 5. You can remove the program binaries and object files from the
47 files that `configure' created (so you can compile the package for
58 the `configure' script does not know about. You can give `configure'
60 a Bourne-compatible shell, you can do that on the command line like
64 Or on systems that have the `env' program, you can do it like this:
70 You can compile the package for more than one kind of computer at the
88 `/usr/local/bin', `/usr/local/man', etc. You can specify an
92 You can specify separate installation prefixes for
[all …]
|
| /netbsd-src/games/fortune/datfiles/ |
| H A D | netbsd-tips | 5 You can keep specific rc.conf configurations in individual files
10 You can see the total used buffers in megabytes with:
18 You can view a value of a variable in pkgsrc by using the show-var
23 You can view the basic order of your rc.d scripts with:
27 You can ask questions about NetBSD at the netbsd-users@NetBSD.org
31 You can view your non-default Postfix settings with:
51 If your console ever gets broken, you can try resetting it to its
62 A new user can be added by using the useradd tool with the -m switch
71 You can temporarily start the SSH server by running the following
86 You can download files via HTTP using the ftp(1) command; for example:
[all …]
|
| /netbsd-src/external/bsd/wpa/dist/wpa_supplicant/ |
| H A D | README-Windows.txt | 46 wpa_supplicant can be built with Microsoft Visual C++ compiler. This
49 can also be used by creating a project that includes the files and
51 files are included in vs2005 subdirectory. This can be used as a
55 WinPcap development package is needed for the build and this can be
58 that Include and Lib directories are in this directory. The files can be
64 OpenSSL source package can be downloaded from
70 this directory can be modified by changing OPENSSLDIR variable in
82 needed) for it. Alternative, you can copy files from
90 wpa_supplicant can be built for cygwin by installing the needed
106 additional tool, win_if_list.exe, can be built by running "make
[all …]
|
| /netbsd-src/external/apache2/llvm/dist/llvm/docs/GlobalISel/ |
| H A D | Pipeline.rst | 33 the gMIR to suit what the backend can support. There is a very small set of
35 can shape the MIR as they wish.
80 alternatives but Combiners can also focus on code size or other metrics.
82 Additional passes such as these can be inserted to support higher optimization
87 Of course, combiners can be inserted in other places too. Also passes can be
100 function with the ``legalized`` property can have the ``MachineVerifier``
111 The main issue is that GlobalISel is a separate library, so we can't
126 can be serialized using ``-stop-before`` or ``-stop-after`` and loaded using
129 We can also go further still, as many of GlobalISel's passes are readily unit
136 FileCheck directives can be embedded using strings so you still have access to
[all …]
|
| /netbsd-src/external/gpl2/gettext/dist/gettext-runtime/ |
| H A D | INSTALL | 11 you can run in the future to recreate the current configuration, a file
18 diffs or instructions to the address given in the `README' so they can
45 5. You can remove the program binaries and object files from the
47 files that `configure' created (so you can compile the package for
58 the `configure' script does not know about. You can give `configure'
59 initial values for variables as arguments. You can do it like this:
65 You can compile the package for more than one kind of computer at the
83 `/usr/local/bin', `/usr/local/man', etc. You can specify an
87 You can specify separate installation prefixes for
93 In addition, if you use an unusual directory layout you can give
[all …]
|
| /netbsd-src/external/gpl2/gettext/dist/gettext-runtime/libasprintf/ |
| H A D | INSTALL | 11 you can run in the future to recreate the current configuration, a file
18 diffs or instructions to the address given in the `README' so they can
45 5. You can remove the program binaries and object files from the
47 files that `configure' created (so you can compile the package for
58 the `configure' script does not know about. You can give `configure'
59 initial values for variables as arguments. You can do it like this:
65 You can compile the package for more than one kind of computer at the
83 `/usr/local/bin', `/usr/local/man', etc. You can specify an
87 You can specify separate installation prefixes for
93 In addition, if you use an unusual directory layout you can give
[all …]
|
| /netbsd-src/external/gpl2/gettext/dist/ |
| H A D | INSTALL | 11 you can run in the future to recreate the current configuration, a file
18 diffs or instructions to the address given in the `README' so they can
45 5. You can remove the program binaries and object files from the
47 files that `configure' created (so you can compile the package for
58 the `configure' script does not know about. You can give `configure'
59 initial values for variables as arguments. You can do it like this:
65 You can compile the package for more than one kind of computer at the
83 `/usr/local/bin', `/usr/local/man', etc. You can specify an
87 You can specify separate installation prefixes for
93 In addition, if you use an unusual directory layout you can give
[all …]
|
| /netbsd-src/external/gpl2/gettext/dist/gettext-tools/ |
| H A D | INSTALL | 11 you can run in the future to recreate the current configuration, a file
18 diffs or instructions to the address given in the `README' so they can
45 5. You can remove the program binaries and object files from the
47 files that `configure' created (so you can compile the package for
58 the `configure' script does not know about. You can give `configure'
59 initial values for variables as arguments. You can do it like this:
65 You can compile the package for more than one kind of computer at the
83 `/usr/local/bin', `/usr/local/man', etc. You can specify an
87 You can specify separate installation prefixes for
93 In addition, if you use an unusual directory layout you can give
[all …]
|
| /netbsd-src/external/gpl2/gettext/dist/autoconf-lib-link/ |
| H A D | INSTALL | 11 you can run in the future to recreate the current configuration, a file
18 diffs or instructions to the address given in the `README' so they can
45 5. You can remove the program binaries and object files from the
47 files that `configure' created (so you can compile the package for
58 the `configure' script does not know about. You can give `configure'
59 initial values for variables as arguments. You can do it like this:
65 You can compile the package for more than one kind of computer at the
83 `/usr/local/bin', `/usr/local/man', etc. You can specify an
87 You can specify separate installation prefixes for
93 In addition, if you use an unusual directory layout you can give
[all …]
|
| /netbsd-src/external/apache2/llvm/dist/llvm/docs/ |
| H A D | XRay.rst | 15 instrumentation points and a runtime library that can dynamically enable and
18 More high level information about XRay can be found in the `XRay whitepaper`_.
45 You can use XRay in a couple of ways:
66 get XRay instrumentation points. You can tweak that number through the
73 The loop detection can be disabled with ``-fxray-ignore-loops`` to use only the
74 instruction threshold. You can also specifically instrument functions in your
76 You can do it using the GCC-style attributes or C++11-style attributes.
88 When linking a binary, you can either manually link in the `XRay Runtime
90 ``-fxray-instrument`` flag. Alternatively, you can statically link-in the XRay
98 If you're using LLVM IR directly, you can add the ``function-instrument``
[all …]
|
| /netbsd-src/crypto/external/bsd/openssl.old/dist/doc/man7/ |
| H A D | X25519.pod | 15 No additional parameters can be set during key generation.
22 A context for the B<X25519> algorithm can be obtained by calling:
26 For the B<X448> algorithm a context can be obtained by calling:
30 X25519 or X448 private keys can be set directly using
33 can also be generated (see the example below). Setting a private key also sets
36 X25519 or X448 public keys can be set directly using
55 The key derivation example in L<EVP_PKEY_derive(3)> can be used with
70 this file except in compliance with the License. You can obtain a copy
|
| /netbsd-src/crypto/external/bsd/openssl/dist/doc/man7/ |
| H A D | X25519.pod | 15 No additional parameters can be set during key generation.
22 A context for the B<X25519> algorithm can be obtained by calling:
26 For the B<X448> algorithm a context can be obtained by calling:
30 X25519 or X448 private keys can be set directly using
33 can also be generated (see the example below). Setting a private key also sets
36 X25519 or X448 public keys can be set directly using
55 The key derivation example in L<EVP_PKEY_derive(3)> can be used with
70 this file except in compliance with the License. You can obtain a copy
|
| /netbsd-src/external/gpl2/diffutils/dist/ |
| H A D | INSTALL | 17 you can run in the future to recreate the current configuration, and a
21 It can also use an optional file (typically called `config.cache'
29 diffs or instructions to the address given in the `README' so they can
58 5. You can remove the program binaries and object files from the
60 files that `configure' created (so you can compile the package for
74 You can give `configure' initial values for variables by setting
75 them in the environment. You can do that on the command line like this:
84 You can compile the package for more than one kind of computer at the
102 `/usr/local/bin', `/usr/local/man', etc. You can specify an
106 You can specify separate installation prefixes for
[all …]
|
| /netbsd-src/external/bsd/file/dist/ |
| H A D | INSTALL | 23 you can run in the future to recreate the current configuration, and a
27 It can also use an optional file (typically called `config.cache'
35 diffs or instructions to the address given in the `README' so they can
61 5. You can remove the program binaries and object files from the
63 files that `configure' created (so you can compile the package for
70 6. Often, you can also type `make uninstall' to remove the installed
80 You can give `configure' initial values for configuration parameters
91 You can compile the package for more than one kind of computer at the
93 own directory. To do this, you can use GNU `make'. `cd' to the
103 On MacOS X 10.5 and later systems, you can create libraries and
[all …]
|
| /netbsd-src/external/gpl2/groff/dist/ |
| H A D | INSTALL.gen | 20 you can run in the future to recreate the current configuration, and a
24 It can also use an optional file (typically called `config.cache'
32 diffs or instructions to the address given in the `README' so they can
61 5. You can remove the program binaries and object files from the
63 files that `configure' created (so you can compile the package for
77 You can give `configure' initial values for configuration parameters
88 You can compile the package for more than one kind of computer at the
106 `/usr/local/bin', `/usr/local/man', etc. You can specify an
110 You can specify separate installation prefixes for
116 In addition, if you use an unusual directory layout you can give
[all …]
|