The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cubexyz@gmail.com (Mark Longridge)
Subject: [TUHS] Unix v1/v2 cp command
Date: Wed, 16 Jul 2014 14:14:36 -0400	[thread overview]
Message-ID: <CADxT5N6DU5CyDRb2Va-nKTuXa3XyZMHHyy=AyifASkTgNkEXWg@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.00.1407141030580.61582@aneurin.horsfall.org>

On 7/13/14, Dave Horsfall <dave at horsfall.org> wrote:
> On Sun, 13 Jul 2014, Mark Longridge wrote:
>
>> > I'm intrigued; in what way is it different?
>>
>> It seems that one must first cp a file to another file then do a mv to
>> actually put it into a different directory:
>
> That generally means that you don't have write permission on the file; I
> assume that you checked for that?
>
> -- Dave

Hi Dave,

The version 1 manual actually mentions that:

A directory convention as used in mv should be adopted to cp.
ken, dmr

Also I was root when I used cp.

Mark



      reply	other threads:[~2014-07-16 18:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14  0:16 Mark Longridge
2014-07-14  0:32 ` Dave Horsfall
2014-07-16 18:14   ` Mark Longridge [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='CADxT5N6DU5CyDRb2Va-nKTuXa3XyZMHHyy=AyifASkTgNkEXWg@mail.gmail.com' \
    --to=cubexyz@gmail.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 NNTP newsgroup(s).