9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@orthanc.ca>
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 14:33:10 -0700	[thread overview]
Message-ID: <251E59BE-8F7D-44E1-8F7D-44E604AD3220@orthanc.ca> (raw)
In-Reply-To: <93744421-726D-4E20-8612-79CD50A6D119@9srv.net>

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


On May 7, 2014, at 2:17 PM, Anthony Sorace <a@9srv.net> wrote:

> What some folks are suggesting is that some coordination would yield better results; that we can do better than the "everyone going off and doing their own thing" part of the above scenarios.
> 
> I believe Erik's point about "falling into disrepair" is that if everyone is spending time fixing the same issues, each on their own without any coordination, is that the resulting system will increasingly fail to keep up with the evolution of the surrounding world. Even if the code for all the parts I need to drive exist, that's not the same as having a running system.

I do think there is an analogy to be made with the 4.x BSD releases.  They were few and far between, but they were also the prescriptive reference points for that UNIX fork.  There was a lot of development that branched off from the UCB code base.  But much of what was of benefit to all (device drivers, VM enhancements, apps) was folded back into the core.  The CSRG encouraged that.  And with the CSRG releases as a reference, it wasn't that difficult to share local modifications between sites.

But the Labs are not the CSRG.  There is no longer a central focus point for the code base.  Not in the community sense – the Labs are no longer interested.  We are losing the 'reference implementation' from which the branches can be compared.  Without an anchor we will drift off in many incompatible directions, to the point where code sharing will become so annoying it just won't happen (in the kernel at least, and in the /dev/* user space as a side effect).

--lyndon


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

  reply	other threads:[~2014-05-07 21:33 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 20:56 sl
2014-05-07 21:17 ` Anthony Sorace
2014-05-07 21:33   ` Lyndon Nerenberg [this message]
2014-05-08 11:57     ` lucio
2014-05-08 12:03       ` erik quanstrom
2014-05-08 12:39         ` lucio
  -- 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 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
2014-05-07 23:01 ` Charles Forsyth
2014-05-07 23:51   ` erik quanstrom
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=251E59BE-8F7D-44E1-8F7D-44E604AD3220@orthanc.ca \
    --to=lyndon@orthanc.ca \
    --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).