[My mail connection wasn't working back in June when I wrote this. This
is the first of many replies to try to prevent breakage of mv.
I have now checked what happens for simple tests on ref11. Details in
later replies.]
On Sat, 28 Jun 2014, Bruce Evans wrote:
On Fri, 27 Jun 2014, Kenneth
On Fri, 27 Jun 2014, Kenneth D. Merry wrote:
On Fri, Jun 27, 2014 at 12:48:29 -0700, Xin LI wrote:
Hi,
Craig have hit an interesting issue today, where he tried to 'mv' a file
from ZFS dataset to a NFS mount, 'mv' bails out because chflags failed.
I think it's probably sensible to have mv
Hi,
Craig have hit an interesting issue today, where he tried to 'mv' a file
from ZFS dataset to a NFS mount, 'mv' bails out because chflags failed.
I think it's probably sensible to have mv ignoring UF_ARCHIVE, and set the
flag on the target unconditionally? i.e.:
Index: mv.c
On Fri, Jun 27, 2014 at 12:48:29 -0700, Xin LI wrote:
Hi,
Craig have hit an interesting issue today, where he tried to 'mv' a file
from ZFS dataset to a NFS mount, 'mv' bails out because chflags failed.
I think it's probably sensible to have mv ignoring UF_ARCHIVE, and set the
flag on the
On Fri, Jun 27, 2014 at 12:48:29PM -0700 I heard the voice of
Xin LI, and lo! it spake thus:
Craig have hit an interesting issue today, where he tried to 'mv' a
file from ZFS dataset to a NFS mount, 'mv' bails out because chflags
failed.
I've been getting these for a while on my -CURRENT
Author: ken
Date: Wed Aug 21 23:04:48 2013
New Revision: 254627
URL: http://svnweb.freebsd.org/changeset/base/254627
Log:
Expand the use of stat(2) flags to allow storing some Windows/DOS
and CIFS file attributes as BSD stat(2) flags.
This work is intended to be compatible with ZFS, the
