wireguard-openbsd/bin/dd, branch master

replace the "write a floppy image" example with a more up to date one;

2020-10-29T07:01:24Z

input/ok deraadt jca

Change install images called .fs to .img. These are UFS filesystem images,

2020-05-17T17:04:27Z

but additionally have a bootblock in the first 8K (since UFS does not use that space). There are some UEFI direct-from-internet bootloaders that require the name *.img. So this makes things more convenient for those, while keeping it consistant in all architectures. ok kettenis beck kn

get rid of an awkward ellipsis noticed by Jan Stary; OK jmc@

2020-02-14T20:13:10Z

Do not mark up punctuation (equal signs), get rid of needless .Xo and .Sm,

2020-02-14T15:55:57Z

and make some wordings more concise. Parts of a patch from Jan Stary , tweaked by me. Feedback and OK jmc@.

When system calls indicate an error they return -1, not some arbitrary

2019-06-28T13:34:58Z

value < 0. errno is only updated in this case. Change all (most?) callers of syscalls to follow this better, and let's see if this strictness helps us in the future.

add fsync to STANDARDS;

2019-02-16T17:01:24Z

Implement the conv=fsync feature which does an fsync(2) after the

2019-02-16T10:54:00Z

final write to output. GNU dd also has this. It is useful for write performance measurement or guaranteed writes to reliable storage. OK kn@ tedu@ deraadt@

Free operand copies after parsing.

2018-07-25T15:09:48Z

We strdup operands before destructively parsing them to keep w(1) output looking nice and neat, but after parsing we ought to free them. We do need to keep copies for file paths, though, so add additional strdups for operands if and of. While here, use the preferred err(1, NULL) for an allocation failure. Also while here, don't assign `oper' to a copy of itself because it looks strange. "sure." deraadt

Don't cast malloc(3) size to u_int.

2018-07-23T23:09:37Z

Large buffer sizes on 64-bit platforms cause the sum to wrap, leading read(2) to fail later. We check prior to this point that all buffer sizes are <= SSIZE_MAX. SSIZE_MAX * 2 < SIZE_MAX on all platforms, so the addition here will not overflow and cause a similar issue. Discovered by tobias@ a while back. ok deraadt millert tobias

snprintf+writev -> dprintf

2018-04-07T18:52:39Z

Much simpler. Dropping writev makes the output from summary() non-atomic, so output lines triggered by SIGINFO can intermingle with output lines triggered by SIGINT or atexit(3). This behavior is difficult to trigger, even deliberately. The buffer in dprintf is large enough so that lines produced by summary() are not garbled if this occurs, though, so this is unlikely to break any scripts. Discussed at length with deraadt@, who helpfully noted that "not all problems have perfect solutions." ok millert@