Menu
▾
▴
italk-devel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(17) |
Jun
(7) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Yutaka O. <yu...@oi...> - 2002-06-04 15:18:13
|
Do you remember this mailing list? Can't I still use Japanese message in this mailing list? By the way, I think all new features which is tightly tied to usability should be discussed deeply by all monkeys (including both quiet and loud people, both ones who feel comfortable with current situation and ones who does not), and (at least) server admins should take care of those various opinions carefully. # I respect Tak-san's freedom on inid design as # the server programmer, but as a server admin # he has some responsibility for all monkeys including us. The multi-room feature testing in main.italk.ne.jp server is very annoying to me. In my opinion, Those features should be optional (i.e. it should be disabled by default), and the room key character (':') is conflicting with very-common notation of time (eg 8:00). # For non-Japanese people: # In Japanese it usually comes to the first word of the line. So, I strongly suggests following three features. 1. The default behavior should be changed to /ta (all chat displayed), from the time of first 10-line log replaying. Or, at least, 2. The room display switch should be changable BEFORE login process. 3. The key character should not be ":" nor "/". The sequence [0-9]: appears 140 times in the main server's log. The sequence [0-9]/ appears 280 times in the main server's log. (both from Jan. 1 to May 31.) My suggestion is to use '|' as a key. I hope those features implemented as soon as possible. Any opinions and suggestions welcome. -- Yutaka Oiwa Yonezawa Lab., Dept. of Computer Science, Graduate School of Information Sci. & Tech., Univ. of Tokyo. Mail addresses: <oi...@yl...>, <yu...@oi...> PGP fingerprint = C9 8D 5C B8 86 ED D8 07 EA 59 34 D8 F4 65 53 61 |
|
From: YAEGASHI T. <t...@ke...> - 2000-12-20 03:44:14
|
SourceForge Japanese Foundry: http://sourceforge.net/foundry/japanese/ -- YAEGASHI Takeshi <t...@ke...> |
|
From: Ein T. <app...@tk...> - 2000-07-09 09:17:15
|
I've committed some another code. Now WIN32_SERVICE - - holds options in the registry. - has Debug Console. I guess that minimul requirement for actual use is now filled. Umm... I wonder how slow I am to do all that simple things. Anyway I'll carry on. ---- Ein Terakawa app...@tk... |
|
From: <ta...@st...> - 2000-06-20 12:53:35
|
Inidwin 1.02.01 is now available.
http://italk.sourceforge.net/servers/inidwin/
Thanks for all developers, testers and other contributors.
--
NAKAMURA Takayuki
ta...@st... (^^;
|
|
From: <ta...@st...> - 2000-06-19 15:20:57
|
Italk developers, "cvs watch" feature is now available. yourhost:your/work/dir% cvs watch add yourhost:your/work/dir% cvs watch remove yourhost:your/work/dir% cvs watchers Mails are sent to: yo...@us... See also: manpage of cvs (or info of cvs) regards, -- NAKAMURA Takayuki ta...@st... (^^; |
|
From: <ta...@st...> - 2000-06-19 15:10:44
|
au- >From: ta...@st... (NAKAMURA Takayuki) >Date: Sat, 17 Jun 2000 23:27:50 +0900 (JST) >Message-Id: <200...@ta...> >>I have created a source archive of inidwin 1.02.01 as a "release candidate." >> >> ftp://italk.sourceforge.net/pub/italk/inidwin-src-1.02.01.tar.gz >> >>If the source archive is inappropriate, I will remove the CVS tag. > >The above archive was INAPPROPRIATE :-) >I created a new source archive and put it into the ftp server as the same >archive name. The second updated file was also INAPPROPRIATE (^^; sando-me-no shou-jiki. Please download and compile it under Win32 environment. >taka@orbital:/home/groups/ftp/pub/italk>ls -l >total 364 >-rw-r--r-- 1 taka users 366532 Jun 19 07:54 inidwin-src-1.02.01.tar.gz >taka@orbital:/home/groups/ftp/pub/italk>md5sum inidwin-src-1.02.01.tar.gz >316860a718ab1e30484f6b956ea96c6f inidwin-src-1.02.01.tar.gz >regards, -- NAKAMURA Takayuki ta...@st... (^^; |
|
From: <ta...@st...> - 2000-06-17 14:31:23
|
Inidwin developers, >From: ta...@st... (NAKAMURA Takayuki) >Date: Sat, 17 Jun 2000 08:58:00 +0900 (JST) >Message-Id: <200...@ta...> >I have created a source archive of inidwin 1.02.01 as a "release candidate." > > ftp://italk.sourceforge.net/pub/italk/inidwin-src-1.02.01.tar.gz > >If the source archive is inappropriate, I will remove the CVS tag. The above archive was INAPPROPRIATE :-) Takeshima have committed the correct files. I created a new source archive and put it into the ftp server as the same archive name. I removed and re-put the CVS tag "inidwin10201" on the main trunk, too. >taka@orbital:/home/groups/ftp/pub/italk>ls -l >-rw-r--r-- 1 taka users 366513 Jun 17 07:16 inidwin-src-1.02.01.tar.gz >taka@orbital:/home/groups/ftp/pub/italk>md5sum inidwin-src-1.02.01.tar.gz >7831ecd60535fc9841d763ddfc1aa331 inidwin-src-1.02.01.tar.gz Please download and compile it under Win32 environment. regards, -- NAKAMURA Takayuki ta...@st... (^^; |
|
From: <ta...@st...> - 2000-06-17 00:01:30
|
Inidwin developpers,
>From: ta...@st... (NAKAMURA Takayuki)
>Date: Wed, 14 Jun 2000 00:48:33 +0900 (JST)
>Message-Id: <200...@ta...>
>I've committed new inidwin files from Takeshima, Thu. Jun 13.
>I've also modified and committed inid.cnf for new inidwin's feature.
>
>We had better go into "release work phase for inidwin 1.02.01", I think.
I have created a source archive of inidwin 1.02.01 as a "release candidate."
Please download and compile it under Win32 environment.
ftp://italk.sourceforge.net/pub/italk/inidwin-src-1.02.01.tar.gz
Inidwin 1.02.01 has a CVS tag "inidwin10201" on the main trunk.
If the source archive is inappropriate, I will remove the CVS tag.
regards,
--
NAKAMURA Takayuki
ta...@st... (^^;
|
|
From: <ta...@st...> - 2000-06-13 15:51:49
|
Hayon, I've committed new inidwin files from Takeshima, Thu. Jun 13. I've also modified and committed inid.cnf for new inidwin's feature. We had better go into "release work phase for inidwin 1.02.01", I think. Dewanen, -- NAKAMURA Takayuki ta...@st... (^^; |
|
From: Ein T. <app...@tk...> - 2000-06-10 18:34:54
|
Added DNS timeout patch by Takeshima to inidwin. I checked it and it seemed to work fairly. But I noticed DNS lookup is a bit slow with current code. To improve, timeout value passed to select should be divided into shorter periods, at lease when any lookup task is pending. DehaDeha. ---- Ein Terakawa app...@tk... |
|
From: Yutaka O. <yu...@oi...> - 2000-05-21 18:06:06
|
Italkplus 0.92beta1 is released at sourceforge. It is also available from http://www.yl.is.s.u-tokyo.ac.jp/~oiwa/temp/italkplus/italkplus-0.92beta1.tar.gz . For developpers: try forest:24690 for beta-testing, please. -- Yutaka Oiwa Yonezawa Lab., Department of Information Science, Graduate School of Science, University of Tokyo. <oi...@yl...>, <yu...@oi...> PGP fingerprint = C9 8D 5C B8 86 ED D8 07 EA 59 34 D8 F4 65 53 61 |
|
From: <ta...@st...> - 2000-05-21 17:47:13
|
yo- >From: "H.Takeshima" <hid...@a2...> >Date: Sun, 21 May 2000 00:24:24 +0900 >Message-ID: <000701bfc26f$7bb856a0$030...@hi...> >> Store as a command-line in the registry? >I recommend to use this. >I think any files which can be modified by a user or an >application should not be stored in the Windows/System32 directory. That's right, as a perfect solution. For just a quick hack, if inidwin is invoked as a service and its command line is empty, inidwin can simply add "-f Windows\system32\inid.cnf" to its command line and call inidmain(). Implementing this will take only a several minutes for applause or takeshima:-) The current implementation of NT service-ize is, to my regret, insufficient for actual use, I suppose. Quick hack is bad solution in general; however, tsukaenai yori mashi. kan -- NAKAMURA Takayuki ta...@st... (^^; |
|
From: <ta...@st...> - 2000-05-21 17:25:02
|
Inid developers,
>From: ta...@st... (NAKAMURA Takayuki)
>Date: Sun, 14 May 2000 21:11:57 +0900 (JST)
>Message-Id: <200...@ta...>
>Sorry for describing in Japanese.
>I will translate this discussion into English before long.
The followings are that.
This document is also available in:
http://italk.sourceforge.net/servers/inid/iniddeve.txt (in English)
http://inid.lefs.org/iniddevs.txt (in Japanese)
-----
Management policy for inid CVS repository (2000-05-22)
This document shows development and management policy for inid and its
CVS repository.
[Version Numbering Scheme]
**Official Release: on the main trunk
inid 1.01 (tag name: inid101 )
inid 1.02 (tag name: inid102 )
inid 1.03 (tag name: inid103 )
: :
**Developing Versions: ("-current" version on the main trunk)
inid 1.01 (official release)
inid 1.02p (between 1.01 and 1.02)
inid 1.02 (official release)
inid 1.03p (between 1.02 and 1.03)
:
A committer who modifies an official release of the source code into
developing version must also update the version number string written
in a header file.
[Management Policy of Source Tree]
1. Assignment of maintenance responsible persons
Current Assignments:
- core part : taka (NAKAMURA Takayuki)
- inidwin : noraneko (TAKESHIMA Hidenori)
- configure : yutaka (OIWA Yutaka)
A responsible person is assigned for a part of inid source codes.
The responsible person has an actual initiative for implementation and
management decision of the assigned part.
Persons who implement and/or frequently update any part of inid will be
naturally responsible persons.
A responsible person may commit any modification in the responsible part
to the main trunk of the CVS repository.
Although compiling check had better to precede the committing, it is not
a duty.
Other persons who create patches may send them to the responsible person.
The responsible person may or not merge the patch.
Each responsible person freely decides detailed management policies for
each responsible part.
The following policies are only for Taka's responsible parts.
2. Committers may create a new branch in the CVS repository.
A branch had better to be from an official release version.
A branch that starts from the version 1.xy should have the branch name
of "INID1xy_FOOBAR".
A committer may also create a branch from "-current" version when
"-current" is far from the previous official release.
The name of the branch should be "INID1xyP_FOOBAR".
Committers should read the inid coding style guide (style.txt).
3. Committers may commit their modifications to the main trunk,
if they satisfy all of the following requirements:
Requirement 1. Test your code before committing.
Your code must be able to be compiled on your environment,
as a minimal requirement for testing.
Requirement 2. Follow the inid coding style guide.
Requirement 3. Degrades are not allowed. All features must be alive.
Requirement 4. If your modification is for bug fixes or obvious extensions
of features, you can commit it freely.
Requirement 5. Else, discussions are needed in the developers' mailing list
before committing.
-----
--
NAKAMURA Takayuki
ta...@st... (^^;
|
|
From: <ta...@st...> - 2000-05-20 21:55:37
|
inid developers and italk server administorators, I have just released inid version 1.02. - A security fix for DoS attack only is a change in its core part. - Class diagrams, located in Doc/rose.pdf, is partially updated. - For inidwin part, applause's service-ize feature is integrated. Please create an inidwin binary archive and register it to sourceforge as a module named "inidwin" version 1.02. (Who will do this?) Version 1.02 is a good chance to obtain a "stable" version of inid. For inid 1.03, I will rewrite some facilities in elegant style, and add some new features. This effort may cause enbug-ging (^^; regards, -- NAKAMURA Takayuki ta...@st... (^^; |
|
From: H.Takeshima <hid...@a2...> - 2000-05-20 15:25:51
|
> Store as a command-line in the registry? I recommend to use this. I think any files which can be modified by a user or an application should not be stored in the Windows/System32 directory. Hidenori Takeshima (nor...@so...) |
|
From: Ein T. <app...@tk...> - 2000-05-20 14:51:11
|
Hello. I've committed some code to make inidwin able to run as a service. Some document is in inid/Windows/w32memo.txt (in Japanese) Now I suppose that we need to discuss how to maintain service's configuration. Store as a command-line in the registry? Or as a file, say named inid.cnf at %SystemRoot%\System32 ? What do you think. DehaDeha. ---- Ein Terakawa app...@tk... |
|
From: <ta...@st...> - 2000-05-17 16:30:37
|
Topic: Yaegashi(server) contains a buffer overflow in DNS resolution Category: tools Module: Yaegashi/Takeshi/Zephyr6 Announced: 2000-05-18 Affects: all versions before 1.01 including relay-0.xx Corrected: 2000-05-18 I. Background Yaegashi/Takeshi/Zephyr6 is a program package contains 3 commands. Yaegashi(server) is one of them and helps to create a simple server by executing a user process that inputs from stdin and outputs to stdout. II. Problem Description Yaegashi accepts a connection from another host, perform DNS reverse lookup, set a host name of the peer to an environment variable and spawn child process. A temporary buffer for the host name Yaegashi allocates is too short, which causes a buffer overflow. III. Impact Remote users who can connect to the Yaegashi port can potentially execute arbitrary code on your system. IV. Workaround Remove the Yaegashi, if you have installed it. V. Solution Upgrade your Yaegashi to 1.02 or later. It can be obtained from: http://download.sourceforge.net/italk/yaegashi-takeshi-1.02.tar.gz http://www.st.rim.or.jp/~tak/file/yaegashi-takeshi-1.02.tar.gz -- NAKAMURA Takayuki ta...@st... (^^; |
|
From: <ta...@st...> - 2000-05-14 12:12:52
|
Inid developers, Sorry for describing in Japanese. I will translate this discussion into English before long. $B$K$[$s$4$G$9$s$^$;$s(B $B$H$j$"$($:(B inid 1.01 $B$N%"!<%+%$%V$r$3$5$($^$7$?!#LdBj$J$1$l$PL@F|$K$G$b!"(B italk.el $B$N?7$7$$HG$H0l=o$K!"(Bsourceforge $B$N%b%8%e!<%kEPO?$r$7$F$*$-$^$9!#(B $B$G!"(BCVS repository $B$N$[$&$b$_$s$J$G$$$8$l$k$h$&$K=`Hw$,$G$-$?$H;W$&$N$G!"(B $B%b%8%e!<%kEPO?$,40N;$7$?8e$O!"!V$h$C$F$?$+$C$F$$$8$k!W$H$$$&$3$H$K$7$?$$$H(B $B;W$$$^$9!#(B $B$=$N$?$a$N4IM}J}?K(B($B0F(B)$B$r"-$K<($7$^$9!#$=$N$&$A1QJ8$b=q$-$^$9!#(B $B%3%a%s%H$,$"$l$P$$$^$N$&$A$K$I$&$>!#(B $BF1$8$b$N$O"-$K$bCV$$$F$*$-$^$9!#(B http://inid.lefs.org/iniddevs.txt ----- inid $B$N3+H/$r$3$&$7$h$&$H$$$&OC!#(B $B%P!<%8%g%sHV9f$E$1(B $B8x3+HG(B main trunk: inid 1.01 ($B%?%0L>(B inid101 ) inid 1.02 ($B%?%0L>(B inid102 ) inid 1.03 ($B%?%0L>(B inid103 ) : : $B3+H/Cf$NHG(B inid 1.01 $B8x3+HG(B inid 1.02p (1.01$B$H(B1.02$B$N4V$NHG(B) $B@53N$K$O!"G/7nF|(B $B;~J,IC(B $B$GHG$r;XDj$9$k!#(B inid 1.02 $B8x3+HG(B inid 1.03p (1.02$B$H(B1.03$B$N4V$NHG(B) $B@53N$K$O!"G/7nF|(B $B;~J,IC(B $B$GHG$r;XDj$9$k!#(B : $B%=!<%9%D%j!<4IM}J}?K(B (1) $B%a%s%F%J%s%9@UG$<T$r3d$j?6$k!#(B $B%a%s%F%J%s%9@UG$<T$O!"$=$NItJ,$N%3!<%I$rNI$/$$$8$C$F$$$F!";v<B>e$N(B $B4IM}7hDj8"$r;}$C$F$$$k?M$H$$$&$3$H$K$9$k!#(B $B%a%s%F%J%s%9@UG$<T$O@UG$HO0O$K$D$$$F!"(Bmain trunk $B$K<+M3$K(B commit $B$7$F$h$$!#(B $B%3%s%Q%$%k$/$i$$$ODL$C$?$[$&$,$$$$$1$I!"I,?\$G$O$J$$!#(B $B%Q%C%A$r:n$C$?$R$H$O%a%s%F%J%s%9@UG$<T$KAw$j$D$1$F$h$$!#(B ($B%^!<%8$5$l$k$+$I$&$+$OITL@(B) $B$=$l0J30$N4IM}J}?K$O!"4pK\E*$K$O!"%a%s%F%J%s%9@UG$<T$,7hDj$9$k!#(B - core part $B"*$C$?$/!y(B - inidwin $B"*$?$1$7$^(B #$B$F$$$&$+$I$&$7$h$&!#$7$P$i$/$OL5K!COBS(B? - configure $B"*$*$*$$$o(B $B0J2<$O$C$?$/!y$,4IM}$9$kItJ,$K$D$$$F$NJ}?K$G$"$k!#(B (2) committer $B$O%V%i%s%A$r@Z$C$F$h$$!#(B $B%V%i%s%A$O$J$k$Y$/8x3+HG$+$i@Z$k$N$,$h$$!#(B $B8x3+HG$N%?%0$O(B "inid1xy" $B$G$"$k!#%V%i%s%A$NL>A0$O(B INID1xy_HOGEHOGE $B$H(B $B$9$k$N$,NI$$$H;W$&!#(B $B8x3+HG$H(B current $B$,5!G=E*$KN%$l$9$.$F$$$k$H$-$O!"(Bcurrent $B$+$iJ,4t$7$F$b!"(B $B$^$"!"NI$$!#%V%i%s%A$NL>A0$O(B INID1xyP_HOGEHOGE $B$H$9$k$N$,NI$$$@$m$&!#(B $B%3!<%G%#%s%0%9%?%$%k%,%$%I(B style.txt $B$r;2>H$N$3$H!#(B (3) committer $B$O!">r7o$rK~$?$;$P!"(Bmain trunk $B$K(B commit $B$7$F$h$$!#(B $B>r7o(B1. $B$"$kDxEY$N%F%9%H$O9T$&$3$H!#:GDc8B!"<j85$GF0:n$9$k$3$H!#(B $B>r7o(B2. $B%3!<%G%#%s%0%9%?%$%k%,%$%I$K=>$&$3$H!#(B $B>r7o(B3. $B5!G=Dc2<$7$J$$$3$H!#(B $B>r7o(B4. $B%P%0%U%#%C%/%9$d<+L@$J5!G=DI2C$N$H$-$O!"<+M3$K(B commit $B$7$F$h$$!#(B $B;v8e$G9=$o$J$$$N$G!"3+H/<T(BML$B$KJs9p$9$k$3$H!#(B $B>r7o(B5. $B>e5->r7o(B4 $B$rK~$?$5$J$$>l9g!";vA0$K3+H/<T(BML$B$G5DO@$9$k$3$H!#(B ($BBg5,LO$J2~=$$J$I!#(B) -- $B$J$+$`$i(B $B$?$+$f$-(B ta...@st... (^^; |
|
From: IWAMOTO T. <iw...@sa...> - 2000-05-10 12:23:39
|
When I was tweaking the web pages, something went wrong with cvs.
If you try to run /home/groups/italk/update_WWW.sh, it will abort with
the following error and will result in a incomplete web source tree.
cvs server: failed to create lock directory in repository `/cvsroot/italk/WWW/htdocs/people/iwamoto': Permission denied
cvs server: failed to obtain dir lock in repository `/cvsroot/italk/WWW/htdocs/people/iwamoto'
cvs [server aborted]: read lock failed - giving up
I hope this problem will be fixed soon by some kind of magic.
You can check the existence of this problem by:
$ cd /home/groups/italk/htdocs/people/iwamoto; cvs update
In the meanwhile, please keep in mind the above problem.
Sorry for inconvenience caused.
--
IWAMOTO Toshihiro
|
|
From: YAEGASHI T. <yae...@ma...> - 2000-05-07 20:17:56
|
Hi, >Developers, > >I have imported inid source tree into CVS repository. >italk/servers/inid/inid/* are available. >But, this effort is *experimental*, please do not modify nor commit. I've moved servers/inid/inid/* to servers/inid in the repository, with taka's permission. For your reference, how to remove the whole tree from the repository: % cvs -d yae...@cv...:/cvsroot/italk co servers/inid/inid % cd servers/inid % rm `find inid -type f | grep -v CVS` % cvs remove inid % cvs commit -m "Moved to the correct position." -- YAEGASHI Takeshi <yae...@ma...> |
|
From: <ta...@st...> - 2000-05-07 19:23:50
|
Developers, I have imported inid source tree into CVS repository. italk/servers/inid/inid/* are available. But, this effort is *experimental*, please do not modify nor commit. regards, -- ta...@st... (^^; |
|
From: YAEGASHI T. <yae...@ma...> - 2000-05-05 17:52:53
|
>Here is a proposal to the cvs tree structuring.
*snip*
>Any comments? Objections?
Fine, your plan will be approved. I'm going to move italk-java/
to clients/italk-java/ soon...
The web documents should follow this structure, for example
WWW/htdocs/clients/{italk-el,witalk2} and so forth.
--
YAEGASHI Takeshi <yae...@ma...>
|
|
From: IWAMOTO T. <iw...@sa...> - 2000-05-05 16:58:54
|
Here is a proposal to the cvs tree structuring.
There should be three top level directories:
servers/ : central servers
clients/ : user clients
tools/ : misc. tools (log statistics, italk daemons...)
In each of these directories, projects should be placed in a flat
structure. For example:
servers/
italk+/
inid/
clients/
italk-el/
witalk2/
tools/
iss/
Each project should create one directory directly below {servers,clients,tools}/.
The only exception to this rule is small self-contained tools
each of which consists of a single file. Such files should go to
tools/misc/.
Any comments? Objections?
--
IWAMOTO Toshihiro
|
|
From: YAEGASHI T. <yae...@ma...> - 2000-05-05 04:14:33
|
Hi Iwamoto, welcome to our project. :-> >At Fri, 05 May 2000 09:59:05 +0900, >IWAMOTO Toshihiro <iw...@sa...> wrote: >> >> Hi. >> I can't see what is intended by the web update script below. >> Does it use both pserver and ssh??? > >I noticed that ssh is not used. So the bogus line was removed. :-) Thanks. It used ssh formerly, but switched to anonymous pserver because of bothersome ssh configuration. >And, can we put this script into the cvs repository to trace changes? Already resides in our repository, see /WWW/tools/. Feel free to improve it. >IWAMOTO Toshihiro >あたしの英語がぶっこわれてて parse できないなら次回からおとなしく >LANG=ja にします ;-) I noticed that this very line of your message is bukkowareteru at italk-devel archive, so we should decide to set LANG=C simply. :-> http://www.geocrawler.com/lists/3/SourceForge/3604/0/3695314/ -- YAEGASHI Takeshi <yae...@ma...> |
|
From: IWAMOTO T. <iw...@sa...> - 2000-05-05 01:41:22
|
At Fri, 05 May 2000 09:59:05 +0900, IWAMOTO Toshihiro <iw...@sa...> wrote: > > Hi. > I can't see what is intended by the web update script below. > Does it use both pserver and ssh??? I noticed that ssh is not used. So the bogus line was removed. :-) -- IWAMOTO Toshihiro |
