Searched full:able (Results 1 – 25 of 2996) sorted by relevance
12345678910>>...120
| /freebsd-13-stable/tests/sys/cddl/zfs/tests/cli_root/zpool_upgrade/ |
| HD | zpool_upgrade.cfg | 36 # work out which types of pool we should be able to upgrade on this
176 # This statement builds up a list of configurations we should be able to
181 # we should be able to upgrade pools of version 1
186 # we should be able to upgrade pools of version 1 & 2
191 # we should be able to upgrade pools of version 1, 2 & 3
197 # we should be able to upgrade pools of version 1, 2, 3 & 4
203 # we should be able to upgrade pools up to version 5
209 # we should be able to upgrade pools up to version 6
215 # we should be able to upgrade pools up to version 7
221 # we should be able to upgrade pools up to version 8
[all …]
|
| HD | zpool_upgrade_009_neg.ksh | 41 # Zpool upgrade -V shouldn't be able to upgrade a pool to an unknown version
66 "Zpool upgrade -V shouldn't be able to upgrade a pool to an unknown version"
89 "Zpool upgrade -V shouldn't be able to upgrade a pool to an unknown version"
|
| HD | zpool_upgrade_008_pos.ksh | 41 # Zpool upgrade should be able to upgrade pools to a given version using -V
69 "Zpool upgrade should be able to upgrade pools to a given version using -V"
97 "Zpool upgrade should be able to upgrade pools to a given version using -V"
|
| /freebsd-13-stable/sys/contrib/openzfs/tests/zfs-tests/tests/functional/cli_root/zpool_set/ |
| HD | zpool_set_features.ksh | 21 # 'zpool set' should be able to enable features on pools
25 # 2. Verify 'zpool set' is able to enable a single feature
27 # 4. Verify 'zpool set' is *not* able to disable a single feature
39 log_assert "'zpool set' should be able to enable features on pools"
52 # Verify 'zpool set' is able to enable a single feature
63 # Verify 'zpool set' is *not* able to disable a single feature
|
| /freebsd-13-stable/sys/contrib/openzfs/tests/zfs-tests/tests/functional/rsend/ |
| HD | send_encrypted_props.ksh | 88 log_note "Must not be able to receive an embedded stream as encrypted"
93 log_note "Must not be able to use 'keylocation=prompt' on receive"
102 log_note "Must not be able to disable encryption properties on raw send"
110 log_note "Must not be able to change encryption properties on incrementals"
122 log_note "Must be able to receive stream as encryption root"
137 log_note "Must be able to override sharesmb property for encrypted raw stream"
146 log_note "Must be able to receive stream with props as encryption root"
164 log_note "Must be able to receive recursive stream as encryption root"
180 log_note "Must be able to receive stream with props to encrypted child"
194 log_note "Must be able to receive recursive stream to encrypted child"
[all …]
|
| /freebsd-13-stable/cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/privs/ |
| HD | tst.procpriv.ksh | 29 # When we have dtrace_proc (but lack dtrace_kernel), we expect to be able to
32 # structures that we know we shouldn't be able to read, as they require reading
34 # are a few fields that we may or may not be able to read depending on the
36 # think we should be able to, that we can't read what we think we shouldn't be
37 # able to, and (for purposes of completeness) that we are indifferent about
82 * be able to read pr_pgid -- but we won't if not.
|
| /freebsd-13-stable/sys/contrib/openzfs/tests/zfs-tests/tests/functional/cli_root/zpool_upgrade/ |
| HD | zpool_upgrade_009_neg.ksh | 38 # zpool upgrade -V shouldn't be able to upgrade a pool to an unknown version
53 log_assert "zpool upgrade -V shouldn't be able to upgrade a pool to" \
65 log_pass "zpool upgrade -V shouldn't be able to upgrade a pool to" \
|
| HD | zpool_upgrade_008_pos.ksh | 39 # zpool upgrade should be able to upgrade pools to a given version using -V
57 log_assert "zpool upgrade should be able to upgrade pools to a given version" \
79 log_pass "zpool upgrade should be able to upgrade pools to a given version" \
|
| /freebsd-13-stable/usr.sbin/jail/ |
| HD | jail.8 | 451 This determines what information processes in a jail are able to get
542 privileged users inside the jail will be able to mount and unmount file
552 privileged users inside the jail will be able to mount and unmount the
659 privileged users inside the jail will be able to mount and unmount the
667 privileged users inside the jail will be able to mount and unmount
675 privileged users inside the jail will be able to mount and unmount the
683 privileged users inside the jail will be able to mount and unmount the
691 privileged users inside the jail will be able to mount and unmount the
699 privileged users inside the jail will be able to mount and unmount the
707 privileged users inside the jail will be able to mount and unmount the
[all …]
|
| /freebsd-13-stable/usr.bin/diff/tests/ |
| HD | simple.out | 2 < to be able to test diff
5 > to be able to test diff utility
|
| HD | simple_u.out | 5 -to be able to test diff
7 +to be able to test diff utility
|
| /freebsd-13-stable/sys/contrib/openzfs/tests/zfs-tests/tests/functional/acl/posix-sa/ |
| D | posix_001_pos.ksh | 63 # Should be able to write to file
86 # Should NOT be able to create new file
89 # Root should be able to run file, but not user
|
| /freebsd-13-stable/sys/contrib/openzfs/tests/zfs-tests/tests/functional/acl/posix/ |
| HD | posix_001_pos.ksh | 63 # Should be able to write to file
86 # Should NOT be able to create new file
89 # Root should be able to run file, but not user
|
| /freebsd-13-stable/contrib/apr-util/ |
| HD | README.FREETDS | 2 It is known to have problems, and we are not able to maintain it.
4 The source code is still available. If you want it and are able
|
| /freebsd-13-stable/share/man/man9/ |
| HD | crypto_driver.9 | 193 If this method is not able to complete a request due to insufficient
285 indicates which types of requests the driver is able to handle again:
288 indicates that the driver is able to handle symmetric requests passed to
291 indicates that the driver is able to handle asymmetric requests passed to
|
| /freebsd-13-stable/sbin/fsck/ |
| HD | fsck.8 | 169 or if it is able to do its job in background after the
173 A zero exit code indicates that it is able to run later in background
181 or if it is able to do its job in background after the
185 A zero exit code indicates that it is able to run in background
|
| /freebsd-13-stable/tests/sys/netpfil/common/ |
| HD | tos.sh | 57 # Check if the firewall is able to set the ToS bits
72 # Check if the firewall is able to set the ToS bits
87 # Check if the firewall is able to filter the
|
| /freebsd-13-stable/sys/contrib/device-tree/Bindings/power/ |
| HD | power-controller.txt | 4 sometimes able to control the system power. The device driver associated with these
8 marks the device as able to control the system power. In order to test if this
|
| /freebsd-13-stable/sys/contrib/device-tree/Bindings/power/supply/ |
| HD | axp20x_ac_power.txt | 14 The AXP22X is only able to tell if an AC power supply is present and
17 AXP813/AXP803 are able to limit current and supply voltage
|
| /freebsd-13-stable/crypto/heimdal/appl/telnet/telnetd/ |
| HD | telnetd.8 | 401 Indicates a desire to be able to request the
412 Indicates a desire to be able to request information
416 Indicates a desire to be able to request the name
420 Indicates a desire to be able to request environment
423 Indicates a desire to be able to request environment
|
| /freebsd-13-stable/sys/fs/cd9660/ |
| HD | TODO.hibler | 3 Since it was modelled after the inode code, we might be able to merge
7 2. It would be nice to be able to use the vfs_cluster code.
|
| /freebsd-13-stable/lib/libpmc/pmu-events/arch/x86/silvermont/ |
| HD | other.json | 7 …es that fetch is stalled due to any reason. That is, the decoder queue is able to accept bytes, bu…
16 …is stalled due to an outstanding ITLB miss. That is, the decoder queue is able to accept bytes, bu…
|
| /freebsd-13-stable/share/man/man7/ |
| HD | security.7 | 94 It may not be able to take your machine down, but it can fill up your Internet
121 able to do nothing more than mess with the user's files or crash the machine.
129 may find a bug in a root-run server and be able to break root over a network
197 Of course, as a sysadmin you have to be able to get to root, so we open up
251 This way an intruder may be able to steal the password
252 file but will not be able to break into any staff accounts or root, even if
272 Being able
329 onion approach to security still stands: if someone is able to break in
395 intruder might be able to read
418 may not be able to do so with any general user accounts you might have.
[all …]
|
| /freebsd-13-stable/usr.sbin/bluetooth/rfcomm_pppd/ |
| HD | rfcomm_pppd.8 | 219 enable lqr
242 enable lqr
272 enable force-scripts
284 enable dns
|
| /freebsd-13-stable/tests/sys/cddl/zfs/tests/xattr/ |
| HD | xattr_007_neg.ksh | 38 # we shouldn't be able to list the xattrs of files in snapshots who didn't have
82 # we shouldn't be able to alter the first file's xattr
89 # we shouldn't be able to list xattrs at all on the second file
|
12345678910>>...120