Re: [9fans] New wiki pages about 9p services and building grids

2013-03-02 Thread Richard Miller
Thanks for producing this compendium of useful information.

One question - there's a mention of hubfs, which I wasn't familiar
with until I tracked it down in your contrib area.  Perhaps you could
provide a reference?




[9fans] iwp9 8e 31-oct — 2-nov 2013

2013-03-02 Thread erik quanstrom
this is your monthly iwp9 spam!

it's not too early to register.  i'll try to get
a special iwp9 rate this week.

- erik



Re: [9fans] iwp9 8e 31-oct — 2-nov 2013

2013-03-02 Thread David Leimbach
Where? How?

Sent from my iPhone

On Mar 2, 2013, at 10:23 AM, erik quanstrom quans...@quanstro.net wrote:

 this is your monthly iwp9 spam!
 
 it's not too early to register.  i'll try to get
 a special iwp9 rate this week.
 
 - erik
 



Re: [9fans] iwp9 8e 31-oct — 2-nov 2013

2013-03-02 Thread erik quanstrom
On Sat Mar  2 14:25:26 EST 2013, leim...@gmail.com wrote:
 Where? How?
 
 Sent from my iPhone
 
 On Mar 2, 2013, at 10:23 AM, erik quanstrom quans...@quanstro.net wrote:
 
  this is your monthly iwp9 spam!
  
  it's not too early to register.  i'll try to get
  a special iwp9 rate this week.

sorry.  hotel rate.  http://iwp9.org for currently
known details.

- erik



Re: [9fans] MS office XML to txt/troff

2013-03-02 Thread erik quanstrom
On Tue Feb 26 06:26:55 EST 2013, st...@quintile.net wrote:
 New toys in my contrib to convert modern
 microsoft office XML files to text or troff/tbl source.
 
 these live in a directory opc as the standard is known as Open
 Packaging Conventions and there may be more tools to come.
 
 docx2troff works pretty well, the formatting is imperfect but
 looks OK, embedded drawings are ignored (sorry, too hard).
 
 xlsx2txt works find for text output but custom number formats are
 not handled which is disappointing - this means they work fine
 for most documents but clever spreadsheets can cause problems.
 This may get fixed one day - feel free if you want to try.
 
 code in /n/sources/contrib/steve/opc.tgz and depends on
 /n/sources/contrib/steve/libxml.tgz
 
 fixes and extensions greatfully received. please don't reformat
 the code without contacting me first.

this has been included in 9atom.

it works pretty well for my purposes, and has reduced the need
to switch to google docs for much of anything.  

it would be nice to have a troff2docx as well.  i've recommended
parsing excel format strings as a gsoc project.

- erik



Re: [9fans] curious mtime of cwfs

2013-03-02 Thread erik quanstrom
  From stat(5):
 
 For a plain file, mtime is the time of the most recent
 create, open with truncation, or write; for a directory
 it is the time of the most recent remove, create, or
 wstat of a file in the directory.

does this apply to synthetic file servers as well?  does any
one know the reasoning behind this change?  at first
glance, it seems like a relatively large impact considering
the potential gain.

- erik



Re: [9fans] curious mtime of cwfs

2013-03-02 Thread arisawa
Hell erik,

Thanks for your attention.

I looked old Plan 9 manual ver.2.
The quoted portion of stat(5) is not changed since that time.

Plan 9 does not have ctime.
If the directory mtime is not updated in changing wstat info,
It will be bothersome to detect changes in permission etc since given time.
And in addition, if cwfs works same as manual, we can quickly get correct info 
of changes in each dump.

Kenji Arisawa

On 2013/03/03, at 6:08, erik quanstrom quans...@labs.coraid.com wrote:

 From stat(5):
 
For a plain file, mtime is the time of the most recent
create, open with truncation, or write; for a directory
it is the time of the most recent remove, create, or
wstat of a file in the directory.
 
 does this apply to synthetic file servers as well?  does any
 one know the reasoning behind this change?  at first
 glance, it seems like a relatively large impact considering
 the potential gain.
 
 - erik
 




Re: [9fans] New wiki pages about 9p services and building grids

2013-03-02 Thread mycroftiv
Richard Miller 9fans@ham... wrote:
 Date: Sat, 2 Mar 2013 15:32:27 + 
 Thanks for producing this compendium of useful information.  
 One question - there's a mention of hubfs, which I wasn't familiar 
 with until I tracked it down in your contrib area.  Perhaps you could 
 provide a reference?

Thanks for the feedback on the wiki pages and the suggestion.  I
created and linked a new wiki page with extensive hubfs documentation
and usage examples.

http://www.plan9.bell-labs.com/wiki/plan9/hubfs/index.html

I wrote hubfs several years ago after noticing the absence of a
general purpose screen type utility in Plan 9.  aux/consolefs is
focused on a particular use case, serial consoles.  I feel that the
excellent Plan 9 design (no tty and 9p to handle local/remote clients
identically) helped me luckily stumble into a very nice simple fs
design that does both screen and general purpose network pipe
muxing.

On my current grid, my main cpu server hosts hubfs and every other
machine connects to it and shares services into it, and accesses other
machines through it.  I have persistent shells from several Plan 9
systems and two linux systems always available, and a separate hubfs
is used for things like irc sessions and mail reading sessions and
telnet connections to BBSes.  My profile does import -a of the /srv of
the main cpu so i can type hub main lapsh on any node and then be
connected to the subshell with p9p rc running on my linux laptop which
has a 9p connect to the hubfs server.

I think hubfs is a nice design for bringing shells of machines on the
network into the 9p file namespace.  I don't take any personal credit
for any nice things about it, I just tried to find the simplest way to
make a screen for Plan 9 and modifying a ramfs to have pipe-like
semantics and a queue of client responses seemed like the simplest way
to do it.  As it happened, the simplicity of doing it that way made it
more general purpose than a TTY-based screen and let me separate the
management of the shells from the basic idea of pipe buffering/muxing.

I'm less experienced as a developer than many so there are probably a
few naive things and eccentricities in hubfs, but it has been very
useful to me and in my use and testing it is stable and resource
efficient since all it does is just copy bytes into static buffers and
fill the 9p requests that come in.  To me, the fact that getting rid
of the TTY layer means that screen/tmux functions can be done in a
vastly simpler way - with new functionality as a free bonus - is a
nice demonstration of the benefits of clean design.

Sorry if this response was unnecessarily long, but thanks for your
interest in the wiki pages and the suggestion to write up and link
hubfs for clarity.

-Ben Kidwell 
mycroftiv