From: patv@monmouth.com (patv@monmouth.com)
Subject: [TUHS] Bell Labs Holmdel site coming down
Date: Wed, 17 May 2006 16:39:31 EST [thread overview]
Message-ID: <200605172139.k4HLdVx5001770@wwws.monmouth.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2543 bytes --]
I have heard some grumblings of TOG possibly releasing CDE as open source,
but have no idea of where that stands. To be perfectly frank, it had a
lot of problems, especially in a 64-bit world. There were too many word
size assumptions, and a very good friend struggled for many, many hours
fixing those problems before it went to DEIL in India for support. It
could probably still benefit from a good �many eyes� developer review and
bug fix session in the hands of open source developers. However, IMHO, it
no longer has any advantage over KDE or Gnome, but, as I said, that is my
opinion.
Personally, I�d love to see OSF1 released open source. There were
experimental x86 and two Itanium versions in various states of completion
floating around DEC/Compaq/HP. I was part of the last Itanium effort
before the HP merger. That one booted to single user before the project
was killed.
OSF1/Digital UNIX/Tru64 UNIX was already branded as UNIX, and it would be
fun to see what would happen to the landscape if a branded UNIX was free.
Unfortunately, too many proprietary licensed pieces of code in the HP
version, especially in System V support, for that to ever happen. Oh well,
we can all dream �
Pat
> On Wed, 17 May 2006, patv at monmouth.com wrote:
>
> > Another loss to the UNIX community that I can personally report was the
> > closing, one year ago this month, of the old DEC Manalpan facility (UNX).
> > This was the home of VAX System V, a large portion of Ultrix, and
> > everything that made up OSF1/Digital UNIX/Tru64 UNIX except for kernel,
> > drivers, and several other components (although I personally did some
> > kernel work on occasion). We did shell and utilities, about 1/2 of X,
> > Motif, CDE, installation, mail, and other parts of the OS that made it
> > useful. If you look at old uucp headers anywhere on usenet, any of the
> > traffic with headers that included systems with "unx" in the name was
> > routed through this facility. I was there from when it was Digital
> > through Compaq and finally HP, almost all the way through to the closing.
>
> It would be nice if CDE were free, the rest is either part of the Heirloom
> project or cloned in some open-source system (e.g., Lesstif). --;
>
> -uso.
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
---------------------------------------------
This message was sent using Monmouth Internet MI-Webmail.
http://www.monmouth.com/
next reply other threads:[~2006-05-17 21:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 21:39 patv [this message]
2006-05-17 23:27 ` Lyrical Nanoha
-- strict thread matches above, loose matches on Subject: below --
2006-05-18 14:34 Michael Sokolov
2006-05-18 2:48 Norman Wilson
2006-05-17 22:40 Michael Sokolov
2006-05-17 22:30 Stuart, Jon
2006-05-17 23:13 ` John Cowan
2006-05-18 1:42 ` Wesley Parish
2006-05-18 8:36 ` Tim Bradshaw
2006-05-19 8:16 ` Wesley Parish
2006-05-19 20:41 ` Tim Bradshaw
2006-05-18 8:50 ` Peter Jeremy
2006-05-18 9:42 ` Wilko Bulte
2006-05-17 19:56 patv
2006-05-17 20:48 ` Lyrical Nanoha
2006-05-17 15:29 tuhs
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=200605172139.k4HLdVx5001770@wwws.monmouth.com \
--to=patv@monmouth.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).