9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] the futility of #plan9 on irc
Date: Tue, 24 May 2005 17:18:47 -0400	[thread overview]
Message-ID: <ee9e417a05052414187cbbd378@mail.gmail.com> (raw)
In-Reply-To: <20050524210721.GA2250@xware.cx>

On 5/24/05, Chris Collins <xfire-9fans@xware.cx> wrote:
> Russ Cox was once rumoured to have said:
> > Tim Newsham:
> > > Despite what Andrey said (most of which is true), IRC is still
> > > the first place I'd recommend someone with a plan9 question
> > > go ask.  Depending on who is watching, they could get a good
> > > answer, or perhaps just a snide 'RTFM.'  When it works it
> > > works well and when it doesn't, there's 9fans for a slightly
> > > less timely response.
> >
> > I think reading the FAQ, poking around the Wiki, and then
> > asking on 9fans is a much more reliable way to go.
> >
> > Poking around the IRC logs from the first week of May,
> > I have learned that the /sys/src/9 kernels have no
> > SCSI support (only /sys/src/fs does) and that there is
> > no way for acme to pipe the current buffer through a
> > program.  Sometimes, when such misinformation is stated
> > as fact, someone is around to correct it.  But just as often
> > it seems that no one is around to correct it.  And if you're
> > a newbie and you get the latter, I don't believe that you've
> > done better than asking on 9fans and waiting a little while.
> 
> Of course, if you had actually bothered to hang around and listen, you
> would have had heard the prior case (SCSI support) corrected at the
> very least. (I was online to see that one myself).

Sometimes, when such misinformation is stated
as fact, someone is around to correct it.  But just as often
it seems that no one is around to correct it.  And if you're
a newbie and you get the latter, I don't believe that you've
done better than asking on 9fans and waiting a little while.

The SCSI comment did get corrected, eventually, though
the comment about acme not being able to pipe a buffer
through an external program did not.

Russ


  reply	other threads:[~2005-05-24 21:18 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 11:27 Russ Cox
2005-05-23 12:18 ` Vester Thacker
2005-05-23 17:44   ` Bruce Ellis
2005-05-23 17:46     ` Rob Pike
2005-05-23 18:43       ` Tim Newsham
2005-05-24  4:41     ` Dan Cross
2005-05-23 12:22 ` Uriel
2005-05-23 15:55   ` jmk
2005-05-24  0:54   ` Country Joe
2005-05-23 23:33 ` Chris Collins
2005-05-23 23:57   ` andrey mirtchovski
2005-05-24  0:03     ` Eric Van Hensbergen
2005-05-24  0:12       ` andrey mirtchovski
2005-05-24  4:29       ` Tim Newsham
2005-05-24 15:19         ` Russ Cox
2005-05-24 16:39           ` Vester Thacker
2005-05-24 16:43             ` William Josephson
2005-05-24 17:08               ` Vester Thacker
2005-05-26  4:02               ` McLone
2005-06-19 11:41             ` Vester Thacker
2005-06-19 11:43               ` Vester Thacker
2005-05-24 21:07           ` Chris Collins
2005-05-24 21:18             ` Russ Cox [this message]
2005-05-25 16:42               ` David Leimbach
2005-05-25 16:58                 ` Bruce Ellis
2005-05-26  9:17                 ` Abhey Shah
2005-05-24 21:20             ` Dan Cross
2005-05-24 21:31               ` Jack Johnson
2005-05-24 21:54                 ` Devon H. O'Dell
2005-05-26  4:04               ` McLone
2005-05-26  4:19                 ` Devon H. O'Dell
2005-05-26  4:29                 ` Dan Cross
2005-05-24  4:46       ` Dan Cross
2005-05-24  5:29         ` Lucio De Re
2005-05-24  0:14   ` 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=ee9e417a05052414187cbbd378@mail.gmail.com \
    --to=russcox@gmail.com \
    --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).