Talk:Tru64 UNIX

Latest comment: 5 years ago by Letdorf in topic Split into OSF/1 and Tru64 Unix?

OSF/1 codebase?

edit

What was the codebase used for OSF/1? Was it SVR3, BSD, some mixture? The article says:

After the OSF gave up on OSF/1, DEC renamed OSF/1 AXP to Digital UNIX and made it the main operating system for the company's Alpha processors. It was 64-bit and retained the basis on the Mach kernel but with components from Berkeley Software Distribution, System V, and other sources.

Were these BSD and SysV components already present in OSF/1, were they imported directly or from Ultrix? Qwertyus 18:24, 13 April 2006 (UTC)Reply

The code base for OSF/1 was 4.3-Reno from Berkeley, Mach 2.5 from MIT, and System V Release 2 via IBM from AT&T. There was no Ultrix code in the original code base. 98.197.222.98 11:26, 22 August 2007 (UTC)Reply

Hybrid kernel?

edit

Another question: could the OSF/1 kernel rightly be called a hybrid kernel? Qwertyus 16:01, 18 April 2006 (UTC)Reply

It's debated whether Mach is actually a Microkernel to begin with, so this is not necessarily a meaningful question. :) -- 98.197.222.98 11:40, 22 August 2007 (UTC)Reply

POSIX compatibility holes?

edit

I'd love to see references to the POSIX compatibility holes. From what I've seen, Tru64 is usually more compatible than older commercial *NIX's! —The preceding unsigned comment was added by 209.63.53.142 (talkcontribs) .

Version table

edit

I added the bare bones of a version table, in the spirit of the release-by-release info on the Solaris or HP-UX pages. I have not found release notes for versions before 4.0 anywhere online, so for dates on the older releases, I looked at posts in comp.unix.osf.osf1. Release notes for the older versions would improve these dates. Also, it would probably be good to list important "letter" releases like 4.0d, etc. I hope that with some more eyes on the table it can be made more useful. JFinigan (talk) 18:17, 18 May 2009 (UTC)Reply

4.0 and older release dates are given in the book "Digital UNIX System Administrator's Guide" JFinigan —Preceding undated comment added 05:15, 19 October 2009 (UTC).Reply

Split into OSF/1 and Tru64 Unix?

edit

Most of the content of this page is about OSF/1 in general, not just Digital's version of it called Tru64 Unix. I plan to create a new article, OSF/1, for the general information about OSF/1, leaving Tru64 Unix for the Digital implementations (including Digital Unix, DEC OSF/1). There is also material in the Open Software Foundation article that I'll move to OSF/1. Any objections? --Macrakis (talk) 15:44, 4 September 2012 (UTC)Reply

Sounds reasonable. Letdorf (talk) 22:42, 4 September 2012 (UTC).Reply
...and, finally, it's done! Letdorf (talk) 23:32, 11 February 2019 (UTC)Reply
edit

Hello fellow Wikipedians,

I have just modified one external link on Tru64 UNIX. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 05:58, 24 May 2017 (UTC)Reply