loco-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Loco-dev] actually, nothing...


From: tok
Subject: [Loco-dev] actually, nothing...
Date: 24 Feb 2003 23:03:09 +0100

hi everybody,

just browsed through the latest checkout, here's what i found:

1) some typos in the docs. i've added a diff for those i've noticed.

2) some problems when there is no key in ~/.loco, the program tried to 
create key (queried for real name) but broke after the first step (bash:
[name] command not found) and screwed up the terminal.
it seems to have generated a key but it appeared to be random binary
data (set_key(...) in locod.wsl contained mainly unprintable chars).
after creating a key manually (gpg --homedir ~/.loco --gen-key) and
modifying locod.wsl set_key to the appropriate real name, the daemon
seemed to start.

3) i had to remove locod.pid file a few times, maybe some signal handler
doesn't remove it properly?

4) i don't get any feature in com working, i can't even find my own peer
(searching for my name/email). anything implemented here?

regards,
tok

begin diff
-----------------------------------------
Index: doc/loco.texi
===================================================================
RCS file: /cvsroot/loco/loco/doc/loco.texi,v
retrieving revision 1.11
diff -r1.11 loco.texi
250c250
< status two). Packats with status three do not have this field.
---
> status two). Packets with status three do not have this field.
260c260
< is sufficient for an application to send data in the format sepcified
---
> is sufficient for an application to send data in the format specified
273c273
< The type tag indicates how to hadle this packet. The content blocks
---
> The type tag indicates how to handle this packet. The content blocks
278c278
< tag, it sould inform the sender (@pxref{Responses}) and discard the
---
> tag, it should inform the sender (@pxref{Responses}) and discard the
366c366
< defines valid proceudres, functions and structures for a context as
---
> defines valid procedures, functions and structures for a context as
439c439
< desiable to define @code{name}, @code{nickname}, @code{key} and
---
> desirable to define @code{name}, @code{nickname}, @code{key} and
470c470
<  <strucutre_name> ::= <string_literal>
---
>  <structure_name> ::= <string_literal>
566c566
< than one line) or conaints binary data or can occur different numbers
---
> than one line) or contains binary data or can occur different numbers
672c672
< structutre address (string cname, int port)
---
> structure address (string cname, int port)
676c676
< The @code{peer} containts the connection information and a
---
> The @code{peer} contains the connection information and a
682c682
< To find sonething in the @dfn{CaptainChord} system (even one's own
---
> To find something in the @dfn{CaptainChord} system (even one's own
783c783
< is asked for hin name, email address and a nickname, so a new key can
---
> is asked for her/his name, email address and a nickname, so a new key
can
----------------------------------------------------
end diff






reply via email to

[Prev in Thread] Current Thread [Next in Thread]