From owner-freebsd-hackers Thu Oct 23 00:33:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA06199 for hackers-outgoing; Thu, 23 Oct 1997 00:33:46 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA06192 for ; Thu, 23 Oct 1997 00:33:37 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA07307 for hackers@FreeBSD.ORG; Thu, 23 Oct 1997 09:33:35 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id JAA04206; Thu, 23 Oct 1997 09:28:48 +0200 (MET DST) Message-ID: <19971023092847.TP39265@uriah.heep.sax.de> Date: Thu, 23 Oct 1997 09:28:47 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: ACLs [Was: C2 Trusted FreeBSD?] References: <19971021205331.53826@worldgate.com> <199710230105.TAA13328@xmission.xmission.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199710230105.TAA13328@xmission.xmission.com>; from Wes Peters - Softweyr LLC on Oct 22, 1997 19:05:39 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk (Moved back to -hackers, it's technicall stuff.) As Wes Peters - Softweyr LLC wrote: > Yes, but how do you back them up, or, worse yet, restore them? How do > you copy your HTML directory tree to another drive you're bringing > on-line and preserve all the ACL settings? As noted before, *none* > of the system tools support the ACLs. I think you could make compatible changes to dump and restore to support ACLs. Perhaps, drop a second record containing the ACLs right behind an inode record (or even before, so the restore program knows about the intended ACLs before actually even seeing the inode information). The unknown records should simply be ignored by a restore that doesn't understand them. I once thought about extending dump to support gzip'ed files as well, but never got around to actually do it. The idea is to invent a new flag for the gzip'ed stored files, and then store the filename(s) as `originalname.gz'. If the archive goes on to a restore that doesn't understand the extension, it would extract the files with the new .gz suffix, so not all is lost. If the archive goes on to a restore that does understand the extension, it can decompress on the fly, and restore the original filename(s). Files that did already have the suffix .gz simply don't set the flag when being archived, and go to the tape verbatim. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)