Slashdot Mirror


Ransom Love on United Linux, SCO Unix

tit4tat writes: "Caldera chief executive Ransom Love confessed to ZDNet UK that "[Caldera is] not moving Open Unix [i.e., the former SCO Unix] onto Intel's 64-bit platform...." I suspected that Caldera bought SCO just to kill SCO Unix, even though they denied it at the time. Now, the first Unix I ever knew is about to be no more. "

66 of 246 comments (clear)

  1. SCO is gone by codeguy007 · · Score: 4, Informative

    Well considering that SCO sucked why would they ever want to port it to IA-64. No they didn't by SCO to kill it. It was going to die anyway. They bought it for the Intellectual Property and some of the application software that SCO had developed. Also I understand they were interested in SCO's support division.

  2. title by Dionysus · · Score: 5, Funny

    For some reason I read it as Random Love Unites Linux...

    --
    Je ne parle pas francais.
    1. Re:title by scotch · · Score: 2
      Never trust anything (or anyone) called "Random Love" - you'll only have your heart broken.

      --
      XML causes global warming.
    2. Re:title by sporty · · Score: 2

      Random Love Unties Linux?

      Yslexdexics of the world untie!

      --

      -
      ping -f 255.255.255.255 # if only

  3. good riddance by Roadmaster · · Score: 4, Insightful

    At long last, and hopefully every single one of my sco-using customers will finally see a reason to migrate from that.

    SCO has got to be the single ugliest, un-friendliest, most incomplete and failure-prone unix i've ever used. I was called in to solve problems even the dedicated admins couldn't, and they always turned out to be windows-like, unexplainable glitches that took lots of kludging around to fix.

    1. Re:good riddance by Doktor+Memory · · Score: 3, Interesting

      You need to learn an OS to be able to use it and understand it well.

      Indeed you do. For instance, want to know how to completely kill a SCO system (and I mean "restore from installation media" kill) with a single command?

      mv /opt /opt.old

      Why, might a sane person ask, would renaming /opt (which we tend to assume stands for optional for some strange reason like that it's defined as such by the SVR4 spec) completely destroy a running system? Well, let's just say that SCO's idea of what comprises "optional" system components includes things like "ld.so".

      I've learned many things about SCO in my time. First among them is that it will not be missed.

      --

      News for Nerds. Stuff that Matters? Like hell.

  4. Caldera's Not Killing Off SCO! by BlueLines · · Score: 5, Informative

    *sigh*

    (from the article)

    So OpenUnix will continue in parallel to OpenLinux?
    Yes. Open Unix could well keep going in parallel to OpenLinux. We are not moving Open Unix onto Intel's 64-bit platform, but IA32 will be around for a long time yet.


    Please read the articles before you post them....

    -BlueLines

    --
    --BlueLines "The cost of living hasn't affected it's popularity." -anonymous
    1. Re:Caldera's Not Killing Off SCO! by outlander78 · · Score: 2, Insightful
      Indeed. There is no way a start-up could afford to buy an established competitor just to remove them from the market. That's what competition is for.

      Caldera has limited resources. They likely can't afford to pay developers to port an operating system to IA64, so that keeps OpenUNIX on IA32. Meanwhile, Linux is being ported to IA64 by open-source developers, so Caldera gets that move for the cost of testing, not developing.

      Relax! I doubt any conspiracy is lurking here.

      --
      cheers,
      Andrew
  5. SCO should die by juan2074 · · Score: 5, Funny

    the first Unix I ever knew
    more like, the worst Unix I ever knew

    1. Re:SCO should die by einhverfr · · Score: 2

      Hmm...

      SCO routinely scores low with sysadmins in every article I have ever read. (Remember, it originally was a Microsoft product :P)

      But Caldera used to be one of the great market leaders in Linux, and they are quickly falling from that position (per-seat licensing often kills their market share, and any Linux vendor whose CEO states that the GPL is bad for business has more problems that I can handle).

      I guess birds of a feather flock together.

      --

      LedgerSMB: Open source Accounting/ERP
  6. Why Should They? by DA_MAN_DA_MYTH · · Score: 2

    I mean why should they spend money porting SCO Unix to the IA-64, instead they should spend that effort porting United Linux to the IA-64, plus they have the capital behind them to do it with SuSe, Turbo and Connectiva behind them now. My question is are the 4 companies going to become one now?

    --
    "It takes many nails to build a crib, but one screw to fill it."
  7. ScoAdmin by Da_man · · Score: 4, Interesting

    I have never used SCO Unix but I have a lot of experience with OpenServer. IMHO "scoadmin", the tool administring everything on a sco box, was a work of art.

    The transparent (to the user) method it had for Kernel compiles is something I would love to see Linux do. Not that I haven't cut a few Linux kernels myself, but it was very neat.

    Another great thing was the software installer, and driver support from major manufacturers. Download drivers from Compaq, go to scoadmin/software, add the new software and it would recompile the kernel if needed. Sweet!!

    1. Re:ScoAdmin by cgleba · · Score: 2

      The proper term is "re-linking" the kernel. SCO did not give you the source to the Openserver kernel so therefore you can not compile it.

      The reason why the util is so neat is that you have to re-link OpenServer very often -- it does not have kmalloc (meaning you constantly had to 'tune' different buffers) and it does not support loadable modules.

      BTW I am pretty sure that OpenServer is ported to IA64. . .with that in mind (ahem) I would look at it more as Caldera not counting on the IA64 then Caldera not counting on Unixware.

  8. SCO is dead by mongoks · · Score: 3, Interesting

    Why is this such a shock? Who needs another x86-based Unix at this point? The only thing that kept SCO alive was the system vendors who needed to be able to run on cheap hardware but didn't want to use a "free" OS.

  9. Why I will never use United Linux... by bogie · · Score: 4, Insightful

    Ransom Love

    " The only difference is that the UnitedLinux binaries will not freely distributed. People will be able to download the source code and compile their own binaries, but they will not be able to use the UnitedLinux brand"

    Please people now is the time to rally behind the truely free distros out there. If your going to use linux use Redhat,Debian,Gentoo,Slackware,Mandrake, or any of the other fine binary/iso friendly distros out there.

    While I applaud standards I don't think this is the way to go about it.

    --
    If you wanna get rich, you know that payback is a bitch
    1. Re:Why I will never use United Linux... by Phexro · · Score: 3, Informative

      Uh, this is pretty common practice. For example, you can compile all the source that makes up Red Hat and distribute binaries of it, you just can't call it "Red Hat".

      I assume that they made this decision to try and increase their sales of official boxed products, versus having everyone download a free ISO. There's nothing to stop you from compiling the whole system, building an ISO, and distributing it under the name "Divided Linux".

    2. Re:Why I will never use United Linux... by erat · · Score: 3, Insightful

      Excuse me, but what exactly is your beef?

      All you're restricted from using is the brand. This is a problem? I guess you also can't sleep at night because Linux can't use the UNIX trademark?

      Who cares?? Compile the sources and say they're "UnitedLinux compatible". As long as you don't say "compliant" (which implies passing the certification tests) everything should be peachy.

      You're reading drama into a situation that has none. Promote your favorite distros as much as you want, but don't do so at the unnecessary expense of others, especially when those others are putting forth an honest effort to help Linux.

    3. Re:Why I will never use United Linux... by Jason+Earl · · Score: 4, Insightful

      Exactly right. This is nothing more than yet another wacky hare-brained Caldera scheme to get people to pay more for Free Software without having to actually do more. United Linux is nothing more than a binary version of the LSB plus some additional, fairly basic, packages. Each of the distributions that is participating will have these packages installed and available. Clearly this is not a revolutionary idea. Caldera, and their new compadres are trying to set this package up to be the "new standard" because they know that otherwise folks will continue to use RedHat as the de-facto standard.

      However, Caldera continues to overlook the reason that RedHat became the de-facto standard. That reason is simple. They wrote cool software and gave it away. Because of RedHat's policy of writing GPLed software, their software became the standard and their technology has been adopted by pretty much every other distribution (in one form or another). By and large Linux users, and Linux customers in general, aren't interested in being locked into a single distribution. Nor are they interested in paying per seat licensing fees. Apparently they also aren't interested in purchasing support from companies that sell distributions that rely on such tactics.

      You would think that years of being beaten over the head with a clue stick by the folks at RedHat would have knocked some sense into Mr. Love, but apparently some folks are just amazingly slow learners.

    4. Re:Why I will never use United Linux... by Arandir · · Score: 2, Funny

      How is this different from any other Linux distro that has a trademark? You can't build Redhat from sources, burn it onto a CD, and call it "Redhat". You can't do it with Mandrake. You can't do it with Slackware. I'm not as familiar with the others, but Slackware has specific rules about calling a CD "Slackware". You have to have your CD laid out in a certain manner with certain files, etc.

      You can of course call those CD's "Redhat Derived", or "Unofficial Mandrake Burnings", or "Remarkable Slackware-Like Distro".

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    5. Re:Why I will never use United Linux... by Tony+Shepps · · Score: 2

      Okay, so there isn't a moral "free speech" issue. IMO there is still a free beer issue. Free ISOs can be a real boon when you're trying to get things done... especially on a budget and in a hurry.

    6. Re:Why I will never use United Linux... by erat · · Score: 2

      It doesn't seem that anything would stop you from doing that, nor do the UL folks give a rat's patootie if you do. Just don't call it "United Linux". I thought this was made quite clear in the conference call (perhaps lots of folks that have been posting didn't bother to call in. That's understandable. If the Linux media has any credibility whatsoever this will all be clarified in the various news publications, online or otherwise).

      Seems simple to me.

    7. Re:Why I will never use United Linux... by Malcontent · · Score: 2

      IIRC things like RPM and Webmin were written by Caldera and given away. I am sure there are more.

      --

      War is necrophilia.

    8. Re:Why I will never use United Linux... by _Sprocket_ · · Score: 2
      Caldera bought Webmin and changed its license to BSD (I believe it was free for Linux only, but I forget the exact details). One would think Caldera continued to develop Webmin at that point, but I'm not sure if they released their work back to the public (with Ransom Love's comments in the past, it is really questionable). Redhat certainly didn't write Webmin though.


      RPM. What do you suppose that stands for? Not Caldera Package Manager, for sure. Could it be... Redhat?

    9. Re:Why I will never use United Linux... by _Sprocket_ · · Score: 2


      However, Caldera continues to overlook the reason that RedHat became the de-facto standard. That reason is simple. They wrote cool software and gave it away.


      Lets not forget that Redhat was the first strong push for a commercial Linux distribution. Redhat wasn't just for hobbiests and covert server projects. They went after the IT Industry as mainstream product. Hiring leaders in various Linux development projects and funding further development is a bonus (and certainly worthy of praise).


      Ransom Love made one good point in the interview. Linux players have to come up with ways to differentiate themselves. This, despite the fact that they all pretty much work with the same pool of software. I have a hard time believing that Redhat wasn't included in the United Linux front because of time constraints. Redhat doesn't need United Linux because Redhat IS the competition.


      So how does Caldera and other United Linux players differentiate themselves from the competition (much less each other)? They have to offer something Redhat doesn't. Let's look at some of their points:

      • Standards - Redhat is already a defacto business standard. There's been talk of the LSB and Redhat has said they would be releasing a distro based on it. Soon. Perhapse sooner now. United Linux might be able to claim a truer standard than Redhat. Time will tell.
      • Software - same pool of software for both Redhat and United Linux. Free or proprietary.
      • Support - Caldera (and I suppose other United Linux offerings) has mentioned 12 months of support with their software package. Redhat comes with limited support on the boxed set, but also sells support packages no matter how you got your distribution.
      • Price - United Linux will be targeted at the enterprise with an enterprise price tag. Redhat is available with enterprise features and price tag. It is available at a desktop price. It is available at a "Pink Tie" price from Cheapbytes. It can be downloaded from any one of a worldwide network of mirrors.


      Caldera and its United Linux brethen look like they're running in to the same problem they had before. This tactic provides little differentiation. And if United Linux members hold to the same marketing plan that Ransom Love mentiones - holding on to binaries - they may find themselves at a loss. Imagine the conversation between management and their IT techies.


      "Uhhhh. Yea. We've decided to go ahead with this Linux thing. But there is so much choice, we're not sure what to consider. There seems to be two solid players here: Redhat and United Linux. Which one will work?"


      "Redhat. I downloaded the latest version last week and put it up on our dev machine. Its been solid - a lot better then the dot-oh release. And I've been running the last release and development updates for the last few months. Its good."


      Management nods their heads and goes back to look up support contracts with Redhat.

    10. Re:Why I will never use United Linux... by Znork · · Score: 3, Insightful

      My guess: because there are dozens of other distributions that do distribute ISO images for free.

      I wont be using (or even trying) united linux either. I'll stick with Redhat and Debian for home use and Redhat for corporate use. The price of buing another Linux distribution is small, but with corporate purchasing involved, the difference between Redhat and, for example, SuSE isnt a few bucks, it's several hundred dollars worth of paperwork time and several weeks to go through processing. Unless I pay for it myself.

      So, give me a complete ISO download to speed up implementation projects and I can dump the support contract through purchasing, without the red tape that comes automatically with an incoming pricetag to a large corporation.

      It's not a question of price. It's completely a question of convenience, and if it isnt convenient it's not what's going to get installed.

    11. Re:Why I will never use United Linux... by Mr.+Fred+Smoothie · · Score: 2

      That is NOT true. They ask the techs for their opinions, and then completely ignore them.

      --

    12. Re:Why I will never use United Linux... by Jason+Earl · · Score: 2

      Either way RedHat gets the contract. After all, RedHat already has the traction with the suits. In a lot of cases, especially skunkworks projects that later become official projects, the techs end up with a lot of say. The fact that RedHat is freely available to test with is a big deal.

    13. Re:Why I will never use United Linux... by _Sprocket_ · · Score: 2


      As someone who's worked for a Fortune 10 ("enterprise") company, let me assure you of one thing:


      Management never consults their IT techies.


      Yes and no. I've been in environments when it was a pleasant shock for management to consult their technical help. And I've worked for a major corp with a strong tech-culture and had to help mop up the mess when a non-technical business unit made infrastructure decissions on a technical project.
  10. Is it worth mentioning that by Scareduck · · Score: 3, Informative

    ... SCO sucked? It was late to market with every major improvement of BSD, had obnoxious licensing restrictions enforced by code (which was easily overridable -- just drop in a Linux-derived /bin/login with some obvious patches), and did its best to be absolutely unusable as hell at all times. The only way to fix it without Linux was to install the unsupported Skunkware CD, which made life tolerable, but never fun. SCO's dead? Well, good riddance, say I. (Oh, and did I mention it derived from Microsoft's Xenix? All the more reason to stake the bugger.)

    --

    Dog is my co-pilot.

  11. Sad, but I can't say it's unwarranted by marian · · Score: 3, Interesting

    My own experiences with SCO have all been awful. Having been forced to install it in order to qualify some products with it for a customer, it was a nightmare. The documentation is bad enough that it makes life more difficult that if it wasn't there in the first place. The people at SCO were universally unhelpful, even when we were contacting them to BUY their product. It was a disaster and I can't say I'm sorry to see it go.

    --
    "Suppose you were an idiot..... And suppose you were a member of Congress... But I repeate myself."
  12. Remember trying to port Unix software to SCO? by Anonymous Coward · · Score: 2, Interesting

    Remember trying to get standard Unix source code to compile under SCO? Remember dinking with the makefiles, the oddball compiler flags, and non-standard libraries? I sure do. I remember how much I hated SCO and longed for a real Unix. The SCO compiler was closer to Microsoft QuickC (it was an MS compiler!) than it was to ATT cc. It was a royal pain in the ass to use, and I do not hold out nostalgia for those days of pain.

  13. Releasing only the source code? by Shisha · · Score: 3, Interesting

    In the article it says, that they will only release the source code, but that they will sell the binary distributuins. I guess that means no more downloading of ISO installation images.

    I'm wondering, though, what would they do if someone just decided to download the source code (I guess SRPMS), compile them and the install program and bang it all on a install CD?

    Apart from that I like the United Linux idea. The guy has a point about not competing in an area where there's no differentiator between the different distributions. I mean Apache will still be Apache, Squid will be Squid and Postfix..., you get the idea, no matter who packages it (I know that they sometimes apply extra patches, but on the whole, if it's important then all will have it).

  14. Re:Good riddens by Anonymous Coward · · Score: 2, Funny

    Maybe it was your poor grammar and inability to spell that caused your navigational woes.

  15. Open Source? by comcn · · Score: 3, Interesting

    So UnitedLinux will remain an open-source project?

    Absolutely. The only difference is that the UnitedLinux binaries will not freely distributed. People will be able to download the source code and compile their own binaries, but they will not be able to use the UnitedLinux brand.

    ...and...

    Caldera will provide the product through its reseller channel; one problem that resellers currently face is that Linux is free. This way we give them more of a profit motive to sell Linux, because by adopting UnitedLinux they can generate more revenue.

    Huh? So anyone can download the source and compile, (can't call it UnitedLinux, no problem), but you have to buy the binaries (no problem). Doesn't their business model fall apart when people start burning copies of the binary CDs for their friends?

    This is, of course, allowed by the GPL, which most of UnitedGNU/Linux will be licenced under, I assume.

    1. Re:Open Source? by Phexro · · Score: 3, Interesting

      It sounds like they are just raising the barrier to entry. If you want to download the source & build your own copy, go right ahead. But you already have to have Linux (possibly some othe *nix with a cross-compiler) installed, as well as the ability to compile all those packages. And I'd be surprised if they released tools that made it easy to build the binary installation CDs.

      Of course, anyone who already has a Linux box and the ability to compile all that source probably is going to be running something else already, and won't be inclined to switch. Besides, if you want to compile all that crap, why not just run Gentoo, LFS, or *BSD?

    2. Re:Open Source? by _Sprocket_ · · Score: 2


      It sounds like they are just raising the barrier to entry.


      Or they're simply creating a market for Cheapbytes' new offering right next to "Pink Tie Linux" - "Untied Linux".
    3. Re:Open Source? by fanatic · · Score: 2

      Doesn't their business model fall apart

      Isn't this what Suse does now? My recollection is there's no way to download, for no money, a Suse ISO, at least no way that Suse sanctions. Since I don't want to tray and download 8 zillion tarballs and compile them all (many dependent on other things being compiled/installed first), if I wanted to run this version, I'd buy the box set.

      Of course, I just download Redhat, so your basic point may be right on, after all.

      --
      "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody
  16. No Weeping here. by LowellPorter · · Score: 4, Informative

    The wholesale company I work for used SCO Unix for 12 years. Our customers would dial into it with our windows software to order product. The last few years was a real pain in the butt. SCO Unix didn't have many device drivers, was hard to install even with the recommended hardware, and crashed too often.
    Four years ago when I started working for the company, I recommended Linux. My boss didn't want to use it because at the time there were no companies that had decent support. Last year we finally switched to Red Hat. They have decent support. The only big problem with RH is being able to install from a backup tape. SCO unix had utilities for this that worked well. With Linux this is much more difficult.
    We have been more than satisfied since the switch to Red hat.
    Good Riddance to SCO. It was good at one point, but they let it fall to peices.

  17. No room for SCO by brsmith4 · · Score: 2, Interesting

    There are too many other projects out there right now for Caldera to be messing around with SCO. I think its attention should be on this United Linux thing (tacky name btw). Get that running on IA64 with enterprise features and reliability. Give SCO to the OSS developers that may want to borrow a few ideas. In addition, what does caldera have to gain from continuing work on an OS which is being replaced by more competent, open sourced equivalents (not quite equivalent)? I think it would help them to support the platform (for those unfortunate souls still clung to it) financially, but its time to phase it out. As for 'United Linux', I think I will keep my box 'United' with a clean copy of slack.

  18. Re:Kill, Kill, Kill, Kill by nomadic · · Score: 2

    Why on earth would a small player buy another small player just to get rid of a little competition? It's like a small hardware store buying another small hardware store to put them out of business, even though both stores are next to Home Depot and business already sucks.

  19. That's now why they bought SCO by sterno · · Score: 2

    I suspected that Caldera bought SCO just to kill SCO Unix, even though they denied it at the time.

    Actually that would be silly for them to do since SCO was already dieing. What they did was buy a company that gave them a base of customers who wanted to run Unix on x86. Furthermore they got access to any technology that SCO had developed. So to suggest they were just trying to off them seems simplistic. If they wanted to get rid of them, why would they still be offering upgrades?

    --
    This sig has been temporarily disconnected or is no longer in service
  20. Bye bye, won't miss ya by Linux_ho · · Score: 2

    I always had the feeling that SCO actually stood for "Symlinks, can't overdo". Then the engineers went on a mad spree to prove that statement incorrect.

    Half or more of the files on the systems I had were symlinked by default to something like /var/sys/SCO/install/SCO5432/HJ5678RTYrftyfgF 5w/etc/bin/opt/suck

    --
    include $sig;
    1;
  21. Re:LINUX FUCKING SUCKS by brsmith4 · · Score: 3, Informative

    You aren't using a 'fucking' winmodem, are you? It takes no time at all to get it working if you are using the correct hardware. Just a thought.

    *desperately desires karma*

  22. Most people will miss this interesting footnote by binaryDigit · · Score: 2

    If/when Caldera drives a stake through the heart of SCO Unix, it will bring an end to what was a very interesting journey for Unix in general. The trail of this version of Unix back to it's origin really strikes at the heart of where *ix is at this point in time. Going back to AT&T and Sun and the OSF (DEC/IBM/et al). Those of us who are old timers will silently mourn the day when it does pass, as it will represent a passing of a generation gone by.

    sigh

    1. Re:Most people will miss this interesting footnote by buckeyeguy · · Score: 3, Insightful

      Yeah, but having done the SVR3 generation of Unix (incl. older Dynix/PTX for Unisys platforms, egaaaaddds), it's better to look back and say "wow, I'm glad I don't have to deal with the quirks anymore". Or the days where making it Internet ready meant you had to hack somebody's BSD sockets package to get things connected... hehe, when 'networking' meant UUCP. Those are good old days I can do without.

      --
      I'd have a personalized plate on my car, but "toxic bachelor" won't fit into 7 letters.
  23. United Linux. Join the WAR on Terrori-MS-ism. by Ken+Broadfoot · · Score: 2


    United Linux: If you aren't with us your with the Terrori-MS-sists.

    It is either United Linux or those guys.

    ( Avoid those peace loving RedHatters... )

    *wink*

    --
    Bitcoin pyramid: Join here: http://www.bitcoinpyramid.com/r/1427 it's FREE!
  24. ransom note by jeffehobbs · · Score: 5, Funny


    wE hAVe YoUR UniX. PlaCE tWEnty
    THOusaNd DolLarS IN UnMArkeD
    hUNdreD DollaR BiLLs in OuR
    PaypAL AccouNT By JuNE 1St
    or wE WiLL kiLL -9 IT.

    ~jeff

  25. Not well known by PD · · Score: 2, Interesting

    It's a little known fact that Sun Microsystems considered using SCO Xenix on their systems before deciding the write their own. The reason they wrote their own was that their main competitor, Apollo, had a fully System 7 compliant UNIX implementation, and DEC was rumored to be releasing that as well on their VAX hardware. Sun decided thta Xenix wasn't UNIX, so they wrote their own.

    True story.

    1. Re:Not well known by edhall · · Score: 5, Informative

      It's not well known, because it isn't true.

      Sun's OS derived directly from BSD. One of Sun's founders, Bill Joy (now their Chief Scientist), was one of the primary developers of BSD and one of the people responsible for getting BSD to run on the 68000 (which was the processor used in the first Suns).

      At the time, Apollo didn't even run Unix, but rather their own OS named "Domain." To compete, Apollo modified Domain to support a Unix emulation (including a switching mechanism based on conditional symlinks). Domain didn't die until HP bought Apollo, though I believe they did ultimately port native Unix to Apollos just before then.

      -Ed
  26. Love = Smoke and Mirrors by reaper20 · · Score: 2

    The issue is not to compete with Red Hat but to look at how we can grow Linux on a worldwide basis.

    Nice try to play up to the Linux community Mr. Love. Caldera buys SCO and whatever community spirit was with it went away, Here's what Love really should have said:

    "Well, considering my big cakehole has pissed away any chance at the Linux community ever respecting me or my company, I have decided to gather the other distributions, in the spirit of 'unifying Linux for our customers' bring Linux into the next decade. Oh, and since I have no idea how OSS works (lost my copy of ESRs book), we'll make the distribution of the binaries illegal, because damnit, Red Hat keeps GPLing all their software, and we just can't have that."

    Face it Love, Red Hat is successful because it caters to business needs, and CONTINUTES to GPL it's products. You're anti-OSS views are the reason no one wants to use Caldera. If you take from the community, you better give back.

    Don't blame Redhat because you've made a poor investment in a proprietary Unix company. Sucks that SuSE is stuck with these guys.

  27. Re:Dead Operating System collection by buckeyeguy · · Score: 2

    Interesting idea... don't think you'll ever find a CP/M or Xenix CD, but I could be wrong. Back then, all they put on CD was large shareware collections (PC-SIG, etc.) Wasn't much need when the OS of the day could fit on a 360K floppy. So unless you stretch your scope to early Windows and NetWare versions, not sure what more you would find out there on CD. Old Slackware, maybe? ;)

    --
    I'd have a personalized plate on my car, but "toxic bachelor" won't fit into 7 letters.
  28. My first time by Ratbert42 · · Score: 3, Interesting

    Now, the first Unix I ever knew is about to be no more.

    Ironically, the first Unix I ever used was Microsoft Xenix on the 68000 Tandy.

    1. Re:My first time by Arker · · Score: 2

      Just in case you didn't realise it, that MicroSoft Xenix is actually the same thing as SCO Unix (well, if it carried the Xenix name it was an earlier version, but the same codeline, the same unix.) SCO was Microsofts outsourcer - MS didn't actually write Xenix, they just bought the license and hired SCO to do it. Eventually MS lost interest in Xenix, so SCO bought the license and renamed it SCO Unix...

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    2. Re:My first time by RocketJeff · · Score: 2

      Nope, as others have said previously, SCO Unix was based on the AT&T source (which is why they could brand it as Unix reather then Xenix). It was a different source base and development continued on the Xenix line in parallel for a while afterwards.

    3. Re:My first time by Arker · · Score: 2

      Not quite true. Xenix was based on the AT&T source - the SysIII source. AT&T didn't license the Unix name at the time, just the code - that's why it was called Xenix instead of MS Unix to begin with. SCO updated it with Berkeley components, SysV compatibility, and so forth.

      The part you are correct on, however, is that SCO Unix reflects a new (in '89) license from AT&T, which included rights to the name Unix as well as the actual SysV code.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
  29. Re:SCO is gone - Huh? by foonf · · Score: 2
    Xenix which was an M$ bastardized offshoot was a bit unstable, but worked just fine.


    Not quite. What became SCO developed Xenix along with Microsoft. Microsoft eventually lost interest (although into the early nineties there was a port of MS Word for SCO Unix) and the rights to the whole thing came to SCO, in exchange for some royalties of course. SCO Open Server (and Open Desktop, the deceased client version), the older and cruftier of SCO's Unices, is the direct descendant of Xenix. UnixWare (now Open Unix I guess) was originally developed by Novell, and is a more direct branch from the AT&T source.
    --

    "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
  30. Re:OpenServer's days were numbered anyway by foonf · · Score: 2
    It will mean that the AT&T source will not be represented on Intel's new processor.


    Doesn't HP-UX borrow from the AT&T source? That will still make it to IA-64 eventually, since HP is abandoning every other processor architecture (well, except for IA-32). Irix is still being ported too, but AIUI it was mostly written from the ground up by SGI (even if they might be paying royalties to call it "Unix" anyway).
    --

    "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
  31. Differently Colored Virt. Terminal (Was: ScoAdmin) by markus · · Score: 4, Informative
    Another cool thing about SCO (out of the 3 good things I can say about it) was that the colors of vitual terminals changed. When we migrated to Linux my boss hits ctrl+alt+F2 and says "Hey, they're all the same color!". Is there a way to do this in Linux? it's actually sort of usefull...

    Of course you can do this. This is just a question of configuring your system properly. You need to edit your /etc/inittab and add apropriate -I parameters for your getty processes:

    1:2345:respawn:/sbin/getty 38400 tty1 -I 'ESCcESC[?17;55;248cESC]RESC]P0681800'
    2:23:respawn:/sbin/getty 38400 tty2 -I 'ESCcESC[?17;55;248cESC]RESC]P0686800'
    3:23:respawn:/sbin/getty 38400 tty3 -I 'ESCcESC[?17;55;248cESC]RESC]P0005078'
    4:23:respawn:/sbin/getty 38400 tty4 -I 'ESCcESC[?17;55;248cESC]RESC]P0681868'
    5:23:respawn:/sbin/getty 38400 tty5 -I 'ESCcESC[?17;55;248cESC]RESC]P0006818'
    6:23:respawn:/sbin/getty 38400 tty6 -I 'ESCcESC[?17;55;248cESC]RESC]P0006878'

    Make sure that you enter a literal escape character for ESC (in vi you do this by preceding it with a CTRL-V, in emacs you must press CTRL-Q first).

    After you have made these changes restart all your getty processes:

    telinit q
    killall -HUP getty

    If you want to know what the escape sequences do, then here you go:

    • ESCc clears the screen.
    • ESC[?17;55;248c gives you a non-blinking red block cursor.
    • ESC]R resets the current palette to its default values.
    • ESC]P0RRGGBB changes the color for the first entry in the palette (i.e. for the background color).
  32. *bzzzt* wrong... by EnderWiggnz · · Score: 2

    >Indeed. There is no way a start-up could afford
    >to buy an established competitor just to remove
    >them from the market. That's what competition is
    >for

    you DO buy out your competitor when they start floundring - at the very least, you get a large portion of their customers at a fraction of the cost to you needed to acquire them through traditional channels (competition, sales force).

    At best, you can absorb their "good" technologies, as well as take on some of their sharpest people in areas you need to strengthen.

    Its a damn good way to grow a business.

    --
    ... hi bingo ...
  33. Anti-Trust violation by Skapare · · Score: 2

    I wonder if this is an anti-trust violation. Given that none of the 4 companies has a monopoly, I would guess not. They do say they are open to any company joining. So what if Microsoft joined?

    --
    now we need to go OSS in diesel cars
  34. Only about 8 Itaniums have been sold by DABANSHEE · · Score: 2

    So its no big market loss.

  35. buh-bye by delong · · Score: 2

    Now, the first Unix I ever knew is about to be no more.

    And I say good riddence! SCO was a miserable little Unix.

    Derek

  36. Re:I administered SCO, it sucked. by RocketJeff · · Score: 2
    How about relinking the kernel (and rebooting) everytime you make a minor system configuration change. Perhaps Linux's loadable modules, and dynamic detection of devices has spoiled me

    Welcome to the real Unix world. This was SOP for Unix systems - loadable modules are a recent development on the Unix timeline.
  37. Re:SCO is gone - Huh? by RocketJeff · · Score: 2
    UnixWare (now Open Unix I guess) was originally developed by Novell, and is a more direct branch from the AT&T source.
    Nope, UnixWare is Unix - the real, original source from AT&T. Novell bought it from AT&T in one of their "Let's Out Microsoft Microsoft" spasms.
  38. Re:Not A Compensated Endorser .... by RocketJeff · · Score: 2
    Not just Pizza Hut, I worked on the project at McDonalds to convert the in-store system from SCO Xenix 286 (yep, 286) to SCO Unix. It was running in all company owned stores and quite a few of the franchise stores.

    McDonalds was using Xenix 286 (on AT&T 386 WGS boxes) because of a bug in the original 386 math co-processor (remember those things?). Xenix 386 would crash with the faulty co-processor installed. Rather then try to remove ~1200 co-processors (already in stores) it was decided that it was cheaper/easier to just use the 286 version (SCO came out with a fix/workaround after the 286 version was already distributed)...

  39. Re:The only thing worse than SCO Unix was SCO Xeni by be-fan · · Score: 2

    Its really not their fault. Its users like you who insist on backwards compatibility. They originally put the words at the end (where normal stuff wouldn't interfere) but when they extended the word, the bits wound up in the middle. If you think that's bad, try programming an IDE controller directly. The sector address is broken into three or four parts scattered across 64 bits. Same thing for the GDT entries.

    --
    A deep unwavering belief is a sure sign you're missing something...