From: John Floren <john@jfloren.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] The PATENTED IBM MULTI-PIPE : the evolution of unix pipes
Date: Fri, 15 Mar 2013 10:28:30 -0700 [thread overview]
Message-ID: <CAL4LZyhUtMxjF9Mk5bRCxROyytcfUPvEaa-M7y4BEmozdS1vNw@mail.gmail.com> (raw)
In-Reply-To: <66202831ed10c42258ff9e60c45d43ea@sphericalharmony.com>
On Fri, Mar 15, 2013 at 10:17 AM, <mycroftiv@sphericalharmony.com> wrote:
> John Floren wrote:
>> I probably didn't read the iosrv and hubfs stuff well enough, but
>> multi-pipes are not like gnu screen--unless hubfs and/or iosrv can
>> do barriers and reduces and I just missed that part?
>
> The connection to screen is really only in usage. Iosrv and Hubfs
> were the result of trying to give myself persistent rc shells in Plan
> 9. Because of the absence of the TTY layer, it seemed like the thing
> to do was to buffer and multiplex each file descriptor of a shell, and
> allow multiple clients to connect to those buffers.
>
> Even though this architecture was created for keeping persistent rc
> shells around, I realized that it was actually a very beautiful
> general purpose extension of the original unix pipes, and could be
> used for a large number of purposes, including cluster processing type
> applications.
>
> So the connection to screen is not "technical" at all - just that the
> main purpose I wrote iosrv/hubfs for (and btw hubfs is vastly superior
> to iosrv for practical use if anyone is interested) was to keep
> persistent rc shells around on remote machines for analogous usage to
> screen.
>
> Anyway, I think multipipes/hubs/pipemuxers are just a good idea for
> Plan 9 (and probably standard unixes too) and that they fit
> beautifully with 9P and the whole system. I'd like to move forward
> with trying to make good Plan 9 software and not have this particular
> little patent kerfuffle turn into anything majorly disruptive.
>
> Ben Kidwell
> "mycroftiv"
>
> -Who would rather go back to trying to explain ANTS and hoping
> that other Plan 9 users would take an interest and explore it.
>
Well, you made it a kerfuffle, and then somebody decided to post it to
HN, so well done that. If you come in saying "Oh look somebody made a
patent but I think this is prior art", expect a kerfuffle. (That's a
good word. Kerfuffle)
Looking through my mail archives, I found a link from Eric that led me
to http://graverobbers.blogspot.com/search/label/brasil which I think
contains the seeds of multi-pipes. Note that these were all posted
prior to your time-traveling expedition.
john
next prev parent reply other threads:[~2013-03-15 17:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 17:17 mycroftiv
2013-03-15 17:28 ` John Floren [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-15 17:41 mycroftiv
2013-03-15 15:31 mycroftiv
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=CAL4LZyhUtMxjF9Mk5bRCxROyytcfUPvEaa-M7y4BEmozdS1vNw@mail.gmail.com \
--to=john@jfloren.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).