Lines Matching refs:change

287         such a conflict is undefined, and may change in future releases.
503   +o  You can't change the uid or gid of files.
517   +o  You can't change permissions on directories.
519   +o  You can't change the uid or gid of directories.
544   unable to change the uid, gid or mode of files.  This is normal and is
562   to change the permissions on files.  These errors can safely be
581   to change the permissions on files.  These errors can safely be
599   to change the permissions on files.  These errors can safely be
607   about being unable to change the uid, gid or mode of files.  This is
623   to change the permissions on files.  These errors can safely be
639   to change the permissions on files.  These errors can safely be
656   to change the permissions on files.  These errors can safely be
664   about being unable to change the uid, gid or mode of files.  This is
680   to change the permissions on files.  These errors can safely be
696   to change the permissions on files.  These errors can safely be
709   ``Operation not permitted'' errors from cp when it tries to change the
717   files to change things such as the Creator and Type of a file.
720   special files that you can't change (writes to them will fail
754                __u8    fi_utime[4];            /* Un*x time of last mtime change */
811   header layout.  You may write to the header to change the layout, but
813   the change in format is lost and subsequent opens will yield the
823   and will hopefully change sooner rather than later.
863   Entry id 3 (``Real Name'') is read-only, since it will change
887   field does not change automatically to reflect any modification of the
888   data fork directly (the data does change however).  If the data fork
899   Calling truncate() on a header file can change the length of the
900   resource fork and such a change will automatically be reflected in the