From owner-freebsd-bugs Wed Apr 22 08:27:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01252 for freebsd-bugs-outgoing; Wed, 22 Apr 1998 08:27:22 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from veda.is (adam@veda.is [193.4.230.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01243 for ; Wed, 22 Apr 1998 15:27:17 GMT (envelope-from adam@veda.is) Received: (from adam@localhost) by veda.is (8.8.8/8.8.8) id PAA25485; Wed, 22 Apr 1998 15:24:52 GMT (envelope-from adam) From: Adam David Message-Id: <199804221524.PAA25485@veda.is> Subject: Re: bin/6364 In-Reply-To: <199804221452.AAA32062@godzilla.zeta.org.au> from Bruce Evans at "Apr 23, 98 00:52:12 am" To: bde@zeta.org.au (Bruce Evans) Date: Wed, 22 Apr 1998 15:24:51 +0000 (GMT) Cc: phk@critter.freebsd.dk, freebsd-bugs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I presume that it has nothing to do with schg (cpio doesn't use > chflags(2) and nfs doesn't export file flags), but is for cpio -a > from an fs where the user doesn't have permissions to use utimes(p) > where p != NULL. > > Bruce My misunderstanding, I had not realised that the destination system would not even see the chflags settings on the source system when copying from nfs, but then why did it even complain about "Operation not supported" when copying from nfs? However, this has nothing really to do with nfs, since on ufs... # mkdir foo # touch bar # chflags schg bar # find . -name bar | cpio -dumpav foo cpio: ./bar: Operation not permitted foo/./bar 0 blocks Why does cpio not grok chflags? Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message