| /coreutils/src/ |
| D | mkfifo.c | 155 struct mode_change *change = mode_compile (specified_mode); in main() local
156 if (!change) in main()
160 newmode = mode_adjust (newmode, false, umask_value, change, nullptr); in main()
161 free (change); in main()
|
| D | chmod.c | 69 static struct mode_change *change; variable
279 umask_value, change, nullptr); in process_file()
306 0, change, nullptr); in process_file()
538 change = mode_create_from_ref (reference_file); in main()
539 if (!change) in main()
545 change = mode_compile (mode); in main()
546 if (!change) in main()
|
| D | mknod.c | 152 struct mode_change *change = mode_compile (specified_mode); in main() local
153 if (!change) in main()
157 newmode = mode_adjust (newmode, false, umask_value, change, nullptr); in main()
158 free (change); in main()
|
| D | mkdir.c | 288 struct mode_change *change = mode_compile (specified_mode); in main() local
289 if (!change) in main()
292 options.mode = mode_adjust (S_IRWXUGO, true, umask_value, change, in main()
295 free (change); in main()
|
| D | install.c | 989 struct mode_change *change = mode_compile (specified_mode); in main() local
990 if (!change) in main()
992 mode = mode_adjust (0, false, 0, change, nullptr); in main()
993 dir_mode = mode_adjust (0, true, 0, change, &dir_mode_bits); in main()
994 free (change); in main()
|
| /coreutils/man/ |
| D | chcon.x | 2 chcon \- change file security context
|
| D | stty.x | 2 stty \- change and print terminal line settings
|
| D | chgrp.x | 2 chgrp \- change group ownership
|
| D | touch.x | 2 touch \- change file timestamps
|
| D | chmod.x | 65 system call cannot change their permissions. This is not a problem
|
| /coreutils/ |
| D | HACKING | 63 First of all, realize that to "commit" a change in git is a purely
73 Once your change is committed, you can create a proper patch that includes
75 changes. Use this command to save that single, most-recent change set:
79 The trouble with this approach is that you've just checked in a change
143 So, you've committed a change. But it's only in your local repository,
149 the next-to-last change set.
187 Amending the most recent change on your private branch
189 Let's say you've just committed a change on your private
197 That replaces the most recent change-set with the revised one.
219 to write a few lines of prose describing the change, when the summary
[all …]
|
| D | .mailmap | 14 <P@draigBrady.com> <P@draigBrady.com (trivial change)>
|
| D | NEWS | 375 when their modification time doesn't change when new data is available.
590 directory merely because it was removed. This reverts a change
1098 env now has a --chdir (-C) option to change the working directory before
1519 chroot accepts the new --skip-chdir option to not change the working directory
1707 you can't make a second symlink to any program because that will change the
2431 cp -r could mistakenly change the permissions of an existing destination
2725 part of seconds since the epoch. This reverts a change from
2732 However, with the above change to %X, %Y and %Z, we've made %W work
2793 operating on trees with no hard-linked files, there is no change.
2878 Thus, if a login tty's group would change somehow e.g., to "root",
[all …]
|
| D | COPYING | 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
26 want it, that you can change the software or use pieces of it in new
53 protecting users' freedom to change the software. The systematic
627 free software which everyone can redistribute and change under these terms.
|
| D | TODO | 8 Modify chmod so that it does not change an inode's st_ctime
|
| D | README | 66 consensus that it is a worthwhile change. One way to do that is to send
|
| D | init.cfg | 273 # 2) setfacl only invokes the underlying system call if the ACL would change.
275 # If the given ACL spec would not change the ACLs on the file, then setfacl
|
| /coreutils/doc/ |
| D | perm.texi | 40 permission to write to (change) the file. For directories, this means
66 can change the owner and group of a file by using the @command{chown} and
204 The @var{operation} part tells how to change the affected users' access
295 started out as mode 664 (@samp{rw-rw-r--}), the above mode would change
297 741 (@samp{rwxr----x}), the above mode would change it to mode 745
306 you can change its special mode bits. @xref{Mode Structure}, for a
309 To change the file mode bits to set the user ID on execution, use
313 To change the file mode bits to set the group ID on execution, use
321 To change the file mode bits to set the restricted deletion flag or sticky bit,
|
| D | coreutils.texi | 119 * stty: (coreutils)stty invocation. Print/change terminal settings.
402 * stty invocation:: Print or change terminal characteristics
406 @command{stty}: Print or change terminal characteristics
943 change in the future. For @command{ls} file sizes, the block size
1506 that can be used to change how other commands work.
2777 not change with different values of left @var{margin}. That means a
3149 use @option{--sleep-interval=@var{n}} to change that default -- which can
4480 and check for order. The following options change the operation
4553 can change this. Note blanks may be ignored by your locale's collating
4568 is a space or a tab, but the @env{LC_CTYPE} locale can change this.
[all …]
|
| /coreutils/tests/chgrp/ |
| D | basic.sh | 105 *) echo $host_triplet: no-change chgrp failed to update ctime 1>&2;
|
| /coreutils/.github/ |
| D | PULL_REQUEST_TEMPLATE.txt | 79 If your change is significant (i.e., if it adds more than ~10 lines),
|
| /coreutils/scripts/build-older-versions/ |
| D | README.older-versions | 55 The patch files in this directory change the source code of older
|