Tree
- Tree:
17bf2637c91250f593be22467fd1e6cdac56e093
- Date:
- Message:
- ftp: issue slightly smaller requests to please u9fs u9fs like to return "i/o count too large" on reads/writes that exceeds msize - 24. seems arbiratry, as in theory we should be able to issue a Tread/Twrite for msize - (HEADERSIZE + 4) = msize - 13. Don't know where the other eleven bits come from. To conclude the rant: even if a client issues a Tread/write too large, why don't just return a value smaller than requested? It's explicitly documented in the plan9 manpage for Tread.
.gitignore | commits | blame |
9ps-mode.el | commits | blame |
Makefile.am | commits | blame |
README.md | commits | blame |
fingerprint* | commits | blame |
gencert* | commits | blame |
kamid.service | commits | blame |
README.md
# contrib - `gencert` is a script to generate certificates. Usage: `./gencert name` will generate a certificate in `name` - `fingerprint` is a script that dumps the fingerprint of a certificate in a format suitable for the configuration file. Usage: `./fingerprint filename` - `9ps-mode.el` is an Emacs major mode for the regression suite DSL