| /freebsd/contrib/tcsh/ |
| H A D | WishList | 55 Wish "tcsh -l" would accept other flags. At least "-c".
60 would be to not have the different environment for login compared to
61 other shells, but what I would really like is something like...
95 over the last line, and the copy paste it. It would be very nice, if
101 which would insert the last line of output, similarly <M-2> could
123 variable editing to understand string operations. So I would like to
168 A Csh compatability mode would be nice: I know tcsh is supposed to be
215 Wish tcsh would feature fc (fix command) as in bash !Wish tcsh would
221 Functions would be useful! As would being able to redirect stderr (or
233 "complete cd" at the shell prompt nothing is printed. It would be nice
[all …]
|
| /freebsd/contrib/llvm-project/lldb/include/lldb/ |
| H A D | lldb-defines.h | 62 5 // The register that would contain pointer size or less argument 1 (if any)
64 6 // The register that would contain pointer size or less argument 2 (if any)
66 7 // The register that would contain pointer size or less argument 3 (if any)
68 8 // The register that would contain pointer size or less argument 4 (if any)
70 9 // The register that would contain pointer size or less argument 5 (if any)
72 10 // The register that would contain pointer size or less argument 6 (if any)
74 11 // The register that would contain pointer size or less argument 7 (if any)
76 12 // The register that would contain pointer size or less argument 8 (if any)
78 13 // The register that would contain thread specific data, like TLS data and
108 // fly. That would have the added benefit of making this unreadable.
|
| /freebsd/sys/contrib/dev/iwlwifi/cfg/ |
| H A D | 22000.c | 189 * HT size; mac80211 would otherwise pick the HE max (256) by default.
225 * HT size; mac80211 would otherwise pick the HE max (256) by default.
238 * HT size; mac80211 would otherwise pick the HE max (256) by default.
251 * HT size; mac80211 would otherwise pick the HE max (256) by default.
263 * HT size; mac80211 would otherwise pick the HE max (256) by default.
276 * HT size; mac80211 would otherwise pick the HE max (256) by default.
289 * HT size; mac80211 would otherwise pick the HE max (256) by default.
301 * HT size; mac80211 would otherwise pick the HE max (256) by default.
315 * HT size; mac80211 would otherwise pick the HE max (256) by default.
328 * HT size; mac80211 would otherwis
[all...] |
| /freebsd/usr.sbin/cron/doc/ |
| H A D | MAIL | 70 This method would prove very helpful for those programs that get started
72 number would specify the base time, and the second number the repetition
98 figured it out ) but a comment feature would SURE BE NICE!.
111 Hi, I do have a BIG one that I would like. I want to log ALL output
114 This would seem to work best if done by cron, as it is now I have a google
148 or second since the command was last run would be pretty hard to
187 Get the picture? This would be compatible with existing versions of
189 that old crontabs would be handled correctly).
207 Log files! It would be nice to be able to specify a log for cron
209 The latter can of course be done with > and 2> but it would be nice if
[all …]
|
| /freebsd/contrib/bmake/unit-tests/ |
| H A D | directive-for-empty.mk | 30 # variables were real variables, calling 'empty' would work on them as well.
51 # loop would be naive and require many special cases, as there are many cases
109 # would be difficult to understand for humans as well. Technically, they are
112 # removed from the scope, which would need to make the outer 'i' visible
113 # again. This would suggest to use one variable scope per .for loop.
116 # a custom scope to be passed as parameter. This would have another side
119 # This would mean that the combination of a .for variable and the modifiers
120 # '::=', '::+=', '::?=', '::!=' and ':_' would lead to different behavior than
|
| H A D | cond-token-number.mk | 11 # Even though -0 is a number and would be accepted by strtod, it is not
22 # Even though +0 is a number and would be accepted by strtod, it is not
33 # Even though -1 is a number and would be accepted by strtod, it is not
44 # Even though +1 is a number and would be accepted by strtod, it is not
|
| /freebsd/lib/libpmc/pmu-events/arch/x86/amdzen3/ |
| H A D | other.json | 22 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
28 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
34 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
40 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
52 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
58 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
64 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
|
| /freebsd/sbin/ipf/ipnat/ |
| H A D | ipnat.5 | 40 would become
69 with no change in address, we would write it as:
234 This would be used with "pass out" rules that includes a stanza such
252 order. In this case, hme0 would be the return interface and le0 would be
254 interface, the correct syntax to use would be:
274 would result in 172.192.0.0/24 being mapped to 209.1.2.0/32
277 of (say) 172.192.0.2 wanted 260 simultaneous connections going out, they would
278 be limited to 252 with \fBmap-block\fP but would just \fImove on\fP to the next
294 This would only match packets that are coming from hosts that have a source
306 that we would like to match up with then we can define a pool using
[all …]
|
| /freebsd/share/doc/papers/devfs/ |
| H A D | paper.me | 112 device would be inode number 5, the paper-tape-punch number 6 and so on,
147 The first sign that this would not hold up as a solution came with
152 would allow a process to ``act as hardware'' for the tty.
153 The telnetd(8) daemon would read and write data on the ``master'' side of
154 the pseudo-tty and the user would be running on the ``slave'' side,
155 which would act just like any other tty: you could change the erase
168 just which special nodes they would need and how to create them were
174 a special boot sequence would take effect if the kernel or
176 This boot procedure would
269 devices would provide caching and alignment for disk device access.
[all …]
|
| /freebsd/share/doc/papers/jail/ |
| H A D | future.ms | 32 Limiting the scope of the raw socket would allow its safe use within
39 Specifically, this would require that the jail of a process play a rule in
72 A new jailkill() syscall would permit the direction of signals to
86 A jailinit would also present a central location for delivering
93 Improvements in the host environment would also assist in improving
98 These improvements in the jail framework would improve both raw
|
| /freebsd/lib/libc/string/ |
| H A D | strverscmp.3 | 36 (thus, the ordering would be "a", "b", "train").
38 (thus, the ordering would be "9", "10", "420" which is different to lexicographic order,
41 would have done).
44 (thus, the ordering would be "000", "00", "01", "010", "09", "0", "1", "9", "10").
|
| /freebsd/usr.bin/gzip/ |
| H A D | unpack.c | 41 * tree levels, each level would consume 1 byte (See [1]).
51 * [1] If we count EOB into the symbols, that would mean that we will
54 * will have at least 2 symbols. Therefore, pack(1) would reduce the
56 * range [0..254], so all levels' symbol count would fit into 1 byte.
65 * Represent the huffman tree in a similar way that pack(1) would
95 * We don't zero out pointers here because nobody else would ever
119 * The internal nodes would be 1/2 of total internal nodes and in unpackd_fill_inodesin()
121 * would be no internal node by definition. in unpackd_fill_inodesin()
220 * In order to fit the count in one byte, pack(1) would offset in unpack_parse_header()
225 * adjustment would be done later afterward. in unpack_parse_header()
|
| /freebsd/contrib/googletest/googlemock/include/gmock/ |
| H A D | gmock-nice-strict.h | 163 // Ideally, we would inherit base class's constructors through a using
164 // declaration, which would preserve their visibility. However, many existing
166 // constructors as public. These tests would need to be cleaned up first.
205 // Ideally, we would inherit base class's constructors through a using
206 // declaration, which would preserve their visibility. However, many existing
208 // constructors as public. These tests would need to be cleaned up first.
247 // Ideally, we would inherit base class's constructors through a using
248 // declaration, which would preserve their visibility. However, many existing
250 // constructors as public. These tests would need to be cleaned up first.
|
| /freebsd/crypto/openssl/crypto/property/ |
| H A D | README.md | 15 all of their implemented algorithms. E.g. the FIPS property would be set
47 maintained separately. This cache would be a hash table, indexed by
49 would share their definition structure. Again, reducing space use.
51 * A query cache is desirable. This would be a hash table keyed by the
52 algorithm identifier and the entire query string and it would map to
|
| /freebsd/share/doc/usd/04.csh/ |
| H A D | csh.1 | 119 I would especially like to thank Michael Ubell
331 command was executed; the shell would have created the file if it did
334 If it had existed previously these previous contents would have been discarded!
358 would more likely do
412 We would more likely say
426 then the sort program would sort lines from its
430 the standard input, it would sort lines as we typed them on the terminal
450 to see if there was an option to do this but would eventually discover
474 This would give us a sorted list of our files by size, but with the
690 For instance the word `~bill' would map to the pathname `/usr/bill'
[all …]
|
| /freebsd/contrib/tcp_wrappers/ |
| H A D | tcpdmatch.8 | 10 \fItcpdmatch\fR predicts how the tcp wrapper would handle a specific
36 \fItcpd\fR would do when client name lookup fails.
56 To predict how \fItcpd\fR would handle a telnet request from the local
67 To predict what tcpd would do when the client name does not match the
|
| /freebsd/sys/fs/fuse/ |
| H A D | fuse_file.h | 99 * filehandles in the vnode. One option would be to only store a single file
106 * Another option would be to never open FUSE files concurrently, but send a
107 * FUSE_ACCESS prior to every open after the first. That would give the server
144 * FOPEN_NONSEEKABLE: Adding support would require a new per-file
145 * or per-vnode attribute, which would have to be checked by
168 * file descriptor it would would be dangerous to include anything more than
|
| /freebsd/crypto/openssl/ |
| H A D | README-ENGINES.md | 76 would help make this happen.
190 following code would load and use it (NB: obviously this code has no
200 of thing. For example the above code excerpt would achieve much the
218 such commands through to ENGINEs. As such, you would select "dynamic"
219 as the ENGINE to use, and the parameters/commands you pass would
234 value. In such a case, the command would be passed to the ENGINE after
235 it has been initialised for use, and so the "-post" switch would be
248 would have to use "dynamic" to load any such ENGINE - but on the other
249 hand such applications would only have the memory footprint of any
293 before. 'gcc' on Linux, for example, would use the following syntax;
|
| /freebsd/contrib/llvm-project/libcxx/include/__chrono/ |
| H A D | time_zone.h | 95 …__info.result != -1, "cannot convert the local time; it would be before the minimum system clock v… in to_sys()
97 …__info.result != -2, "cannot convert the local time; it would be after the maximum system clock va… in to_sys()
125 …__info.result != -1, "cannot convert the local time; it would be before the minimum system clock v… in to_sys()
127 …__info.result != -2, "cannot convert the local time; it would be after the maximum system clock va… in to_sys()
141 "cannot convert the system time; it would be before the minimum local clock value"); in to_local()
145 "cannot convert the system time; it would be after the maximum local clock value"); in to_local()
|
| /freebsd/lib/libpmc/ |
| H A D | pmc.3 | 102 that its owner process would otherwise be permitted to debug.
431 An application would first invoke function
435 Signal handling would then be set up.
437 Next the application would allocate the PMCs it desires using function
443 If a log file is necessary for the PMCs to work, it would
447 Process scope PMCs would then be attached to their target processes
451 The PMCs would then be started using function
456 For PMCs that write events to the log file, this logged data would be
|
| /freebsd/contrib/llvm-project/llvm/lib/Target/SystemZ/ |
| H A D | README.txt | 61 part of 128-bit memory operations would probably need to be done
89 but truncating the load would give:
122 address into a register. In many cases it would be better to create
141 that rounded amount. It would be simpler to subtract the unrounded
158 for signed overflow check is currently quite bad. This would improve
|
| /freebsd/share/man/man9/ |
| H A D | counter.9 | 113 Enter mode that would allow the safe update of several counters via
165 oid that would represent a
177 oid that would represent a
189 oid that would represent an array of
206 oid that would represent an array of
|
| /freebsd/share/doc/psd/15.yacc/ |
| H A D | ss9 | 107 the parser would be a bit bigger, and the items would be seen, and reduced,
110 would be in danger of overflowing if a very long sequence were read.
121 Once again, the first rule would always be reduced exactly once, before the
123 and then the second rule would be reduced once for each item read.
|
| /freebsd/share/doc/smm/05.fastfs/ |
| H A D | 4.t | 167 less than it would be if the data blocks were written out
197 This would be especially desirable when transferring
199 We did not implement this because it would change the
201 user programs would be required to allocate buffers on page boundaries,
202 and data would disappear from buffers after being written.
206 This would allow contiguous disk blocks to be read
225 would require rewriting all the disk drivers in the system,
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | ASYNC_WAIT_CTX_new.pod | 53 this would have a one-to-one correspondence with an SSL connection.
99 waiting on by calling ASYNC_WAIT_CTX_set_wait_fd(). Typically this would be done
113 An example of typical usage might be an async capable engine. User code would
114 initiate cryptographic operations. The engine would initiate those operations
173 code would initiate cryptographic operations, and the engine code would dispatch
175 code would call ASYNC_pause_job() to return control to the user code. After
|