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. Even if the kernel is compiled with ACL support, a specific filesystem must be mounted with the `acl` option in its `/etc/fstab` entry or during a manual mount command for ACLs to be enabled and functional on that filesystem.

Answer

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

Answer

B. There is no user on the system named hugh. If there were no user named hugh, `setfacl` would likely return an error about an invalid user, not "Operation not supported."

Answer

D. The file afile.txt doesn't exist. If `afile.txt` didn't exist, `setfacl` would report "No such file or directory."

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