In order to go about implementing [dd(1)](https://www.man7.org/linux/man-pages/man1/dd.1p.html) in a shell script we must first have feature parity. dd(1p) does the following things:
- input/output direction (`dd if=in of=out`) and control (`dd ibs=1024 obs=128 skip=5 seek=10 count=1`) - see dj(1), #15
- case conversion (`dd conv=lcase`, `dd conv=ucase`)
- endianness swapping (`dd conv=swab`) - see swab(1), #22
- character set conversion (`dd conv=ascii`, `dd conv=ebcdic`, `dd conv=ibm`)
- block alignment stuff (`dd conv=block`, `dd conv=ublock`)
Emma and I have discussed a solution to input/output direction, mm(1), which will replace cat(1p) and tee(1p). I've yet to write a utility proposal though.
Emma and I have discussed a solution to input/output direction, mm(1), which will replace cat(1p) and tee(1p). I've yet to write a utility proposal though.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In order to go about implementing dd(1) in a shell script we must first have feature parity. dd(1p) does the following things:
dd if=in of=out) and control (dd ibs=1024 obs=128 skip=5 seek=10 count=1) - see dj(1), dj(1) - disk jockey (#15)dd conv=lcase,dd conv=ucase)dd conv=swab) - see swab(1), `swab(1)` - swap bytes (#22)dd conv=ascii,dd conv=ebcdic,dd conv=ibm)dd conv=block,dd conv=ublock)Emma and I have discussed a solution to input/output direction, mm(1), which will replace cat(1p) and tee(1p). I've yet to write a utility proposal though.
dd(1p)to tests/posix: dd(1p)tests/posix: dd(1p)to tests/posix: `dd(1p)`We have decided verbally that POSIX tests will go in another repository.