Slashdot Mirror


Does Unisys Really Get It?

Joe Barr writes "There's an interesting story on NewsForge today about Unisys and its new-found love for Linux. In the story, Robin Miller interviews Unisys VP of engineering Anthony Gold and asks such delicate questions as how Unisys 'planned to make amends for its use of GIF patents against open source projects'? It's a good read, and in this day and age of software dinosaurs trying for peaceful co-existence with Linux, a very timely one."

63 of 253 comments (clear)

  1. Patents by Anonymous Coward · · Score: 5, Funny

    Let me guess... they're embracing linux and having 50 developers workingg on it as a place to embed submarine patents?

  2. Gee... by Anonymous Coward · · Score: 4, Funny

    Is Unisys still in business? They were so clueless, they didn't realize "The power squared" means you have less of a company then when you started when you take half a company and square it!

  3. survival by bandy · · Score: 4, Insightful

    Unisys is trying to survive any way it can. They are a dying dinosaur of a company who has always dreamed of being IBM.

    --
    "You might as well get your son a ticket to hell as give him a five string banjo." -unknown minister
    1. Re:survival by Sirwar · · Score: 5, Interesting

      You could definately say that. I work for Unisys, and they are moving towards a more 'service-based' business model. Like IBM, they provide a 'solution', not just a product.
      They find out what you need, they either make or buy a program, install it, support it. Buy the hardware, install it, support it, etc.

      While it is trailing in IBM's shoes, its not a bad business model.

      Now Unisys is still pretty big, but we did miss expectations for the first time in 4 years, and the stock price dumped, its now ~$9. And our stock is considered 'moderate gain, low-risk'.

      Still, I'm new here, so I don't have much info on the "why's" of GIF.

    2. Re:survival by Performer+Guy · · Score: 2, Interesting

      Missed expectations? That may have to do with your gif patent expiring and your corporate pigs getting their snouts pulled out of everyone elses troughs. Life is tougher when you have to earn your cash instead of raking in millions for bupkis through legal extortion.

    3. Re:survival by toxic666 · · Score: 2, Interesting

      You work for a company that is miles behind and has a culture that is out of touch with the kinds of clients it needs to grow -- private enterprise. Unisys has never adapted to cultures that are anything but huge bureaucracies, and that is not where the new investments the company needs will come from. Basically, they have all the government -- megacorporate contracts they will ever see and are not going to win new ones; they are not tolerated by companies where rapid solutions, fast and intelligent responses matter.

      Not that I'm questioning your qualifications, but I have a cousin who works there, too. The toughest question he had in the interview was "tell me how to improve server performance." The intelligent answer is a dissertation. His response "add more memory or buy a new server" was considered right on the mark. Yeah, don't benchmark the subsystems to identify the bottleneck, tell 'em they need a new server.

      That doesn't cut it when the competition is IBM, with more experience dealing with real business and a 6-year Linux head start. Polish up the resume, because your co-workers do not have the skill sets to compete.

    4. Re:survival by Anonymous Coward · · Score: 5, Interesting

      I have long years of experience with Unisys, back from the time they actually created fine technology (only way, way overpriced). Actually, I started working for them in the early 90s, about the time they started to devolve from a technology company into a "systems integrator", as they like to put it. I did a couple of small chores on series A equipment, but most of my work was done on the x86 BTOS, then CTOS, machines.

      (Those were beautiful machines, by the way. You extended them by daisychaining "blocks" into a bus that started from the CPU and grew to the right. E.g., you snapped in a SCSI disk block, a video card block, etc., all without having to open the case or fiddle with cables. Your workstation just grew longer and longer with each hardware expansion---mine was just under a meter long. You created native "LANs" (called "clusters") daisychaining stations using the dual "cluster ports", zero configuration required. And every machine included high speed synchronous serial ports. Also, they had a really stable OS, I never saw a single crash. It was a bit weird, but in a creative, interesting way. Probably had to do with the mainframe background of the company, because it was completely different from UNIX inspired OSs. This thing was even more alien than the original MacOS. The text editor was lovely. One of my first Unisys workstations was a B28, which sported an Intel 286 @ 8MHz and a whole two megabytes of RAM, IIRC. I also remember using an Intel 186 processor on some BTOS box---yes, it really existed, it was sold, and used.)

      Unisys management was never too bright, their pointy-hairness surpassed only by that of Commodore execs, IMO. And when they dropped their technology division, they fired almost every engineer. At least I can personally attest that every friend of mine that worked there, and knew two things about computers, was fired or left on his own. The execs and the salesmen stayed. Maybe they kept a couple of smart techs in Atlanta, but from what I've seen, from then on they've been hiring only inexperienced technical people (read: cheap interns) for when a project plan calls for that, and they fire them as soon as possible afterwards. And I've seen them blow projects, or lose money in penalizations, because they lacked competent techs to do the work, or even to timely warn their salespeople that they were being sold, and in turn selling, snake oil.

      Today Unisys, the technology company, has been dead for over a decade. It is a company of salespeople, and they mostly trade with the Unisys name. You know, they deal with banks and airlines and the likes, customers who were buying Unisys stuff three decades ago, and still regard them as the company they used to do business with. They sell expensive software they buy from other companies (Microsoft being a major supplier, indeed), or consultancy projects where they hire experts in the market just for the event. And yes, the name is eroding, even as we speak. And there's not much left of it, again IMO.

      That "ES7000" thing, well, it's a PC with 16/32 processors, large and ugly as a fridge, and it runs Windows. Which, by the way, does not seem to scale all that well on that many processors: I've seen several of those choke as application servers with just over 300 clients. To be fair, the application software was a hideous contraption that costs several hundred thousand bucks to license---so maybe the suckitude did not come from Windows entirely. Anyway, you may call the ES7K "innovative", but to me, having seen the stuff the old Unisys used to make, is only boring, and a bit sad.

    5. Re:survival by bonehead · · Score: 2, Interesting

      I also remember using an Intel 186 processor on some BTOS box---yes, it really existed, it was sold, and used.

      Yep, I'll vouch for that.

      I used to own an 186 upgrade card for an 8086 PC. It was an interesting little card. Had an 80186 processor on it, plugged into an ISA slot, and a ribbon cable that was terminated with a connector that plugged into the CPU socket after you pulled the 8086 chip out.

      I never got around to installing it, so I can't say how well it worked.

  4. But don't they have the way out? by Anonymous Coward · · Score: 5, Interesting

    Wow. This is the same Unisys as the "We have the way out" Unisys?...

  5. This is all a Microsoft plan... by tekiegreg · · Score: 4, Insightful

    Granted that Unisys makes crappy code (I cite the Bally Fitness credit card processor system built by them that 98% of the Bally fitness employees I've talked to complain about as proof, anyone who goes to Bally fitness might know what I mean).

    So in going open source, Unisys is planning on developing crappy code for Linux and souring the reputation of the OS everywhere. To Microsofts gain.

    To quote Admiral Akbar once again, IT'S A TRAP!!!

    --
    ...in bed
    1. Re:This is all a Microsoft plan... by logic+hack · · Score: 5, Funny
      anyone who goes to Bally fitness might know what I mean
      Have you forgotten where your posting to?
    2. Re:This is all a Microsoft plan... by Rosco+P.+Coltrane · · Score: 2, Insightful

      Is Linux truly a modern OS? Let's be realistic here.

      Is a Northstar engine a modern ICE?

      It's called modern because it's the same old stuff that's proven to work, yes, but with a lot of technical improvements and a solid helping of public perception dusting.

      And also, the real value of Linux isn't its technology or its architecture (god forbids), but in its community. That concept, in the scale it's applied in the free software world today, is quite novel.

      --
      "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
    3. Re:This is all a Microsoft plan... by tpgp · · Score: 4, Interesting
      Yeah, read about Unisys being sued by RACV for building a pile of crap


      Unisys stated that the response times, (which were instant at the demonstrations) were indicative of the performance that could be expected.

      Unisys' configured a system that was fraught with functionality and technical problems. Information sought by a RACV claims officer could often be contained on several discs and frequently response times would be at least 20 seconds.

      The system was, at one stage, no more than 30 percent functional and crashed on several occasions. Eventually the project was abandoned and RACV terminated the contract.


      I hate to admit it - I worked for Unisys (Australia) back in the day (and still know many people who continue to work there) - and although they treated their employee's very well - it was hell.

      They're so top heavy its unbelievable. They charge more then even EDS does, and the service levels you get frankly leave something to be desired.

      Thank God all their Patents from when they were a real (not a sleazy wintel) vendor in the 80s are expiring - without that teat to suckle upon, they should die a fast death.
      --
      My pics.
    4. Re:This is all a Microsoft plan... by fishbowl · · Score: 2, Interesting

      "anyone who goes to Bally fitness might know what I mean"

      Bally Fitness? The one that requires you to hand over your bank accounts so that they can charge you even if they don't keep up their end of the bargain?

      I had a sales guy repeatedly urge me to go to his club, saying that I could have a free this and a free that. Finally, because of his persistence, I visited the club. I didn't get to actually do anything except listen as he told me how great the club was, etc. Finally, it came down to this. If I wanted to use this club, I was expected to sign a long-term contract, and, get this, give them a bank account number so that they could EFT a monthly payment.

      I asked why they were unique in that they could not bill by monthly invoice, or why I could not take advantage of a pay-as-you-go scheme, say, by paying with a credit card for each visit.

      I wanted to leave already, and the sales guy physically placed himself between me and the door. He pushed me into a situation where I had to tell him that I would be outside the building within the next sixty seconds, or else I would be calling the police from his desk phone. It came to THAT, as if he somehow thought there was a possibility that I would still be willing to do business with this company!

      After that experience, I looked into Bally's and discovered, to no surprise, that MANY people have been fleeced by them. I also discovered that by simply re-enrolling part-time at my University, I could take advantage of vastly superior exercise resources, and even was able to receive inexpensive physical therapy when I needed it, including treatment by a well-known sports doctor!

      Crazy, that Bally's is. I can't believe that anybody is dumb enough to sign their contract.

      --
      -fb Everything not expressly forbidden is now mandatory.
    5. Re:This is all a Microsoft plan... by Anonymous Coward · · Score: 2, Funny

      I don't quite understand why your brother would even consider a heath club membership. I'm sure those bears provide ample exercise opportunities.

  6. Forgive em. by Anonymous Coward · · Score: 4, Interesting

    The .GIF dispute didn't do *that* much damage.
    If Unisys really is willing to peacefully co-exist with Linux/OSS, I say we let them.

    1. Re:Forgive em. by Tumbleweed · · Score: 4, Insightful

      One could argue the world actually benefitted from their greed - it inspired the creation of the vastly superior format, PNG. Thanks, Unisys! :)

    2. Re:Forgive em. by tarquin_fim_bim · · Score: 2, Insightful

      The .GIF dispute didn't do *that* much damage.

      It didn't do any damage to anything apart from Unisys' reputation. Everyone who cared just used PNG, and laughed everytime Unisys was mentioned. Would you invite a chainsaw wielding a madman into your house? No, you'd point him to the nearest Microsoft developers convention. Begone Judas.

    3. Re:Forgive em. by ScrewMaster · · Score: 4, Funny

      I not disputing your opinion since I agree with you, but I'm still waiting to see a madman being wielded by a chainsaw.

      --
      The higher the technology, the sharper that two-edged sword.
  7. Does the GPL protect against that? by Anonymous Coward · · Score: 5, Interesting

    Does the GPL protect against that? If Unisys contributes code with their own pending patents to a GPL'd work like Linux, would the GPL force them to give the Linux community the rights/license to those patents?

    1. Re:Does the GPL protect against that? by js7a · · Score: 4, Informative
      7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
      -- GPL
    2. Re:Does the GPL protect against that? by 0x0d0a · · Score: 3, Informative

      This is not true. The GPL specifically addresses patents -- it if you cannot grant all the rights under the GPL (right to produce derivate works and the like) you cannot GPL your code.

      That being said, it would still be a pain in the ass for the GPL-using world, since we'd have to go back and rewrite code, but there would be no liability for anyone other than the person trying to insert patent-infringing code.

  8. Coexistence? by Rosco+P.+Coltrane · · Score: 3, Insightful

    It's a good read, and in this day and age of software dinosaurs trying for peaceful co-existence with Linux

    They coexist with Linux the same way Ralph Nader coexists with Bush and Kerry: occationally he makes noises and sounds really serious, but ultimately he doesn't really matter...

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
  9. Re:Do slashdot editors read slashdot? by Carnildo · · Score: 3, Informative

    "Quite some time ago"? It's been less than two months!

    --
    "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
  10. My take: "You can't trust us." by dillon_rinker · · Score: 4, Interesting

    (edited slightly for format, but retaining ALL the sense of the original article"

    Q: "How does Unisys plan to make amends for its use of GIF patents against open source projects?"
    A: "No comment" [If they had plans to make amends, they'd share them.]

    Q: "Why should open source developers trust Unisys after the GIF nastiness?"
    A: "I can't comment on past activities. I can only talk about where we're going." [They refuse to apologize.]

    If a human being dealt with you like this, you'd be right to shun them. Why is a corporation any different?

    Take anything you want from Unisys, but don't expect anything good from them. They clearly understand the harm they did, and THEY DON'T CARE. They realize that they behaved badly, but THEY EXPRESS NO PLANS FOR CHANGING.

    OK, now that the first paragraphs lost my respect for them, on to the rest of the article!

    1. Re:My take: "You can't trust us." by Lisandro · · Score: 5, Funny

      a human being dealt with you like this, you'd be right to shun them. Why is a corporation any different?

      Actually, corporations are treated as individuals under US law, IIRC. So i'm shunning them. Keep your nasty GIF patents where the sun doesn't shine!

    2. Re:My take: "You can't trust us." by thogard · · Score: 4, Interesting

      Thats why a few years ago I proposed a AUGPL (Anti Unisys GPL) which explicitly excludes them from the normal GPLisms and requires they obtain a different license. After all they are happy to use my code without paying me but were willing to send me a letter asking how I was going to pay them for gif stuff. At the time I sent them a letter saying they weren't allowed to use any more of my code so they are still violating my copyright. Maybe this jerk can send me an apology letter if he's serious but like everything else they are are just following the herd of PHB playing buzzword bingo. If the open source community wants to fight these idiots who claim to be friends while stabbing us in the back, the next release of linux should have a paragraph saying that any company that makes threats over patent rights is not covered under the standard license. Had this been done a few years ago, SCO and Unisys would both be dead and buried by now.

    3. Re:My take: "You can't trust us." by Phleg · · Score: 2, Insightful

      At the time I sent them a letter saying they weren't allowed to use any more of my code so they are still violating my copyright.

      Sorry, you can't retroactively revoke the terms of a license, unless provisions exist in the license to do so. If you licensed them under the GPL, they can continue to use your code under the license you provided them.

      --
      No comment.
  11. Re:Do slashdot editors read slashdot? by angryLNX · · Score: 2, Insightful

    I don't believe that is what the editors meant--the fact that they DID put pressure on the open source projects because of using their patented technology shows how Unisys did not, in the past, respect the ideals of open source.

  12. Re:Do slashdot editors read slashdot? by nacturation · · Score: 2, Insightful

    And what does that have to do with this article? Nothing in the summary mentions Unisys currently going after GIF patent usage in Open Source. You should read it as:

    how Unisys 'planned to make amends for its [former] use of GIF patents against open source projects'

    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  13. The real question by Otter · · Score: 2, Interesting

    The real question is whether it is true (or whether Unisys believes it to be true, so it's really two questions) that convincing Roblimo and the "Linux community" that they have "truly seen the open source light" makes any difference to their mainframe business. Given how fueled Linux adoption is by word of mouth, maybe it is true, but I suspect companies realize that being perceived as "getting it" isn't quite as important as was thought in 1998.

  14. Dynamic partitioning... by cbiffle · · Score: 4, Insightful

    Most of the comments so far have been along the lines of "UNISYS IS TEH EV1L!!!" but I'll break from the trend.

    The dynamic partitioning stuff strikes me as very useful. I'm on some large Solaris machines here with static partitioning; if the Unisys boxen can shuffle CPUs around to adapt to load, that'd be pretty damn cool.

    They might actually have some interesting products to offset their general cluelessness.

    1. Re:Dynamic partitioning... by spinlocked · · Score: 2, Insightful

      I'm on some large Solaris machines here with static partitioning..

      Sun didn't make any domainable machines which aren't dynamic, unless not enough boards are present on yours. They're hardware domainable at the board level and at the Solaris level using processor sets or Solaris Resource Manager. Shifting CPUs around without some sort of hardware failure fencing is asking for trouble.

      --
      # init 5
      Connection closed.


      Oh... ...bugger.
    2. Re:Dynamic partitioning... by sparkz · · Score: 2, Interesting

      Sun don't have "static partitioning" - what could it possibly mean, anyway? SF3800+ (ie, all partitionable hardware) support DR, so, dynamic repartitioning. Shuffling CPUs around on demand can be scripted (eg, "I need 4 more CPUs at night for the backup server; give them back to the database in the daytime". It's not straightforward - it's a complex reorganisation of two systems - and being trusted to scripts. Not something I'd like to plan my business around, really. But if you're so short of cash for a few more CPUs to be worth the cost of developing (and testing and proving) some scripts to switch CPUs around, it's certainly do-able. Just very expensive, compared to buying a few more CPUs in the first place. Of course, I don't know your situation, but if it's something like my guess, then my initial response would be to buy more CPUs for the backup server.

      --
      Author, Shell Scripting : Expert Re
  15. Unisys = t3h sux by StandardDeviant · · Score: 2, Interesting

    Unisys sucks. I've known a number of people who've had to work there to make ends meet over the years, and to a (wo)man, they've all described it as a really toxic environment to work in, like a wanna-be EDS (which has been described to me as the 7th circle of IT hell).

    Frankly, without even needing to RTFA, unless something really unexpected is happening here, this is just another example of a crass, stupid company trying to cover itself in the magic pixie dust of Linux or Open Source in the pursuit of a stock price bump. It's easy to talk the talk, but few walk the walk.

    1. Re:Unisys = t3h sux by Anonymous Coward · · Score: 4, Interesting
      Mostly, unisys just runs like any other company. There are a few of top-level managers worried about their stock options, a bunch of lower level managers trying to get more stock options, and some engineering and developer types that just want to do some cool stuff but nothing can get done without manager approval. Just like any other big dinosaur of a company.

      Check out their 3d Visual Enterprise product. You would think that a 3D product would have some screenshots wouldn't you? Nope, it's just vaporware.

  16. No by DarkMan · · Score: 4, Informative



    No.

    That's it, really. Patents are out of the scope of the GPL. The only way they interact is that if you don't have the rights to disribute the source (e.g. by patent liscence), you can't distribute the the binary.

    It's oft talked about that patent might be a method of getting an end run around the GPL, and maintining restrictions on GPL'd code.

    1. Re:No by I_redwolf · · Score: 4, Informative

      Patents are out of the scope of the GPL but you neglect to make it clear. That patents themselves are a problem in software open or closed. Reading this one might get the impression that it's simply just a problem with FOSS when it's clearly a problem; period. So buying closed software with patent violations opens you up to the same legal aspects as getting free software with the same patent violations. Also while this is a discussion people also seem to be under the impression that they are protected from legal action if it's in closed software or that they can "give" their case to the offending closed software manufacturer. This is also wrong. If for instance Microsoft violates a patent in X software; you are also violating the patent and are liable.

    2. Re:No by Alsee · · Score: 4, Informative

      I think you are mistaken, though it not exactly the clearest portion of the GPL.

      7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

      Unisys would be prohibited from distributing any GPL code that contained patents not licenced for royalty-freedistribution by all.

      So for any GPL code Unisys distributes, the result would be two fold if they attempted to enforce any patents there-in against GPL users:
      (1) Their distribution of the code in the first place would in effect be copyright infringment.
      (2) Their attempt to enforce the patent would probably be estopped by the courts.

      ESTOPPEL:
      estoppel is one of those complicated legal concepts designed to prevent an injustice being done by the strict application of law. If someone states that something is so and, in reliance upon that statement, another person acts in a particular way, possibly to their detriment, then the person who made the statement is prevented, or estopped, from denying the correctness of the statement which they originally made.

      If Unisys distributes code containing a patent, and represents that as a valid GPL distribution, and you then use and further distribute that code while relying on Unisys's presentation that it is a valid GPL distribution, then Unisys cannot sue you when you beleive them and further distribute the code they gave you. Unisys would in effect have induced you to infringe their patent by effectively telling you that you were properly licenced. You relied on Unisys's word, and it would be manifestly unjust for Unisys to go back on their word and and sue you and profit from their own bad act.

      And yes, estoppel *may* at some point come up in the SCO case. They would claim ignorance and thus innocence of any knowing misrepresentation, which may or may not fly. However at this point the SCO case is pure contract dispute, and all of their hot-air about infringment has yet to see a courtroom. There is no need for (and no option to use) an estoppel defense unless they actually file an infringement case to defend against.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    3. Re:No by SQLz · · Score: 2, Informative

      Actually it does. Read the GPL and you'll see. If a company wants to distrubute code under the GPL, they cannot do so if the code is not 'royalty free'. I take that to mean if you embed your own patented code, you just released that patent royalty free into the word. This, is a good thing, since software patents are bullshit anyways.

    4. Re:No by DarkMan · · Score: 4, Interesting
      Unisys would be prohibited from distributing any GPL code that contained patents not licenced for royalty-freedistribution by all


      Not quite. Unisys would be unable to distribute GPL code that implemented the ideas covered by a patent, that they were aware of, and that the patent holder had denied the use of said patent.

      That is, if you don't know it's patented, you still distribute. 'Cos, like, otherwise we'd all be paralysed.

      If they own the patent, and then distribute GPL'd code, that's implicitly that the patent is liscenced under a liscence that allows the downloader a patent liscence suitible to fufil the GPL.

      Thing is, that's a liscence to distribute the code. Not use.

      See, funny thing about the GPL is that you don't have to agree to it to use the code covered by it. Actually, it's not funny at all, it's the norm, just years of (very porbably bogus) EULA's make that less clear. So all the GPL covers is distribution of the code.

      But, a patent requires a liscence to 'use' the patented invention.

      So, Unisys could do the following:

      1) Patent an idea.
      2) Impement the idea in code.
      3) Release the code under GPL, and not mention the patent.
      4) Let it grow.
      5) Point out that they only gave a patent liscence to re-distributed the code, not use it, and charge for it's use. Once it's popular.
      6) Profit!

      Any explicit mention of the patent would make the situation clear - either by explict licence, estoppel, or clear that you don't have that. No mention of the patent makes it really, really, hard. That's the first patent/copyright GPL hack.

      Now, consider what happens if they add a patented algorithm to a GPL'd codebase. The only liscence they can put the implentation under is GPL. But they can stick a patent liscence on top of thier implemention, that effectivly prohibits re-disribution by parties other than themselves. What happens then?

      Section 7 does not apply, becuase the condition is not _imposed_ on them - they have chosen that patent liscence. (Semantic's, perhaps. Still, that's one to be settled by the courts).

      So, they can offer it for download, and then anyone who does get the patented implementation from them can't redistribute. That's a second hack.

      Or, another option - offer a royalty-free liscence to use and redistribute the patented implemention (in effect, giving the implemention all the GPL-type conditions). Great, you think, and grab a copy, and modifiy and resdistribute.

      They then change the patent liscence. What?! Well, it's an explict liscence, and if it doens't say that it's irrevokable, or if it has a clause that lets them change it a bit, then tough. Estoppel doesn't apply - the terms were explicit, and clear.

      There are probably other hacks that can be applied in a situation with patents, but that's more than plenty to be getting on with.
    5. Re:No by Anonymous Coward · · Score: 2, Funny
      (2) Their attempt to enforce the patent would probably be estopped by the courts.

      ebusiness, ecommerce, and now estoping, will it never end.

      I can't wait for the apple version istop!

    6. Re:No by 0racle · · Score: 2, Informative

      This entire thread started with someone suggesting Unisys would seed GPL code with their patents. I think they know what their patents were.

      --
      "I use a Mac because I'm just better than you are."
    7. Re:No by Jah-Wren+Ryel · · Score: 3, Interesting

      All your examples are suspectible to the same end-run that LAME and the XViD guys use - source distribution. Source code is almost (not quite, but getting there) universally considered speech or in other words a communication between humans explaining how to implement something - no different from a paper or book that describes a process. Thus distributing source code for a program that when compiled and run would implement/violate a patent is not prohibited by patent law, at least not yet. I'm sure there are lawyers itching for a new clause about "contributory patent infringement" or somesuch nonsense.

      Note, this end-run does not protect the end-user who compiles and then runs the code, but hunting them down and extorting fees out of them is orders of magnitude harder and more expensive than doing the same for a nice big fat slow moving target like HP or IBM.

      --
      When information is power, privacy is freedom.
  17. Come on by Azureflare · · Score: 3, Insightful
    Unisys has GOT to be better than 30% of the projects on sourceforge.net

    Honestly man, when it comes to open source, the more the merrier!

    Besides we'll have lots of l33t coders to go through their code and make snide comments. I'm sure the devs at Unisys will die of shame, if they don't revise their coding practices.

    Or even better (this way no one dies) someone who's better can fix their code and submit it back to them.

    Wow, I love open source. Can you tell?

  18. we seek... peaceful... co-existence!!! by damaskr0se · · Score: 3, Funny

    plops out of cranium, scuttles away

  19. Large companies are not single entities by Performer+Guy · · Score: 4, Interesting

    Large companies are not single entities with a single thought process. It is understandable that a company can have multiple product divisions and multiple differing interests. That said they are run by individuals at the highest levels and owned in total by the same stockholders. What Unisys did was despicable, not only did they cash in on a windfall as a result of the incidental inclusion of a trivial compression patent in the gif image standard (which was never challenged in court), but they moved the goalposts throughout the lifetime of their extortion even threatening webmasters who used gifs while trying to license their 'technology' beyond the period of their patent. They got so addicted to their easy and unearned cash that they just couldn't get their snout out of the trough in the end as they sought more and more ways to exploit gif useage sowing confusion & fear as the did so, and little guys everywhere suffered. We can't stop Unisys using GPL'd code, but really who the heck cares, ignore them and certainly don't work with these rats. We know how dangerous a morally bankrupt company can be and the damage they can wreak on a nacent industry. Unisys gave us themselves as that example. They can't comment on past activities, but we sure as heck can and should and we can remember. What other weapon do we have against miscreants who act as Unisys has acted? Where is the incentive to behave better is anyone treats Unisys with anything other than contempt?

    1. Re:Large companies are not single entities by johnny_sas · · Score: 2, Insightful
      "Large companies are not single entities with a single thought process"

      But funny how when it comes to legal matters that might work out to its advantage, the whole company acts in unison... I mean, I didn't see anyone else from Unisys breaking away from the prosecution side and join the fight along with the defensive side.

  20. Useless-sys by toxic666 · · Score: 4, Interesting

    What can I say, they managed to pull off the only Y2K problem I encountered.

    Seems they had a "mainframe" Windows system that only their team -- of three clueless fossils -- were authorized to service. I gave them the minimum list of patches, and they certified the system Y2K compliant.

    Sure enough, on January 1, the system had WINS resolution problems and applications broke. So the system was reliant upon a kluge name resolution method that was -- you guessed it -- still on non-Y2K compliant SP3.

    Well, I confronted the three fossils when they finally showed up (January 3), and they told me I did not know what I was talking about, turned around and walked out. I yelled down the hall after them that I was going to report each of them to their supervisor and would go after their jobs. They weren't impressed and left.

    They must have gotten scared, because they came back 45 minutes later with coffee and donuts for the department VP, and tried to pin the blame on me. Well, the VP was a PHB-extrordinaire, but even HE understood only Useless-sys was authorized (under an expensive contract) to service the ancho -- er, server. He then invited me into the office to answer the charges they leveled against me.

    Two days later they finally patched the server, because "applying SP4 to an NT server is very serious business and requires a great deal of advanced planning."

    And this is the company you want to go to for a Linux solution? Umm, they have a long heritage of milking government contracts, but those worthless government contractor types are now the guys out there servicing businesses that rely on software to MAKE MONEY.

    No thanks. Even without the legacy of the gif shakedown, the company chased me away long ago.

  21. This is silly by crucini · · Score: 5, Insightful

    There's no point in applying some ideological purity test to Unisys. As Rob pointed out, they speak with forked tongue. Not unlike IBM, who claims to be investing billions in Linux, but recommends Microsoft ® Windows ® XP Professional and generally assumes Windows is the only OS on the planet when they're not putting on their Linux act.

    Unisys exists to make money, primarily by selling to big, dumb organizations that have a poor understanding of technology. If Linux is trendy they'll sell Linux. They don't care what slashdotters think. Nobody reading this will buy or recommend anything from Unisys, no matter how "nice" they act, because they simply inhabit a different sphere.

    This idea that Unisys "sinned" by asserting their patent rights and should now beg for forgiveness is childish. Companies are moving to exploit their intellectual property. Read Rembrandts in the Attic if you don't understand this trend yet. You think they're going to carve out an exception for free software, when that free software is being used by businesses to make money by infringing patents?

    Quit attributing moral good and bad to profit-driven companies. They are all essentially running the same algorithm.

    1. Re:This is silly by zulux · · Score: 3, Informative

      IBM, who claims to be investing billions in Linux, but recommends Microsoft ® Windows ® XP Professional

      All the desktop vendows have this boiler-plate phrase on their websites/advertising. When they put this in there - Microsoft gives them marketing dollers (read money).

      So what if IBM recomends XP for it's Thinkpads. They certainly don't recomend it for their POWER5 servers or mainframes - the places where it counts.

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    2. Re:This is silly by Spruce+Moose · · Score: 3, Interesting
      All the desktop vendows have this boiler-plate phrase on their websites/advertising. When they put this in there - Microsoft gives them marketing dollers (read money).
      The "marketing development funds" for the company I work for are so large that they are actually hiring extra people to make extra sure we are compliant with Microsoft's random demands.

      It kind of makes a mockery of the whole anti-trust thing. If you don't say "we recomment Microsoft AssHat 2.0" enough times you are effecively fined.

    3. Re:This is silly by jumpingfred · · Score: 2

      It won't be people who are reading slashdot instead of getting something useful done.

  22. ES7000s are not good by Saint+Stephen · · Score: 5, Interesting

    I worked with some ES7000s when I was at Microsoft. They are a NUMA architecture, and there is very, very high latency across the crossbars: a 32-way is basically 4 8-ways with a very, very, VERY VERY high latency interconnect between them. You need to partition your app so that groups of threads execute on an individual group of 8 processors, NEVER cross the crossbar, or perf blows up.

    Once you've done all that work to partition to only run on 8 CPUs, you might as well just scale out like Google does. You can't truly scale up.

    Of course things get better all the time, and maybe Linux will be a better NUMA os, but scaling up with Unisys is really just easier and cheaper to do with scaling out.

    1. Re:ES7000s are not good by Anonymous Coward · · Score: 2, Funny
      They will be happy to sell you some expensive performance profiling tools to help you analyze your performance problems and which will show you that it's your application's fault not unisys's hardware for not scaling.

      Actually, it kind of reminds me of Prime Computer from the late 70's/early 80's. They were so afraid of reducing sales from existing products that they wouldn't allow development of newer and faster products that would accidentally be cheaper and thus less profitable per unit.

    2. Re:ES7000s are not good by SuperQ · · Score: 2, Interesting

      yep.. i admin a 16-way ES-7000 system, runnin linux, with almost no help from unisys themselvs. We had ia32 machine running 2k datacenter, and it was a dog. we traded up (donation to my school both times) for a ia64 model, and told them that this time we wanted linux on one of the partitions, they looked at us funny, and handed us a "how to install suse" guide, and said "call suse"

      we ended up running RHEL 3 on the box, because of problems with suse. officialy supported my ass.

      Funny thing is, they sell the boxes as 32-way machines, but they're actualy pairs of 16-way machines, that fail-over to each other, because windows isn't stable enough to just run on one box.

      Unisys and MS are trying to break into the HPC market.. but it's just not working.

      (my opinions, not my employer, just in case my managment sees this)

  23. Unisys MCP, Windows, their mainframe environment by Anonymous Coward · · Score: 5, Interesting

    I "inherited" a unisys ClearPath MCP mainframe admin job and hated everything about it. They never used any "open" standards, and tasks as simple as telneting into the box was made mode difficult since the environment only accepted the "unisys telnet", a proprietary version of telnet, which you need to buy a client license. The CANDIE environment was horrible, and the MCP environment actually existed as a VM within Windows NT 4.0. The MCP environment used NT for hardware recognition, drivers, etc., so not only did you have the overhead of the Windows environment on the system, you had a VM which prescribed to this model. Everything about Unisys was about making money for Unisys. Documentation needed a license to download, pay-for-use transactions, thier vewsion of Cobol (which is actually Sperry-RAND COBOL), their print servers, etc. I'm getting the willies just thinking about it all over again.
    I wouldn't be surprised that Unisys would charge a transaction-based license for their Linux, or a Unisys-branded Linux licence (similar to SCO). Unfortunately, many East Coast (US) universities, especially in Pennsylvania, use their systems for accounting, grading, etc...

  24. Their Jet Blue ad was seriously funny! by the-matt-mobile · · Score: 4, Funny

    The marketing department at Unisys has a lot to learn. Last October, they ran an ad that said:

    We helped JetBlue Airways do something unique with their data: treat customers like people.
    Unisys
    Imagine it. Done.


    This wasn't a terrible ad, except that they ran it right after the JetBlue scandal. It was like they were completely out of touch with what was going on in the industry. I couldn't help but send them a little message asking if I could work for their marketing department, since there was no possible way I could do any worse than the one they presently have.

  25. UNISYS is actually an acronym by crimethinker · · Score: 2, Interesting
    When my former employer was bought by Uselessness in 1999, the word went around that UNISYS stands for "Unemployment Now Imminent; Start Your Search." Sure enough, within 2 years, Uselessness had slowly strangled the company to death.

    I do have a point here relevant to the current topic. In the "welcome to Uselessness" speech by the CMO (Chief Masturbatory Officer), he said all kinds of stuff about how the people were the real asset, and if they bought us just for the tech, well, there were easier ways to get our tech than to buy the company.

    Then they failed to back that up with any kind of actual action, and people saw how full of shit they were. Fast-forward one year, and a junior-level CMO is out there announcing the slow closure of the division. Allow me to quote Mr. Ch***: "I know it's a bad decision, but we're going to do it anyway." Wow. One year later, it was all over. (At least I picked up a several $K worth of software and hardware that was headed directly for the trash bin. Thank you, ebay.)

    So, based on their past double-speak corporate behaviour, of which I have been a direct victim, also remembering the GIF nastiness, I say, with friends like this, who needs enemies?

    -paul

    --
    Pistol caliber is like religion: everyone has their favourite, and theirs is the only right choice.
  26. Yeah by 0x0d0a · · Score: 4, Insightful

    See, the difference between corporations and a community of people is that:

    (a) There is no single atomic point where a "partner/foe" evaluation is made.

    (b) Communities actually care about percieved relationships and treatments, and have a long memory. Every bias and irritation from years of experience comes out, because there's no requirement to "present a corporate front".

    (c) If you have screwed people over quite a bit, you will pay for it for a long, long time in attacks, even when unjustified. Microsoft screwed a *lot* of people over for a long time (not that they've stopped). As a result, a lot of people really don't like Microsoft, and will bash them for anything they do (take SP2 as an example).

    This means that there is no "person" who Unisys can win over to win over the open source world. Not ESR, not RMS, not Linus, not Perens, Lessig or PJ. It will take a long time and a lot of nice treatment for a long time, and probably be very discouraging.

    If you want someone to support your platform, to write documentation for it and to avoid introducing compatibility issues, and they are doing this in their *hobby time*, then they have to feel rather friendly toward you. Unisys has spent years screwing people over in a rather unjustified manner. They wasted the time of *many* open source developers and users in the form of removed and disabled features, legal problems, anguished discussions, reformatting images, information campaigns, debugging software ported to PNG and other alternatives, and so forth.

    So, is it impossible for Unisys to get OSS people to like them? No. Are there people in the OSS community that don't have any problem with them? Sure. Is it going to be long, hard and expensive (much more expensive than all the money they got from the GIF licensing stuff)? Probably.

  27. dinosaurs? Please explain by swordgeek · · Score: 2

    Are you suggesting that Unisys is a dinosaur, or that any company writing not writing open source software is a dinosaur? The former I might agree with but the latter is just nonsense.

    --

    "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
  28. My wife got the ES-7000 sales briefing last week.. by novapyro · · Score: 3, Informative

    ...and found out you have to run Windows on the box as the primary operating system. I imagine that's why M$ isn't too ruffled by this. Linux can run on it on 4 or more of the processors, in groups. (I suspect "4 or more" requirement is due to the internal communications/synchronization buses.)

    Apparently the box management is run from within the custom windows apps, so it won't be pure native Linux, at least not soon.

    They say their market is datacenter server consolidation, specifically seeking situations where people want to move UNIX apps off old Solaris or HP-UX boxes onto a Linux box. Why anyone would do that by buying a box that comes with a built-in annuity to Redmond is a bit of a mystery. What's not a mystery is why Redmond wouldn't stand in the way of this effort. If it's successful (can't imagine it, personally) it would have the effect of putting compulsary Windows licenses into server rooms that might otherwise have switched to some more "pure" Linux install.

    My wife (a Unisys employee) was pleased they were trying, but not impressed with the effort.

  29. The "why's" of GIF by mwa · · Score: 5, Informative
    I remember.

    GIF was developed as an image format by Compuserve (I think). They used LZW compression, which was a Unisys patented compression algorithm, but they never notified, let alone licensed LZW. Unisys, being the mainframe shop it was, didn't even notice for a long time. When they did, they pressed the patent issue.

    The important point is that they didn't press the LZW patent because of it's use in GIFs, per se. They pressed it because it was an important patent to them at the time for other compression purposes. Unisys was big in air-traffic control and a variety of other communications applications that used LZW for dynamic, real-time, streaming compression (which is about the only application it was still good for when you look at the other algorithms available, even then). If they didn't press it on LZW in GIFs, they could have lost the ability to press it in those other lines.

    Remember that uncompressed GIFs did not infringe, they asked only for licensing on commercial use, and as the article states they did make not-for-profit licenses available. Questions like "What if a licensed program made the GIF, but I editted it with Gimp" made no sense to them. (Besides, Gimp didn't exist then either ;)

    I was a Unisys systems programmer at the time, and I didn't know much about "open source", so I suspect Unisys management didn't have much of a clue either. I seriously doubt they had (or even now have) any idea how the community reacted to that issue. No one ever really grasped that it was Compuserve's fault for pushing a patent encumbered format (with the patent held by someone else) as a "standard". Unisys was caught by surprise and acted in the way most any company would at that time.

    Times change. I learned about open source (and TCP/IP, and Unisys' brand new C compiler, and how a 36-bit word architecture complicates a C libarary implementation) by porting a subset of NCSA's httpd server to OS/2200, partially because the GIF issue introduced comp.sys.unisys to open source. (iirc, this was when Mosaic was the browser and the "graphical web" was barely graphical at all.) Some time later, Unisys demo'ed their ClearPath model for us and said "they were even working on a web server for it". I wasn't there, but a co-worker donned a medieval french helmet and said "I doubt if we're interested. We already have one, you see!"

    So Unisys and I went different ways (although I did get a "wayback-machine call" for Unisys help last week). I moved on into UNIX, self-taught by downloading Slackware and trying to get it to do anything on Token Ring. Unisys moved on to buy Burroughs and into the "datacenter push" of Microsoft. One of us apparently learns quicker ;) Still, the 2200 was seriously unstoppable from both a hardware and a software standpoint, and even attemting to use MVS or anything else on the "newer" IBM 390 made me want to run screaming to the hills.

    If Unisys has woken up, they have the potential to do incredible things with hardware and helping them release that hardware from the constraints of Windows is a huge opportunity for both Unisys and the Linux community. If the haven't woken up, then they will once the see what Linux can do on their hardware. I was on vacation when they demo'ed the ClearPath and heard I had already written a web server on their previous (non-Intel) hardware and the day I got back a Unisys SE was waiting in my cube to ask "how'ed you do that!". He was fascinated and ate up everything about open source I had to offer (sadly, not much at the time).

    Bottom line: What does it hurt us to give them a chance? If they screw up, it's going to be their fault. We've already shown that we can help any company that really wants to play nice. If we snub them for what we see as a past slight to open source, when they probably didn't know what open source was, we present ourselves as being petty about something that we still, as a community, fail to acknowledge was a situation not of their own making.