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. "

246 comments

  1. Sad by 3th3rn3t · · Score: 0, Redundant

    this is sad indeed. i guess some people cant appreciate other peoples years of hard work ....

  2. 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.

    1. Re:SCO is gone by Anonymous Coward · · Score: 0

      Why did it suck? You don't state your reason. It is still one of the most stable o/s's under x86. Back in the day you could run a whole company up to 64 terminals on a single 80486.

    2. Re:SCO is gone by Anonymous Coward · · Score: 0
    3. Re:SCO is gone by (outer-limits) · · Score: 1

      How can you call an OS dead because it is not being ported to an architecture that is looking dead before it is born?

      --

      Microsoft - Where would you like to go today, Maybe Jail?

  3. argh by athlon02 · · Score: 1

    granted i've never used SCO myself, but if you're gonna buy a flavor of unix or what not, and don't want to develop and/or support it, the least you could do is release it to the public for free. I like my little OS collection on CD, and I wouldn't mind adding another one to the heap.

    1. Re:argh by Anonymous Coward · · Score: 0
      I like my little OS collection on CD, and I wouldn't mind adding another one to the heap.

      I'm pretty nerdy, but that was more than I can handle. Die slow.

    2. Re:argh by Anonymous Coward · · Score: 0

      Wow are you gay. Are you a software hermit?

    3. Re:argh by Anonymous Coward · · Score: 0

      SCO is AT&T, AKA UNIX Labs, and may not be eligible for open source style distribution. There may be a way around that and I'd like to hear REAL rational explanations as to how it might be done.

    4. Re:argh by Anonymous Coward · · Score: 0

      Here's the plan: release it under GPL, and call it GITU, which of course stands for GITU Is Too Unix.

  4. 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 zootread · · Score: 0

      Never trust anything (or anyone) called "Random Love" - you'll only have your heart broken.

      That and herpes

      --
      Zoot!
    3. Re:title by sporty · · Score: 2

      Random Love Unties Linux?

      Yslexdexics of the world untie!

      --

      -
      ping -f 255.255.255.255 # if only

  5. 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 nomadic · · Score: 1

      And yet according to this story Caldera was so terrified of SCO they bought it to kill it.

    2. Re:good riddance by ratzmilk · · Score: 1

      I don't know, my SCO customers are my Bread and Butter customers. I have suggested on many occasions that they should migrate to Linux or BSD, but noooo, they liked the idea of having a support structure, and were very distrustful of a 'free' OS.

      My main reason for recommending a migration was because I often felt guilty of the amount of support Sco needed compared to my Linux customers.

      Oh well, time for me to go and get my MCSE.

      --
      I wish I could think of a witty Sig. Sigh!
    3. Re:good riddance by diabloii · · Score: 1

      I'm tired of the people that bash things even though they most likely have grievances against many other Unix variants, but admit it because they don't have a clue. There are many places that use and are very happy with both Open Unix (UnixWare) and OpenServer. Just ask the VARs that continue to make money off of installations and custom application development. Ask people in Asia what they think of SCO.

      Yes, I worked for SCO for a few years, and yes it was/is dying, but it isn't necessarily because the products they developed were/are crap. Many of the developers up until that past year were from AT&T or USL (Unix System Labs). Therefore the people that worked on everything upto SVR4. Novell screwed up things when they took over the codebase and created UnixWare. They mis-managed the product and they can probably be blamed on the current state of OpenUnix or whatever you want to call it (still UnixWare to me).

      All the negative comments I see I could easily say about all the other Unix variants or Linux for that matter. I use Linux everyday and enjoy using it, but not everything is straight forward, nor bullet proof. You need to learn an OS to be able to use it and understand it well.

      --
      ---- "It is never too late to give up our prejudices." --Henry David Thoreau(1817-1862)
    4. 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.

  6. Yeah, But You Still Have... by tealover · · Score: 0, Interesting

    the PS2 Linux. Clearly, this is where Linux will be moving in the next decade. Set top boxes, watches, microwaves, etc.

    We need to stop thinking nostalgically about computing. The old days are gone. Let's move forward and think of new ways to utilize computing. And by doing that, it may mean thinking about moving beyond Unix.

    --
    -- You see, there would be these conclusions that you could jump to
    1. Re:Yeah, But You Still Have... by Anonymous Coward · · Score: 0

      Yup, people have been saying that for close to 30 yrs now. You saying it isn't gonna really make it happen.

  7. 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
    2. Re:Caldera's Not Killing Off SCO! by Anonymous Coward · · Score: 0

      If they are not going 64bit then the end is in sight. That is killing off SCO but not on a particularly fast time table.

    3. Re:Caldera's Not Killing Off SCO! by Anonymous Coward · · Score: 0

      Or maybe they just seen no demand for IA64 in their markets anytime soon.

      Remember 2 years ago when Itanium was about to ship and revolutionize the low-end server market? When SCO and IBM were working on their super Project Monterey OS for IA64? Big Vapor Cloud, and now nobody care.

      If AMD64 starts to catch on for POS systems or whatever it that sells SCO, it's a much cheaper and easier port.

    4. Re:Caldera's Not Killing Off SCO! by Anonymous Coward · · Score: 0

      Yeah, but the way Intel 64 bit systems are selling now, it's only a matter of time before there's no 32 bit platform available.

  8. 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 Anonymous Coward · · Score: 0
      >>the first Unix I ever knew
      >more like, the worst Unix I ever knew

      Well, for me, it was both. I really wanted SCO Xenix, back in the day when it cost a month's pay and ran on Altos boxes with 8086s in them. The Altos boxes cost more than a month's pay. I fixed the hardware, so I had to know enough about the OS to do a backup or restore, and to start and stop them. The competition back then was DOS (2.5 or so, I don't remember well), and bad as SCO Xenix was in hindsight, DOS was worse. Windows 9x was and is worse, for that matter, despite the fact that I never saw a GUI on SCO.

      Getting far off topic:
      Back then, all the terminals used serial ports, and a co worker made a graphical display which ran over a serial line, from a pc. He demo'ed it to HP, and they hired him, either because of it, or in spite of it.

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

      ...despite the fact that I never saw a GUI on SCO.
      You should be thankful for that. Open-Desktop was nicknamed 'Open-DeathTrap' by the very engineers that worked on it.

    3. 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
  9. Kill, Kill, Kill, Kill by dirvish · · Score: 1

    Are they still denying that they bought SCO just to kill SCO Unix or have they fessed up to it now? Where can we find info on Open Unix and SCO Unix? I have never heard of either.

    1. Re:Kill, Kill, Kill, Kill by Anonymous Coward · · Score: 0

      duh

    2. Re:Kill, Kill, Kill, Kill by dirvish · · Score: 1

      Is there any non-caldera created info? Post caldera buy-out stuff.

    3. 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.

    4. Re:Kill, Kill, Kill, Kill by dirvish · · Score: 1

      Uhhh, doesn't that happen all the time. It isn't Home Depot that goes out of business. With the competition that the big guy creates usually only one little guy survives. Some people like the little guy but there isn't usually room for many little guys. Only a select number of people are willing to accept the possible higher prices, lower convenience or whatever drawback of the small guy.

    5. Re:Kill, Kill, Kill, Kill by Anonymous Coward · · Score: 0

      SCO UNIX is a godzilla of profitability when compared to Caldera Linux.

    6. Re:Kill, Kill, Kill, Kill by kberg108 · · Score: 0

      "I have never heard of either.
      "
      your lucky

      --
      I like things that are sweet and not things that are lame. --
  10. 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."
    1. Re:Why Should They? by Anonymous Coward · · Score: 0

      That there are 4 companies doesn't mean they have capital - 2 of them are almost dead, one is in a lot of trouble and the fourth needed a large cash infusion to stay afloat.

      2 now irrelevant companies (how much Linux engineering does Turbo and Caldera have left now?) teaming up with SuSE doesn't mean much. Connectiva is the surprise, but has scaled down quite a bit itself.

  11. Good riddens by GombuMstr · · Score: 1

    What a miserable piece of soft links. Just finding your way around the filesystem is a nightmare. You think your finding the right folder then you find out it's linked to another folder.

    The icky scoansi terminal.

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

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

    2. Re:Good riddens by pstreck · · Score: 1

      probably more likely due to your not so great admin skills

      --

      Later,
      Phil
    3. Re:Good riddens by Anonymous Coward · · Score: 0

      Every Unix variant uses symbolic links and different directory structures. Maybe your better off sticking with a pseudo o/s such as m$ with point & click file manager.

    4. Re:Good riddens by GombuMstr · · Score: 1

      Wow, a distate for SCO sure can come back to haunt you.
      SCO has an unbelievable amount links to other folders. I know that Linux and SYSV OS's have a lot a links. Look at /etc. I had originally come from AIX and BSD world and the filesystem layout was easier to work with.
      I't wasn't just the links that was the biggest problem it was the first thing that I backflashed to.


  12. too late for me to care :P by Pr0xY · · Score: 1

    i would have cared 2 years ago, but i have converted all my cooporate servers to use linux with SCO ABI support patched in.

    Works like a charm :)

  13. 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.

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

      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...

    3. Re:ScoAdmin by jav1231 · · Score: 1

      I took alot of ragging from other UNIX folks when I was a SCO admin. You're right. It works...works well in fact. Buggy? For the most part, No. There are MANY POS and branch offices running SCO as we speak with no issues. I deployed about 400 SCO servers in '99. They were directly replacing SCO servers on obsolete HW as we all planned for Y2K. We ran Progress Db's on them and they were reliable as hell! Before that, I worked at HIWW (Holiday Inn WorldWide aka Bass Hotels) and the majority of our hotels ran SCO lans with dumb terms and THEY were reliable as hell! It's not for everyone and perhaps not as robust as AIX. But not everyone is running 'NIX on a cluster, or mainframe, or an IBM RS6000 with a terrabyte array. For Intel boxes, SCO was the bomb! Nuff said. It's a shame that Caldera isn't doing much with it Furthermore, it's a shame that UnitedLinux is coming off so Caldera Centric. I used to adore Caldera. Yet, they needed SCO support badly, because frankly there's has a long way to go. They target corp customers and don't appear to want to support you very well unless you are a corp customer. >

  14. 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.

  15. 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 Anonymous Coward · · Score: 1, Insightful
      " 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.

      One very good reason to do this is the GPL. If you distribute the binaries, you MUST make source available. If you distribute binaries ONLY with source, or not at all, you have no further obligation to make source available.

      It seems to me that these folks could distribute their product as a binary plus source set, and not make any downloads available at all. They'd save a lot on bandwidth that way. The fact that they aren't speaks well for their good intent. If you want them to do the compile for you, doesn't it seem decent to pay them for it?

    5. Re:Why I will never use United Linux... by ztwilight · · Score: 0, Redundant

      To quote erat:

      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.

      Don't give the impression that UnitedLinux is a bad thing. All Linux companies are Open Source (except for Lindows, which is either going to 1. die suddenly of a court case or 2. will move to BSD and thereby shoot themselves in the foot), therefore, when anyone, including UnitedLinux, creates a Standard, it is always a good thing. Nothing is stopping anyone else from adopting this standard. More standards = easier to use software (unless of course, the standards are no good. but we will assume for now that they are good.)

      ...and the truth gets blurred like a wet letter, but since I gave up hope I feel a lot better...

      --
      Who moved my sig?
    6. 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
    7. Re:Why I will never use United Linux... by kasparov · · Score: 1

      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".

      Maybe, but you can also download the binaries from RedHat. You can download the ISOs from RedHat. I'm not going to argue that the UnitedLinux companies are immoral for only distributing the source freely--I mean, that's the whole point of the GPL isn't it? But you have to admit that it is certainly a lot more convienient to be able to download an ISO if you want to try out a distro. In the end, with RedHat planning a LSB compliant distro--and ISO downloads--I really don't think that they will be putting a major dent in RedHat's dominance. Just my 2 cents.

      --
      There's no place I can be, since I found Serenity.
    8. Re:Why I will never use United Linux... by MAurelius · · Score: 0

      Steve Taylor, I Predict 1990! And you thought no one would recognize this great line! Way off topic, but Jim Morrison's Grave is another awesome tune!

    9. Re:Why I will never use United Linux... by Anonymous Coward · · Score: 0

      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.

      Conectiva is as binary friendly as any of the distros you mentioned and is part of the UL consortium. I have been using it for good 3 years now.

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

      The fact is you'll never use United Linux because it is not targeted for you and me. It is just a codebase onto which, ISVs, developers and hardware manufacturers will look at when building their solutions for the enterprise.

    10. Re:Why I will never use United Linux... by cpaluc · · Score: 1
      But what's going to stop 3rd parties distributing copies of binary ISOs? If you don't stick the trademark on it they can't get you with trademark law. If there's proprietary software on it, just delete it and distribute copies lacking the proprietary stuff.

      Para 3, GPL:

      3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

      * a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

      * b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

      * c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

    11. Re:Why I will never use United Linux... by Anonymous Coward · · Score: 0

      Caldera and SuSe have signficant non-GPLed parts of their OSes, such as the installer and the system config tools. Therefore they can restrict the distribution of the entire package.

    12. 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.

    13. 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.

    14. Re:Why I will never use United Linux... by Phexro · · Score: 1

      "Maybe, but you can also download the binaries from RedHat."

      That was my point - It's the same as what Red Hat does, with that one difference.

      "I'm not going to argue that the UnitedLinux companies are immoral for only distributing the source freely--I mean, that's the whole point of the GPL isn't it?"

      No, it isn't. The point of the GPL is to allow free redistribution of the source. Binaries don't really matter when you have source. Under the GPL, you are only required to provide an offer for the source, though you have to honor anyone's request for the source. Incidentally, if United Linux is completely GPL'd, anyone can rip a copy of the CD and make copies for anyone else, under section 3 of the GPL.

      "But you have to admit that it is certainly a lot more convienient to be able to download an ISO if you want to try out a distro."

      Sure, if you have broadband. If you're on dialup, it's a lot easier to just fork out a few bucks for some official media in a box. It's easier still to fork out that money when the only alternative is to compile everything yourself, which is the point of not offering binaries for download.

    15. Re:Why I will never use United Linux... by Nakarti · · Score: 1

      Same thing keeping people from distribamiting Suse ISOs that aren't readily available from Suse as ISOs. Apparently, since Suse says in they 'come buy me' blurb even says you can redistribute it, free, withouth litigation or license fees. And yet nobody but warez groups have the ISOs that I have seen. Why? My guess is out of respect. Respect, despite wanting, free, the Leinenkugel of OS, that its creators do have developers, service providers, and possibly advertisers to pay, and the only way to get it means people who pay for the distro. So they buy and copy for some friends who ask for it, but don't use Speedy Universal Electronic Distribution(SUED :) via internet, before the originators say ok. Respect. The belief that something that may help provide a free future is worth spending a couple hours of money to someone making an effort to provide it.

    16. 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.

    17. 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?

    18. 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.

    19. 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.

    20. Re:Why I will never use United Linux... by Anonymous Coward · · Score: 1, Insightful

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

      Management never consults their IT techies.

    21. Re:Why I will never use United Linux... by kasparov · · Score: 1

      You misunderstand me, when I say "I mean, that's the whole point of the GPL..." I was saying that the whole point was distribution of the source, not binaries. I wasn't disagreeing with you, just adding that I prefer RedHat's business model.

      --
      There's no place I can be, since I found Serenity.
    22. Re:Why I will never use United Linux... by Anonymous Coward · · Score: 0


      >the only alternative is to compile everything
      >yourself, which is the point of not offering
      >binaries for download.

      I didn't think of that, good catch.
      Then again, how much effort would it be to create a script that would go thru a bunch of source trees and do a ./configure && make && make install on all the source?

    23. 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.

      --

    24. 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.

    25. 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.
  16. 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.

    1. Re:Is it worth mentioning that by Anonymous Coward · · Score: 0

      Derived? not so. SCO had licenses to make Xenix (My first Unix system ever, around 198x). But SCO Unix don't derive from it (Well only in the way all "licensed" Unix derive from good old BSD).
      Just the tools they used on SCO Xenix where ported to SCO Unix, the kernel was completely different.
      BTW.
      Anyone used "micnet", a net of Xenix boxes joined by PtP serial lines (universaly known as uucp). This was my first net and was really exciting to configure. (It had news and mail with the famous "bang" notation)
      It's already in use somewhere?

  17. 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."
  18. 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.

    1. Re:Remember trying to port Unix software to SCO? by Anonymous Coward · · Score: 0

      I can not agree with you:

      The CC in SCO was derived from MS CC 5.x professional C compiler, and NOT from MS Quick C, the consumer product.

      The AT&T CC was available as rcc. But it was very poorly optimizing in comparison to MS CC in those old days. (8086/80286/80386)

      And GCC was a piece of cake to port. The 1st release I used on SCO was GCC 1.34. It was easy to port GNU SW to SCO. There have been even patches for Xenix386 available.

      So, I have just different views on SCO abilities in terms of SW porting.

      I worked on plenty of UNIX systems (Xenix, Xenix286, Xenix386, SCO 3.x, Unixware, System V 4.x, Sinix, Sunos 1.X, Sunos 2.x, Ultrix, DG/UX, The early BSD 0.1 port from Bill Jolitz, FreeBSD 3.x & 4.x, MacOSX, and Linux since the very beginning. On all the platforms I installed gcc or had a gcc and the GNU suite of command line tools. SCO was as good as any other UNIX to port free SW.

      SCO did work reliabale for my company's commercial SW. We had uptimes of a year at customer's sites with continous 15 - 28 V.24 Terminal users online and 12 printers working. This was what I count useful.

      By the way guys. Do you really think the OS world would be so bad, if MS-Xenix and X10 or X11 window system would have been the base of Microsoft's todays operating systems ?

      Just my $0.02

  19. Not moving to Intel's 64 bit platform by Anonymous Coward · · Score: 1, Insightful

    Remember that Caldera has finite resources, they cannot afford to port the system to many architectures. That might be a good move, considering the fact that Intel's IA-64 architecture has not made significant inroads into the market. Now if they move it to AMD's Hammer series or the alternative 64 bit extension to the IA-32 processor family that would make sense.

    1. Re:Not moving to Intel's 64 bit platform by Anonymous Coward · · Score: 0

      Why not port it to the L4 microkernel? Then you can put it on pretty much any hardware to which L4 has been ported. (And L4 is not inefficient! I've seen a bloody quick Linux kernel built on top of it.)

    2. Re:Not moving to Intel's 64 bit platform by Anonymous Coward · · Score: 0

      Why not port it to the L4 microkernel? Then you can put it on pretty much any hardware to which L4 has been ported. (And L4 is not inefficient! I've seen a bloody quick Linux kernel built on top of it.)

      Please recall that layering is not free. SCO has their own kernel, and even if they layer it on top of a microkernel, they may have a substantial rework. If they are going to do that, perhaps they ought to consider RTLinux kernel , since they could get hard real time guarantees out of the scheduler. Unfortunately, that means licensing fees, but that might not substantially alter the price of SCO Unix.
  20. 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).

    1. Re:Releasing only the source code? by Anonymous Coward · · Score: 0

      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?

      So long as that someone did not call their distribution "UnitedLinux" or "Powered by UnitedLinux," it appears there is nothing they could or would do.

      Lack of binaries in this instance is a means for them to sell a low marginal cost product with high profit-margin support services. Don't need their support? Don't use their distro. Don't need their support, but want their distro anyway? Freely download their source and compile.

      It's not evil, it's inconvenient.

  21. 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 Anonymous Coward · · Score: 0

      People passing around binary CDs doesn't break the business model at all because the business they are after is the reseller channel and ISVs. A reseller wants to buy Linux rather than get it for free because it gives them a product that can be resold with a good margin. If they get it for free, then it is difficult or impossible to bundle vendor support (which they also want to sell) and they can't call it "UnitedLinux" (which is what customers will demand, assuming this whole thing works and the software vendors start stamping "UnitedLinux compatible" on their software.

    2. 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?

    3. Re:Open Source? by Anonymous Coward · · Score: 0

      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...


      Hey Jackass, try reading the GPL sometime.

      The GPL doesn't give you any right to copy and redistribute a binary. The GPL says that if you get the binary, and in the case of United Linux you must buy it, that the vendor must give you the source, and the right the modify and redistribute SOURCE. It certainly does not give you the right to make pirate copies of anything.

    4. 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".
    5. 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
  22. Servers Only by Anonymous Coward · · Score: 0

    This United Linux group is not going after the desktop, they are going for the enterprise server market. Expect to see little or no impact on the desktop, which is what MS owns anyway. Oh yeah, I love where RL says that they would have invited RH to play in their sandbox but they just ran out of time. Expect to see UL running on application servers and the like, not anywhere near the desktop. This is Linux for PHBs, not techies.

    1. Re:Servers Only by Anonymous Coward · · Score: 0

      Imagine how hard its got to be to build a distro for PHB's. btw, if the techies don't like it, who's going to tell the PHB's to try it. Oh wait that would be the M$ minions.

  23. 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.

    1. Re:No Weeping here. by Anonymous Coward · · Score: 0

      Install from a backup tape, huh, it's very simple.

      Make a backup with tar -cpzf filename --esxclude tmp --exclude proc . from root
      Use a rescue CD, Mandrake, SuSE, doesn't matter.
      Load the module you need, SCSI ????
      Fdisk your drive, with the filesystems you need.
      Put an filesystem on it.
      Mount them and go to the root of the mounted root, /mnt ???.
      cd /mnt, mkdir tmp proc, tar -xzpf /dev/"tape-unit"
      "Modify" your fstab, lilo.conf, other hardware related stuff if it's needed.
      Maybe chmod 1777 /mnt/tmp for X.
      Don't forget to execute the bootloader, lilo or other bootloaders you use...

      Voila, reboot, you're done.

      Quite simple......

  24. and what happens to the source? by Heraklit · · Score: 1

    So, in case they really "kill off" SCO Unix, what happens to the source? There must be some things vaulable in there, I hope they are contributed to United Linux.

    Even better would be to publish all of it as GPL code, but that will probably not happen because part of the code might be licensed from third parties. (Also, of course no GPL'ing will take place as long as IA32 Open Unix is "still around on the market"...)

    1. Re:and what happens to the source? by cant_get_a_good_nick · · Score: 1
      Even better would be to publish all of it as GPL code, but that will probably not happen because part of the code might be licensed from third parties.


      UNIX has been around for such a long time, and there are so many cooks with a hand in that stew... I think gettting all the folks together to relicense it will be a serious undertaking. Just think, Microsoft's XENIX is a part of it now, so now you have to (possibly) ask Billy Boy to relicense under the GPL. Hmm, how likely is that?

  25. I'm not rubbing it in or anything... by TheLinuxWarrior · · Score: 1
    But the day I heard SCO was acquired by Caldera, I knew it was over. It was only a matter of time.

    I asked our CEO very shortly thereafter...So when are we migrating Oracle over to Linux? "Never!" was his reply. I suppose he didn't realize then that SCO was no longer going to be a viable option as a mission critical platform.

    I certainly can't say it surprises me. I mean look at Caldera's track record. Maybe someone over at the new UnitedLinux should consider giving them the boot before they take that down the tubes too.

    BTW...I'm not being a troll. I'm just a little over opinionated about this I suppose. It's just difficult to have any respect for a company that takes anything they have of any value and pisses it away.

  26. SCO UNIX by HR+Pufnstuf · · Score: 1

    Good lord, it's not dead yet? I had the 'opportunity' to work with SCO a year after I was introduced to Linux. Not what I would say I had in mind when I started studying Linux to get a UNIX job.Do I have tales to tell.

  27. Re:United Linux sucks! by Anonymous Coward · · Score: 0, Informative

    So does Ransoms. The standard desktop client at Caldera is Windows. Pretty pathetic really.

  28. 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.

  29. Good! by AdTropis · · Score: 1

    any OS that allows you to backspace over the login prompt needs to be destroyed!

    1. Re:Good! by Anonymous Coward · · Score: 0

      Oh so true!!! How funny that this ``feature'' bugs the crap out of me as well.

  30. Long-Term Vision by datastew · · Score: 1
    I totally don't agree with the poster of the article about bemoaning the eventual deprecation of SCO Unix. While I have fond memories also an SCO system, I have a much clearer vision now. We need to more toward open programs and operating systems.

    I look forward to the time when all programs will be free and open and similiar to the standard Linux utilities (grep, more, fsck, and so forth) in that programs do one thing, and do it well. Once this happens, and programs are generally well-understood like engineering principles, law principles, or medical principles, then programmers will be there to provide a service, like engineers, lawyers, or doctors. I only see this happening once the programs' source is open.

    We (programmers) need to continue to move toward the "programming as a service" scenario. We need to get away from the "write the program once and sell a million copies and get rich" philosphy.

    1. Re:Long-Term Vision by NDPTAL85 · · Score: 1

      Don't you mean "we open source programmers"? You know the ones who aren't too concerned with making a living from their programming efforts? The proprietary guys will continue to "write once, sell a million times and get rich" for many many years to come.

      --
      Mac OS X and Windows XP working side by side to fight back the night.
  31. Xenix? by Jarvo · · Score: 1

    Xenix? Microsoft?

    Damn. Those Scientologists are everywhere.

    :)

    1. Re:Xenix? by Anonymous Coward · · Score: 0

      You may laugh, but there is good evidence that MS + scientology have an alliance-thing going.

  32. IA-64 == "The Future" ? by timeOday · · Score: 1
    I'm not so sure of that at all.

    I would think a lot of things are not being ported, because it's bombing.

  33. OpenUnix != OpenServer by Anonymous Coward · · Score: 0

    Nothing was actually said about OpenServer (commonly called SCO Unix) moving or not moving to IA64, but the writing is on the wall.

  34. LINUX FUCKING SUCKS by Reality+Master+101 · · Score: 0, Flamebait

    I've just spent EIGHT FUCKING HOURS trying to get this piece of shit laptop to dial up fucking Earthlink. "wvdial" JUST FUCKING DOESN'T WORK.

    Is there ANYONE on earth who thinks Linux is ready for the average person???

    It takes 5 seconds to set this up under Windows.

    Sorry, mod me down as off-topic, but I felt I had to get this off my chest. It's 4:38pm as I type this, and I have someone leaving on a plane for a demo tomorrow at 7am. "Yeah, just gotta set up the modem and you'll be all set! Well, no, I haven't done that before under Linux, but it's menu driven nowadays. How hard can it be?"

    Yes, I've tried a) multiple modems, b) multiple ISPs (for GODS sake), multiple FUCKING everything.

    Excuse me while I try and figure how to set up an old-school chat script.

    Man, there is SO MUCH TRUTH to "Linux is free only if your time is worth nothing".

    --
    Sometimes it's best to just let stupid people be stupid.
    1. Re:LINUX FUCKING SUCKS by Anonymous Coward · · Score: 0

      Try FreeBSD. It's way cool and faster than linux.

    2. 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*

    3. Re:LINUX FUCKING SUCKS by Anonymous Coward · · Score: 0

      Feel better now?

    4. Re:LINUX FUCKING SUCKS by Anonymous Coward · · Score: 1, Insightful
      I've just spent EIGHT FUCKING HOURS trying to get this piece of shit laptop to dial up fucking Earthlink. "wvdial" JUST FUCKING DOESN'T WORK.

      Really? I've never had any trouble with wvdial on debian, or the kppp setup wizard on RedHat. That's what I've always admired about Linux: things Just Work. That hasn't been my experience with Windows, where it takes five minutes to whiz through the wizard, and then things almost work, and then you're screwed. Obviously our experiences have been very different.

      Is there ANYONE on earth who thinks Linux is ready for the average person???

      It takes 5 seconds to set this up under Windows.

      Windows isn't ready for the average person. Neither is Linux (See what I said above). Some things work nicely under Windows, I'm sure, and I've found that most things work nicely under Linux, though obviously not for you. The fact is that the average person isn't ready to use complicated equipment like general purpose computers. Average people manage to kill themselves with toasters!

    5. Re:LINUX FUCKING SUCKS by k0osh.CEOofCLIT · · Score: 0, Flamebait

      you sir are the average dork that makes up the slashdot community. congradulate yourself!

    6. Re:LINUX FUCKING SUCKS by Anonymous Coward · · Score: 0

      actually in gnome / kde it's quite easy to set up an internet connection

      actually _using_ linux is easy in kde / gnome, at least if you have that average Dell computer - with specialized hardware: laptops, foregin architectures (ie non-x86) setting up things may be less easy

      also most laptops have winmodems and not many are even supported by linux, most require special kernel modules, try searching on that laptop model and linux on google - I got lots of info about linux on my ancient Powerbook 3400

      and while many tasks can be a pain to set up and require lots of reading HOWTO's and FAQ's, when it's finally working - It's working, and it wont stop working, thats why I love this Überstable system

      /Thomas

    7. Re:LINUX FUCKING SUCKS by Anonymous Coward · · Score: 0

      Screw you Troll!

    8. Re:LINUX FUCKING SUCKS by Anonymous Coward · · Score: 0

      Why, may I ask, do you read slashdot comments if you believe they are written by moronic dorks? I can understand (not very well) if you despise slashdotters, but if that is so, why join the crowd?

    9. Re:LINUX FUCKING SUCKS by Anonymous Coward · · Score: 0

      I've had four different Linux distro's installed on three different laptops, without any problems what so ever. You must be a real dumb-fuck!

    10. Re:LINUX FUCKING SUCKS by Anonymous Coward · · Score: 0

      winmodems are just correct as any other, linux is just not correct as it does not support these very commonly used devices.

      Best way to fix the problem: install winXP.

    11. Re:LINUX FUCKING SUCKS by Anonymous Coward · · Score: 0
      That's like saying your shoe is a phone, you just have to install a phone to use it.

      news flash: winmodems aren't modems. they're some sort of fucking modem-enabling hardware platform technology.

    12. Re:LINUX FUCKING SUCKS by festers · · Score: 1

      And I've spent 8 hours trying to resolve a soundcard/video card conflict on a friend's Windows computer, so what's the point of all this crying? If you find Linux to be so hard for you, then don't use Linux. Trust me, attitudes like yours won't be missed.

      --


      -------
      "Every artist is a cannibal, every poet is a thief."
    13. Re:LINUX FUCKING SUCKS by MatthewDunbar · · Score: 1

      Perhaps you'd simply have better luck with different hardware.

      Anybody have a spare toaster???

    14. Re:LINUX FUCKING SUCKS by Anonymous Coward · · Score: 0

      Is there ANYONE on earth who thinks Linux is ready for the average person???

      No. I maintain that it's only for the clueful and educated people, and it's a waste of time supporting the masses.

      I'm perfectly happy with Linux as is. I had no trouble with my laptop whatsoever. Just ignore the GUI junk and set it up as you would for any other OS.

  35. 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
  36. OpenUnix is NOT SCO Unix (OpenServer 5) by dokhebi · · Score: 1

    OpenUnix 8 is the successor to Unixware 7. Unixware was created by Novel based on the SysV R4 code, when SCO bought it they continued working on it and got it up to SysV R5. Then Caldera bought most of SCO, and created OpenUnix 8 which is a merger of the SVR5 Unixware and many features from Linux.

    SCO OpenServer 5 is based on SysV R3. It does not suck, and it does do all of the things Bill Gates claims Windows does only better and much more stable.

    If Caldera has no interest in porting Unix to the IA-64 platform, it is now time to open source the AT&T Unix code base. I would love to have several proprietary Unix features available to the world (pg for one)...

    I've used SCO Unix since the OpenDesktop days and I like it!

    Just my $0.02 worth.

    1. Re:OpenUnix is NOT SCO Unix (OpenServer 5) by Anonymous Coward · · Score: 0

      SCO Blows like a Tiajuana hooker. SCO is hideous. Why would you want a Unix that requires $400.00 additional licensing for a weak-ass IP stack?.

    2. Re:OpenUnix is NOT SCO Unix (OpenServer 5) by dokhebi · · Score: 1

      Technicly speaking hookers suck, they don't blow.

      You must be reading some VERY old info if you think SCO Unix requires an additional license for TCP/IP. It has been standard in SCO since the first release of OpenDesktop.

      The only proprietary OS I would leave SCO OpenServer for is SCO Unixware (or it's successor Caldera OpenUnix). Microsoft both blows and sucks. Solaris isn't Unix. And Linux (though I love it) can't get the support it needs from critical systems vendors because they are being bought or brainwashed by Der Fhurer of Redmond.

      Once again, my $0.02 worth.

    3. Re:OpenUnix is NOT SCO Unix (OpenServer 5) by nrc · · Score: 1


      The Unixware/Novell SysV R4 code came from Unix System Labs, which AT&T spun off from Bell Labs. So basically Linux has killed the most direct descendent of the original Bell Labs UNIX.

    4. Re:OpenUnix is NOT SCO Unix (OpenServer 5) by Anonymous Coward · · Score: 0

      Caldera have open sourced the archaic Unix sources (16bit unix up to V7 and 32bit Unix BSD) under a BSD style license. The mirrors are at http://www.tuhs.org/archive_sites.html

    5. Re:OpenUnix is NOT SCO Unix (OpenServer 5) by mjw2002 · · Score: 1

      The AT&T Unix code base has been open sourced under a BSD license at http://minnie.tuhs.org/PUPS. This includes everything up to v7.

  37. 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;
    1. Re:Bye bye, won't miss ya by smash · · Score: 1
      Heh.

      Fun with 'rm' ...

      While I agree that I totally hate the state of the SCO filesystem and its symlinks everywhere, that very quirk saved my ass a couple of months ago.

      I was trying to delete a bunch of spool files with awk and rm I believe, and the statement somehow climbed up into the / directory.

      I caught it before it removed much, but it had removed the kernel (or so I thought).

      After a fairly worried call to a knowledgable SCO guy, he told me that it was just a symlink, and to simply relink it to wherever the hell it was. I was worried I'd have to break out the install CD and start copying stuff ;)

      I still hate SCO tho....

      smash

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  38. Dead Operating System collection by dsyu · · Score: 1

    I've got a collection of 'dead PC operating
    system' CDs that'll make nice wall art some
    day. I guess I'm defining "dead" as an
    operating system that you can't buy anymore
    or is otherwise unsupported today.

    So far, I have original install CDs from:

    SCO Openserver 5
    NextStep
    Novell UnixWare
    OS/2
    BeOS (but just a demo CD, sigh)
    An old DOS CD

    Anyone have any suggestions on CDs to add?
    I'm still looking for a rare CD of a
    rumored version of AIX that was for the PC,
    not RS/6000. Never seen it, though. And
    I missed out on the chance to get that
    CP/M CD a while back.

    1. Re:Dead Operating System collection by Anonymous Coward · · Score: 0
      Anyone have any suggestions on CDs to add?

      Solaris x86. But you can't download it any more. You'll have to order the CDs.

    2. 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.
    3. Re:Dead Operating System collection by zmalone · · Score: 1

      A rumored version of AIX? It most definitely exists, however, it only runs on MCA machines, last I heard. Ask around on the appropriate newsgroups, someone will have a copy of it.

    4. Re:Dead Operating System collection by dsyu · · Score: 1

      Yep. A few years ago someone (I think it may even have been Dr. Dobbs or something similar) put out a CP/M CDROM that had both the OS and pretty much everything ever written for it on one CD. At least I think it had the OS...a quick Google search turns up something from Walnut Creek Software no longer available (http://www.euronet.nl/users/fvempel/walnut.html). Oh well. A Xenix CD would be cool, but yeah, I doubt one exists.

      I guess I have old Win3.1 on a CD too, but dunno if I really consider that an OS. I've thought about adding old CDs of Netware 3.X or the like, but I guess technically newer versions of Netware are still available from Novell, so it doesn't really meet my definition of a dead OS. Probably ought to :-)

    5. Re:Dead Operating System collection by Anonymous Coward · · Score: 0

      I have an OpenStep for Intel/Mach kit here, but it's still worth money so you can't have it.

    6. Re:Dead Operating System collection by steve_l · · Score: 1

      I have a windows 3.1 Beta disk set from MS: on five and half inch floppies. Not brought it up recently.

    7. Re:Dead Operating System collection by steve_l · · Score: 1

      thinking about it, my old OS museum is actually my collection of dead OS style guides

      IBM CUA (came with windows 3.0 SDK)
      HP Newwave (wow)
      Sun OpenView (not bad)
      Motif (it should have died by now)
      Win95 (ditto)
      and my most unique
      -Penpoint

      there is something poignant about all these screen shots and style guidelines for programs that were never written. Or in the windows case, the gulf between the guidelines and the crap that MS wrote themselves.

      I'd like to get hold of a copy of Sun NeWS UI guidelines or the like, if anyone has them around.

    8. Re:Dead Operating System collection by Te1waz · · Score: 1

      DR DOS 6. with Novell Netware light bundled

      This is not so much a dead operating system but a murdered one.
      Win 3.1 real didn't like running on top of it.

      --
      From my Autobiography - "Lifestyles of the Sad and Desperate"...
  39. 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.
  40. at&t releases new "unix for windows" by Anonymous Coward · · Score: 0

    holy shit:

    http://www.research.att.com/sw/tools/uwin/

    who else knew about this?

  41. L O V E by dbretton · · Score: 0, Offtopic

    I like to eat my own scabs.

    1. Re:L O V E by Anonymous Coward · · Score: 0

      mmmmmm...

      crunchy

    2. Re:L O V E by Anonymous Coward · · Score: 0

      fuck yeah!~!!!!!!!~~~

      THIS FUCKING CAHNNEL == OWNAGE

      ANY MOTHER FUCKER up in this bitch get FUNKY WITH THE Wrecking Crew STEP D0WN

  42. Re:SCO is dead by Anonymous Coward · · Score: 0

    free software unemployed?

    Thats what I want to know!

  43. 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!
  44. 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

    1. Re:ransom note by Billobob · · Score: 0

      No, it's more like: You have no chance to survive make your time HA HA HA HA ... Toodles, Cats

      --
      If you have to ask, you'll never know.
  45. Re:Here's a thought. by k0osh.CEOofCLIT · · Score: 1

    too bad you weren't logged in like the elite trolls

  46. Re:SCO is gone - Huh? by Anonymous Coward · · Score: 1, Informative

    SCO UNIX did not suck and was an extremely stable UNIX(tm) for the Intel platform. It was an AT&T variant and was aien to a lot of folks who were BSDers. Suck it did not as long as a competent person admin'd it. It once had a emulation layer that allowed Win 3.x to run with all the apps. And STABLE. Xenix which was an M$ bastardized offshoot was a bit unstable, but worked just fine. I coded a lot of apps and admin'd on both SCO products. I saw my first Xenix running on an i286 with 3 meg of RAM and 10 meg of disk. It will be missed.

  47. 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 e40 · · Score: 1

      Huh? How did they "write their own" by taking doing a (tags-query-replace "BSD" "SunOS") in GNU Emacs (which did exist at the time)??

      I don't know what you're smoking, but it must be good.

    2. 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
    3. Re:Not well known by Anonymous Coward · · Score: 0

      DOMAIN/OS wasn't UNIX (it was based on MULTICS) but it offered SysV and BSD personalities in addition to its own. See http://personal.nbnet.nb.ca/mclays/domainos.html .

  48. Re:SCO is dead by shuffle40 · · Score: 1

    Explain why the project I develop for has SCO Openserver running on $35,000 workstations then?

    You'd be surprised who uses it and how much it is still prevalent...

  49. 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.

  50. slimy tactic by Caldera by Anonymous Coward · · Score: 0

    If this is true, this is just not good free source ethics. But what else can you expect from a linux company? No wonder linux is dying. Long live BSD!

  51. Strawberries work too by Anonymous Coward · · Score: 0

    They can really clean you out and help when you are having problems

  52. Re:Linux? by Anonymous Coward · · Score: 0

    And I suppose you typed this up on your WinME box that mommy bought you? The same box where you tried 20 different times, losing all of your data, to install mandrake linux?<BR><BR> Who is the loser?

  53. Good Ridance by jschmerge · · Score: 1
    Good ridance to the legacy of Xenix.

    Thank God!

    Just my $0.02

  54. Re:This is for the FBI by k0osh.CEOofCLIT · · Score: 0, Flamebait

    you would correct sir! i will violate you and your body will rot! rot! rot! shout outs to the EFF BEE 3y3, SEE iEEE EH, IN SSS 4

  55. "SCO UNIX" not OpenUnix by cant_get_a_good_nick · · Score: 1
    To the comments on "Die XENIX Die", OpenUNIX is NOT tho old SCO code base.


    OpenUNIX 8 is basically UnixWare with Linux binary support and some new driver stuff in it - SCO has been a supporter of Project UDI since the beginning, and this is there new kernel Device Driver Interface.


    The old SCO 5, SVR3 based, file system symlinked to an ounce of it's life code base is called OpenServer. Still being sold, though I bet it's had a fork stuck in it for quite some time.

  56. Re:ScoAdmin Redhat equiv? by bruceg · · Score: 1

    I agree. I would love to see something as complete as scoadmin on linux (redhat). You could configure just about everything from the command line, now all the RH utils are GUI based, requiring X11. It was nice to be able to ssh into a SCO box, and configure a printer. linuxconf had a text based interface, but it is no longer present in RH 7.3. What happened? What is a good text based config utility for RH (besides vi)?

  57. Why didn't you Format And Reinstall? by mangu · · Score: 1

    When all else fails, the Standard Solution For MS-Windows Problems works for Linux as well.

    1. Re:Why didn't you Format And Reinstall? by devnullify · · Score: 1

      What differs between the two is that it is almost never necessary on Linux.

  58. I hadn't heard about SCO before today, regardless by Anonymous Coward · · Score: 0

    SCO Openserver is dying

  59. Re:ScoAdmin Redhat equiv? by bruceg · · Score: 1

    Well, I did find:

    /usr/sbin/setup

    but that's still a far cry from scoadmin. Maybe I'll stick too vi, and editing files, and restarting services. At least with that method, if you break something, it's your fault, and not the admin tools fault (or bug, like a lot of the linuxconf modules)

  60. This calls for a wordplay.. by distributed.karma · · Score: 1

    United Linux == Limited Unix

    --

    --
    If you moderate this, then your children will be next.

  61. OpenServer's days were numbered anyway by dokhebi · · Score: 1

    As much as I like SCO OperServer I knew it's days were numbered when SCO acquired and updated Unixware. But not porting OpenUnix (the successor to Unixware) to the IA-64 plaform is a big mistake. It will mean that the AT&T source will not be represented on Intel's new processor.

    1. 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
  62. 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.
  63. Oh boo hoo. by Anonymous Coward · · Score: 0

    Here's a hint, Timothy: SCO UNIX is CRAP. I've been waiting YEARS for this pile of bitrot to die. YEARS.

    SCO is/was the bastard runt of all UNICES. There is practically NOTHING good I can say about it. It is clunky, ugly, unstable, has a TERRIBLE TCP/IP stack, and was formerly owned by a bunch of idiots. Yes, idiots. I've dealt with SCO. They were clueless.

    Say what you want about other unices...AIX had a wierd interface; HPUX was for some reason reviled by many (although 9.X and up were really nice); Ultrix was well..Ultrix; and Solaris 2.X was a painful change from the old BSD core. All teething pains aside, each one of these could be reliable servers. Even AIX made -sense- at some sick level. But SCO? Good god.

    Good riddance to SCO unix. It's been long overdue.

  64. My Name is my Handle.... by humungusfungus · · Score: 0, Offtopic


    Okay, I hate to regress towards Dude Mentality, but I have to say it: Ransom Love is pretty much the coolest frickin' name I have ever heard. Period.

    --
    No sig.
  65. 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
  66. 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).
  67. Re:SCO is gone - Huh? by jazzydnb · · Score: 1

    SCO sucks, end of story. Give me Solaris, Tru64 or even IRIX for that matter before you give me a crappy SCO box to admin. Of course Linux is a given, but even Windows would be better than SCO.

  68. So? It won't be the first Unix to go away by bafu · · Score: 1

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

    Assuming it does actually go away at some point, so what? If you were to tell me that it was your favorite Unix I'd probably feel more sympathy (tempered by a lack of respect, of course ;-) ), but the fact that it was your first is no biggie. If it's any consolation, if it goes it will be in fine company. Version 6 Unix and SunOS were two that I'd liked that aren't being produced anymore. While I have very fond memories of playing with them, I would not trade what I've got now for either...

    And, guess what? I'll happily kick what I've got now to the curb when a better *nix comes along... ;-)

  69. Nobody but a full monopoly buys to destroy by Anonymous Coward · · Score: 0

    It's really simplistic to say Caldera bought SCO to do anything but build it into a money maker. You just don't spend that much money as a relatively small company to do something destructive with what you just bought.

    Caldera has been in a real fix they've not been able to turn SCO and their closed source holdings into something that people value more than open source linux. Give customers a choice "Pay for Unix or get it for free?" what do you think they chose??

    The combined Linux distributions have to find some sort of exclusivity to keep their service and corporate support model. While I dont think they are doing everything they do to compete with Redhat they are looking for ways to make themselves (the joined companys) more competative in the same market.

    If there is a competative advantage to porting SCO to 64bit systems that will be done, but not casually and not lightly. Dont forget this is closed source developement that is very expensive. If there are things in the closed source codebase that are good contributions to Linux expect that they will be sold\rented\or high profile given to turn them from dead assets to working ones.

    I dont imagine much will be announced until after Linux tests the 64bit waters and proves them profitable and popular.

    It is in everyone's best interestes for Good code not to die but go to the great CVS in the sky.

    For the record, I think Suze and Caldera will make a special kind of powerhouse. I hope they open up some markets in N.America and England.

    I'm very hopeful at the prospects of some very good software.

    Suze makes great distros and Caldera has some very good support stuff. The four companies will have the kind of diversity of outlook and geography that might make some really first rate software.

    Bo

  70. *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 ...
  71. Re:The Secret to Better Bowel Movements by Anonymous Coward · · Score: 0
    When I get constipated, I just ask Hemos to give me a warm yogurt enema. It's the shit.

    -- Robert Malda

  72. Re:Linux? by Anonymous Coward · · Score: 0

    Based on your inclusion of HTML tags in your text formatted post, I'd say the loser is you.

  73. SVR4 is dying! by Anonymous Coward · · Score: 0

    Its true! According to this Netcraft report SVR4 is dying!...

    blah blah blah. Why didn't someone else think of this? Can the BSD is dying troll change for one day?

  74. Slashdot editors strike again by Simon+Garlick · · Score: 1

    Timothy, did you actually READ the article?

    "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. "

  75. 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
  76. Untied Linux by PrismaticBooger · · Score: 1

    Well, what's to stop other party from creating a binary distribution? Called, say, "Untied Linux".

  77. Wish they would open some SCO source by LunarOne · · Score: 1

    if they haven't already, why couldn't they open up something old, like SCO UNIX 3.2 v4.2 or something like that. Just a thought.

    --

    Read my sig if you like, but I'll never see yours, thanks to Discussions, Viewing, Disable sigs...
  78. everybody knows... by smash · · Score: 1
    "Just say no to SCO!"

    :P

    smash

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  79. Everyone knows SCO sucked, but.. by Anonymous Coward · · Score: 0

    ..Does anyone remember the FUD they used to spread against Linux?

    I think that I'm going to go have some random love to celebrate SCO's demise. :p

  80. Re:Here's a thought. by whirred · · Score: 1

    I know that was a blatant troll, but it honestly made me laugh out loud. Very well done.

  81. geos by Anonymous Coward · · Score: 0

    Around the windows 3.0 time there was a very good GUI for XT / 286s that ran really fast with a full suite of office apps called I think it was called geos.

  82. Doesn't matter... by Anonymous Coward · · Score: 0

    Caldera will also be no more soon.

  83. I administered SCO, it sucked. by Improv · · Score: 1

    Dirty laundry list:
    Terminal settings
    Two seperate, incompatible package systems
    Crazy symlinks
    Root's homedir is /
    Nazi license manager

    --
    For every problem, there is at least one solution that is simple, neat, and wrong.
    1. Re:I administered SCO, it sucked. by Trepalium · · Score: 1

      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

      --
      I used up all my sick days, so I'm calling in dead.
    2. 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.
    3. Re:I administered SCO, it sucked. by maxII · · Score: 1

      Perhaps it wasn't so much that you had to reboot but that it didn't know what to do to fully update the system to changes you make in scoadmin (network manager for example). In many cases you could continue without rebooting but just stopping and starting networking and services.

      But yes, I agree, it sucks, and there's many more things wrong with it than that.

      However it has been very stable for the dozens of servers I admin, and only the same few bugs pop up usually, and they can be permanently worked around.

      Another big problem seems to be that hardware vendors aren't supporting SCO systems anymore, in fact I might note that some have been given a big "SCO Certified" tick to hardware that has no drivers (particularly for OpenServer).

      I suggest looking immediately for an alternative or upgrade paths in case your current hardware dies.

  84. Then really UNIX is going away by Hugonz · · Score: 1

    After all, this was the only POSIX/UN*X/OS that could bear the name UNIX. Everything else is called something else: Solaris, AIX, Linux, BSD...

  85. Only about 8 Itaniums have been sold by DABANSHEE · · Score: 2

    So its no big market loss.

    1. Re:Only about 8 Itaniums have been sold by Anonymous Coward · · Score: 0

      ...and that's why the "Itanium II" is right around the corner... Intel never expected to sell volumes of the Itanium, especially since Microsoft still hasn't released a full-version of Windows for it. So if you want a PA-RISC (Itanium not very far removed) to run Unix, why not just buy it from H-Paq...

  86. Re:SCO is dead by mongoks · · Score: 1

    What is it doing on these $35,000 workstations? Why does the application require SCO vs. Solaris, Irix, etc.?

  87. 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

  88. Not A Compensated Endorser .... by ejecto · · Score: 1

    We've been running SCO for 6 years in over 700 locations and we've never had a problem with it. We use Virtual Disk Mirroring to do software disk mirroring, and AFPS/LMC which allows us to communicate to the Windows boxes in our environment. There still is an emulation layer (called Merge) which allows you to install and use Windows and Windows Apps on the SCO box. The bottom line is that for us, it's always been easy to use and administer.

    Unfortunately, the writing is on the wall and it's only a matter of time before Caldera sucks the life out of SCO and gets rid of it. When they do, I too will mourn it's passing.

    1. Re:Not A Compensated Endorser .... by rmadmin · · Score: 1

      If I remember correctly, all the pizza hut stores used SCO... Just because it doesn't have mainstream interest doesn't mean its dead.. I'd run SCO on all my boxen if I knew how to admin it. Why you ask? Security through obscurity. How many SCO sploits do you see? Of course I'm sure their are a few floating around somewhere, but the generalized script kiddies won't find them easily.

    2. Re:Not A Compensated Endorser .... by Anonymous Coward · · Score: 0

      Merge is available for Linux aswell, it's called Win4Lin then.

      Rickard Osser
      ricky@osser.se
      www.lindist.se

    3. 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)...

    4. Re:Not A Compensated Endorser .... by maxII · · Score: 1

      Ummmm have you bothered to look? It has extremely poor security, I maintain dozens of SCO OpenServer boxes and am very unhappy with it.

      Off the top of my head, search for scosessionx hack. There were around 50 exploits all released around the same time for 5.0.5 and many unfixed before 5.0.6.

  89. Shouldnt they release its last release as opensour by mnmn · · Score: 1

    Open UNIX can join the ranks of FreeBSD and linux. I know I would develop for it. There would be nothing like a free OS that can officially and openly be called UNIX.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
  90. Re:SCO is dead by Ilgaz · · Score: 1

    Damn I couldn't stand... You seem not following slashdot lately.

    Cray=Dead (replaced by beowulf)
    SGI=Dead (DirectX and Nvidia rawks)
    SCO= Yea, NASA and huge networks use it but I can't buy it for my home, so its dead.

    and so on. Oh, Novell is dead too!

  91. Re:SCO is gone - Huh? by Anonymous Coward · · Score: 0

    dude.

    Linux is for bitches....

    ...and you sir, are a bitch.

  92. IA32... by Anonymous Coward · · Score: 0

    IA32 may be around a long time, but how long will it be before you can't buy 32 bit processors, except for embedded work, any more?

    Anyone willing to bet on when "Circuit City" ships it's last 32 bit machine?

  93. Re:ScoAdmin Redhat equiv? by Anonymous Coward · · Score: 0

    Try using linuxconf. It has both a text mode interface and a GUI

  94. Re:SCO is dead by broody · · Score: 1

    Who needs another x86-based Unix at this point?

    Common Criteria environments x86 Unix options are fading fast.

    --
    ~~ What's stopping you?
  95. 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.
  96. The only thing worse than SCO Unix was SCO Xenix.. by Anonymous Coward · · Score: 0
    My mind still has the scars from trying to do image processing on a 286 box running SCO Xenix, with all the attendant "huge far pointer" crap.

    Well, I guess intel is somewhat the blame for that.

    I've got an idea that will twist the programmers brains! Lets set things up so that with long addresses, the control bits are in THE MIDDLE OF THE 32 BIT WORD. What a nightmare.
    -- ac at work
  97. Random Notes by Anonymous Coward · · Score: 0

    I cannot help to think that Random is the thorn of Linux's undoing. Every time that there is solidarity in movements, Random seems to divide it for his own self interests.

  98. Re:ScoAdmin Redhat equiv? by bruceg · · Score: 1

    I have had bad luck with linuxconf messing up settings, and then having to go in with vi to fix the config files. It would be great if linuxconf was bug free, since I would prefer to use it.

  99. Off topic, yea, yea, blah, blah by soybean · · Score: 1

    Help me out here. Wasn't there some sci-fi book from a few years ago with a villan named Rasom Love. Somthing about finding life inside of black holes. There were people living in every corner of the solar-system where they had adapted to the habitat. Damn my memory is not helping me much.

  100. Re:SCO is gone - Huh? by lostGeek · · Score: 1

    I agree, SCO Unix was / is great. It was very stable so stable in fact that many voice systems ( PBX, Voice Mail, etc ) use it as the base OS.
    Too bad it is going away.

  101. Did you Know? (To make things worst) by Anonymous Coward · · Score: 0

    Where I Work we still use SCO Unix and Openserver strongly and you know what? When you log in some part of the screen reads this:

    (C) 1980-1994 Microsoft Corporation

    Sad but True.

    Damn, after reading all the titles of the posts for this rant I feel like a jerk for Learning completly the 2 SCO TCP/IP manuals that came with the OS software.

  102. Re:SCO is gone - Huh? by Anonymous Coward · · Score: 0

    Solaris is actually a port of UnixWare to the sparc operating platform. So, if SCO sucks so much, why do you like solaris?

    -AC

    I wish everyone knew as much as I do. :)

  103. 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...
  104. Stuck on the old Unix until Linux grows up by Maxwax · · Score: 1
    For all the negative comments that can be said about SCO Openserver, this is one solid Unix system. I run five production systems on it and sudden, surprising crashes or other problems just don't happen. Not at all.

    This means I can concentrate on writing new software or other activities instead of babysitting an unstable operating system.

    I'd like to say the same about Linux, but Linux is changing too much. For example, my SCO Openserver systems were last reinstalled with a major hardware upgrade 2 years ago. I've gone through 2-3 versions of Redhat in that time, from 6.2 to 7.0, and then to 7.1, 7.2 and now 7.3.

    I _love_ my Redhat systems, but the constant changes in the Linux community on the kernel level, the application level, and the distribution level make it very tough for anyone to pick a version, stick with it and gain confidence. This means as my Openserver systems go on for longer without problems, they gain my confidence and raise the bar as to OS quality. And each time I try a new Linux kernel, a new distribution level, I'm starting over and wondering what surprises I might have in store for me.

    I'm hoping that, for me, Redhat 7.3 will be a strong, solid release and that combined with the 2.4.x series kernels slow and cautious development cycles, those of us that need to demonstrate long term stability will be able to deploy, test and enjoy.

  105. Sad but true ... by puppy0341 · · Score: 1

    $ HEAD http://ir.caldera.com/stock.cfm
    200 OK
    Date: Fri, 31 May 2002 23:53:38 GMT
    Server: Microsoft-IIS/5.0
    ...

  106. Mod tricks (Was: Differently Colored Virt. ...) by Anonymous Coward · · Score: 0

    Nice job fooling the moderators. +4 is pretty impressive for a hoax. If getty, mingetty, or even mgetty had a -I option, your idea might work, but it doesn't! Come-on moderators, use a little common sense. If it looks too good to be true, then it probably is.z

    1. Re:Mod tricks (Was: Differently Colored Virt. ...) by markus · · Score: 1
      I hope I am not just feeding a troll here, but the poster is right in so far as that different versions of getty obviously do have different options.

      I guess, I should have pointed out the distribution that I tested this on. This is for Debian Linux. The current release of util-linux is 2.11n, but as far as I remember the -I option has been there for ever. I did check, and it seems that Debian's getty program is based on agetty; so there is a chance that there are other versions of getty that have different command line parameters.

      Since you said that you have access to mgetty I can make a suggestion that might work for you (I haven't tested this myself). It seems that mgetty can take a -i option to override the /etc/issue file that is displayed before prompting for the user's id and password. If you create seperate issue files for each virtual terminal, you should be able to stick the different escape sequences into these files. This is admittedly not as elegant as the original solution, but it should achieve the same effect.

      In the future, it might help if you didn't complain, but rather replied with a question asking why you had problems replicating the configuration on your system (and please tell us, which distribution you are using). Before your next post, you might want to consult the Smart Questions FAQ. Oh, and please do let us know if my suggestion for mgetty worked, or if you need additional assistance.

  107. Re:SCO is gone - Huh? by Not+The+Real+Me · · Score: 1

    Wrong!!!
    Solaris was originally derived from BSD.

  108. Hold the phone by asdfx · · Score: 1

    Wait wait wait... Microsoft made a flavor of unix
    and it sucked? But, they are infallable!
    Just look at Windows ME; they are just one
    quality product after another.

    But, seriously, no one is buying or supporting the IA-64
    from what I've seen; why would Caldera waste their
    time with it?