Re: Migrate OS to smaller drive?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ron Johnson wrote:
>Never destroy the original until you know the copy works!
In my earlier days I would have avoided mv for exactly that reason. But
when copying (including rsync), you cannot easily see that it worked
from the emptyness of the original file system. And comparing large
filesystem trees (not just 4GB as in this case) is trickier than most
people realize. At least a simple "diff -r" will be far from doing it.
Maybe you have some good way of comparing FS trees?
>> hence hogging the CPU
>
> You won't be doing anything else at the time...
The OP didn't say that. Maybe you would do it that way. Maybe me too.
Not that it matters once compression is disabled.
>> and possibly slowing
>> transfers?
>
> Hah. Speeding up transfers is more likely, since the wire is always the
> bottleneck, and compression means it will be carrying "more bits per bit".
There's no mention of wire transfer anywhere in this thread, and in fact
for most people the upload of >4GB would be too much anyway. I presume
he has both drives build into the same computer. Note that he talks
about migrating / .
Cases of remote transfer (transferring / to a remote machine, which must
hence already have a / ) are theoretically possible but probably not
relevant here.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkvCNrwACgkQ+VSRxYk440/d8wCgkOhMNQfa7OTWUEtcdCKJ5mdr
H20AoNgy5CYLmTdy1Ki1DK4dj58uIe/r
=CzO1
-----END PGP SIGNATURE-----
Reply to: