Home
last modified time | relevance | path

Searched refs:where (Results 1 – 13 of 13) sorted by relevance

/coreutils/tests/cp/
Dcp-mv-enotsup-xattr.sh33 where="$1"
36 fs="$where.bin"
40 mkdir "$where" || skip=1
43 mount -oloop,$opts "$fs" "$where" || skip=1
44 echo test > "$where"/f || skip=1
45 test -s "$where"/f || skip=1
/coreutils/src/
Dtimeout.c180 send_sig (pid_t where, int sig) in send_sig() argument
189 if (where == 0) in send_sig()
191 return kill (where, sig); in send_sig()
/coreutils/
Dbootstrap653 GNULIB_SRCDIR Specifies the local directory where gnulib
657 GNULIB_REFDIR Specifies the local directory where a gnulib
894 GNULIB_SRCDIR Specifies the local directory where gnulib
1345 GNULIB_SRCDIR Specifies the local directory where gnulib
1358 --gnulib-srcdir=DIRNAME specify the local directory where gnulib
1363 --gnulib-refdir=DIRNAME specify the local directory where a gnulib
DNEWS85 platforms like x86 and ARM where time_t was historically 32 bits.
120 where it was unclear whether 'dir' or 'x/dir' was the problem.
122 Similarly for other renames where the destination must be the problem.
148 On GNU/Linux platforms where utmp-format files have 32-bit timestamps,
255 like x86_64 where 'long double' has padding bits in memory.
285 in others, where they exceed integer width limits, they now elicit
437 causes problems on platforms where user names contain ".".
638 and at least 8 times faster where pclmul instructions are supported.
648 This is the case on GNU/Linux systems, where the trailing slash is ignored.
657 where avx2 instructions are supported.
[all …]
DREADME-install58 can be fixed by using 64-bit builds. For example, on AIX where GCC
DREADME-hacking33 where '<packagename>' stands for 'coreutils' or whatever other package
DCOPYING55 use, which is precisely where it is most unacceptable. Therefore, we
283 clear directions next to the object code saying where to find the
289 you inform other peers where the object code and Corresponding
401 where to find the applicable terms.
632 the "copyright" line and a pointer to where the full notice is found.
DTODO34 platforms where the native *printf(3) is deficient.
DHACKING49 authorship. That is important not just to give credit where due, but
80 (remember, it's only local) on the "master" branch, and that's where new
597 If you don't know where to start, check out the TODO file for projects
Dinit.cfg569 # Use timeout if available to skip cases where SEEK_DATA takes a long time.
/coreutils/doc/
Dsort-version.texi307 This sorting order (where @samp{8.5} comes before @samp{8.49}) is common when
579 The following additional rules apply when comparing two strings where
581 strings where both begin with @samp{.} but neither is @samp{.} or @samp{..}.
694 @file{hello-8.2.txt}, and this is where the suffix-removal comes into play:
Dcoreutils.texi1185 and it must work even in a pathological situation where
1285 In the opposite situation, where you want the last operand to be
1411 @c Append the following warning to -L where appropriate (e.g. chown).
2581 is @samp{Page @var{number}} where @var{number} is the decimal page
3388 Split @var{input} to @var{chunks} output files where @var{chunks} may be:
3415 When the input is a pipe or some other special file where the size
3674 Suppress the generation of zero-length output files. (In cases where
4060 Binary mode is the default on systems where it's significant,
4140 Use network byte order (big endian) where applicable:
4515 merge; merging is provided because it is faster, in the case where it
[all …]
Dperm.texi153 where @var{perms} is either zero or more letters from the set
227 @samp{=} operation, where it gives the specified @var{users} no access