From owner-freebsd-hackers Tue May 5 13:33:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00712 for freebsd-hackers-outgoing; Tue, 5 May 1998 13:33:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA00562 for ; Tue, 5 May 1998 13:32:57 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yWnz1-0005wq-00; Tue, 5 May 1998 13:06:35 -0700 Date: Tue, 5 May 1998 13:06:35 -0700 (PDT) From: Tom To: Benjamin Greenwald cc: freebsd-hackers@FreeBSD.ORG Subject: Re: dump/restore (Was Re: Network problem with 2.2.6-STABLE) In-Reply-To: <199805050755.DAA28510@miris.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 May 1998, Benjamin Greenwald wrote: > > uchg is just another file attribute, and could be supported on non-UFS > > filesystems. An archiver should store all file attributes, and restore > > them as possible. > > So you are saying that the archiver should be responsible for backing up every > file attribute from every possible filesystem? How do you propose this be > done? How do you propose the archiver even know these bits exist without > knowing the underlying filesystem? uchg could be supported on other filesystems. The archiver should back up all attributes it knows about. Regardless whether using a tar-like archiver, or dump, the archiver still needs to be taught the attributes. Ideally the interface should be changed, so the attributes can be retrieved as a list of tags, so archivers don't need to understand what the attributes are, and new file attributes can be added (ex. acls) and all archivers work automatically. Even dump/restore don't always restore the new 4.4 attributes properly. See bin/5173 Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message