Dear all,
I am looking for a copy command that I would be absolutely sure that after is finished my file is identical bit my bit.
In other words which is the command that does copy and you would be using it when you know that you have a large file of super-extra-ultra confidential data and after the copy is finished you have to delete the source ?
On 2012-04-24 08:06, alaios wrote:
>
> Dear all,
> I am looking for a copy command that I would be absolutely sure that
> after is finished my file is identical bit my bit.
> In other words which is the command that does copy and you would be
> using it when you know that you have a large file of super-extra-ultra
> confidential data and after the copy is finished you have to delete the
> source ?
Command line, copy file, then do a byte by byte comparison of source and
destination, then delete source if needed. No such tool available as click
and point, afaik.
â
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 âCeladonâ at Telcontar)
> On 2012-04-24 10:06, alaios wrote:
>
>> How I can do this byte by byte comparison? Does a checksum check
>> suffice?
>
> diff, cmp⌠or checksums, of course. The paranoid will not use checksums.
>
But with checksums you can check backups integrity also in future.
Let,s say that I have moved 10.000 files to my network to my local disk. What can be an effective way to do this bit by bit comparison between all these folders and files. How to keep any errors to specific file so to read it later?
On 2012-04-27 07:56, alaios wrote:
>
> One more question came to mind last night,
>
> Let,s say that I have moved 10.000 files to my network to my local
> disk. What can be an effective way to do this bit by bit comparison
> between all these folders and files. How to keep any errors to specific
> file so to read it later?
Midnight commander (mc).
It can compare the contents of two directories, and mark different or
missing files. What it doesnât do is checksum check, for that I would do my
own script.
And if you have to compare over the network, checksum comparison is the
thing to do. Hold on⌠md5sum does check a directory, automatically. You
just give the program a file with checksums and filenames, it will verify
the entire list. With ââquietâ it will only talk for bad files.
What it does not do is verification of a tree.
â
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 âCeladonâ at Telcontar)
Am 27.04.2012 14:46, schrieb alaios:
>
> just to add that I did the job with this one
>
>
> Code:
> --------------------
> rsync -rvnc website/ laptop:projects/website/
> --------------------
>
>
Since the man page of rsync says
Note that rsync always verifies that each transferred file was
correctly reconstructed on the receiving side by checking a
whole-file checksum that is generated as the file is trans-
ferred, but that automatic after-the-transfer verification has
nothing to do with this optionâs before-the-transfer âDoes this
file need to be updated?â check.
that should be a very safe operation to do that copy with rsync.
â
PC: oS 12.1 x86_64 | Intel Core i7-2600@3.40GHz | 16GB | KDE 4.8.2 |
GeForce GT 420
Eee PC 1201n: oS 12.1 x86_64 | Intel Atom 330@1.60GHz | 3GB | KDE 4.8.2
| nVidia ION
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10 |
xf86-video-geode