Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Aug 2005 21:58:18 -0700 (PDT)
From:      Matthew Dillon <dillon@apollo.backplane.com>
To:        Emanuel Strobl <Emanuel.strobl@gmx.net>
Cc:        freebsd-current@freebsd.org, freebsd-questions@freebsd.org
Subject:   Re: cpio and tar are loosing flags (and a panic message without trace)
Message-ID:  <200508270458.j7R4wI5f076140@apollo.backplane.com>
References:  <200508262004.54637@harrymail> <200508270316.j7R3GE7P075733@apollo.backplane.com> <200508270523.50609@harrymail>

next in thread | previous in thread | raw e-mail | index | archive | help
:Thank you, I know cpdup but I haven't known that it's flags aware!
:Unfortunately I need to write to a raw device, I guess there's no way for=20
:cpdup without a filesystem...
:
:I guess cpio and tar really should take care about flags. Am I wrong?
:
:Thanks,
:
:=2DHarry

    cpio won't do it, tar won't do it, dump only does whole partitions,
    cpdup is not an archiver.  Hmm.

    I can think of two possibilities.  First, use a MFS or VN block device,
    create a filesystem, and use cpdup, then gzip the file representing
    the backing store.  Since the extra space in the filesystem will contain
    zeros (you should make sure it does, that is), it should compress pretty
    well.  Second, use cpio and then do a separate 'find' or 'ls' or 
    something to get the chflags info and write a script that restores
    the flags after unpacking.

    They are both pretty narley solutions.

    Hmm.. wait a sec... I just thought up of another possibility... take
    the tar or cpio source code and modify it to also save and restore
    the chflags data.  It won't be a 'standard' utility any more, but it
    WILL work for your needs.  Call it by another name so there's no
    confusion.  That might be your best bet, actually.

						-Matt



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200508270458.j7R4wI5f076140>