The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] Mention TUHS in Linux Magazine (US)?
Date: Sun, 01 May 2005 20:21:50 +1200	[thread overview]
Message-ID: <200505012021.50557.wes.parish@paradise.net.nz> (raw)
In-Reply-To: <14431.1114885731@jpeek.com>

Again, FWIW, I've successfully - with the expenditure of a good long period of 
time - transferred an 80GB file system from one hard drive to another using 
the GNU cp - I didn't read enough of the man page though, and missed out on 
the -p switch to preserve my ownership on the files - I had to return the 
entire 80 GB to my ownership manually ... ;)  God, I felt like the Prize 
Dork!

But it did the massive job without blinking an eyelid, over the three or so 
hours it took to do it.  It's good stuff.  Just massive itself.

Wesley Parish

On Sun, 01 May 2005 06:28, Jerry Peek wrote:
> On 30 April 2005 at 19:31, Wesley Parish <wes.parish at paradise.net.nz> wrote:
> > And, FWIW, in one of the few GNUs Bulletins I actually have received,
> > courtesy of the FSF, RMS (I think) was advising that with the dropping
> > price in memory, GNU hackers could do without worrying about memory size,
> > when it came to replicating Unix utilities..
>
> That's been on my mind as I thought back to my days on VAXen
> with 100 users logged on and a load average of 30.  Back then,
> efficient programming was so very important.  Now, when the GNU
> "cp" has more than 20 options -- and some of those with several
> possible arguments -- one side of me thinks how bloated the GNU
> utilities seem.  But, on the other hand, one of the things I'm
> doing in this series of columns is to compare "how we used to
> do it" vs. the usefulness of some of the new features.  For
> instance, back then we could copy a directory tree recursively
> with "tar" or "find", carefully handling devices and etc. along
> the way.  Now we can do the same thing by typing a cp command
> with a couple of options.  With powerful machines on our desks,
> which sort of "efficiency" do we want these days?
>
> I'm not trying to answer that question!  I'm trying to show
> things in a balanced way and leave it to the reader to decide.
> This has been debated and discussed so much over the years
> that I can't shed any new light on it.  I just want readers to
> keep it in mind, think about where we've been and where we are.
>
> Jerry
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs

-- 
Clinersterton beademung, with all of love - RIP James Blish
-----
Mau e ki, he aha te mea nui?
You ask, what is the most important thing?
Maku e ki, he tangata, he tangata, he tangata.
I reply, it is people, it is people, it is people.


  reply	other threads:[~2005-05-01  8:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 17:59 Carl Lowenstein
2005-04-29 19:10 ` Jerry Peek
2005-04-30  1:19   ` Kurt Wall
2005-04-30  7:31 ` Wesley Parish
2005-04-30 11:35   ` Tim Shoppa
2005-04-30 18:28   ` Jerry Peek
2005-05-01  8:21     ` Wesley Parish [this message]
2005-05-09  8:41       ` [TUHS] Sad news from IBM J. R. Valverde
     [not found] <200504290913.j3T9DdGA016881@skeeve.com>
2005-04-29 10:05 ` [TUHS] Mention TUHS in Linux Magazine (US)? Warren Toomey
  -- strict thread matches above, loose matches on Subject: below --
2005-04-28 16:50 Jerry Peek
2005-04-29  1:55 ` Tim Newsham
2005-04-29  7:04 ` Greg 'groggy' Lehey
2005-04-29  9:02   ` Warren Toomey
2005-04-29 16:20     ` Jerry Peek

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=200505012021.50557.wes.parish@paradise.net.nz \
    --to=wes.parish@paradise.net.nz \
    /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).