/freebsd/sys/contrib/libsodium/test/default/ |
H A D | kdf.exp | 11 Failure -- probably expected for output length=0 12 Failure -- probably expected for output length=1 13 Failure -- probably expected for output length=2 14 Failure -- probably expected for output length=3 15 Failure -- probably expected for output length=4 16 Failure -- probably expected for output length=5 17 Failure -- probably expected for output length=6 18 Failure -- probably expected for output length=7 19 Failure -- probably expected for output length=8 20 Failure -- probably expected for output length=9 [all …]
|
/freebsd/share/termcap/ |
H A D | README | 6 will probably be small, and can be empty if you like, but you should 7 probably put your own terminal in it. 15 although they don't have to go to the front, they are probably quite 29 will probably be in subdirectories with the other UCB software. 42 It is probably easiest to make local termcap changes in separate
|
/freebsd/contrib/file/magic/Magdir/ |
H A D | alliant | 7 # instruction set, the "short" should probably become "beshort" and the 8 # "long" should probably become "belong". 9 # If it's the i860-based one, they should probably become either the
|
/freebsd/sys/compat/freebsd32/ |
H A D | syscalls.conf | 50 # afs3_syscall - requires significant porting, probably doesn't make sense 53 # nlm_syscall - requires significant porting, probably doesn't make sense 54 # nnpfs_syscall - requires significant porting, probably doesn't make sense
|
/freebsd/crypto/krb5/src/lib/krb5/asn.1/ |
H A D | TODO.asn1 | 36 better than relying on the "type_*" variable names. Probably use 42 exported probably. 72 compiler the function will probably collapse to a simple
|
/freebsd/contrib/bmake/unit-tests/ |
H A D | directive-if.mk | 65 # expect+1: Quotes in plain words are probably a mistake. 66 . info Quotes in plain words are probably a mistake. 67 # XXX: Accepting quotes in plain words is probably a mistake as well.
|
H A D | dep-var.mk | 5 # Uh oh, this feels so strange that probably nobody uses it. But it seems to 50 # therefore this feature is probably not widely used. 64 # probably be appropriate to just error out in such a case.
|
/freebsd/crypto/krb5/src/man/ |
H A D | sserver.man | 137 This probably means you didn\(aqt edit /etc/inetd.conf correctly, or 167 This probably means sserver couldn\(aqt find the keytab file. It was 168 probably not installed in the proper directory.
|
/freebsd/sys/contrib/device-tree/src/arm/st/ |
H A D | ste-db9500.dtsi | 23 * This is probably only used if the kernel tries 25 * applications, which the mainline kernel probably
|
H A D | ste-db8500.dtsi | 41 * This is probably only used if the kernel tries 43 * applications, which the mainline kernel probably
|
H A D | ste-db8520.dtsi | 41 * This is probably only used if the kernel tries 43 * applications, which the mainline kernel probably
|
/freebsd/crypto/openssl/doc/man3/ |
H A D | SSL_get_client_random.pod | 49 You probably shouldn't use these functions. 52 use in low-level protocols. You probably should not use them, unless 64 secret, you should probably use SSL_export_keying_material() instead, and
|
H A D | OPENSSL_fork_prepare.pod | 33 Platforms without fork(2) will probably not need to use these functions. 34 Platforms with fork(2) but without pthread_atfork(3) will probably need
|
/freebsd/tools/regression/ |
H A D | TODO | 11 This probably means a simple libtest.so that they can link against to 12 provide an ok() function (the non-fatal assert), probably with some helper
|
/freebsd/contrib/sqlite3/tea/ |
H A D | pkgIndex.tcl.in | 4 # Unless this file is named pkgIndex.tcl.in, you are probably looking 5 # at an automatically generated/filtered copy and should probably not
|
H A D | _teaish.tester.tcl.in | 3 # Unless this file is named _teaish.tester.tcl.in, you are probably 5 # probably not edit it.
|
/freebsd/secure/lib/libcrypto/man/man3/ |
H A D | SSL_get_client_random.3 | 107 You probably shouldn't use these functions. 110 use in low-level protocols. You probably should not use them, unless 122 secret, you should probably use \fBSSL_export_keying_material()\fR instead, and
|
/freebsd/usr.bin/indent/ |
H A D | README | 5 to be completely redone, but it is probably the nicest C pretty printer 68 | Berkeley's copyright probably should only cover their changes, and I 89 me know that 4.3 version is off-limits, in which case we would probably
|
/freebsd/lib/libdevstat/ |
H A D | devstat.3 | 346 This may be the wrong behavior, and probably requires additional thought. 802 There should probably be an interface to de-allocate memory allocated by 811 should probably not select more than 817 There should probably be functions to perform the statistics buffer 824 structures should probably be cleaned up and thought out a little more.
|
/freebsd/sys/contrib/zlib/ |
H A D | FAQ | 101 can #include <zlib.h>, it's there. The -lz option will probably link to 283 Probably what you want is to use zlib in Java. zlib is already included 310 Probably not. Look in the comp.compression FAQ for pointers to various 324 probably have called the second one "zlib" instead to avoid confusion with 332 for), using the "gzip" transfer encoding is probably more reliable due to 346 There are no zip functions in zlib. You are probably using minizip by
|
/freebsd/tests/sys/ses/ |
H A D | nondestructive.c | 102 /* Probably an SGPIO device */ in do_getelmdesc() 302 /* Probably an SGPIO device */ in do_getelmmap() 362 /* Probably an SGPIO device */ in do_getelmstat() 432 /* Probably SGPIO; sg_ses unsupported */ in do_getencid() 477 // Probably an SGPIO device, INQUIRY unsupported in do_getencname() 518 /* Probably on SGPIO device */ in do_getencstat() 575 /* Probably SGPIO, sg_ses unsupported */ in do_getnelm()
|
/freebsd/crypto/openssl/doc/designs/quic-design/ |
H A D | dgram-api.md | 221 these allocations probably will need to be on the stack, and therefore 372 like setters and getters of the same variables from the name.) We probably want 385 We probably want this for our own QUIC implementation built on top of this 398 QUIC implementation so probably not a big deal. We can always support 427 Since we will probably need to support platforms without 448 Probably not worth supporting this. So we can have the following rule: 476 contention suggest that this probably wouldn't be a good idea anyway.
|
/freebsd/lib/libutil/ |
H A D | pidfile.3 | 256 Probably called before 287 Probably called not from the process which made 311 Probably called not from the process which used
|
/freebsd/contrib/nvi/cl/ |
H A D | README.signal | 11 *probably* start blocking around any imported function that we don't know 121 This is probably the easiest to code, and provides the smoothest 145 program goes to sleep immediately (since it probably didn't have a SIGTSTP 171 The simplest solution is probably to twiddle the tty, install a handler for
|
/freebsd/contrib/pam-krb5/ |
H A D | TODO | 24 Kerberos upstream, the best approach is probably to configure a custom 39 that would trigger password expiration handling, which probably isn't
|