From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Can I eliminate diagnostic messages from cp
Date: Sun, 22 May 2016 07:09:00 -0000 [thread overview]
Message-ID: <loom.20160522T090447-193@post.gmane.org> (raw)
In-Reply-To: <3e817f56-2193-6a63-ec27-1f49dc2b2e00@att.net>
lostbits <aschwarz1309 <at> att.net> writes:
> I use cp as my backup tool from disk to USB. There are maybe 40,000
> files involved and each one has a message of
> "cp: preserving permissions for <file>’: Not supported". These messages
> slow down the backup and obscure meaningful faults. Is there any option
> for removing the messages?
> My command line is: cp <directory> /<usb>
cp --preserve=all is documented as suppressing operation not supported
messages, and cp -a (archive) is documented as suppressing messages about
inability to preserve information which can not be stored on the target
filesystem.
Alternatively, instead of using the default USB DOS/VFAT format, you could
format the USB drives as NTFS, which would allow cp to preserve the
ownership and ACLs on the files.
prev parent reply other threads:[~2016-05-22 7:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 17:45 lostbits
2016-05-20 17:48 ` Eliot Moss
2016-05-20 18:05 ` Andrey Repin
2016-05-22 7:09 ` Brian Inglis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20160522T090447-193@post.gmane.org \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).