Slashdot Mirror


Novell Vice Chairman on Ximian, SCO

dotnothing writes "microsoft-watch.com has an interview with Chris Stone, who is the Vice Chairman of Novell. Stone says that Novell will be introducing a Linux distribution with Novell products and the Ximian desktop, but that they are not out to compete with Microsoft. He also expressed some gratitude to Red Hat for countersuing SCO."

20 of 228 comments (clear)

  1. Red Hat/SCO legal docs by viewstyle · · Score: 5, Informative

    Speaking of Red Hat -- SCO released some of their legal threats which I found to be entertaining. Excerpts are in this story...

    1. Re:Red Hat/SCO legal docs by RevMike · · Score: 4, Insightful
      Compilers don't always produce the same binary from the smae source.

      Besides the obvious issues - which compiler/linker, precisely what version, what patches, which static libraries, what versions, etc - there is also the issue of alignment. I've worked with compilers/linkers that would not zero out empty space within the created images. Therefore the binary image would contain random gibberish that happened to be in memory when the compile ran. Thus, the "same" binary could generate different checksums.

  2. not to compete with M$? by gurisees · · Score: 5, Insightful

    but that they are not out to compete with Microsoft


    so, will they install Ximian on XP?

    --
    ... information wants to be forwarded ...
    1. Re:not to compete with M$? by Havokmon · · Score: 4, Interesting
      but that they are not out to compete with Microsoft
      so, will they install Ximian on XP?

      Well, I work for a small company running Netware 5.1 and Win98 desktops. I'm looking into doing an LTSP+Mosix type setup, because we only use about 4 applications on older PII hardware.

      I'd hate to give up my Netware box, file permissions alone (Inherited rights/filters) are enough to keep me on it. Getting a seemless login (legally - I have an awesome NDS Pam module from France ;) from a Linux box would be awesome.

      So, no. In my case, they're not competing with MS, because MS isn't being considered.

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
  3. Right... by mschoolbus · · Score: 5, Funny

    "but that they are not out to compete with Microsoft"

    "Uh... Yeah... We want to sell this but, uh.. not a lot of it..." - Chris Stone

  4. Bet they hadn't thought of this by Sir+Haxalot · · Score: 5, Funny

    Stone: We are going to continue to push it. .Net on Linux is a great idea. We just hope Microsoft isn't against the idea.
    I'd 'just hope' Linux users aren't against the idea.

    --
    I have over 70 freaks, do you?
    1. Re:Bet they hadn't thought of this by Lord_Slepnir · · Score: 5, Interesting

      I don't see why they could be against this idea. One thing that keeps many people away from switching to linux is that there are a lot of products you can't get for linux that you can get for windows. By making .Net for linux, software makers can easily port products from windows to linux. If done right, it would just be a matter of compiling it on a linux version of .Net and including a .run file with the distribution CD.

    2. Re:Bet they hadn't thought of this by JanneM · · Score: 4, Informative

      You are right; the WinForms stuff, specifically are not only protected (AFAIK), they aren't even functional outside a Win32 environment (they more or less just wrap the Win32 api). Of course, that means a lot less than you may think. The portability is likely to be important mostly for server stuff, where you won't have an UI anyway. And as we've already been seeing, apps written under mono will tend to use GTK anyway.

      I don't really think the promise of portability bewtween Win and Linux is the important part of mono. It is rather that the system is a pretty clean, well-designed one. Also, it _does_ offer excellent portability between Linux versions - run the same binary on whatever distro, on whatever hardware. Redhat on x86, Linux on an iPaq, Debian on a Sparcstation, RH on an IBM s390 - it will just work, without recompiling or installation issues.

      The core of .net is a standard, and the IP is offered royalty free. MS is unlikely to be able to change that. Beyond the core, it would be nice to keep compatibility wherever it makes sense to do so, but if MS makes a fuss, just dump the pieces they want to keep to themselves. Mono doesn't live or die on 100% compatibility the way Wine does, for example.

      In fact, given Linux' steadily increased prescence as a server, if MS goes off and makes mono incompatible with their own version (whether by API changes, implementation secrets or licensing stupidity), chances are developers who use .net for server stuff will decide to use the mono equivalents instead (since they are feee to move over to the windows side). WIth enough mono deployments, MS may well find itself locked in from raising too much of a fuss. But again, the real benefit of mono doesn't lie there anyway.

      --
      Trust the Computer. The Computer is your friend.
    3. Re:Bet they hadn't thought of this by Lord_Slepnir · · Score: 4, Insightful
      There are three ways to get around that.

      (a) have some software layer that can use windows .dlls in linux, just like Wine. Software will be significantly slower, however.

      (b) have something that can compile .Net code the way .Net does, but uses Linux libraries instead. You'll get things to run a bit faster than option a, but it's going to be quite an undertaking to rewrite every microsoft library to be completly compatable with linux, especially the DirectX stuff. Wine has already done a lot of that, but thier windows libraries don't function exactly like the native windows ones.

      (c) Microsoft decides to open-source thier libraries, embraces linux. Then I'll be able to port my copy of Duke Nukem Forever to Linux. This will be the second largest article on slashdot that week, right behind the second coming of Christ.

  5. Don't buy SCO. by nuggz · · Score: 5, Insightful

    Don't buy out SCO, it is a bad investment.

    To buy SCO you would need a reason why this is a good use of money, to make them go away is probaly not a good use of corporate funds.

    Those millions could do a lot of legal fighting, or development, or even advertising. All with a better ROI then removing SCO.

  6. Yay! by donmiguel42 · · Score: 5, Interesting
    "We will have an Evolution-Groupwise connector."

    They aren't going to destroy Evolution AND they're going to make it work with GroupWise. Ahh... for those of us running Novell/Linux in the academic world who are getting rather tired of Microsoft's mafia-esque licensing tactics (software assurance, anyone?), this is great news. One less major hurdle between now and a Linux desktop rollout. Yay Novell!

  7. SCO Teleconference by jmkaza · · Score: 5, Informative

    This may be a bit off topic, but I didn't want to submit a story and have two SCO headlines in a row. Darl's holding a teleconference today to answer questions about the Red Hat suit. The press release is here.
    Call 1 (800) 238-9007 and enter 274040 as the access code.

  8. Re:This is why Mono is such a bad idea by KamuSan · · Score: 4, Interesting

    It's a bad idea.

    Remember OS/2? No? See? Nobody remembers OS/2 (Bill Gates quote!).
    OS/2 ran Win3.1 apps natively, so nobody wrote OS/2 apps, but Win3.1 apps.

    The lesson is that as soon as you support somebody else's standard, then nobody has any reason to use your standard.

  9. Re:This is why Mono is such a bad idea by alienw · · Score: 5, Insightful

    Why don't you people get a clue first? No underlying Mono infrastructure is threatened by patents, since ECMA requires that all patents be licensed at no charge, and .Net is standardized with them. There are a few pieces which could potentially be patented, but their removal would not significantly harm Mono. If Microsoft still hasn't sued the Wine project, there's a very slim chance they could sue Mono.

    Your other side of the argument is basically the "not invented here" thing. If Microsoft invented it, it must be bad for free software. It's not like Microsoft can force Mono to change its ways, so I fail to see your point. Mono is not a Wine clone, it's a development framework for Linux, one that could potentially be very useful for writing portable software.

    I don't see anyone here bitching about Java, even though it's also a similar, proprietary technology controlled by one party -- Sun. Hell, I would say that Linux is more of a threat to Sun than Microsoft. So why isn't Java a threat to Linux?

  10. Great exposure for Linux by lrandall · · Score: 4, Insightful

    This can only be a good thing. Despite what a lot of people say, Novell has lots of customers, and most are really commited to Novell products. Thus with them starting to move to Linux, and push it to their customers, we will see a lot of corporate Novell users switching to Linux. Novell has great tools for Windows, and if they port them to Linux (seems like they plan too), it will make convincing people to use Linux that much easier. PHB's still love to pay for software, let them pay for Novell Linux

  11. 10 years later by Anonymous Coward · · Score: 5, Informative

    I found this bit interesting:


    Microsoft Watch: Now that you are buying Ximian, will Novell offer a Linux desktop distribution?

    Stone: Yes. The plan is to package the Ximian desktop with some of our products. Specifics are yet to be determined. But we want to cover Linux from the desktop to the server.


    Ten years ago, Novell was the owner of DR-DOS, Netware, and Unixware, and had the potential to be a solutions provider for everything from the desktop, to medium sized workgroups, to enterprise scale solutions, but what did they do? They tried to compete against Lotus Smartsuite and MS Office with an office suite based on Quattro Pro and WordPerfect.

    NT wasn't even ready yet, they coulda been a contender...

  12. Re:This is why Mono is such a bad idea by alienw · · Score: 5, Insightful

    OS/2 ran Win3.1 apps natively, so nobody wrote OS/2 apps, but Win3.1 apps.

    If OS/2 hadn't run Windows apps, nobody would have ever used it. The reason it died was the high price and poor hardware support (it didn't run on non-IBM machines without a lot of tweaking). Stop using that example, for fuck's sake.

    The lesson is that as soon as you support somebody else's standard, then nobody has any reason to use your standard.

    Does linux have anything remotely resembling .Net? Other than mono, of course.

  13. Chris Stone and Novell Linux Distributions by alistair · · Score: 4, Insightful

    Chris Stone is an excellent guy for Novell to have as a VP, as well as being a well respected chair of the Open Group he also used to be base player for the band that became Aerosmith (he left 6 months before they had their first big hit).

    However, I have to wonder about the wisdom of producing yet another Linux distribution, particularly one aimed at the desktop arena. Although you may not know it from the figures, many internaional companies have already standardised on SuSE or Red Hat for their Linux vendors and the name Novell still has some bad connertations in the Corporate world.

    Much of Novells strategy today seems to be selling very high value (expensive) products based around XML and Web Services (see their Silverstream aquisition) to Fortune 500 / FTSE 100 companies. I know as an implemetor for their excellent DirXML Meta Directory in a 100,000 employee company.

    To my mind they would be better forming an alliance of the sort that SuSE and Sun announced yeterday, where Sun support and Distribute SuSE Linux and SuSE use Sun's Java in all their distributions. Novell could add their tools to SuSE and Red Hat, such as Directory Clients and Xen Works clients, concentrate on selling their servers on the SuSE and Red Hat platforms they already support and bundle SuSE and RedHat desktops for Netware customers. This would give them client penetration and server sales opportunities without having to compete with the Linux vendors. They could also leverage the relationship these vendors have with Sun and IBM who would be happy as the Novell server components also run on Solaris and (I think) AIX. Thoughts?

  14. LOL by JoeLinux · · Score: 4, Funny

    As located here, RedHat calls SCO's practices "likely to cause confusion, mistake or to deceive". Is that legalese for "Fear, Uncertainty, and Doubt"?

    Just a thought,

    Joe

  15. For another perspective by wahgnube · · Score: 5, Informative
    Check out this phone interview with Miguel on OSNews.com.

    Seems like all is well, for now anyway.