You are certain that your kernel has been compiled with ACL support, however, when you try to set an ACL on a file, you get the following output: % setfacl m user:hugh:r afile.txt setfacl: afile.txt: Operation not supported What is the most likely reason for this problem?

Question

Accepted Answer

C. The partition has not been mounted with the acl option. For ACLs to be functional on a filesystem, the partition must be mounted with the `acl` option, even if the kernel itself supports ACLs; otherwise, operations like `setfacl` will fail with 'Operation not supported'.

Answer

A. There is an error in the command line parameters. The command `setfacl -m user:hugh:r afile.txt` is syntactically correct for setting an ACL.

Answer

B. There is no user on the system named hugh. If the user 'hugh' did not exist, the error message would typically be 'No such user', not 'Operation not supported'.

Answer

D. The file afile.txt doesn't exist. If 'afile.txt' did not exist, the error message would typically be 'No such file or directory', not 'Operation not supported'.

You are certain that your kernel has been compiled with ACL support, however, when you try to set an ACL on a file, you get the following output: % setfacl m user:hugh:r afile.txt setfacl…

Question

Options

How the community answered

Why each option

Topics

Community Discussion