Red Hat Bugzilla – Bug 120269
Filesystem should have "acl" option automatically set in /etc/fstab, if supported.
Last modified: 2007-11-30 17:10:39 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312
Description of problem:
One of the feature of kernel 2.6 I was eagerly waiting for is POSIX
ACL support standard. After installing FC2T2, I saw it was not
defined in /etc/fstab; I had to to add the "acl" option myself by hand
and remount the filesystem.
I believe ACL are an important improvement of kernel 2.6, and having
them work out-of-the-box on filesystem that support them would raise
awareness about this new capability of Fedora.
Version-Release number of selected component (if applicable):
Don't know !
Steps to Reproduce:
Install Fedora. See /etc/fstab do not have the "acl" option setted
for filesystems that could support them.
I filed this bug with the filesystem package although it is probably
not related. I am sorry, I cannot determine which package /etc/fstab
belong to (rpm -qf tell me it is not owned by any package).
Perhaps making it a mount default?
Yes, setting it in /etc/fstab automatically would seem like a good
idea. That's the obvious place a user will look for it if they want
to see if it's enabled or if they want to change the settings.
An obvious question is whether to do it on upgrades too, or just on
install. It's a common enough thing on 2.6 now that it probably does
make sense to do it on upgrade, but you could argue it either way.
I'd argue that it should just be on default. If everybody's going to
get it then _it is the default_. Having the installer maintain logic
of what the kernel defaults should be seems horribly broken.
I'd rather not have to carry around a new kernel patch for the
defaults. What about just "tune2fs -o acl" by default on new
filesystems, and release-note it if people want to change the defaults
on upgrade? That keeps us entirely compatible with the rest of the
world in terms of how the ext3 tools/kernel behave, and appears to
have the desired effect.
It's somehow better to have the patch to change defaults in the
installer? There is no way for me to keep up with what the kernel
people think defaults should be changed to this week. So either it
needs to be the default per the kernel or anaconda isn't changing it