From: cubexyz@gmail.com (Mark Longridge)
Subject: [TUHS] Unix v1/v2 cp command
Date: Sun, 13 Jul 2014 20:16:46 -0400 [thread overview]
Message-ID: <CADxT5N7aRiXkkh36_3TA=G=w_Y1iHJ-sptSV-aH2p2ELY+vaoQ@mail.gmail.com> (raw)
>> the cp command seems different from all other versions, I'm not sure I
>> understand it so I used the mv command instead which worked as expected.
>
> 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:
e.g. while in /usr/src
as ctr0.s
cp a.out ctr0.o
mv ctr0.o /usr/lib
...rather than trying to just "cp a.out /usr/lib/ctr0.o"
Mark
next reply other threads:[~2014-07-14 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 0:16 Mark Longridge [this message]
2014-07-14 0:32 ` Dave Horsfall
2014-07-16 18:14 ` Mark Longridge
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='CADxT5N7aRiXkkh36_3TA=G=w_Y1iHJ-sptSV-aH2p2ELY+vaoQ@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).