Commits


fix url to the git repo


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.


ftp: allow user@host syntax; guard against empty user or port


specify that the syntax for the host optionally accepts a port number


add links to the shasums and current key


add a contributing and porting section on the readme


we don't have the 16K msize anymore


tag 0.2 * fix twstat handling of mode bits * rejects incoming connections with a ridiculously small msize * allow "jumbo" (i.e. more than 16K) Twrite and Treads * allow Tread to read exactly msize bytes * kamiftp: fix reads wrt msize * kamiftp: do maximum reads and writes


fix git link and add codeberg mirror


prepare the site for 0.2


rework & re-export Yotsuba


artwork for 0.2


declare a variable for the homepage image


- [regress] added test to write a file using a big buffer (msize).


simplify check in handle_message