commit - 1d081be3b41f4332190f81f921393a79a7c4b776
commit + f2a3064aa7c71ca923547daf78915239d6996c4e
blob - 55f0735044a727204be66d7b8cdf8a84cc7d73fc
blob + 04d99ec9fae92288188f362f0603a0bd140a4679
--- TODO
+++ TODO
@@ -13,12 +13,6 @@ Stuff that's still to-do
 
  - tweak iounit so it's always lower than the choosen msize
 
- - handle message bigger than MAX_IMSGSIZE - IMSG_HEADER_SIZE.  One
-   way to do that would be to *not* use asynchroonus imsgs in client.c
-   but synchronous I/O: this way, once a message has been processed,
-   we can just receive the next in the same function (i.e. twrite) and
-   go ahead.
-
  - fill user and group name in struct stat.  The problem is that, being
    chrooted, we don't have access to /etc/passwd nor /etc/group. We
    could use setpassent(3) and setgroupent(3), but if they change in the
blob - feeae5020f21a63cfa2ec0bbdc9e5a8eba46d1a6
blob + 679b9c9ee1ca3ffd182ba4d1fd158e8b0a5831fb
--- site/caveats.gmi
+++ site/caveats.gmi
@@ -15,8 +15,3 @@ kamiproxy(1) can help with this, as will relay and enc
 kamid aims to be completely compatible with all existing software that speaks 9p, but at the moment it is not yet.  It’s more like 99% compatible, there’s still something missing.
 
 A known bug is that 9front can’t create or write files in a directory tree exported by kamid.  The cause is still unknown.
-
-
-### it's more slower than it needs to be
-
-Due to a technical issue, kamid uses a very small ‘msize’ (the maximum size of the packages) which is critical for reads and writes of big files.  Future version will increase the default ‘msize’.