9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] How 'bout a 9 USER site?
Date: Tue, 23 Feb 2010 12:06:41 -0800	[thread overview]
Message-ID: <13426df11002231206p394b48f2ld97ba3346eeacb86@mail.gmail.com> (raw)
In-Reply-To: <2424953b-3f00-4f3e-a4c1-f02fa846b65e@v36g2000vbs.googlegroups.com>

I've just had someone here try to install reFit on her Mac. She got it
done in spite of the wikis. There's so much wrong info out on the web
now in the form of wikis that it was all virtually useless. I become
more disappointed in wikis as the years go by.

Even the Plan 9 wiki has instructions in it that are not quite right
any more. If you're determined to do a wiki, perhaps you could do it
by offering corrections and additions to that one, rather than a new
one.

A wiki is a thing separate and apart from a Plan 9 file system, and
people have to go find it. Invariably, there are errors and problems
and info gets out of date. It's not synced to man pages or other
documents.  I don't like to assume failure either but after the n'th
time somebody has offered to put up a wiki and it's followed the same
sad trajectory, well, I end up feeling that wiki is the wrong model.
It's like the CADT model applied to support.

The standard Plan 9 information-passing mechanism is the man pages.
The standard script for "mount this stuff" are tools like 9fat and
9fs. Maybe the real problem is we need more scripts to help people
along.

It leads me to wonder if you could not glean what you need to know and
create a script called '9usb', for example. Once it's in there as a
script it's there for good and might even get maintained.

Sorry to be so discouraging, I just think the wiki is not going to do
what you want.

ron



  parent reply	other threads:[~2010-02-23 20:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-23 16:17 Purple_Q
2010-02-23 16:37 ` John Floren
2010-02-23 16:43   ` erik quanstrom
2010-02-23 17:32     ` John Floren
2010-02-23 17:52       ` erik quanstrom
2010-02-24 10:10     ` Purple_Q
2010-02-24 11:26       ` John Stalker
2010-02-24 13:23         ` Eric Van Hensbergen
2010-02-24 16:00           ` David Leimbach
2010-02-23 17:50   ` Purple_Q
2010-02-23 18:25     ` K T Kutani
2010-02-23 18:51       ` hiro
2010-02-23 19:31     ` Tim Newsham
2010-02-24 10:10   ` Purple_Q
2010-02-23 19:45 ` Dave Eckhardt
2010-02-23 20:12   ` Steve Simon
2010-02-23 23:20     ` David Leimbach
2010-02-23 23:23       ` David Leimbach
2010-02-23 23:52         ` Steve Simon
2010-02-24  0:20           ` Lyndon Nerenberg
2010-02-24  0:25             ` erik quanstrom
2010-02-24  2:26               ` David Leimbach
2010-02-24 16:43         ` hiro
2010-02-24 16:44         ` hiro
2010-02-23 20:18   ` erik quanstrom
2010-02-24 10:10     ` Purple_Q
2010-02-24 19:59       ` Tim Newsham
2010-02-23 20:06 ` ron minnich [this message]
2010-02-24  0:40 ` Federico G. Benavento
2010-02-24  9:24 José Brandão
2010-02-26 21:06 ` Georg Lehner

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=13426df11002231206p394b48f2ld97ba3346eeacb86@mail.gmail.com \
    --to=rminnich@gmail.com \
    --cc=9fans@9fans.net \
    /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).