User talk:Slawmaster: Difference between revisions

→‎VFS tasks: new section
m (I lied...put it in OS)
(→‎VFS tasks: new section)
 
(5 intermediate revisions by 3 users not shown)
Line 1:
You should write a Plan 9 article for the [[:Category:Encyclopedia|Encyclopedia]]. If you do, make sure you put <nowiki>[[Category:Operating Systems]]</nowiki> on it somewhere. --[[User:Mwn3d|Mwn3d]] 09:05, 24 January 2008 (MST)
 
 
==logger bot==
 
Now that we've got a server we can run on, the requirements for the logger bot are slightly different. (Such as, you could insert records into a database, or even write files directly.) Are you still interested in finishing lumberjack? --[[User:Short Circuit|Short Circuit]] 04:22, 11 July 2008 (UTC)
 
== Welcome back! ==
 
Long time no see! --[[User:Short Circuit|Michael Mol]] 23:09, 14 December 2009 (UTC)
 
: Considering your programming language preferences, maybe that should be Long time no C. --[[User:Rldrenth|Rldrenth]] 20:07, 14 December 2009 (UTC)
::Aw boooooo! Bad pun! :p --[[User:Mwn3d|Mwn3d]] 21:56, 14 December 2009 (UTC)
 
== VFS tasks ==
 
I would like to set up a number of VFS tasks intended for three-axis comparison: language, task and VFS API. Obvious VFS APIs that come to mind are Plan9, FUSE, GNOME VFS and Windows Shell extensions. With RC's layout, I expect that they'll need to be named [[Task (VFS API)]], with languages on each page. I expect you'd be interested in writing some of the Plan9 versions?
 
Hmm. I suspect a bidirectional Plan9-FUSE bridge might be an effective way to cover both APIs for each language; It handles the server and client aspects of both, though it may not necessarily show all of the capabilities of Plan9. --[[User:Short Circuit|Michael Mol]] 23:15, 14 December 2009 (UTC)