From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Dynamics between BSD and Linux
Date: Fri, 2 Feb 2018 08:46:15 -0700 [thread overview]
Message-ID: <CANCZdfpFK=2zkRRs4fhrkQbySs6Aaz5rfJ1oF1pnLnTQWs43Ng@mail.gmail.com> (raw)
In-Reply-To: <20180202152904.GG2632@mcvoy.com>
On Fri, Feb 2, 2018 at 8:29 AM, Larry McVoy <lm at mcvoy.com> wrote:
> On Fri, Feb 02, 2018 at 04:07:06PM +0100, Steffen Nurpmeso wrote:
> > Larry McVoy <lm at mcvoy.com> wrote:
> > ...
> > |Here's a personal example of the differences. When I was looking at
> > |working with Netflix I emailed McKuisik to ask him about some UFS
> stuff.
> > |And this was me, I know Kirk, I've been to his house, had wine with him
> > |and Eric. No reply. Ok, I'm old and washed up, I get it.
> >
> > Even though i have read your message as a maybe even ironic
> > sharpening, i feel i have to step in and find this hard to
> > believe. Maybe there have been technical reasons.
>
> I didn't really mean to shine a light on Kirk, I like Kirk, I'm one of
> the few people besides Kirk to work on UFS.
>
There's about a dozen. They talk. Even Kirk. But you can't expect people
whose time is their own to reply to you on a short timeline. It's not a
reasonable expectation.
That said, I stand by what I said, it's what happened. And it seems to
> be reflective of the BSD "culture", it appears to be the opposite of
> inclusive. Disappointing.
>
I've had a completely different experience. But when people don't answer, I
ask again. I just just go off and sulk that they were mean to me.
> Linux has a very different culture. Everyone is welcome and they
> maintain sanity largely via Linus willing to call a spade a spade.
> He doesn't suffer fools but he's willing to engage with anyone until
> they prove themselves to be a fool and nothing more.
>
Sure, if you love a toxic culture that's hard to break through the machismo
when the anointed ones are wrong....
Needless to say, I have a completely different perspective and
two-decades-long experience with BSD and its collaboration.
Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180202/98ecc811/attachment.html>
next prev parent reply other threads:[~2018-02-02 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 8:39 Kevin Bowling
2018-02-02 3:44 ` Larry McVoy
2018-02-02 6:11 ` Bakul Shah
2018-02-02 6:29 ` Warner Losh
2018-02-02 6:36 ` George Michaelson
2018-02-02 6:43 ` George Michaelson
2018-02-02 20:10 ` Larry McVoy
2018-02-02 15:07 ` Steffen Nurpmeso
2018-02-02 15:29 ` Larry McVoy
2018-02-02 15:46 ` Warner Losh [this message]
2018-02-02 17:00 ` Theodore Ts'o
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='CANCZdfpFK=2zkRRs4fhrkQbySs6Aaz5rfJ1oF1pnLnTQWs43Ng@mail.gmail.com' \
--to=imp@bsdimp.com \
/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).