From 0b240c05a83fee728c6a177833bf618e0922fec4 Mon Sep 17 00:00:00 2001 From: Tom Rhodes Date: Wed, 11 Dec 2002 01:22:23 +0000 Subject: [PATCH] Remove old note, add a new note. This has to do with use of extended attributes on ACLs. Submitted by: rwatson (original version) --- en_US.ISO8859-1/books/handbook/security/chapter.sgml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/security/chapter.sgml b/en_US.ISO8859-1/books/handbook/security/chapter.sgml index da8e3191b0..32e4bb1f72 100644 --- a/en_US.ISO8859-1/books/handbook/security/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/security/chapter.sgml @@ -3511,10 +3511,12 @@ user@unfirewalled.myserver.com's password: *******UNIX file system or UFS2. - The use of extended attributes on UFS1 file - systems will lead to higher administration overhead and lower overall - file system performance. UFS2 does not have this - problem. + A higher level of administrative overhead is required to + configure extended attributes on UFS1 than on + UFS2. The performance of extended attributes + on UFS2 is also substantially higher. As a + result, UFS2 is generally recommended in preference + to UFS1 for use with access control lists. To enable ACLs on a file system, the option can be passed to &man.tunefs.8; in a manner similar to the Soft Updates