Oh my. I wake up every morning, just for the purpose of finding out the most recent developments on the exciting SCO case, where IBM is going to have to pay BILLIONS and BILLIONS (to quote Mr. Sagan) because of the way that the evil IBM corporation screwed SCO. The climax, just around the corner, is going to be exquisitely exciting.
Heavens to Betsy, I didn´t know so many were willing to go to jail and pay fines just to get Microsoft software and operating systems!
Oh my. And I thought an old lady on a red dress used to write all those lovely articles at Groklaw.
It seemed as though Sun tried to prevent licence holders from sharing code with other licence holders in 2000. If true, it would certainly make the Solaris licence less desirable to hobbyists than the ancient UNIX licence, unfortunately. I´m so sad!
Many programs require shared libraries. If you have access to the shared
libraries for the system you're emulating under iBCS2, you can use them
via iBCS2 under Linux. However, it is your responsibility to
check whether your license allows you to do this.
(2) Following from that, it would be helpful to distinguish between the
two cases where the user has access to the emulated system and where he
doesn't. In the former case, it seems possible to deal with the shared
library problem, at least for UnixWare. (Pointers to specific directories or
at least file names would be helpful).
(3) Since Free UnixWare is close at hand (from SCO), if there's any
information available about whether these libraries can be used in an
emulation within the terms of the SCO license, and how to do it, that
would be very valuable.
Is it possible to use SCO Openserver shared libraries under iBCS2?
I am running Linux with the latest iBCS2. I bought the SCO
Openserver CD-ROM, mostly out of curiosity. Some small binaries, which
don't use shared libraries, do work, but most stuff needs libraries. I
have had absolutely no success in getting the libraries to work, even
though I have copied them into the right place etc.
Is there something else I need to do or is it just impossible?
Following a very polite response from SCO, who say they do not see any
reason why I should not use my licenced freeSCO Motif libs with linux for
non commercial use, here's how i did a dynamic compile of xbill and xmcd.
1). I copied the directory /us/rinclude/X11/Xm/ on my SCO partition to the
relevant include directory in Linux.
2) I copied libXm.* to my Linux X11 lib directory (running ldconfig).
3) I ensured that I was running iBCS.
4) I untarred and compiled xbill with the use motif flag defined in the
5) The compilation bombed out at the linking stage, complaining about
undefined references. As far as I could tell, the undefined references were
for routines found either elsewhere in Linux or peculiar to SCO.
6) took a note of the symbols which were undefined (__foo, __bar, etc)
7) I created a small C program called motif.c which contained some void
functions for the linker to pick up ie
8) I added motif.c to the SRCs part of the Makefile and motif.o to the OBJs
part to ensure it linked.
9) Typed make
10) Played a dynamically linked version of xbill
I'm not promising that this will work for every motif app, but it certainly
works for the two I tried.
Give it a go!
John M Dow
UNIX Systems Administrator
As an excercise in bloody-mindedness (don't do this - it breaks the Free SCO
licence agreement) I have (fairly easily) managed to compile and dynamically
link several Motif apps under linux using the SCO libs, but as I said, why
spoil your prisitine Linux box with pirated software? If you want motif, buy
SCO seem to have made a big contribution to the iBCS2 project. Im sure they
didnt mean too. But they have a nice offer whereby you can get SCO licenses
free for personal and/or educational use. Looks a very nice way of getting
the troublesome SCO shared libraries for many iBCS2 users. Just throw the
rest of SCO away.
Linux kernel developer
Oh my. Based on your response, it seems there's not a version of Outlook for Linux. Why?
Heavens to Betsy, the future of Unix/Linux on IBM's mainframes doesn't look good. I feel sorry for good folks at IBM.
Oh my, there's a wonderful paper by Henry Spencer titled 'How To Steal Code or Inventing The Wheel Only Once' that I'm sure Linux developers read to get ideas on how to get code from AT&T and use it in Linux.