Commits
- Commit:
55c3776073a03773f5690862f9d1b564e540aacf
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add TODO
- Commit:
3e92d717b9b64d69e5c273ac7e6732eb4bde8208
- From:
- Omar Polo <op@omarpolo.com>
- Date:
readability
- Commit:
7ede6c1f9feb8b4a0e2c13b4432f6d3702be3f24
- From:
- Omar Polo <op@omarpolo.com>
- Date:
specify the suite components
- Commit:
20f7a94e1890facb6e7f1a12acf4cf5e1e8de977
- From:
- Omar Polo <op@omarpolo.com>
- Date:
work around missing LOGIN_NAME_MAX
Both Linux and OpenBSD have LOGIN_NAME_MAX available when including
limits.h, FreeBSD, Darwin and possibly others don't.
FreeBSD (and maybe Darwin) have MAXLOGNAME, so try to use that if
available. Otherwise use _POSIX_LOGIN_NAME_MAX, but only has a fallback
since it has a lower value (9 at the time of writing).
If everything fails, use 32 which is what OpenBSD use by default;
OpenSMTPd also defaults to it.
See also github issue #1
- Commit:
a02f394431fcc473fb8290b17036d1275d2ccf0a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix url to the git repo
- Commit:
7bafb2fd590c5e1b2ebf342df0c431ff4ca6b74c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
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.
- Commit:
e22049ccccf16f61c96360a85afc0d0a0ef1085f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
ftp: allow user@host syntax; guard against empty user or port
- Commit:
9e0cb8280f65c70592dc41030a8a0a18c7c2ef3e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
specify that the syntax for the host optionally accepts a port number
- Commit:
7ac009984a28504538eab905651d32f78f64fc69
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add links to the shasums and current key
- Commit:
ab513264e882b201406436f238007a5026c2b0ad
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add a contributing and porting section on the readme
- Commit:
f2a3064aa7c71ca923547daf78915239d6996c4e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
we don't have the 16K msize anymore
- Commit:
1d081be3b41f4332190f81f921393a79a7c4b776
- From:
- Omar Polo <op@omarpolo.com>
- Date:
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
- Commit:
ee8d745002fe582ffced6cbbfb994fd43dd9c942
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix git link and add codeberg mirror
- Commit:
4aaeb83ab413218aae8aa065f00445195c4f3185
- From:
- Omar Polo <op@omarpolo.com>
- Date:
prepare the site for 0.2
- Commit:
3095ac4a4227c4f1e8f8967d457cb69b00382d02
- From:
- Omar Polo <op@omarpolo.com>
- Date:
rework & re-export Yotsuba