checksum

Definitions, parts of speech, synonyms, and sentence examples for checksum.

Home Featured words Jump to examples

Editorial note

In that case, --checksum will overwrite that file with your source version, and a --no-checksum wouldn't.

Examples15

Definitions2

Parts of speech2

Quick take

(mathematics, computing) To compute a checksum.

Meaning at a glance

The clearest senses and uses of checksum gathered in one view.

verb

(mathematics, computing) To compute a checksum.

noun

(mathematics, computing) A number, derived by applying a suitable algorithm to some data, used to check whether errors have occurred in transmission, storage or data entry.

Definitions

Core meanings and parts of speech for checksum.

verb

(mathematics, computing) To compute a checksum.

noun

(mathematics, computing) A number, derived by applying a suitable algorithm to some data, used to check whether errors have occurred in transmission, storage or data entry.

Example sentences

In that case, --checksum will overwrite that file with your source version, and a --no-checksum wouldn't.

Also, the checksum is a CRC32C and the SSE4.2 CRC32 instruction can calculate these really fast.

If the checksum is provided (as part of the sh snippet) by the website with the SSL certificate, isn't that enough reassurance?

Because the TCP checksum was incorrect, the packet would never reach a higher level such as TLS.

Edit: thinking about it, Gobolinux could perhaps be extended with checksum dirs inside the version-subdir to separate different compiles.

Would this be better if the pasted command included some checksum which was checked before piping into the `sh`?

It's worse -- these CPF numbers have nothing special but a simple checksum at the end.

They saved eight bytes and some negligible amount of checksum processing, and got no other benefits from being a first-class protocol.

Switch itself corrupts payload; dense enough to pass the tcp checksum in use.

--checksum makes it ignore file size or modification time, and compare the file checksum in order to decide if it's time for a transfer (delta or not).

Thus, we checksum each file on your computer and ensure that it is returned to you upon restore identically.

For a slightly out there and arguably more interesting financial checksum algorithm, and one that is actually amazingly effective, do some statistics on mod97's performance.

Quote examples

Here is the chance of that case: "checksum will fail to detect errors for roughly 1 in 16 million to 10 billion packets".

Use rsync --checksum --ignore="..." unless you have a damn good reason not to (--checksum is essential to prevent corruption/malicious modification, without it you are implicitly assuming the version on the remote machine is exactly how you left it: that assumption is why Linus built git around shasum in the first place).

The error estimate that "between 1 in 16 million and 1 in 10 billion TCP segments will have corrupt data and a correct TCP checksum" is from "Performance of Checksums and CRCs over Real Data" [Stone and Partridge] which only analyzed a particular type of framing error over ATM.