Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: TUHS main list <coff@minnie.tuhs.org>, Josh Good <pepe@naleco.com>
Subject: Re: [COFF] [TUHS] Zombified SCO comes back from the dead, brings trial back to life against IBM
Date: Fri, 2 Apr 2021 10:54:18 -0700
Message-ID: <20210402175418.GH8268@mcvoy.com> (raw)
In-Reply-To: <YGdZVFUsErA8Lwd+@mit.edu>

On Fri, Apr 02, 2021 at 01:50:12PM -0400, Theodore Ts'o wrote:
> On Fri, Apr 02, 2021 at 09:11:47AM -0700, Larry McVoy wrote:
> > > Long before Linus released Linux into the wild in 1990 for the >>386<< much
> > > less any other ISA, IBM had been shipping as a product AIX/370 (and AIX/PS2
> > > for the 386); which we developed at Locus for them.  The user-space was
> > > mostly System V, the kernel was based on BSD (4.1 originally) pluis a great
> > > deal of customization, including of course the Locus OS work, which IBM
> > > called TCF - the transparent computing facility.  It was very cool you
> > > could cluster 370s and PS/2 and from >>any<< node run a program of either
> > > ISA.   It has been well discussed in this forum, previously.
> > 
> > It's really a shame that TCF didn't get more widespread usage/traction.
> > That's exactly what BitMover wanted to do, I wanted to scale small cheap
> > SMPs in a cluster with a TCF layer on it.  I gave some talks about it,
> > it obviously went nowhere but might have if we had TCF as a starting
> > point.  TCF was cool.
> 
> (Moving this to COFF...)
> 
> Out of curiousity, how was TCF different or similar to Mosix?

The thing I remember most about TCF is that it virtualized struct
proc, so process pointers were like vnodes and you could move a
process to a different node in the cluster and ps still saw it
and could dig info out of the remote kernel.
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

      reply	other threads:[~2021-04-02 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210401145025.GA1202@naleco.com>
     [not found] ` <CANCZdfoa6WiKWH5rk_kU0dj_C5QH=LLhQbNsm0ni6ms+Fu3f+A@mail.gmail.com>
     [not found]   ` <CACNPpeafZb=Ty_AuT2m_GBDQwzMzWMabKUhqgwJXH4zvbXY6VA@mail.gmail.com>
     [not found]     ` <CAC20D2OyBP9ThQ4mY4ACLsvFapCX912k=e1VSMgX3AocqDY+OA@mail.gmail.com>
     [not found]       ` <20210402161147.GG8268@mcvoy.com>
2021-04-02 17:50         ` Theodore Ts'o
2021-04-02 17:54           ` Larry McVoy [this message]

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=20210402175418.GH8268@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=coff@minnie.tuhs.org \
    --cc=pepe@naleco.com \
    --cc=tytso@mit.edu \
    /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

Computer Old Farts Forum

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.vuxu.org/coff

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 coff coff/ https://inbox.vuxu.org/coff \
		coff@minnie.tuhs.org
	public-inbox-index coff

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.coff


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git