The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] Banyan Vines?  Banyan/ePresence dissolves self
Date: Thu, 31 Jan 2008 21:35:51 +1300	[thread overview]
Message-ID: <200801312135.52821.wes.parish@paradise.net.nz> (raw)

I was reading Graklaw for more-of-the-same - boneheaded companies taking on 
productive people with intent to reduce dangerous productivity in favour of 
monopolizing transaction tokens ie, money - and I came across the article on 
some_bright_spark suing some other company for daring to try protecting 
networks from email-borne spam:
http://www.groklaw.net/article.php?story=20080125135544713

Which got me thinking - Banyan Vines was a player back then, and the comments 
mentioned only Novell.  Surely there's something about Banyan's Vines?

I did a google search and found this:

http://www.bizjournals.com/masshightech/stories/2007/12/24/daily7.html?ana=from_rss
Wednesday, December 26, 2007
Liquidating ePresence distributes cash
Mass High Tech: The Journal of New England Technology
<snip>
 
 Framingham's ePresence Inc. reports a plan to distribute cash to its 
shareholders as part of its dissolution plan. 
 The distribution of $3.6 million, or 14 cents per common share, is expected 
to be paid this week to those who were ePresence shareholders as of June 23, 
2004. The distribution, combined with the previous distributions totaling 
$4.15 per share, would return a total $4.29 per share to ePresence 
shareholders, company officials said. 
 EPresence was launched in 1983 as Banyan Systems, selling a network operating 
system and directory. But competitors such as Novell Inc. and Microsoft Corp. 
subsequently moved into that market and Banyan switched focus in 1997. 
 In 2003, ePresence sold it services business to Unisys Corp. for $11.5 
million. In 2004, the company sold its online telephone directory division 
Switchboard Inc. to Bellevue, Wash.-based InfoSpace Inc. for $160 million.
--------------------------------------------------------------------------------------------------------------

Who would one need to get in touch with, to ask about the possibility of 
getting the various obsolete Banyan Vines bits and pieces donated to TUHS?  
(It was based on a Unix kernel, so I would say it - one of the first NOSes to 
have a directory - should be part of the TUHS repository.)

Thanks

Wesley Parish

-- 
Clinersterton beademung, with all of love - RIP James Blish
-----
Gaul is quartered into three halves.  Things which are 
impossible are equal to each other.  Guerrilla 
warfare means up to their monkey tricks. 
Extracts from "Schoolboy Howlers" - the collective wisdom 
of the foolish.
-----
Mau e ki, he aha te mea nui?
You ask, what is the most important thing?
Maku e ki, he tangata, he tangata, he tangata.
I reply, it is people, it is people, it is people.



             reply	other threads:[~2008-01-31  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31  8:35 Wesley Parish [this message]
2008-01-31  8:56 ` Andrew Warkentin
2008-02-04 22:05 Janet Sala

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=200801312135.52821.wes.parish@paradise.net.nz \
    --to=wes.parish@paradise.net.nz \
    /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).