Call me Chip...
For sure I'm running the proper kernel. I just built it once more so I could
tell you I built it this morning ;-)
noposix_acl.o isn't created, but posix_acl.o is, as another point of
Attached is my .config. /boot/vmlinuz is the only kernel listed in lilo.conf.
I do this:
cp ~/config .config
make menuconfig (verify settings...)
cp arch/i386/boot/bzImage /boot/vmlinuz
From: Timothy Shimmin [mailto:tes@xxxxxxxxxxxxxxxxxxxxxxx]
Sent: Sunday, May 06, 2001 21:04
To: Christian, Chip
Cc: 'Linux XFS (E-mail)'
Subject: Re: chacl usage
On Fri, May 04, 2001 at 11:38:34AM -0400, Christian, Chip wrote:
> Oh, and I specified
> when building the kernel.
> > -----Original Message-----
> > From: Christian, Chip
> > Sent: Friday, May 04, 2001 11:37
> > To: Linux XFS (E-mail)
> > Subject: chacl usage
> > Am I missing something to get acls to work on XFS? I'm on a frsh RedHat
> > 7.1install, built a kernel from the 1.0 XFS release. I installed the SGI
acl-1.0.1-0. Built an XFS filesystem:
> > [root@betanas1 pkgs]# chacl u::rwx,g::rwx,o::rwx foo
> > chacl: error setting access acl on "foo": Function not implemented
This is strange.
The only way I know that you'd be getting ENOSYS (Function not implemented)
for ACLs is if CONFIG_FS_POSIX_ACL is not set.
(See linux/fs/noposix_acl.c (used in linux/fs/Makefile))
Are you sure you have the right kernel running ?
Description: Binary data