9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: mycroftiv@sphericalharmony.com
To: 9fans@9fans.net
Subject: [9fans] The PATENTED IBM MULTI-PIPE : the evolution of unix pipes
Date: Fri, 15 Mar 2013 15:31:43 +0000	[thread overview]
Message-ID: <d723c62ca76edfdf9df48920708a5a9c@sphericalharmony.com> (raw)

Kurt H Maier wrote:
> So what's the real difference between iosrv/hubfs and MULTI-PIPES?
> Is anyone here good enough at translating patentese to code to tell
> what the technical differences are?  The patent even specifically
> mentions 9P.

Well, since I'm trying to deal with this in human way rather than a
legalistic way, I'll just share my honest perspective without any kind
of sarcasm etc.  I didn't really mean to kick any hornet's nests.

Software patents are basically BS. I don't think I "invented" anything
in any software I have written.  At the end of the manpage for hubfs,
I put a big quote from an interview with Ken Thompson where he is
talking about Doug McIlroy's ideas in the 60s and how they were too
complex.

The point I was making was that I perceived hubfs to be a simple way
to implement the ideas that Doug McIlroy had invented - and I don't
think HE should have gotten a patent either!

MULTI-PIPES have a more complicated control interface and I'm sure the
implementation is in every single way more robust and better
engineered than my little 9pfile 9pfs.  When I said I know better than
to disagree with the professional opinion of the IBM lawyers, I meant
it.  I highly doubt any random individual who writes software is going
to accomplish anything arguing with them about who the inventor of an
idea is.  My belief is that Doug McIlroy is the inventor, if anyone.

Before I saw this patent, to whatever extent I knew about multi-pipes
in relation to anything I'd done, I was just happy if there was some
kind of parallel evolution or inspiration or anything between myself
as a hobbyist and the big time pros working on Blue Gene.  Seeing a
patent though makes me feel differently - because I don't think anyone
should be paying IBM for using buffered muxed network transparent
pipes.

Anyway, I meant what I said about how on a personal level I feel
friendly toward everyone on the Blue Gene project and I'd love to have
a positive and not antagonistic relationship with everyone involved in
Plan 9.

-Ben Kidwell "mycroftiv"



             reply	other threads:[~2013-03-15 15:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 15:31 mycroftiv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-15 17:41 mycroftiv
2013-03-15 17:17 mycroftiv
2013-03-15 17:28 ` John Floren
2013-03-15 13:21 mycroftiv
2013-03-15 14:58 ` erik quanstrom
2013-03-15 15:04 ` Kurt H Maier
2013-03-15 15:51   ` hiro
2013-03-15 16:47   ` John Floren
2013-03-15 17:29 ` Bakul Shah
2013-03-15 17:37   ` hiro
2013-03-15 17:46   ` Kurt H Maier
2013-03-15 18:17     ` Bakul Shah
2013-03-15 18:21       ` erik quanstrom
2013-03-15 20:32       ` Charles Forsyth
2013-03-15 19:20     ` Matthew Veety
2013-03-15 19:26       ` Kurt H Maier

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=d723c62ca76edfdf9df48920708a5a9c@sphericalharmony.com \
    --to=mycroftiv@sphericalharmony.com \
    --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).