tangled
alpha
login
or
join now
jcs.org
/
openbsd-src
0
fork
atom
jcs's openbsd hax
openbsd
0
fork
atom
overview
issues
pulls
pipelines
openbsd-src
/
bin
/
dd
/
at
jcs
10 files
Makefile
gcc 2.8.X.X fixed this bug, back to a sane Makefile.
28 years ago
args.c
Implement the conv=fsync feature which does an fsync(2) after the 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@
7 years ago
conv.c
Nuke a bunch of whitespace nits seen while '%q' hunting.
9 years ago
conv_tab.c
The "old" conversions are not mandated by any standard and are underspecified. The man page offers little guidance as to their use. Remove them and spare people the (likely poor) decision to use them. ok deraadt jmc millert
12 years ago
dd.1
replace the "write a floppy image" example with a more up to date one; input/ok deraadt jca
5 years ago
dd.c
refactor the signal handlers for clarity, inverting the situation: the signal handler was calling a big function which is shared between multiple contexts -- that hides the rule that this big function has signal safe requirements (which it fails). now, the signal handler contains all the code, and everyone else calls the signal handler function as a regular function, from their (normal) contexts. the signal handler context is the most strict, so this pattern is better. ok florian
2 years ago
dd.h
Implement the conv=fsync feature which does an fsync(2) after the 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@
7 years ago
extern.h
refactor the signal handlers for clarity, inverting the situation: the signal handler was calling a big function which is shared between multiple contexts -- that hides the rule that this big function has signal safe requirements (which it fails). now, the signal handler contains all the code, and everyone else calls the signal handler function as a regular function, from their (normal) contexts. the signal handler context is the most strict, so this pattern is better. ok florian
2 years ago
misc.c
Rewrite bytes/sec calculation using fixed point math.
2 years ago
position.c
refactor the signal handlers for clarity, inverting the situation: the signal handler was calling a big function which is shared between multiple contexts -- that hides the rule that this big function has signal safe requirements (which it fails). now, the signal handler contains all the code, and everyone else calls the signal handler function as a regular function, from their (normal) contexts. the signal handler context is the most strict, so this pattern is better. ok florian
2 years ago