/coreutils/tests/cp/ |
D | same-file.sh | 136 1 [cp: 'foo' and 'symlink' are the same file] (foo symlink -> foo) 137 1 -d [cp: 'foo' and 'symlink' are the same file] (foo symlink -> foo) 138 1 -f [cp: 'foo' and 'symlink' are the same file] (foo symlink -> foo) 139 1 -df [cp: 'foo' and 'symlink' are the same file] (foo symlink -> foo) 156 1 [cp: 'symlink' and 'foo' are the same file] (foo symlink -> foo) 157 1 -d [cp: 'symlink' and 'foo' are the same file] (foo symlink -> foo) 158 1 -f [cp: 'symlink' and 'foo' are the same file] (foo symlink -> foo) 159 1 -df [cp: 'symlink' and 'foo' are the same file] (foo symlink -> foo) 160 1 --rem [cp: 'symlink' and 'foo' are the same file] (foo symlink -> foo) 161 1 -b [cp: 'symlink' and 'foo' are the same file] (foo symlink -> foo) [all …]
|
/coreutils/tests/mv/ |
D | part-symlink.sh | 156 [cp: 'loc_reg' and 'rem_sl' are the same file] 169 [cp: 'loc_reg' and 'rem_sl' are the same file] 173 [cp: 'rem_sl' and 'loc_reg' are the same file] 176 [cp: 'rem_sl' and 'loc_reg' are the same file] 179 [cp: 'rem_sl' and 'loc_reg' are the same file] 182 [cp: 'rem_sl' and 'loc_reg' are the same file] 185 [cp: 'rem_sl' and 'loc_reg' are the same file] 192 [cp: 'rem_sl' and 'loc_reg' are the same file] 196 [cp: 'loc_sl' and 'rem_reg' are the same file] 199 [cp: 'loc_sl' and 'rem_reg' are the same file] [all …]
|
/coreutils/scripts/git-hooks/ |
D | commit-msg | 15 # program names and a few general category names. 54 and die "$ME: $log_file: the editor ($editor) failed, aborting\n"; 62 and return ''; 68 and return 'do not use a period "." at the end of the first line'; 76 and return 'invalid first word(s) of summary line: ' . join (', ', @bad); 81 # Given a $LOG_FILE name and a \@LINE buffer, 82 # read the contents of the file into the buffer and analyze it. 99 # and if we were to ignore them here, it could lead to committing 102 # Filter out leading blank and comment lines. 105 # Filter out blank and comment lines at EOF. [all …]
|
/coreutils/ |
D | README-install | 1 Please see the file INSTALL for generic build and installation instructions. 2 This file details coreutils and system specific build instructions. 12 in several files in src/. There is code in configure to find and, if 14 find a C99 compiler, it continues nonetheless, and your build will fail. 24 A known problem exists when compiling on HPUX on both hppa and ia64 25 in 64-bit mode (i.e., +DD64) on HP-UX 11.0, 11.11, and 11.23. This 28 compilation mode is 32-bit and the software compiles fine using the 42 OSF/1 4.0d and AIX build failures 62 however, this will mishandle timestamps after 2038, and please file 67 "make check" failure on IRIX 6.5 and Solaris <= 9 [all …]
|
D | README | 2 the GNU fileutils, sh-utils, and textutils packages. 5 counterparts, such as greater speed, additional options, and fewer 24 then see the file INSTALL for general compilation and installation 25 instructions, or README-install for system and coreutils specific instructions. 28 POSIX, with BSD and other extensions. For closer conformance, or 30 and the _POSIX2_VERSION environment variables, as described in 33 The ls, dir, and vdir commands are all separate executables instead of 40 Kaveh Ghazi, and François Pinard for help with debugging and porting 42 time to submit problem reports and fixes. All contributed changes are 52 on Debian's unstable distribution, and to all the kind folks who used [all …]
|
D | TODO | 2 over the years. Beware: some are quite old and no longer valid. To avoid 4 longer pertinent, please search the mailing list and post your intent 20 since the inttypes module and newer versions of gettext allow things 23 all instances of imaxtostr and umaxtostr in coreutils and gnulib. 25 cp --recursive: use fts and *at functions to perform directory traversals 26 in source and destination hierarchy rather than forming full file names. 28 become very long, and requires space and time that is quadratic in the 48 no longer incurs the overhead of saving src. dev/ino and dest. filename 52 See notes in README-install -- and remove them once there's a work-around. 61 Instead, maybe use a macro and return nonzero. [all …]
|
D | NEWS | 7 cp, mv, and install no longer issue spurious diagnostics like "failed 19 base32 and base64 no longer require padding when decoding. 26 and will take precedence over previously specified formats or hyperlink mode. 37 wc is now much faster in single-byte locales and somewhat faster in 45 On GNU/Linux s390x and alpha, programs like 'cp' and 'ls' no longer 57 'cp --sparse=never' will avoid copy-on-write (reflinking) and copy offloading, 73 factor, numfmt, and tsort now diagnose read errors on the input. 84 pinky, uptime, users, and who no longer misbehave on 32-bit GNU/Linux 85 platforms like x86 and ARM where time_t was historically 32 bits. 101 and is being built again on FreeBSD and Haiku. [all …]
|
D | HACKING | 11 https://git-scm.com/ and build from source. 26 dating back to 1991. The repository (the part you download, and which 35 If you *have* made changes and mistakenly committed them to "master", 36 do the following to put your changes on a private branch, "br", and 53 it if needed, and put your name and email address in place of these 61 Your first commit: the quick and dirty way 70 include a one-line summary, a blank line, and ChangeLog-style entries 74 a log message and authorship information as well as any permissions 80 (remember, it's only local) on the "master" branch, and that's where new 87 However, if your cloned directory is for a one-shot patch submission and [all …]
|
D | COPYING | 5 Everyone is permitted to copy and distribute verbatim copies 11 software and other kinds of works. 13 The licenses for most software and other practical works are designed 14 to take away your freedom to share and change the works. By contrast, 16 share and change all versions of a program--to make sure it remains free 24 have the freedom to distribute copies of free software (and charge for 27 free programs, and that you know you can do these things. 41 (1) assert copyright on the software, and (2) offer you this License 42 giving you legal permission to copy, distribute and/or modify it. 44 For the developers' and authors' protection, the GPL clearly explains [all …]
|
D | README-release | 17 and that the NixOS/Hydra autobuilder is reporting all is well: 50 Run the following on at least one SELinux-enabled (enforcing) and 60 may occur. Often there are other shells available, and you can select 73 * To set the date, version number, and release type [stable/alpha/beta] on 74 line 3 of NEWS, commit that, and tag the release; run: 76 build-aux/do-release-commit-and-tag X.Y stable 86 * Test the tarball. copy it to a few odd-ball systems and ensure that 87 it builds and passes all tests. 103 Once all the builds and tests have passed, 107 * Wait a few minutes (maybe up to 30?) and then use the release URLs to [all …]
|
D | README-hacking | 13 (The requirements to build from a release are much less and are just 15 Specific development tools and versions will be checked for and listed by 44 time and file system space requirements: 48 The next step is to get and check other files needed to build, 60 and the Git master copy: 69 If you get warnings with recent GCC and Glibc with default 94 Run the command "vc-dwim" and make sure its output (the diff of all 99 Run the command "git format-patch --stdout -1", and email its output 106 This program is free software: you can redistribute it and/or modify
|
D | bootstrap | 655 have gnulib sources on your machine, and 660 and history on your machine, and do not want 667 update this script, and then restart it with 683 For build prerequisites, environment variables like \$AUTOCONF and \$AMTAR 690 are fetched from that local directory. If it is a git repository and 695 submodule configured, then that submodule is initialized and updated 696 and sources are fetched from there. If GNULIB_REFDIR is set (either 697 as an environment variable or via the --gnulib-refdir option) and is 707 used. If it is a git repository and the configuration variable 711 If you maintain a package and want to pin a particular revision of the [all …]
|
/coreutils/doc/ |
D | perm.texi | 5 @c Permission is granted to copy, distribute and/or modify this document 8 @c Invariant Sections, with no Front-Cover Texts, and with no Back-Cover 20 * Operator Numeric Modes:: ANDing, ORing, and setting modes octally. 21 * Directory Setuid and Setgid:: Set-user-ID and set-group-ID on directories. 28 which control ordinary access to the file, and @dfn{special mode 41 permission to create and remove files in the directory. 62 Files are given an owner and group when they are created. Usually the 63 owner is the current user and the group is the group of the directory 65 file system the file is created on, and the way the file is created. You 66 can change the owner and group of a file by using the @command{chown} and [all …]
|
D | fdl.texi | 11 Everyone is permitted to copy and distribute verbatim copies 20 functional and useful document @dfn{free} in the sense of freedom: to 21 assure everyone the effective freedom to copy and redistribute it, 23 Secondarily, this License preserves for the author and publisher a way 49 licensee, and is addressed as ``you''. You accept the license if you 55 modifications and/or translated into another language. 60 subject (or to related matters) and contains nothing that could fall 79 be at most 5 words, and a Back-Cover Text may be at most 25 words. 86 drawing editor, and that is suitable for input to text formatters or 97 DTD, and standard-conforming simple HTML, [all …]
|
D | sort-version.texi | 5 @c Permission is granted to copy, distribute and/or modify this document 8 @c Invariant Sections, no Front-Cover Texts, and no Back-Cover 22 @dfn{Version sort} puts items such as file names and lines of 24 contains a mixture of letters and digits. 41 @samp{ls --sort=version}, @samp{sort -V}, and 49 Two GNU Coreutils programs use version sort: @command{ls} and @command{sort}. 103 @node Version sort and natural sort 104 @subsection Version sort and natural sort 113 general input such as textual strings and file names 116 In other contexts, such as other programs and other programming [all …]
|
D | coreutils.texi | 45 * basename: (coreutils)basename invocation. Strip directory and suffix. 47 * cat: (coreutils)cat invocation. Concatenate and write files. 51 * chown: (coreutils)chown invocation. Change file owners and groups. 58 * date: (coreutils)date invocation. Print/set system date and time. 59 * dd: (coreutils)dd invocation. Copy and convert a file. 78 * install: (coreutils)install invocation. Copy files and set attributes. 92 * nl: (coreutils)nl invocation. Number lines and write files. 101 * printf: (coreutils)printf invocation. Format and print data. 137 * uptime: (coreutils)uptime invocation. Print uptime and load. 140 * wc: (coreutils)wc invocation. Line, word, and byte counts. [all …]
|
/coreutils/.github/ |
D | ISSUE_TEMPLATE.txt | 3 Github is a downstream mirror and is not frequently monitored, 16 contains a list of some quirks and unexpected behavior (which are often 22 * Search the archives for previous questions and answers: 24 * Coreutils Mailing list (General usage and advice): 40 you experience a problem, and what the problem is). 42 * Include the operating system and the type of hardware you are using 44 * Include the exact command and parameters you have used. 45 * Clearly explain what is the output you expected to get, and what is 51 * List policy is reply-to-all, and non-subscribers may post. 64 output, and other content resulting in messages over about 40 kB. [all …]
|
D | PULL_REQUEST_TEMPLATE.txt | 4 Github is a downstream mirror and is not frequently monitored, 10 Before sending the bug, please consult the FAQ and Mailing list 15 and you can also contribute to its development. For information about 25 contains a list of some quirks and unexpected behavior (which are often 31 * Search the archives for previous questions and answers: 33 * Coreutils Mailing list (General usage and advice): 54 output, and other content resulting in messages over about 40 kB. 56 you encounter on the terminal, copy and paste the text to your message. 57 * List policy is reply-to-all, and non-subscribers may post. 64 files contain information about hacking and contributing to GNU coreutils: [all …]
|
/coreutils/man/ |
D | chmod.x | 36 removed; and \fB=\fP causes them to be added and causes unmentioned 49 and the permissions granted to users that are in neither of the two preceding 53 adding up the bits with values 4, 2, and 1. Omitted digits are 55 The first digit selects the set user ID (4) and set group ID (2) and 58 and execute (1); the third selects permissions for other users in the
|
D | id.x | 2 id \- print real and effective user and group IDs
|
D | tee.x | 2 tee \- read from standard input and write to standard output and files
|
/coreutils/tests/ |
D | filefrag-extent-compare | 5 # the logical block numbers and lengths from filefrag -v for each. 8 # This helper function, f, extracts logical block number and lengths. 24 and die "$ME: unexpected input: odd number of numbers; expected even\n"; 40 and last; 42 and ++$i, next; 64 # last extent can vary, and can extend beyond the length of the file. 74 ### Setup "GNU" style for perl-mode and cperl-mode.
|
/coreutils/m4/ |
D | include-exclude-prog.m4 | 4 dnl gives unlimited permission to copy and/or distribute it, 28 # install-by-default programs and the list of do-not-install-by-default 29 # programs, modify the former variable to reflect "no-install" and 45 # If you want to refrain from installing programs A and B, 64 # Fail upon a request to install and not-install the same program. 66 *" $gl_i "*) AC_MSG_ERROR(['$gl_i' is both included and excluded]) ;;
|
/coreutils/src/ |
D | dircolors.hin | 5 # Copying and distribution of this file, with or without modification, 6 # are permitted provided the copyright notice and this notice are preserved. 9 # The keywords COLOR, OPTIONS, and EIGHTBIT (honored by the 72 MISSING 00 # ... and the files they point to 76 STICKY_OTHER_WRITABLE 30;42 # dir that is sticky and other-writable (+t,o+w) 77 OTHER_WRITABLE 34;42 # dir that is other-writable (o+w) and not sticky 78 STICKY 37;44 # dir with the sticky bit set (+t) and not other-writable 87 # to color below. Put the suffix, a space, and the color init string. 88 # (and any comments you want to add after a '#').
|
/coreutils/tests/fmt/ |
D | goal-option.sh | 24 @command{fmt} prefers breaking lines at the end of a sentence, and tries to 31 Donald E. Knuth and Michael F. Plass 42 and tries to avoid line breaks after the first word of a sentence 49 E. Knuth and Michael F. Plass in ''Breaking Paragraphs Into
|