Slashdot Mirror


HP Plots New Courses with HP-UX/Tru64

Uberhacker.Com writes "HP has given up on trying to bring key parts of Compaq/DEC's Tru64 operating system into HP-UX. They had once planned for the Tru64 goodies to arrive this year and made a big deal of this quick turnaround when it first acquired Compaq. Ironically, HP also announced today that it is expanding its Alpha RetainTrust program for Tru64 UNIX customers." The linked article also notes that HP has decided that it will proceed forward with purchasing some of the technology from Veritas.

3 of 133 comments (clear)

  1. Two big piles of stuff on top of standard Unix by shoppa · · Score: 4, Interesting
    Both Tru64 (or whatever it's called this month, I've been using it for over a decade now, so I still tend to call it OSF/1, and occasionally slip into Digital Unix) and HP-UX have a lot of layers added on over their core of "standard" Unix. (Others will go into great detail about how these are neither "standard" Unix cores but some variant of some variant of some variant of some microkernel but nobody cares anymore, that is really so early 90's.) They both have extensive system management GUI's, of course not compatible with each other, as well as fundamentally different "clustering" support. (Note my quotes, whenever you talk about any other product's clustering you always denigrate it by quoting that word.) To mix the two together is a holy living nightmare.

    Most sites that are migrating are going away from both as fast as they can. There are a small fraction that truly depend on clustering or other proprietary feature, unfortunately everybody is holding on tenaciously to said features despite the fact that they really do 99% of the applications no good. And most commercial applications have been somehow hoodwinked into the proprietary hooks.

  2. Re:Perhaps I'm naive by GreatBallsOfFire · · Score: 4, Interesting

    They're not based on the same code. Tru64 came from OSF/1 which was a clean room rewrite of Unix, back when AT&T was the evil OS overlord. It was written by IBM, HP and DEC. Only Digital stuck with it, and renamed it twice: OSF/1 -> Digital UNIX -> [Digital|Compaq|HP] Tru64. And that's the point, that they are so incompatible that the task was monumental in the way HP approached it.

    Enough said.

  3. Re:Aargh! This is really frustrating! by bsdnazz · · Score: 4, Interesting

    Having first used VAXClusters in 1987 eveything else I've come across seems toy in comparison. A VAXCluster gave us disk that worked just like a local disk but was shared across the cluster. No one VAX 'owned' it (no LAVC here!). It's peer to peer disk sharing with all the lockin problems sorted. We ran a navigational database (VAX RMS) over the VAXCluster with 3 VAXes and hundreds of users.

    If VAXCluster technology is lost then it's a tragic waste of a good technology.