From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dumb question
Date: Thu, 27 Jun 2002 10:05:57 +0900 [thread overview]
Message-ID: <20020627010700.D1566199A3@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
Please let me say one very important thing. ^_^
If you feel something is missing in Plan 9, you'd better to think why they
eliminated it, particularly when it's related to basic unix commands.
I think there is no such thing which they eliminated carelessly in Plan 9.
I'm saying this from my many such experiences. :-)
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 3269 bytes --]
From: Andrew Stitt <astitt@cats.ucsc.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dumb question
Date: Wed, 26 Jun 2002 17:41:06 GMT
Message-ID: <Pine.SOL.3.96.1020626101934.26964C-100000@teach.ic.ucsc.edu>
On Wed, 26 Jun 2002, Nigel Roles wrote:
> On Wed, 26 Jun 2002 08:41:06 GMT, Andrew Stitt wrote:
>
> >On Tue, 25 Jun 2002, Fco.J.Ballesteros wrote:
> >
> >> Again, from rsc tiny tools :-)
> >>
> >> ; cat /bin/dircp
> >> #!/bin/rc
> >>
> >> switch($#*){
> >> case 2
> >> @{cd $1 && tar c .}|@{cd $2 && tar x}
> >> case *
> >> echo usage: dircp from to >[1=2]
> >> }
> >>
> >>
> >why must i needlessly shove all the files into a tar, then unpack them
> >again? thats incredibly inefficient! that uses roughly twice the space
> >that should be required, it has to copy the files twice, and it has the
> >overhead of having to needless run the data through tar. Is there a better
> >solution to this?
> > Andrew
>
> This does not use any more space. The tar commands are piped together.
> I doubt a specific cp -r type command would be particularly more efficient.
>
>
>
>
>
i beg to differ, tar uses memory, it uses system resources, i fail to see
how you think this is just as good as just recursively copying files. The
point is I shouldnt have to needlessly use this other program (for Tape
ARchives) to copy directorys. If this is on a fairly busy file server
needlessly running tar twice is simply wasteful and unacceptable when you
could just follow the directory tree.
next reply other threads:[~2002-06-27 1:05 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 1:05 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-15 0:37 [9fans] Dumb question Dan Cross
2003-07-15 3:23 ` boyd, rounin
2002-07-05 9:43 [9fans] dumb question Geoff Collyer
2002-07-01 11:03 rog
2002-07-02 8:53 ` Douglas A. Gwyn
[not found] <rob@plan9.bell-labs.com>
2002-06-28 16:49 ` rob pike, esq.
2002-06-29 2:23 ` Scott Schwartz
2002-06-28 16:39 rob pike, esq.
2002-06-28 16:31 rog
2002-06-28 16:14 rob pike, esq.
2002-06-28 14:10 rob pike, esq.
2002-06-28 15:42 ` Douglas A. Gwyn
2002-06-28 14:08 rog
2002-06-28 7:52 Fco.J.Ballesteros
2002-06-27 22:59 Geoff Collyer
2002-06-28 4:32 ` Lucio De Re
2002-06-27 18:38 forsyth
2002-06-28 8:45 ` Douglas A. Gwyn
2002-06-27 17:07 rog
2002-06-27 17:07 forsyth
2002-06-27 16:33 ` Sam
2002-06-27 14:43 Richard Miller
2002-06-27 14:33 forsyth
2002-06-27 13:20 rob pike, esq.
2002-07-05 9:07 ` Maarit Maliniemi
2002-06-27 13:19 rob pike, esq.
2002-06-27 13:21 ` david presotto
2002-06-27 15:40 ` Douglas A. Gwyn
2002-06-27 12:27 rog
2002-06-27 12:12 Fco.J.Ballesteros
2002-06-27 12:06 Fco.J.Ballesteros
2002-06-27 11:13 ` Sam
2002-06-27 11:15 ` Sam
2002-06-27 10:29 nigel
2002-06-27 9:44 Stephen Parker
2002-06-27 9:43 Fco.J.Ballesteros
2002-06-27 9:36 Fco.J.Ballesteros
2002-06-27 1:22 okamoto
2002-06-26 23:08 forsyth
[not found] ` <171e27d5f2cfd12a9303117e58818e5b@plan9.bell-labs.com>
2002-06-26 18:27 ` Andrew Stitt
2002-06-26 17:39 ` Sam
2002-06-27 9:17 ` Andrew Stitt
2002-06-27 9:33 ` Ish Rattan
2002-06-27 9:59 ` Lucio De Re
2002-06-27 10:05 ` Boyd Roberts
2002-06-27 10:21 ` Lucio De Re
2002-06-27 15:40 ` Douglas A. Gwyn
2002-06-27 16:57 ` Lucio De Re
2002-06-28 8:45 ` Douglas A. Gwyn
2002-06-28 9:31 ` Boyd Roberts
2002-06-28 14:30 ` Douglas A. Gwyn
2002-06-28 15:06 ` Boyd Roberts
2002-07-01 9:46 ` Ralph Corderoy
2002-06-27 15:36 ` Douglas A. Gwyn
2002-06-27 15:12 ` Sam
2002-06-28 8:44 ` Douglas A. Gwyn
2002-06-26 22:07 ` Micah Stetson
2002-06-26 22:59 ` Chris Hollis-Locke
2002-06-27 0:03 ` Micah Stetson
2002-06-27 0:44 ` Micah Stetson
2002-06-27 9:17 ` Ralph Corderoy
2002-06-27 9:48 ` Boyd Roberts
2002-06-27 10:07 ` John Murdie
2002-06-27 15:40 ` Douglas A. Gwyn
2002-06-26 19:04 rog
2002-06-26 19:00 Warrier, Sadanand (Sadanand)
2002-06-27 0:13 ` Steve Arons
2002-06-26 18:41 forsyth
2002-06-26 18:40 David Gordon Hogan
2002-06-26 17:53 rog
2002-06-26 17:45 rob pike, esq.
2002-06-27 9:16 ` Andrew Stitt
2002-06-27 9:17 ` Douglas A. Gwyn
2002-06-26 19:53 ` arisawa
2002-06-27 11:43 ` Ralph Corderoy
2002-06-27 11:04 ` Sam
2002-06-26 8:55 Stephen Parker
2002-06-26 17:18 ` Andrew Stitt
[not found] <nemo@plan9.escet.urjc.es>
2002-06-25 17:06 ` Fco.J.Ballesteros
2002-06-25 18:01 ` Scott Schwartz
2002-06-26 8:41 ` Andrew Stitt
2002-06-26 9:14 ` Nigel Roles
2002-06-26 17:41 ` Andrew Stitt
2002-06-26 16:08 ` Ish Rattan
2002-06-25 16:48 Andrew Stitt
2002-06-26 8:45 ` arisawa
2002-06-26 17:36 ` Andrew Stitt
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=20020627010700.D1566199A3@mail.cse.psu.edu \
--to=okamoto@granite.cias.osakafu-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).