From owner-freebsd-bugs  Wed Apr 22 07:56:14 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA26244
          for freebsd-bugs-outgoing; Wed, 22 Apr 1998 07:56:14 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26227
          for <freebsd-bugs@FreeBSD.ORG>; Wed, 22 Apr 1998 14:56:12 GMT
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id AAA32062;
	Thu, 23 Apr 1998 00:52:12 +1000
Date: Thu, 23 Apr 1998 00:52:12 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199804221452.AAA32062@godzilla.zeta.org.au>
To: adam@veda.is, phk@critter.freebsd.dk
Subject: Re: bin/6364
Cc: freebsd-bugs@FreeBSD.ORG
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>>> Synopsis: cpio complains about file flags
>>> 
>>> State-Changed-From-To: open-closed
>>> State-Changed-By: phk
>>> State-Changed-When: Tue Apr 21 23:29:52 PDT 1998
>>> State-Changed-Why: 
>>> from what you say it pprobably should say so.
>>
>>this is a feature?
>
>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...

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

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message