9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: uriel@cat-v.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9p and how can I know when a write is finished
Date: Fri,  3 Mar 2006 02:49:58 +0100	[thread overview]
Message-ID: <411d13a9f092e08cb5fe4ee6292e44bf@cat-v.org> (raw)
In-Reply-To: <4405D798.8090909@lanl.gov>

> uriel@cat-v.org wrote:
>
>> What is wrong with gpsfs(8)?
>
> damn, another thing I missed. I will look at it, sigh. I should RTFM more.

It's not surprising almost no one has noticed about it, the only
application that I know that uses it(EFIS) remains unreleased for
unknown reasons despite my repeated requests.  *sigh*

Oh, and the man page index doesn't contain any reference to gpsfs(8)

Any reason why /sys/lib/man/lookman/mkindex is not run automatically?
There seems to be quite a few things missing from the index.  (The
comment at the bottom of man(1) about lack of automatic way of
keeping indexes uptodate can probably be removed.)


> Although, I may want my gpsfs to produce s-expressions.

Oh, yea, because s-expressions are so much easier to parse with awk...
I think we should replace /adm/users to use s-expressions too, and
/proc/$pid/ns should also be s-expressions!  And next we replace rc
with a scheme interpreter...

I love scheme, and s-expressions are a billion times better than XML
will ever be, but I'm starting to suspect s-expressions fanboys are
not too different from XML zealots and think s-expressions should be
used for everything everywhere.

S-expressions are not much better than XML when dealing with them from
a Unix/Plan 9 shell, and I can think of very few, if any, cases where
they might be justified, specially having in mind that the file system
already can provide a hierarchical structure.

uriel



  reply	other threads:[~2006-03-03  1:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-01 14:29 Gabriel Diaz
2006-03-01 14:49 ` Sape Mullender
2006-03-01 15:14 ` [9fans] " Gabriel Diaz
2006-03-01 15:15 ` [9fans] " Anselm R. Garbe
2006-03-01 15:20   ` uriel
2006-03-01 15:29     ` Anselm R. Garbe
2006-03-01 15:49       ` Gabriel Diaz
2006-03-01 15:57       ` C H Forsyth
2006-03-01 16:31         ` jmk
2006-03-01 16:47     ` Russ Cox
2006-03-01 22:55       ` Dave Eckhardt
2006-03-01 22:59         ` rog
2006-03-01 23:06           ` Ronald G Minnich
2006-03-01 16:58     ` Ronald G Minnich
2006-03-01 17:21       ` uriel
2006-03-01 17:19         ` Ronald G Minnich
2006-03-03  1:49           ` uriel [this message]
2006-03-03  2:34             ` Ronald G Minnich
2006-03-03 21:26             ` David Leimbach
2006-03-01 17:29         ` Russ Cox
2006-03-01 17:41           ` Paul Lalonde
2006-03-01 19:48             ` Ronald G Minnich
2006-03-01 19:58               ` "Nils O. Selåsdal"
2006-03-01 20:16               ` uriel
2006-03-02  1:45                 ` erik quanstrom
2006-03-01 18:50         ` Latchesar Ionkov
2006-03-01 18:55           ` uriel
2006-03-01 17:21       ` Gabriel Diaz
2006-03-01 17:22         ` Ronald G Minnich
2006-03-01 18:10           ` rog
2006-03-01 19:49             ` Ronald G Minnich
2006-03-01 20:15               ` rog
2006-03-01 17:59         ` Skip Tavakkolian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=411d13a9f092e08cb5fe4ee6292e44bf@cat-v.org \
    --to=uriel@cat-v.org \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).