Re: [**SPAM**] RE: how to compile acl patched coreutils under slackwarelinux?

> Switch distro? Personally I'd say no. I use Slackware for everything and
> have found it to be the most stable and compliant distributions
> available.

I like it as well, so I want to use it for this server as well...

> As for coreutils, I just re-ran configure myself to check my output. I
> get:
>
> checking sys/acl.h usability... yes
> checking sys/acl.h presence... yes
> checking for sys/acl.h... yes
> checking for acl... no
> checking for library containing acl_get_file... -lacl
> checking acl/libacl.h usability... yes
> checking acl/libacl.h presence... yes
> checking for acl/libacl.h... yes
> checking for acl_get_file... yes
> checking for acl_set_file... yes
> checking for acl_free... yes
> checking for acl_to_text... yes
> checking for acl_from_text... yes
> checking for acl_delete_def_file... yes
> checking for acl_entries... yes
> checking for acl_extended_file... yes
>
> So it appears that I too get the "no" for ACL, and yet I do have ACL
> working. Curious.

But I do get this error during make:
...
/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../../../i486-slackware-linux/bin/ld:
cannot find -lpam
collect2: ld returned 1 exit status
make[3]: *** [su] Error 1
make[3]: Leaving directory `/usr/src/coreutils-5.2.1/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/src/coreutils-5.2.1/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/coreutils-5.2.1'
make: *** [all] Error 2


> With Samba I used:
>
> ./configure --with-acl-support -with-smbmount
>
> With the relevant output being:
>
> checking whether to support ACLs... checking for getxattr in -lattr...
> yes
> checking for acl_get_file in -lacl... yes
> checking for ACL support... yes
> Using posix ACLs

I get this output as well.
What does your "smbd -b" tells you? I see no WITH_ACL or similar :(

> Personally I'd run a little getfacl / setfacl check, before you install
> Samba, just to make sure that you can get and set acl bit correctly.
> Also run an ls to make sure your output has the "+" at the start. Note
> that "ls" default install is to /usr/bin are coreutils default ls
> install is to /usr/local/bin. I simple changed my path order to use the
> patched ls out of preference. Personally I did not want to overwrite my
> existing ls (and other coreutils) in case of problems. Of course the
> relevant configure options can be passed to coreutils to change its
> installation location as an alternative to the path modification option.

see above, I can't compile coreutils :(
And I don't know if Samba was compiled correctly ... how can I test this?

Greets, Matthias
_______________________________________________
acl-devel mailing list
[email protected]
http://acl.bestbits.at/mailman/listinfo/acl-devel