Subject: Re: restore and schg flag
To: Manuel Bouyer <>
From: Luke Mewburn <>
List: tech-userlevel
Date: 10/12/2004 11:58:34
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 12, 2004 at 12:06:18AM +0200, Manuel Bouyer wrote:
  | On Mon, Oct 11, 2004 at 10:33:52PM +0200, Manuel Bouyer wrote:
  | > [...]
  | >=20
  | > My idea for this is to defer this work to mtree. I'll add a -M<file> =
flag to
  | > restore, which, when set, will cause restore to not set the file flags
  | > (either for files or directory), but instead write (append, so that w=
e can
  | > have in a single file the output of a multilevel restore) a mtree fil=
e in the
  | > format of /etc/mtree/*. Then the user can run mtree against this file
  | > to restore the flags. I can't think of a better way to handle all the
  | > corner cases *chg or *appnd can create for restore.
  | >=20
  | > Comments ?
  | Here is a patch. It works in my case, at last:
  | #/tmp/restore -M /tmp/mtree -rvf ../wd0a.0
  | [...]
  | #/tmp/restore -M /tmp/mtree -rvf ../wd0a.1
  | [...]
  | # sort /tmp/mtree | mtree -e -i -u
  | testdir:=20
  |         flags ("uchg" is not "none", modified to "uchg")
  | We need to process the file though sort, because mtree needs to have
  | the specs for a directory before the files in this directory. But it
  | works very well for my test cases.
  | Should I update the man page, and commit this ?

If you've tested it well, I have no objection.

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.6 (NetBSD)