🚀 go-pugleaf

In aus.computers.linux, on 1 Oct 1999 05:21:57 GMT
loki <eloki@zip.com.au-nospam> wrote:
> Steve Oxley <viking@valhalla.cc.monash.edu.au> wrote unto us:
> >In article <37F433E9.D6C97D1@pantek.com>, Richard Zack wrote:
> >>mv /newusr /usr

Eek.  No.  Just use the tar trick below, then change your /etc/fstab
to mount the new disk on /usr instead of the old partition... then
reboot (and make *sure* you've got some sort of fully bootable rescue
disk so you can mount the root filesystem and change /etc/fstab *back*
if you need to), and check it worked.

> >Or better still, mount the new disk under /mnt, and then:
> >cd /usr
> >tar cf - . | (cd /mnt;tar xvf - )

Yeps.

>   This is less line and doesn't use disk space for a temp file, but isn't it
> possibly going to use a heck of a lot of RAM?

Nope.  It's a pipe.  Unix pipes DON'T store everything from the input
process then push the whole thing through to the next process.  That's
msdog pipes (which use temporary disk files, blech!).

Both processes run (look ma!  multitasking! :)), output from the first
one gets piped through to the second one, while they're both running.
Usually the first process will use blocking output calls, which means
that if the second process isn't pulling stuff out of the pipe fast
enough, the first process will wind up blocking on its output...

It's all very sexy stuff. :)

ook,

  Thorfinn

-- 
<a href = "http://netizen.com.au/~thorfinn/">thorfinn@netizen.com.au</a>
I cannot believe that God plays dice with the cosmos.
    -- Albert Einstein, on the randomness of quantum mechanics