From owner-freebsd-bugs Wed Apr 22 08:11:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29189 for freebsd-bugs-outgoing; Wed, 22 Apr 1998 08:11:16 -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 PAA29184 for ; Wed, 22 Apr 1998 15:11:10 GMT (envelope-from adam@veda.is) Received: (from adam@localhost) by veda.is (8.8.8/8.8.8) id PAA25066; Wed, 22 Apr 1998 15:09:03 GMT (envelope-from adam) From: Adam David Message-Id: <199804221509.PAA25066@veda.is> Subject: Re: bin/6364 In-Reply-To: <3570.893254136@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 22, 98 04:08:56 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Wed, 22 Apr 1998 15:09:01 +0000 (GMT) Cc: 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 > No, that is how schg works, isn't it ? I pressume from the > rather sparse data in your PR that you had schg set on some > files on the ufs tree... > > If not please provide some more info... Sorry about the terse wording. It seems odd to me that cpio doesn't set schg on the destination file when the source file has it set, or that this behaviour is not documented and there is no flag to let cpio handle chflags on the files it is working with. I expect an nfs destination to fail setting the flags because that is a remote operation, but it surprised me when a ufs destination did not preserve the flag settings. Under other circumstances I would have made a fuller analysis and a patch but my time is tied at the moment. Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message