The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] First Unix-like OSes not derived from AT&T code?
Date: Mon, 2 May 2022 14:31:00 -0600	[thread overview]
Message-ID: <CANCZdfrdp4yGJwum0QDEoPRwCfvVPLe3C0M7Lr3MQ7TsG0BwSg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2Mue5sU6H4sPojvj_ov1R9ZyeFgpwE4_shqmoX4GYT8AQ@mail.gmail.com>

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

On Mon, May 2, 2022 at 9:41 AM Clem Cole <clemc@ccc.com> wrote:

>
>
> On Mon, May 2, 2022 at 10:46 AM tytso <tytso@mit.edu> wrote:
>
>> So it appears that it was not a
>> matter of "the upstream Linux kernel team.... [being] willing to take
>> the VPROC changes", it was more like no one asked, or prepared patches
>> that could be considered by usptream.
>>
> FWIW:  I know that at least 3 people on the OpenSSI team were telling me
> they were told to go away.   I do not know the details of the interchange,
> but doing some Linux work at the time, I too found the reception to kernel
> changes to often be a tad cold (it took 10 years to get the core RDMA
> support up-streamed). It's possible the way the OpenSSI team asked, the
> prayers offered were not acceptable to those in charge at the time.  I
> don't know, but please be careful here. *They were tried and feel
> that they were rejected.*   *That is history*.  I understand that you
> want to try to say, well there is no evidence of the proper emails/git
> change, *etc.*   But that team ran into blocks.  So you can be a lawyer
> about it, or you can try to accept what actually happened to those of us on
> the other end with some grace.
>

I know from wearing my FreeBSD hat that random people on mailing lists
often say 'nope' and people go away not realizing they aren't the abitors
of what gets into FreeBSD. We lost a lot of good contributions because of
delays created by scenarios like this...

I also know that getting changes into Linux suffers from this and for a
long time (especially pre-git) was almost impossible unless you knew
someone and were on good terms with them.

Also, people will get frustrated after one or two things don't go up and
they don't do the rest. Or they do one big huge thing that's impossible to
review (maybe it went to the wrong place) and they give up too unless
there's an 'advocate' that works with them to make the changes bite-sized
and sorts out the wheat from the chaff that's almost always in huge change
sets. The process that was documented was hit or miss. Plus lkm wasn't the
nicest of places with the best of interactions, which put off a lot of
people from even trying... Much has been done to improve things in the last
20 years, but for a while things were truly awful for someone without a
huge reputation to get anything non-trivial into Linux. Even today,
projects following the Linux model can be difficult to land changes in,
even when you are nominally the maintainer of a part of the tree...

VPROC was done for 2.6, which is long enough ago to be in the 'bad old
days' of getting things upstreamed.

It wouldn't surprise me at all that enough things were done wrong, and/or
they listened to the wrong people and/or submitted things in the wrong
place they the OpenSSI folks just gave up in frustration early on w/o
getting the right people's attention...

Warner

[-- Attachment #2: Type: text/html, Size: 3932 bytes --]

  reply	other threads:[~2022-05-02 20:33 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01  9:30 Andrew Warkentin
2022-05-01 11:43 ` Ron Natalie
2022-05-01 11:56   ` Rob Pike
2022-05-01 14:03     ` Kenneth Goodwin
2022-05-03  4:37       ` Jim Carpenter
2022-05-01 14:09   ` Kenneth Goodwin
2022-05-01 18:08     ` ron minnich
2022-05-01 18:22       ` Charles H Sauer (he/him)
2022-05-01 19:49         ` Dan Stromberg
2022-05-01 20:37           ` Charles H Sauer (he/him)
2022-05-02  2:08       ` Kenneth Goodwin
2022-05-02  9:21         ` Dr Iain Maoileoin
2022-05-02 20:19           ` Rich Morin
2022-05-02 21:30             ` Clem Cole
2022-05-02 21:36             ` Dan Cross
2022-05-10 15:28         ` Mary Ann Horton
2022-05-10 16:08           ` Warner Losh
2022-05-10 16:40             ` Heinz Lycklama
2022-05-10 16:42             ` James Frew
2022-05-14  2:56             ` Mary Ann Horton
2022-05-10 16:59           ` Clem Cole
2022-05-10 17:18             ` Clem Cole
2022-05-10 18:05               ` Charles H Sauer (he/him)
2022-05-10 19:27                 ` Lars Brinkhoff
2022-05-10 19:08               ` Henry Bent
2022-05-10 19:33                 ` Richard Salz
2022-05-10 20:18                   ` Ronald Natalie
2022-05-11 16:20                     ` James Frew
2022-05-11 16:51                       ` Paul Winalski
2022-05-10 20:28                   ` Henry Bent
2022-05-10 20:43                   ` Warner Losh
2022-05-10 20:46                   ` Clem Cole
2022-05-11 16:44                     ` Paul Winalski
2022-05-11 17:09                       ` Clem Cole
2022-05-11 17:35                       ` Larry McVoy
2022-05-12  0:16                         ` George Michaelson
2022-05-13  2:46                         ` Adam Thornton
2022-05-15  0:48                           ` Larry McVoy
2022-05-15  5:36                             ` Adam Thornton
2022-05-15 13:37                               ` Larry McVoy
2022-05-12  5:22                       ` Warner Losh
2022-05-12 12:06                         ` Ron Natalie
2022-05-12 12:43                           ` John Cowan
2022-05-15  2:00         ` Stuart Remphrey
2022-05-02  2:42       ` Phil Budne
2022-05-02  6:46         ` Ron Natalie
2022-05-02 13:50           ` Clem Cole
2022-05-02 14:46             ` tytso
2022-05-02 15:38               ` Clem Cole
2022-05-02 20:31                 ` Warner Losh [this message]
2022-05-03  5:01                   ` tytso
2022-05-03 11:35                     ` Richard Salz
2022-05-02 23:30           ` Gregg Levine
     [not found]           ` <CAK7dMtD08weh+97mx+ncrq0cxprKgke42C0vFYNPnBkd8Fx9Sg@mail.gmail.com>
2022-05-03  7:28             ` Ronald Natalie
2022-05-02 12:59         ` Kenneth Goodwin
2022-05-02 14:13           ` Richard Salz
2022-05-02 13:14         ` tytso
2022-05-02 13:32           ` Larry McVoy
2022-05-02 13:16         ` Dan Cross
2022-05-02 14:14           ` Miod Vallat
2022-05-02 14:50             ` ron minnich
2022-05-02 16:13             ` Al Kossow
2022-05-02 18:46               ` Miod Vallat
2022-05-02 19:54               ` Chet Ramey
2022-05-02 21:17             ` Dan Cross
2022-05-02 23:49               ` George Michaelson
2022-05-03  7:22                 ` Ronald Natalie
2022-05-03  7:40               ` Miod Vallat
2022-05-03  8:03                 ` Ron Natalie
     [not found]               ` <CAEoi9W4eD8AF=FwjMT-KPRfyYgD+qgVvE1u3sBwiovm4=1WWLg@mail.g mail.com>
2022-05-03 12:14                 ` John Foust via TUHS
2022-05-01 20:55 ` Michael Huff
2022-05-03  4:55   ` Jim Carpenter
2022-05-02 15:43 ` Clem Cole
2022-05-02 16:16   ` Bakul Shah
2022-05-02 16:19     ` Bakul Shah
2022-05-02 17:14       ` Clem Cole
2022-05-02 16:29     ` Larry McVoy
2022-05-02 17:42     ` Clem Cole
2022-05-02 17:59       ` Bakul Shah

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=CANCZdfrdp4yGJwum0QDEoPRwCfvVPLe3C0M7Lr3MQ7TsG0BwSg@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=clemc@ccc.com \
    --cc=tuhs@minnie.tuhs.org \
    /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).