Home
last modified time | relevance | path

Searched refs:each (Results 1 – 25 of 3527) sorted by relevance

12345678910>>...142

/titanic_50/usr/src/cmd/power/
H A Dsysidpm.po17 # When distributing Covered Code, include this CDDL HEADER in each
31 # In the following message, each escape sequence requires
35 # three backslashes for each escape sequence.
45 # In the following message, each escape sequence requires
49 # three backslashes for each escape sequence.
/titanic_50/usr/src/uts/common/io/ib/clients/rdsv3/
H A Dinfo.c171 klen = lens.nr * lens.each; in rdsv3_info_ioctl()
182 lens.each); in rdsv3_info_ioctl()
190 *rvalp = lens.each; in rdsv3_info_ioctl()
/titanic_50/usr/src/test/zfs-tests/tests/functional/inheritance/
H A DREADME.state13 # When distributing Covered Code, include this CDDL HEADER in each
70 # 1) there must be a <property src..> line corresponding to each dataset
75 # there must be at least one, and the effect of each block is cumulative
77 # each block. If that is desired then each block must be placed in its
H A Dstate007.cfg13 # When distributing Covered Code, include this CDDL HEADER in each
34 # used to verify that when we can set properties on each level of the
H A Dstate008.cfg13 # When distributing Covered Code, include this CDDL HEADER in each
35 # properties of each dataset have their default values.
H A Dstate009.cfg13 # When distributing Covered Code, include this CDDL HEADER in each
34 # data hierarchy where the properties of each dataset have their
H A Dstate010.cfg13 # When distributing Covered Code, include this CDDL HEADER in each
34 # data hierarchy where the properties of each dataset have their
H A Dstate011.cfg13 # When distributing Covered Code, include this CDDL HEADER in each
33 # Verify that running 'zfs inherit' at each level of the data hierarchy
H A Dstate013.cfg13 # When distributing Covered Code, include this CDDL HEADER in each
33 # Verify that executing 'zfs inherit' on each level when the middle
/titanic_50/usr/src/lib/libsqlite/test/
H A Dlastinsert.test74 create trigger r1 after insert on t1 for each row begin
113 create trigger r1 after update on t1 for each row begin
152 create trigger r1 instead of insert on v for each row begin
191 create trigger r1 before delete on t1 for each row begin
230 create trigger r1 instead of update on v for each row begin
274 create temp trigger r1 instead of insert on v1 for each row begin
280 create temp trigger r2 instead of insert on v2 for each row begin
H A Dlaststmtchanges.test87 create trigger r1 after insert on t1 for each row begin
119 create trigger r1 after update on t1 for each row begin
151 create trigger r1 before delete on t1 for each row begin
196 create temp trigger r1 instead of insert on v1 for each row begin
206 create temp trigger r2 instead of insert on v2 for each row begin
/titanic_50/usr/src/uts/common/io/e1000api/
H A DREADME.illumos17 thus while they used identical common code from Intel, they each only ever used
21 however, this code is not in its own module, each has its own copy of the code
25 an e1000_osdep.h. Currently each version of the driver defines its *own* version
27 that implements this is different in each directory, specifically e1000g_osdep.c
97 depend on rather than building separate copies of the common code into each
/titanic_50/usr/src/cmd/initpkg/init.d/
H A DREADME.rc314 # When distributing Covered Code, include this CDDL HEADER in each
36 each 'K' script within /etc/rc3.d/ with the argument 'stop', followed by
37 each 'S' script within /etc/rc3.d/ with the argument 'start'. All
/titanic_50/usr/src/lib/fm/libdiagcode/common/tests/
H A DREADME14 # When distributing Covered Code, include this CDDL HEADER in each
34 uses to tell it what tests to run against each dictionary. These
50 to each function. For example:
/titanic_50/usr/src/cmd/ssh/doc/
H A DWARNING.RNG35 The ssh_prng_cmds file also specifies a 'rate' for each program. This
48 Executing each program in the list can take a large amount of time,
54 "sshd -d -d -d"). This will list each program as it is executed, how
71 between versions of each OS.
/titanic_50/usr/src/test/zfs-tests/tests/functional/cli_user/zfs_list/
H A Dzfs_list.cfg13 # When distributing Covered Code, include this CDDL HEADER in each
32 # we want to set for each dataset.
/titanic_50/usr/src/cmd/vi/misc/
H A Ddel.h.cb14 * When distributing Covered Code, include this CDDL HEADER in each
29 ** only has one bit for each kind of delay so it's somewhat
34 ** particular system. For each type of delay, the bits used
/titanic_50/usr/src/common/
H A DREADME14 # When distributing Covered Code, include this CDDL HEADER in each
35 *each* of the derived components to ensure they all work.
/titanic_50/usr/src/uts/common/io/warlock/
H A Dst.wlcmd13 # When distributing Covered Code, include this CDDL HEADER in each
30 ### Give warlock a dummy target for each of the function
H A Dsd.wlcmd13 # When distributing Covered Code, include this CDDL HEADER in each
40 ### Give warlock a dummy target for each of the function
/titanic_50/usr/src/
H A DREADME.license-files13 # When distributing Covered Code, include this CDDL HEADER in each
41 you'll put one in each source directory (i.e. one per library,
47 that really are independent of each other, you may instead
67 2. Give each of the license files a corresponding ".descrip" file with
/titanic_50/usr/src/tools/pmodes/
H A DREADME.pmodes13 # When distributing Covered Code, include this CDDL HEADER in each
68 -v Preceed the output caused by each processed file by a
74 In default mode of operation, pmodes processes each argument.
82 Pmodes outputs a line for each change made:
/titanic_50/usr/src/cmd/sgs/rtld.4.x/
H A DMakefile.4.x14 # When distributing Covered Code, include this CDDL HEADER in each
39 # compile each object.
/titanic_50/usr/src/grub/
H A Dcapability13 # When distributing Covered Code, include this CDDL HEADER in each
29 # version is incremented by 1 each time there is a bugfix or enhancement to
/titanic_50/usr/src/cmd/sgs/rtld/common/
H A Drtld.chk.msg17 # When distributing Covered Code, include this CDDL HEADER in each
30 # aren't required for each target, but chkmsg has no way of dealing with

12345678910>>...142