From owner-9fans@cse.psu.edu Sun Feb 6 11:54:38 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id LAA09843 for 9fans-outgoing; Sun, 6 Feb 2000 11:54:38 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by cse.psu.edu (8.8.8/8.8.8) with ESMTP id LAA09838 for <9fans@cse.psu.edu>; Sun, 6 Feb 2000 11:54:30 -0500 (EST) Received: from cotswold.demon.co.uk ([194.222.75.186] helo=cotswold) by anchor-post-33.mail.demon.net with smtp (Exim 2.12 #1) id 12HUx4-0009jr-0X for 9fans@cse.psu.edu; Sun, 6 Feb 2000 16:54:22 +0000 Message-ID: <007f01bf70c2$d0bee140$6464a8c0@demon.co.uk> From: "Nigel Roles" To: <9fans@cse.psu.edu> Subject: [9fans] Booting from MS-DOS Date: Sun, 6 Feb 2000 16:54:12 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu Russ Cox and I have written an MS-DOS based boot program, with similar intentions to b.com. The difference is that it uses MS-DOS to access the local filesystem, allowing a kernel to be booted from any disk device you can find a driver for. In addition, it can use Packet Drivers to boot over the ether. This is very useful under circumstances where the main kernel has the right driver, but b.com does not. If you would like to give it a whirl, it is available (and vaguely documented at) http://www.9fs.org/boot/index.html Let us know how you get on; we might fix some things. Nigel Roles From owner-9fans@cse.psu.edu Tue Feb 15 00:01:25 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id AAA07207 for 9fans-outgoing; Tue, 15 Feb 2000 00:01:24 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from smtp.fywss.com (84.angoss.com [209.47.149.84] (may be forged)) by cse.psu.edu (8.8.8/8.8.8) with ESMTP id AAA07202 for <9fans@cse.psu.edu>; Tue, 15 Feb 2000 00:01:19 -0500 (EST) Received: (from steve@localhost) by smtp.fywss.com (8.9.3/8.9.3) id AAA25016 for 9fans@cse.psu.edu; Tue, 15 Feb 2000 00:01:00 -0500 Date: Tue, 15 Feb 2000 00:01:00 -0500 From: Steve Kotsopoulos Message-Id: <200002150501.AAA25016@smtp.fywss.com> To: 9fans@cse.psu.edu Subject: [9fans] [reminder] pointer to Plan 9 FAQ Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu The Plan 9 faq is posted to comp.os.plan9 at the beginning of each month. It is also at news.answers archive sites, look for comp-os/plan9-faq The latest hypertext version of the faq is available at url http://www.fywss.com/plan9/plan9faq.html From owner-9fans@cse.psu.edu Wed Feb 16 21:50:07 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id VAA02925 for 9fans-outgoing; Wed, 16 Feb 2000 21:50:06 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from granite.cias.osakafu-u.ac.jp (granite.cias.osakafu-u.ac.jp [157.16.91.52]) by cse.psu.edu (8.8.8/8.8.8) with SMTP id VAA02921 for <9fans@cse.psu.edu>; Wed, 16 Feb 2000 21:50:01 -0500 (EST) From: okamoto@granite.cias.osakafu-u.ac.jp Message-Id: <200002170250.VAA02921@cse.psu.edu> To: 9fans@cse.psu.edu Date: Thu, 17 Feb 2000 11:50:39 +0900 Subject: [9fans] My current ktrans-jisho MIME-Version: 1.0 Content-Type: Text/Plain; charset="US-ASCII" Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu I put my current jisho for ktrans to our Web page (http://basalt.cias.osakafu-u.ac.jp/plan9/p9index.html). Copy the file to your $home/lib as the name of ktrans-jisho, and put a line in your profile file as KTJISHO=$home/lib/ktrans-jisho. Kenji From owner-9fans@cse.psu.edu Sun Feb 20 20:51:36 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id UAA18040 for 9fans-outgoing; Sun, 20 Feb 2000 20:51:35 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from ar.aichi-u.ac.jp ([202.250.160.71]) by cse.psu.edu (8.8.8/8.8.8) with SMTP id UAA18019 for <9fans@cse.psu.edu>; Sun, 20 Feb 2000 20:51:19 -0500 (EST) From: arisawa@ar.aichi-u.ac.jp Message-Id: <200002210151.UAA18019@cse.psu.edu> To: 9fans@cse.psu.edu Date: Mon, 21 Feb 2000 09:41:55 +0900 Subject: [9fans] b.com from fd Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu Hello 9fans! I am in trouble. Starting b.com from fd fails on some PCs and not on other PCs. that is, A> b fd!0!9pcdisk for example, fails to detect 9pcdisk on fd. One of the differences among my PCs is MPU. It seems to me that PCs with K6-2 cannot detect 9pcdisk on fd. If you have PCs with K6-2 or highter, please try to boot from fd and report the results to me. Kenji Arisawa E-mail: arisawa@aichi-u.ac.jp From owner-9fans@cse.psu.edu Mon Feb 21 03:06:53 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id DAA23160 for 9fans-outgoing; Mon, 21 Feb 2000 03:06:52 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from mailgate.Cadence.COM (mailgate.Cadence.COM [158.140.2.1]) by cse.psu.edu (8.8.8/8.8.8) with ESMTP id DAA23154 for <9fans@cse.psu.edu>; Mon, 21 Feb 2000 03:06:47 -0500 (EST) Received: from symnt3.Cadence.COM (symnt3.Cadence.COM [194.32.101.100]) by mailgate.Cadence.COM (8.9.3/8.9.3) with ESMTP id AAA27331 for <9fans@cse.psu.edu>; Mon, 21 Feb 2000 00:06:04 -0800 (PST) Received: by symnt3.cadence.com with Internet Mail Service (5.5.2650.21) id ; Mon, 21 Feb 2000 08:05:45 -0000 Message-ID: <1E485299309FD211A2100090271E27A401AF059B@symnt3.cadence.com> From: Nigel Roles To: "'9fans@cse.psu.edu'" <9fans@cse.psu.edu> Subject: RE: [9fans] b.com from fd Date: Mon, 21 Feb 2000 08:05:45 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Received: By mailgate.Cadence.COM as AAA27331 at Mon Feb 21 00:06:04 2000 Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu I have b.com working from floppy on a K6-3 350Mhz. -----Original Message----- From: arisawa@ar.aichi-u.ac.jp [mailto:arisawa@ar.aichi-u.ac.jp] Sent: 21 February 2000 00:42 To: 9fans@cse.psu.edu Subject: [9fans] b.com from fd Hello 9fans! I am in trouble. Starting b.com from fd fails on some PCs and not on other PCs. that is, A> b fd!0!9pcdisk for example, fails to detect 9pcdisk on fd. One of the differences among my PCs is MPU. It seems to me that PCs with K6-2 cannot detect 9pcdisk on fd. If you have PCs with K6-2 or highter, please try to boot from fd and report the results to me. Kenji Arisawa E-mail: arisawa@aichi-u.ac.jp From owner-9fans@cse.psu.edu Mon Feb 21 05:14:27 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id FAA24604 for 9fans-outgoing; Mon, 21 Feb 2000 05:14:27 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from ar.aichi-u.ac.jp ([202.250.160.73]) by cse.psu.edu (8.8.8/8.8.8) with SMTP id FAA24598 for <9fans@cse.psu.edu>; Mon, 21 Feb 2000 05:14:21 -0500 (EST) From: arisawa@ar.aichi-u.ac.jp Message-Id: <200002211014.FAA24598@cse.psu.edu> To: 9fans@cse.psu.edu Date: Mon, 21 Feb 2000 18:05:04 +0900 Subject: [9fans] Re: b.com from fd Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu Thank you, Russ and Nigel, boot.exe works fine. It can surely load 9pc*. My goal is to construct 9fs on the PC with K6-2/350. 9pcfs does not recognize dos on FD. I first tried to adjust my clock and replaced the data: { 5, 8, 23, "AMD-K6 3D", }, /* guesswork */ { 5, 9, 23, "AMD-K6 3D+", },/* guesswork */ in /sys/src/9/pc/clock.c and /sys/src/fs/pc/8253.c by { 5, 8, 11, "AMD-K6 3D", }, /* guesswork */ { 5, 9, 11, "AMD-K6 3D+", },/* guesswork */ It seems that the values work fine for 9pc and 9pcdisk, and probably for other 9pccpu*. However the CPU speed value shown by 9fs is unsteady. It shows: 20MHz or other values. Kenji Arisawa E-mail: arisawa@aichi-u.ac.jp From owner-9fans@cse.psu.edu Mon Feb 21 20:10:40 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id UAA17186 for 9fans-outgoing; Mon, 21 Feb 2000 20:10:40 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from ar.aichi-u.ac.jp ([202.250.160.73]) by cse.psu.edu (8.8.8/8.8.8) with SMTP id UAA17181 for <9fans@cse.psu.edu>; Mon, 21 Feb 2000 20:10:33 -0500 (EST) From: arisawa@ar.aichi-u.ac.jp Message-Id: <200002220110.UAA17181@cse.psu.edu> To: 9fans@cse.psu.edu Date: Tue, 22 Feb 2000 09:01:11 +0900 Subject: [9fans] AMD cpu detection Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu Hello 9fans, I received a mail from Jim. His patch to: /sys/src/9/pc/clock.c /sys/src/fs/pc/8253.c fixed the problem with the CPU speed being unsteady. Thanks Jim. Kenji Arisawa E-mail: arisawa@aichi-u.ac.jp From: jmk@plan9.bell-labs.com Subject: Re: [9fans] Re: b.com from fd Date: Mon, 21 Feb 2000 11:45:30 -0500 To: arisawa@aichi-u.ac.jp Here's something which might fix your problem with the CPU speed being unsteady. This code is from our current fileserver kernel and goes in 8253.c/clockinit: ... /* * set clock for 1/HZ seconds */ outb(Tmode, Load0|Square); outb(T0cntr, (Freq/HZ)); /* low byte */ outb(T0cntr, (Freq/HZ)>>8); /* high byte */ /* * Introduce a little delay to make sure the count is * latched and the timer is counting down; with a fast * enough processor this may not be the case. * The i8254 (which this probably is) has a read-back * command which can be used to make sure the counting * register has been written into the counting element. */ x = (Freq/HZ); for(loops = 0; loops < 100000 && x >= (Freq/HZ); loops++){ outb(Tmode, Latch0); x = inb(T0cntr); x |= inb(T0cntr)<<8; } /* find biggest loop that doesn't wrap */ ... I admit to not having tried this on a non-Intel processor. The delay is also necessary in the terminal/cpuserver kernels. If that fixes your problem, let me know and feel free to post the fix to 9fans. By the way, the x86amd[] table values for the Athlon are the same as for the K6: { 6, 1, 11, "AMD-Athlon", },/* trial and error */ { 6, 2, 11, "AMD-Athlon", },/* trial and error */ I have a 700MHz Athlon with an ASUS K7M motherboard; it's quite refreshing to see not a single Intel chip in the system. --jim From owner-9fans@cse.psu.edu Tue Feb 22 11:21:47 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id LAA04076 for 9fans-outgoing; Tue, 22 Feb 2000 11:21:47 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from mtiwmhc02.worldnet.att.net (imail@mtiwmhc02.worldnet.att.net [204.127.131.37]) by cse.psu.edu (8.8.8/8.8.8) with ESMTP id LAA04064 for <9fans@cse.psu.edu>; Tue, 22 Feb 2000 11:21:37 -0500 (EST) Received: from default ([12.79.201.117]) by mtiwmhc02.worldnet.att.net (InterMail v03.02.07.07 118-134) with ESMTP id <20000222162134.DORR14952@default> for <9fans@cse.psu.edu>; Tue, 22 Feb 2000 16:21:34 +0000 Reply-To: From: "Thomas West" To: <9fans@cse.psu.edu> Subject: [9fans] netlib f2c installation Date: Tue, 22 Feb 2000 11:21:21 -0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1162 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20000222162134.DORR14952@default> Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu I could use an example of an f2c installation on plan9. ie f77 library locations, tailoring of sh script, other hints and tips. -Tom From owner-9fans@cse.psu.edu Tue Feb 22 12:24:09 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id MAA06099 for 9fans-outgoing; Tue, 22 Feb 2000 12:24:09 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from bio.cse.psu.edu (galapagos.cse.psu.edu [130.203.12.17]) by cse.psu.edu (8.8.8/8.8.8) with SMTP id MAA06094 for <9fans@cse.psu.edu>; Tue, 22 Feb 2000 12:24:02 -0500 (EST) Received: (qmail 24734 invoked by uid 991); 22 Feb 2000 17:24:01 -0000 Message-ID: <20000222172401.24733.qmail@g.bio.cse.psu.edu> Date: 22 Feb 2000 12:24:01 -0500 To: 9fans@cse.psu.edu From: Roman Shaposhnick Subject: [9fans] 9p question Date: Fri, 18 Feb 2000 10:47:35 GMT Organization: St.Petersburg University Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu While playing with u9fs and 9p I ask myself: Is there are any good reason that each R-message contains fid ? I take a look at u9fs sources and have found that R-messages have exactly the same fid as T-messages. Is this a common behavior and if yes, why do we need fids in R-messages at all ? Thanks, Roman. From owner-9fans@cse.psu.edu Thu Feb 24 08:29:50 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id IAA01393 for 9fans-outgoing; Thu, 24 Feb 2000 08:29:50 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from spitfire.fywss.com (cr1009567-a.bloor1.on.wave.home.com [24.114.171.41]) by cse.psu.edu (8.8.8/8.8.8) with ESMTP id IAA01388 for <9fans@cse.psu.edu>; Thu, 24 Feb 2000 08:29:42 -0500 (EST) Received: (from steve@localhost) by spitfire.fywss.com (8.9.3/8.9.3) id IAA30300 for 9fans@cse.psu.edu; Thu, 24 Feb 2000 08:29:04 -0500 Date: Thu, 24 Feb 2000 08:29:04 -0500 From: Steve Kotsopoulos Message-Id: <200002241329.IAA30300@spitfire.fywss.com> To: 9fans@cse.psu.edu Subject: [9fans] testing ... Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu will this msg be automagically posted to comp.os.plan9? if so, how long will it take? From owner-9fans@cse.psu.edu Thu Feb 24 09:58:38 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id JAA04088 for 9fans-outgoing; Thu, 24 Feb 2000 09:58:38 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by cse.psu.edu (8.8.8/8.8.8) with SMTP id JAA04082 for <9fans@cse.psu.edu>; Thu, 24 Feb 2000 09:58:33 -0500 (EST) Received: from nslocum.cs.bell-labs.com ([135.104.8.38]) by dirty; Thu Feb 24 09:56:13 EST 2000 Received: (from jmk@localhost) by nslocum.cs.bell-labs.com (8.9.3/8.9.3) id JAA20212; Thu, 24 Feb 2000 09:56:12 -0500 (EST) Date: Thu, 24 Feb 2000 09:56:12 -0500 (EST) From: Jim McKie Message-Id: <200002241456.JAA20212@nslocum.cs.bell-labs.com> To: 9fans@cse.psu.edu Subject: Re: [9fans] testing ... Newsgroups: comp.os.plan9 In-Reply-To: <200002241329.IAA30300@spitfire.fywss.com> Organization: Bell Laboratories Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu >will this msg be automagically posted to comp.os.plan9? >if so, how long will it take? not long, apparently. will this reply make it back to the mailing list? From owner-9fans@cse.psu.edu Thu Feb 24 10:39:57 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id KAA05364 for 9fans-outgoing; Thu, 24 Feb 2000 10:39:57 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by cse.psu.edu (8.8.8/8.8.8) with ESMTP id KAA05347 for <9fans@cse.psu.edu>; Thu, 24 Feb 2000 10:39:27 -0500 (EST) Received: from cygnus-x1.we.lc.ehu.es (cygnus-x1 [158.227.6.44]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id QAA01956 for <9fans@cse.psu.edu>; Thu, 24 Feb 2000 16:39:05 +0100 (MET) From: Borja Marcos Received: (from borjam@localhost) by cygnus-x1.we.lc.ehu.es (8.9.1/8.9.1) id QAA05534 for 9fans@cse.psu.edu; Thu, 24 Feb 2000 16:39:04 +0100 (MET) Message-Id: <200002241539.QAA05534@cygnus-x1.we.lc.ehu.es> Subject: Re: [9fans] testing ... To: 9fans@cse.psu.edu Date: Thu, 24 Feb 100 16:39:04 +0100 (MET) In-Reply-To: <200002241456.JAA20212@nslocum.cs.bell-labs.com> from "Jim McKie" at Feb 24, 0 09:56:12 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu > > > >will this msg be automagically posted to comp.os.plan9? > >if so, how long will it take? > not long, apparently. will this reply make it back to the mailing list? Yes :-) -- *********************************************************************** Borja Marcos * Internet: borjam@we.lc.ehu.es Alangoeta, 11 1 izq * borjamar@sarenet.es 48990 - Algorta (Vizcaya) * borjam@well.com SPAIN * borjam@uninet.edu *********************************************************************** --- FreeBSD, turning PCs into workstations From owner-9fans@cse.psu.edu Thu Feb 24 23:18:11 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id XAA29371 for 9fans-outgoing; Thu, 24 Feb 2000 23:18:10 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from ar.aichi-u.ac.jp ([202.250.160.71]) by cse.psu.edu (8.8.8/8.8.8) with SMTP id XAA29366 for <9fans@cse.psu.edu>; Thu, 24 Feb 2000 23:17:57 -0500 (EST) From: arisawa@ar.aichi-u.ac.jp Message-Id: <200002250417.XAA29366@cse.psu.edu> To: 9fans@cse.psu.edu Date: Fri, 25 Feb 2000 12:08:43 +0900 Subject: [9fans] FD Formatting on some CPUs Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu Hello, A few days ago, I said that A> b fd!0!9pcdisk fails to detect 9pcdisk on FD on some CPUs(K6-2 300MHz and 350MHz). I found more curious phenomena. Dos command: format a:/s is unstable! Format command sometimes fails to detect FD! On the other hand, we have no trouble on formatting FD on Win98 or WinNT. Experiments is done using Dos version 6.3 on K6-2 300MHz and K6-2 350MHz. I asked to one of my friends (SE of our university) if he had a similar experience. His answer is YES. How is your PCs? Kenji Arisawa E-mail: arisawa@aichi-u.ac.jp From owner-9fans@cse.psu.edu Mon Feb 28 13:07:16 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id NAA13469 for 9fans-outgoing; Mon, 28 Feb 2000 13:07:16 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from plan9.cs.bell-labs.com (plan9.bell-labs.com [204.178.31.2]) by cse.psu.edu (8.8.8/8.8.8) with SMTP id NAA13464 for <9fans@cse.psu.edu>; Mon, 28 Feb 2000 13:07:12 -0500 (EST) Message-Id: <200002281807.NAA13464@cse.psu.edu> From: "rob pike" Subject: [9fans] Re: 9p question Date: Mon, 28 Feb 2000 13:07:00 -0500 To: 9fans@cse.psu.edu MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu The Topen message generates a permission check and enables I/O. Before the open, you may not read or write on the fid. There is no close (well, there is, but it's called clunk) because you must dispose of fids that have not been Topened, so it seemed that Tclose would be the wrong name for the operation. The manual says somewhere I believe, and the code says somewhere I know, that once a fid is opened, it cannot be walked or cloned further. This avoids some difficult implementation problems for the servers. -rob From owner-9fans@cse.psu.edu Mon Feb 28 22:25:52 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id WAA27035 for 9fans-outgoing; Mon, 28 Feb 2000 22:25:52 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from granite.cias.osakafu-u.ac.jp (granite.cias.osakafu-u.ac.jp [157.16.91.52]) by cse.psu.edu (8.8.8/8.8.8) with SMTP id WAA27027 for <9fans@cse.psu.edu>; Mon, 28 Feb 2000 22:25:46 -0500 (EST) From: okamoto@granite.cias.osakafu-u.ac.jp Message-Id: <200002290325.WAA27027@cse.psu.edu> To: 9fans@cse.psu.edu Date: Tue, 29 Feb 2000 12:26:49 +0900 Subject: [9fans] Re: Japanese Support? MIME-Version: 1.0 Content-Type: Text/Plain; charset="US-ASCII" Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu Well, I'm in trouble to post news from our Univ temporally (be avle to read though). Then, I post my response to this mailing-list. >any convinient applications for japanese text processing. I wrote many emails and an article of 50Kbytes long by acme and ktrans. I have no problem to write those. I recommend acme rather than sam to write long Japanese text. You can find all the neccessarry patches for Japanese text processing in our web page (http://basalt.cias.osakafu-u.ac.jp/plan9/p9index.html). Good luck Kenji From owner-9fans@cse.psu.edu Tue Feb 29 20:12:31 2000 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id UAA24766 for 9fans-outgoing; Tue, 29 Feb 2000 20:12:31 -0500 (EST) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from granite.cias.osakafu-u.ac.jp (granite.cias.osakafu-u.ac.jp [157.16.91.52]) by cse.psu.edu (8.8.8/8.8.8) with SMTP id UAA24760 for <9fans@cse.psu.edu>; Tue, 29 Feb 2000 20:12:25 -0500 (EST) From: okamoto@granite.cias.osakafu-u.ac.jp Message-Id: <200003010112.UAA24760@cse.psu.edu> To: 9fans@cse.psu.edu Date: Wed, 1 Mar 2000 10:13:18 +0900 Subject: Re: [9fans] Re: Japanese Support? MIME-Version: 1.0 Content-Type: Text/Plain; charset="ISO-2022-JP" Sender: owner-9fans@cse.psu.edu Precedence: bulk Reply-To: 9fans@cse.psu.edu >I recommend acme rather than sam to write long Japanese text. I forgot to write the reason of this, and then please let me try to elaborate this more. You may want to add a new word for Kana to Kanji translation (ktrans does this) sometimes during writing long Japanese text. In those cases, if you are using acme, with top menu of ktrans, you can open the Japanese dictionary file($user/jisho/ktrans-jisho in default), and edit it by ktrans, and then, hit ^q(control+q) to end the ktrans, and then click ktrans menu to open ktrans session agian. The new ktrans use the new dictionary. I decided to use plain text as dictionary item, we have no serious reason to have add/delete function of ktrans-jisho items. In my case, I usually open "Koujien" dictionary as a acme window by the command of "win jisho", and search th unregistered item from this complete Jpanases dictionary, and then cut and past to my ktrans-jisho. If you use sam, you will lose above functionarities. I hope this may help someone. Kenji