Lines Matching refs:bits
46 fail on files with inode numbers that do not fit into 32 bits.
85 platforms like x86 and ARM where time_t was historically 32 bits.
92 shred again operates on Solaris when built for 64 bits.
255 like x86_64 where 'long double' has padding bits in memory.
890 and leaves mode bits of existing files unchanged.
891 Previously it would have set executable bits on created special files,
892 and set mode bits for existing files as if they had been created.
1591 chmod -Rc no longer issues erroneous warnings for files with special bits set.
2261 modes do not preserve directory setuid and setgid bits; for example,
2265 setuid and setgid bits, so that 'chmod 00755 FOO' now clears FOO's setuid
2266 and setgid bits. This allows scripts to be portable to other systems which
2268 modes do not preserve directory setuid and setgid bits.
2877 permission bits, and not consider the group of the TTY device file.
2880 of whatever the permission bits might imply. Now, when configured
4036 When cp -p copied a file with special mode bits set, the same bits
4039 To fix this, special mode bits are now set in the copy only if its
4248 set-group-ID bits unless you explicitly request otherwise. E.g.,
4250 set-user-ID and set-group-ID bits instead of clearing them, and
4252 clear the bits, mention them explicitly in a symbolic mode, e.g.,
4256 systems where these bits inherit from parents. Unfortunately other
4258 cannot assume the bits are set, cleared, or preserved, even when the
4259 bits are explicitly mentioned. For example, OpenBSD 3.9 'mkdir -m
4313 mkfifo and mknod no longer set special mode bits (setuid, setgid,
4798 special permission bits, as POSIX requires.
5388 - chown no longer tries to preserve set-user-ID and set-group-ID bits;
5389 on some systems, the chown syscall resets those bits, and previous
5396 those bits), an unwary admin. could use chown unwittingly to create e.g.,
5679 * cp now ensures that the set-user-ID and set-group-ID bits are cleared for