Date: Sun, 26 Dec 2010 21:04:28 +0100 From: Polytropon <freebsd@edvax.de> To: freebsd-questions@freebsd.org Subject: Re: cpio misunderstanding? Message-ID: <20101226210428.da2114c5.freebsd@edvax.de> In-Reply-To: <AANLkTikP8Wb%2BmpDQpud32sgdVRV3wdfbfhPQvvUkwcey@mail.gmail.com> References: <if2rdo$tk5$1@dough.gmane.org> <201012242042.21257.ken@mthelicon.com> <if3fi6$2k4$1@dough.gmane.org> <AANLkTikP8Wb%2BmpDQpud32sgdVRV3wdfbfhPQvvUkwcey@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 26 Dec 2010 11:30:59 -0800, David Brodbeck <gull@gull.us> wrote: > On Fri, Dec 24, 2010 at 4:57 PM, Joe Kraft <jvk-list@thekrafts.org> wrote: > > OK, now I know what's going on. =A0I just don't know why. =A0The immuta= ble flag > > was set on all these files, if you clear it cpio will happily copy them= to > > the new directory. >=20 > Does cpio attempt to preserve flags? Since the error is "could not > create," I'm wondering if it's trying to set the same flags on the > copy of the file and failing to do so. I'm not sure about that - "man cpio" doesn't give a hint about flags. On the other hand, tar's -p option does keep the file mode (permissions), flags and maybe ACLs intact. I've tried "info cpio" ouch! ouch!, but that's not a continuous manual that allows easy searching for strings. :-( Some search in the /usr/src/bin subtree for the "chflags" call revealed that it is used by the chflags binary, cp, mv and rm commands, but no hint it is involved directly in cpio. --=20 Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101226210428.da2114c5.freebsd>