From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <48ea2444ed319fbca6d322b8ac0a80b1@plan9.escet.urjc.es> To: 9fans@cse.psu.edu Subject: Re: [9fans] Serving 9p in python - anyone started that? From: Fco.J.Ballesteros MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-nvsfyldwcjwfgzbqqcidsrtrqi" Date: Thu, 14 Nov 2002 09:34:09 +0100 Topicbox-Message-UUID: 1e60b868-eacb-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-nvsfyldwcjwfgzbqqcidsrtrqi Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Just curiosity. Why did you take that way instead of trying to get a toolset for doing rc 9p servers? I mean, IMHO, rc is the preferred way of scripting. I've some times wanted to be able to plug rc scripts into a generic 9p server skeleton, and alto to write an rc script that uses other tools to speak 9p. --upas-nvsfyldwcjwfgzbqqcidsrtrqi Content-Type: message/rfc822 Content-Disposition: inline Received: from mail.cse.psu.edu ([130.203.4.6]) by aquamar; Wed Nov 13 20:37:28 MET 2002 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.16.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id DA1A519A80; Wed, 13 Nov 2002 14:37:11 -0500 (EST) Delivered-To: 9fans@cse.psu.edu Received: from pd4mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id BAB06199A3 for <9fans@cse.psu.edu>; Wed, 13 Nov 2002 14:36:52 -0500 (EST) Received: from pd6mr1so.prod.shaw.ca (pd6mr1so-qfe3.prod.shaw.ca [10.0.141.216]) by l-daemon (iPlanet Messaging Server 5.1 HotFix 0.8 (built May 12 2002)) with ESMTP id <0H5J007DO51DJX@l-daemon> for 9fans@cse.psu.edu; Wed, 13 Nov 2002 12:34:25 -0700 (MST) Received: from pn2ml10so.prod.shaw.ca (pn2ml10so-qfe0.prod.shaw.ca [10.0.121.80]) by l-daemon (iPlanet Messaging Server 5.1 HotFix 0.8 (built May 12 2002)) with ESMTP id <0H5J00CJX51DI7@l-daemon> for 9fans@cse.psu.edu; Wed, 13 Nov 2002 12:34:25 -0700 (MST) Received: from HPN5415 (h24-76-73-101.vc.shawcable.net [24.76.73.101]) by l-daemon (iPlanet Messaging Server 5.1 HotFix 0.8 (built May 12 2002)) with SMTP id <0H5J0058T51DZV@l-daemon> for 9fans@cse.psu.edu; Wed, 13 Nov 2002 12:34:25 -0700 (MST) From: "John E. Barham" Subject: Re: [9fans] Serving 9p in python - anyone started that? To: 9fans@cse.psu.edu Message-id: <012d01c28b4b$7e8aaa20$620da8c0@HPN5415> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Mailer: Microsoft Outlook Express 6.00.2720.3000 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <003201c28b39$4f813620$6501a8c0@KIKE> Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Wed, 13 Nov 2002 11:33:07 -0800 I've started writing a generic 9P server in Python. I'm aiming to have something comparable to <9p.h> that will handle the 9P invariants but allow one to override whatever methods are needed for your particular service. With Python's good win32 extensions it should be relatively simple to let Plan 9 boxes speak to an SMB network. --upas-nvsfyldwcjwfgzbqqcidsrtrqi--