Running chmod 640 filea.txt as a regular user doesn't update filea.txt's permission. What might be a reason why chmod cannot modify the permissions? (Choose two.)
Running chmod 640 filea.txt as a regular user doesn't update filea.txt's permission. What might be a reason why chmod cannot modify the permissions? (Choose two.)
A regular user cannot change the permissions of a file owned by another user, and a symbolic link's permissions are a fixed value which cannot be changed.
filea.txt is a symbolic link whose permissions are a fixed value which cannot be cha"N"ged.
you can change the permissions on a hard link file without issues due it will be change the permissions in the original source too. You cannot change the permissions on symbolic inks due all is under 777
A Sticky bit is a permission bit that is set on a file or a directory that lets only the owner of the file/directory or the root user to delete or rename the file. No other user is given privileges to delete the file created by some other user.
Sticky bit is just for directories
Permissions on all hard links to the same data on disk are always identical. The same applies to attributes. That means if you change the permissions/owner/attributes on one hard link, you will immediately see the changes on all other hard links.
Wait, isn't D is more correct? A hardlink permission is inherited and cannot be changed by anyone else but root/owner
are correct
Is correct answer
A, B is correct bcos you cannot change permission of softlink/symbolic link.