From: arisawa@ar.aichi-u.ac.jp
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] cpdir
Date: Tue, 27 Mar 2007 00:46:36 +0900 [thread overview]
Message-ID: <92E7B9B4-B519-4856-B7D3-15CE3C5C0B24@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <c15a2a234186072c0ffbae5e0c6f960e@coraid.com>
Hello
Current disk/mkfs works similar to cpdir
disk/mkfs -s foo -d bar /sys/lib/proto/allproto
However old mkfs had not -d option.
Cpdir was designed and coded at that time of Plan 9 (ver.2),
so that I can make a copy of directory more handy.
Cpdir has a functionality that is different from disk/mkfs.
Kenji Arisawa
On 2007/03/26, at 22:31, erik quanstrom wrote:
> i still don't understand why this doesn't duplicate the
> functionality of disk/mkfs. according to the comment in mkfs.c
>
> * name: cpdir
> * version: 1.5e
> * date: 2005/02/19
> * os: plan9 v4
> * usage: cpdir [-mstugvR] [-l file] srcdir dstdir [path ...]
> * srcdir: source directory
> * dstdir: destination directory
> * path: path to copy. file or directory.
> * options:
> * -m: merge (this option is used if dstdir is already exist)
> * -u: copy owner info.
> * -g: copy groupe info.
> * -v: verbose
> * -R: remove redundant files in destination
> * -s: safe mode in removing files; just renames foo to _foo
> * -t: ignore mtime
> * -l file: path list and pattern list file
> *
> * path or pattern list is a file that contains path or pattern per
> line.
>
>
> - erik
>
> On Mon Mar 26 09:27:19 EDT 2007, gabidiaz@gmail.com wrote:
>> hello
>>
>> i think he is speaking about /n/sources/contrib/arisawa/cpdir/README
>>
>> :-?
>>
>> slds.
>>
>> gabi
>>
>>
>> On 3/26/07, Gorka Guardiola <paurea@gmail.com> wrote:
>>> We have one which is a recursive cp of a directory using tar, but
>>> you are not
>>> talking about that are you?.
>>>
>>> On 3/26/07, Russ Cox <rsc@swtch.com> wrote:
>>>> I give up: what is cpdir?
>>>>
>>>> Russ
next prev parent reply other threads:[~2007-03-26 15:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 13:06 Russ Cox
2007-03-26 13:10 ` Gorka Guardiola
2007-03-26 13:26 ` Gabriel Diaz
2007-03-26 13:31 ` erik quanstrom
2007-03-26 15:46 ` arisawa [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-21 15:44 Devon H. O'Dell
2007-03-21 17:15 ` Abhey Shah
2007-03-21 17:22 ` C H Forsyth
2007-03-21 20:03 ` David Leimbach
2007-03-22 11:15 ` Abhey Shah
2007-03-22 16:14 ` Paul Lalonde
2007-03-22 17:55 ` David Leimbach
2007-03-22 17:54 ` David Leimbach
2003-09-29 14:03 Kenji Arisawa
2003-09-29 20:44 ` Kenji Arisawa
2003-09-29 21:14 ` boyd
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=92E7B9B4-B519-4856-B7D3-15CE3C5C0B24@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@cse.psu.edu \
/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).