ACL-0.5 release

[Robert Watson]

I've updated the ACL patch on www.TrustedBSD.org to reflect the latest ACL
code developments, including adaptation for the VADMIN changes I committed
to the base source tree, and bugs in directory creation handling.  Further
work is still required to provide a POSIX.2c setfacl, so I continue to
provide a non-complaint setacl tool in the src/test directory of the
tarball.

Further work needs to happen in the following areas, if there is interest:

1) Over-all stability testing, preferably in the form of creation of
   regression tests.  I already have some test programs in src/test, but
   something more thorough would be good. 

2) Development of an acl_from_text_np and an acl_to_text_np that allow
   flags to be passed specifying a bit more about the text format to be
   used, including whether or not to use usernames or uids, etc.  Also, it
   might be desirable to have an acl_combine_from_text(oldacl,
   textofrelativeacl) for use in setfacl.

3) Implementation of POSIX.2c setfacl tool

4) Modification to base system utilities to view and propagate ACLs (cp,
   ls, mv)

5) Deal with the backup issue.

I've had contact from the GNU fileutils maintainer discussing portability
issues for their ls implementation, and will follow up on that shortly.
Also, there has been discussing of ACLs on the linux-fsdevel mailing list
that may be relevant.

I'm also in the process of preparing the mac-0.1.tgz release, but am
currently encountering build problems relating to Perl.  I hope to have
those resolved later today and get a tarball out the door tomorrow.  That
said, this first release is going to be fairly rough, so unless you're
willing to play with a kernel debugger, you may want to hold off for 0.2
in a few weeks, which will hopefully include better network labeling
support.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Project
robert at fledge.watson.org      NAI Labs, Safeport Network Services

To Unsubscribe: send mail to majordomo at trustedbsd.org
with "unsubscribe trustedbsd-discuss" in the body of the message