9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [GSOC] plan9 which arch code to use?
Date: Wed,  7 May 2014 18:46:26 -0400	[thread overview]
Message-ID: <4A005A0B-50D6-465D-B39F-577319A308F6@9srv.net> (raw)
In-Reply-To: <a76458dfd06fb48b58b559b2e5fdad94@pi.att>

[-- Attachment #1: Type: text/plain, Size: 1780 bytes --]

sl said:

> The original post (in its way) was asking for advice about
> an amd64 kernel that is not publicly available.

No, it wasn't. There was some confusion over the point that
Plan 9, unlike some other systems, selects the arch based
entirely on the running kernel (no 386 binaries running on
amd64 machines).

> Some people (not knowing the full situation) offered advice
> about publicly available amd64 kernels and were shot down.

Again, that's not what happened. Erik and cinap pointed out
one can use 9atom or 9front; Charles gave instructions for
building the amd64 userland. He then, later, pointed out that
there are things other than just the 64-bit kernels in 9atom
and 9front. It's at that point some folks seem to have felt
compelled to dredge up the old mess of the original amd64
kernel, which was not what Charles was talking about and was
not otherwise at issue here.

I'm not sure who in this conversation you think is "not knowing
the full situation"; I'm fairly confident that all the salient points
on this topic have been discussed on 9fans ad nauseam.

> Everything else follows from that.

From two faulty premises. Got it.

You should re-read the thread. You may think you've been
responding to what people are actually saying, but the
bunker-mentality defensiveness you repeatedly exhibit has
caused you to misinterpret much.

As for how the situation could be improved: well, there's lots of
potential answers to that question. This has nothing to do with
hiring professional project managers or whatever you seem to
think is required for actual coordination, but taking some care
for your upstream sources is a really effective first step common
among open source projects. Try starting there.

Anthony

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 169 bytes --]

  parent reply	other threads:[~2014-05-07 22:46 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 21:38 sl
2014-05-07 22:32 ` Charles Forsyth
2014-05-07 22:39   ` Bakul Shah
2014-05-08  1:38   ` Kurt H Maier
2014-05-08  8:41     ` Charles Forsyth
2014-05-08 14:06     ` erik quanstrom
2014-05-08 14:14       ` balaji
2014-05-08 14:20         ` Charles Forsyth
2014-05-07 22:46 ` Anthony Sorace [this message]
2014-05-07 23:01 ` Charles Forsyth
2014-05-07 23:51   ` erik quanstrom
  -- strict thread matches above, loose matches on Subject: below --
2014-05-08 13:45 erik quanstrom
2014-05-08 13:55 ` Kurt H Maier
2014-05-08 16:35   ` Jeremy Jackins
2014-05-08 17:16     ` Kurt H Maier
2014-05-08 17:47       ` Jeremy Jackins
2014-05-07 23:37 sl
2014-05-07 23:29 sl
2014-05-07 23:42 ` andrey mirtchovski
2014-05-07 22:36 sl
2014-05-07 20:56 sl
2014-05-07 21:17 ` Anthony Sorace
2014-05-07 21:33   ` Lyndon Nerenberg
2014-05-08 11:57     ` lucio
2014-05-08 12:03       ` erik quanstrom
2014-05-08 12:39         ` lucio
2014-05-07 19:57 sl
2014-05-07 20:06 ` erik quanstrom
2014-05-07 20:11   ` Jacob Todd
2014-05-07 20:19     ` Lyndon Nerenberg
2014-05-08 12:11       ` lucio
2014-05-07 18:56 sl
2014-05-07 19:53 ` erik quanstrom
2014-05-07 18:29 sl
2014-05-07 18:48 ` erik quanstrom
2014-05-08  5:56   ` lucio
2014-05-08  8:58     ` cinap_lenrek
2014-05-08 11:20       ` lucio
2014-05-08 12:07         ` erik quanstrom
2014-05-08 12:46           ` lucio
2014-05-08 13:15             ` Charles Forsyth
2014-05-08 13:48               ` Kurt H Maier
2014-05-08 14:07                 ` lucio
2014-05-08 14:04               ` lucio
2014-05-08 14:15                 ` erik quanstrom
2014-05-08 14:51                   ` lucio
2014-05-08 14:56                     ` Charles Forsyth
2014-05-08 15:16                       ` lucio
2014-05-08 10:55     ` erik quanstrom
2014-05-07  1:14 sl
2014-05-06 21:00 yan cui
2014-05-06 21:33 ` cinap_lenrek
2014-05-06 21:48   ` yan cui
2014-05-06 21:47 ` Charles Forsyth
2014-05-06 21:53   ` yan cui
2014-05-06 21:56   ` Charles Forsyth
2014-05-06 21:59     ` Charles Forsyth
2014-05-06 22:02       ` cinap_lenrek
2014-05-06 22:05       ` Charles Forsyth
2014-05-07  5:14         ` lucio
2014-05-07  5:38           ` David du Colombier
2014-05-07  6:59             ` lucio
2014-05-07  8:38               ` Riddler
2014-05-07  8:59                 ` Charles Forsyth
2014-05-07  9:05             ` erik quanstrom
2014-05-07  9:10               ` Charles Forsyth
2014-05-07  9:16                 ` erik quanstrom
2014-05-07  9:42                 ` erik quanstrom
2014-05-07  9:23               ` David du Colombier
2014-05-07  9:25                 ` erik quanstrom
2014-05-07  9:31             ` David du Colombier
2014-05-07 11:13               ` lucio
2014-05-07 11:30                 ` Charles Forsyth
2014-05-07 14:36                 ` erik quanstrom
2014-05-07 17:51                   ` lucio
2014-05-07 18:22                     ` erik quanstrom
2014-05-08  5:39                       ` lucio
2014-05-07  8:45           ` Charles Forsyth
2014-05-07  9:12             ` erik quanstrom
2014-05-07  9:20               ` Charles Forsyth
2014-05-07  9:21                 ` erik quanstrom
2014-05-07 12:59                 ` Kurt H Maier
2014-05-07 13:36                   ` Charles Forsyth
2014-05-07 14:39                     ` erik quanstrom
2014-05-06 22:09 ` Kurt H Maier
2014-05-07  0:40 ` erik quanstrom
2014-05-07  1:01   ` Charles Forsyth
2014-05-07  1:12     ` Kurt H Maier
2014-05-07  1:39       ` Charles Forsyth

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=4A005A0B-50D6-465D-B39F-577319A308F6@9srv.net \
    --to=a@9srv.net \
    --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).