|
Request for Info: Ransom Love Talks - Updated 2 Xs |
 |
Saturday, January 16 2010 @ 10:49 PM EST
|
Mind if I pick your brain a bit? I've found some press releases and announcements of talks that Ransom Love gave when he was still CEO of Caldera, but it would be wonderful if by any chance someone taped them or even took notes at them. Were any of you there? Do you recall any details?
Here are some announcements of some appearances he made:
Love spoke at LUNY on April 13, 1999. Here's the notation:
Tuesday April 13th, 1999
Preview of the next release of Caldera OpenLinux with the new Linux 2.2 kernal.
Ransom Love, the President of Caldera Systems
was our guest speaker, along with esteemed Caldera staff members.
Mr. Love brought CDs of the new release, which began shipping the following week.
Were any of you there? Did you get the CD? Here's an announcement of another talk he was supposed to give the next year at the same group:
[nylug-talk] LUNY Meetings: April & May 2000
* To:
* Subject: [nylug-talk] LUNY Meetings: April & May 2000
* From: "LUNY Communications" [luny@virtualalley.com]
* Date: Thu, 30 Mar 2000 08:11:11 -0500
* Importance: Normal
* Sender: owner-nylug-talk@electriclichen.com
The LUNY meeting scheduled for April 11, 2000 has been CANCELLED.
Please join us at the May 9, 2000 meeting for the triumphant return of
Ransom H. Love, CEO of Caldera Systems http://www.calderasystems.com , in
the wake of Caldera's billion dollar IPO.
During Ransom's visit last year, copies of OpenLinux 2.0 were generously
distributed to all in attendance, prior to the public release.
LUNY - Tuesday May 9, 2000
6:30pm - 9:00pm
Sybase Financial InSITE Center
1 World Trade Center
Floor 87, Suite 8755
http://www.luny.org/location/map.html
As usual we will follow the meeting with drinks and networking at the
"TallShips Bar" downstairs and around the corner in 1 World Trade Center.
Please be sure to bring picture-id with you to show at the visitors desk in
the lobby on the main floor.
If your name is not on the visitors list, then have the visitors desk phone
up to Sybase and we will send someone down to escort you up to the meeting.
For more information, see http://www.luny.org/location/security.html .
To get on the visitor's list for this event you MUST send email to
lunyvisitor@usa.net Please put "LUNY Visitors List" as the subject of your
email, and have your full name in the body of the message.
We can only guarantee names received by the Thursday night before the
meeting. So please register BEFORE May 4. The WTC visitors desk requires us
to give them this list three business days before the meeting, so we need to
receive your name by the Thursday before the meeting. We will try to get
names received later than that onto a supplemental list, but there is no
guarantee.
If you registered for a past meeting, then you do not need to re-register
for the May meeting. Please look for your name on the attendee list
(http://www.luny.org/location/signin.html) to see if you are already
registered.
Anyone attend that meeting? Do you recall what he said, or better have a tape or contemporaneous detailed notes? Or a CD?
Here's the announcement of that April 1999 talk on Linux-Misc and note the comment on redistribution:
Linux-Misc Digest #225
Digestifier
Sun, 16 May 1999 07:21:52 -0700...
* To: "NYLUG"
* Subject: [nylug-talk] Reminder: Ransom Love coming to LUNY! this Tuesday
* From: "Matthew Hunt"
* Date: Thu, 8 Apr 1999 16:44:27 -0400
* Sender: owner-nylug-talk@electriclichen.com
Just a reminder for all NYLUGers, LXNYers, and LUNIES! -
Ransom Love, the president of Caldera, will be coming to speak at LUNY!
along with Lynn Nielson, Caldera's Director of Engineering. 250 copies of
the gold code for the new rev of Caldera, which uses the new 2.2 kernal and
KDE 1.1, are being shipped to me and will arrive tomorrow. They will be
distributed for free at the meeting.
Ransom & the gang will be demonstrating on machines they are bringing with
them, which will be connected to the 15-foot rear-projection set up front.
As always, the meeting is at 55 Broad Street on the 4th floor from 6:30 - 9.
Please pass the word on so that we New Yorkers can give the folks from Utah
a good crowd. LUNY's web site is available at www.luny.com.
I look forward to seeing you all there!
Matt Hunt
Head LUNY!
...
From: [EMAIL PROTECTED] (John Forkosh)
Crossposted-To: comp.os.linux.setup,comp.text.tex
Subject: Re: [?] problem w/ TeX under RH 6.0
Date: 16 May 1999 09:50:18 -0400
Simon Cozens ([EMAIL PROTECTED]) wrote:
snip
: and give us the results. Meanwhile, I'll look at the SRPM. (I'm currently
: in the middle of testing all the 6.0 SRPMs and boy are they broken...)
This is somewhat off original topic (sorry)...
At the April meeting of LUNY (Linux Users of New York),
Ransom Love and a few cohorts spoke about Caldera. One point they
emphasized is that you could cleanly rebuild the entire distribution
from their "pristine" sources. Can you remark about the accuracy
of that claim?
John ([EMAIL PROTECTED])...
From: Simon Cozens
Subject: SRPMs, was Re: [?] problem w/ TeX under RH 6.0
Date: 16 May 1999 14:04:15 GMT
I've trimmed the newsgroups, since this isn't a TeX problem any more; please
note that I don't regularly read colm, so if you've any comments you think I
should know, send them by email too.
In comp.text.tex John Forkosh wrote:
> At the April meeting of LUNY (Linux Users of New York),
> Ransom Love and a few cohorts spoke about Caldera. One point they
> emphasized is that you could cleanly rebuild the entire distribution
> from their "pristine" sources. Can you remark about the accuracy
> of that claim?
It seems that a lot of the RH6 SRPMS failed on rebuild for various reasons,
mainly due to dodgy .spec files. (egcs failed because it tried to write to
a file that had already been created as a directory by the tarball, but I
can't remember the details.) On a considerable number of them, the ./configure
stage had been commented out. Needless to say, this caused a lot of trouble.
The problem's been around for a while - in 5.2 I did a mostly-clean upgrade
by rebuilding all the packages from source, and then only 10-20 of them failed;
this time, it seems like a whole lot more is broken, but it's a .0 release,
and what do you expect? :)
It would be interesting to list all in one place any talks he gave that any of you remember, and of course anything said about the GPL, distribution, anything on any of the topics of particular interest to us would be helpful.
Update: Of course, you guys came through. We have three mp3s now, and some links to interviews. First, the audio: -
Ransom Love interview, 1999
- NetworkWorld, 2002, "Linux Showdown": (1:15:00) Linux distributions and fragmentation. With: Brian Biles, VP
Marketing, VA Linux Systems, Robert Bruce, President and CEO, Walnut
Creek CDROM, Ransom Love, President and CEO, Caldera, Cliff Miller, CEO,
TurboLinux, Stefan Wintermeyer, President, SuSE Linux AG. Media Panel:
Bob Brown, News Editor, Network World, April Jacobs, Senior Editor,
Network World, Nick Petreley, Editorial Director, LinuxWorld Online
Publication. John Gallant, VP and Editorial Director, Network World,
Moderator. At 1:09, approximately, Love is asked what Caldera Systems would do if someone took GPL code and tried to make it proprietary. He answers that it would, along with the community, work to protect the GPL.
- Ransom Love's Keynote address,
LINUXWORLD 2000. His speech was on the SCO acquisition. He mentions the importance of getting the reseller network. He also addresses the need to have multiple kernels, so as to scale from thin clients to high end. He also talks about services model, and he compares it to selling bottled water, so it turns out Darl McBride did not come up with that first. Love also mentions the GPL and says the company will release under the GPL, but also other licenses. He says he didn't write the speech. Says that it is estimated that a million Linux servers were shipped in 1999. We've had this talk since 2003, but the link we posted is no longer good, so I'm putting a local version here.
Here's the transcript of the section of Q & A where Love spoke about Project Monterey:"Q: What happens about Project Monterey, because that conflicts with the IA-64 Linux, 64-bit Linux?
"Love: OK. I don't -- if we do our job right in making Linux scale over like UnixWare to the degree that everybody, that we know we can... May I ask, some people have said, "Well, people have tried this in the past, but they haven't been that successful," may I suggest: we don't have any ulterior motives for not making it successful. Technologically has not been the reason why it hasn't done it before. There's always some other motive, right? And so to talk about Monterey, clearly we want to make sure we have the same level of Linux integration on Monterey that we would have in our Unixware product. Now, we don't control, I mean, we have a great relationship... it's a joint development relationship with IBM which we intend to preserve ... but they have similar interests and so this is really a very synergistic, uh, this transaction is great for all of the major partners as they have already wanted to embrace Linux moving forward.
"Now, let me address one other aspect of your question, which is that the Monterey Project is in conflict with the IA-64 Linux Project. I don't believe it's in conflict at all. Now, clearly, we have tremendous vested interest in the IA-64 Linux Project and with the acquisition of SCO, they've been doing a lot, so you combine those, and we've got one of the more comprehensive offerings, I believe, on the IA-64 Linux. So that's clearly an area that we're very committed to. But like Unixware, there's elements of the Monterey kernel that are more scalable, OK? Now, on the IA-64 platform, I don't know how long of window that is, but today, it's a little bit more robust and more scalable than the IA-64 Linux is today. Now, I'm not saying that over time that won't change.
"But, and let me address one other thing. Sorry, (laughs) you're getting all of it through one question. But clearly we are going to add components back to the Linux kernel on both IA-32 and IA-64 platforms. We'll work with Linus and everyone in order to make that available. That will take some time. And as I mentioned earlier, I don't know that over time you can have a single kernel -- in fact I know you can't -- that will scale, you know, the breadth of IT technology needs. So I think we're looking, in the Linux community, at having multiple kernels, so...
"Q: Multiple Linux kernels? Or multiple UNIX kernels?
"Love: Multiple Linux kernels as well, over time.
"Q: Thank you.
"Love: You bet.
Second, some interviews:-
Ransom Love's Answers About UnitedLinux (2002):
Q: If it's UnitedLinux, is each vendor prepared to pay to fix snafus committed by the others? If it's the individual vendors, what happens when one of them screws it up and wrecks confidence in UnitedLinux?
Ransom:
Every company will be shipping a common CD that will include a complete Linux distribution including installer and desktop. This is the UnitedLinux aspect of the distribution. All the additional value-add will be on separate CDs. Consequently, there will be a common quality check on the base components. The testing of the value-added components will be the responsibility of the individual companies.
-
Caldera CEO Ransom Love Foresees Linux "left-sizing" of Business,
Linux Today (1999):
To support his views, Love pointed out that current trends show Linux becoming the predominant server operating system, having grown over 200% last year to command a 17% share of the market. Also, businesses such as Cendant and Burlington Coat Factory are validating Linux by committing to major Linux deployments....Caldera Systems, Inc. is a leading vendor of the open-source Linux operating system. Caldera's flagship product, OpenLinux 2.2, is targeted for enterprise deployment. Caldera is hoping that its recently announced partnership with IBM will favorable position OpenLinux for deployment in the Fortune 500.
-
SCO customers need not fear, says Caldera chief , ZDnet (UK) (2000):
[Doug] Michels emphasised that, whatever potential Linux might have, Unix will stick around in the near term: "Linux and Unix will exist side by side."
"There is no winner or loser at this point. They are going to come together and coexist as one community of open systems for the next few years, and Caldera is in a unique position to exploit this."...
Caldera plans to continue selling and supporting such systems, but will also offer Linux systems and a Linux migration path for those who want it. The installed base will also get access to such Linux goodies as applications and driver support, Love said. "Linux can help that [installed] base. Caldera will provide a seamless way to embrace Linux, and you can move to Linux if you want."
It makes sense for Unix and Linux to exist side by side at the same company, according to some industry observers. While Linux is moving toward a more robust, business-friendly form, Caldera will be able to offer existing Unix products to fill those needs, and may eventually be able to convert those customers to Linux....
Love also reiterated the company's commitment to Monterrey, the version of Unix co-developed by SCO and IBM for Intel's IA-64 platform. "Officially it is to continue, and it has a reason to continue," Love said. He remarked that the company would be interested in Linux integration into Monterrey, which now has the somewhat less picturesque moniker AIX 5L.
-
Linux Planet (2001). This is an article, not an interview:
Caldera has, to my great sadness, breathed new life into the phrase "a day late and a dollar short." You can now order the Workstation 3.1 product or download ISO images and burn your own CDs for free. From what I have heard -- I have not seen it -- it's a nicely updated though austere version of the traditional Caldera Linux. And had Caldera's plans been made clear a month or two ago, there's a good chance that I, like many Caldera refugees who aren't, would be using it. But it's not something to which regular desktop users are likely to be drawn, and those users are not being sought by Caldera. These factors, combined with a licensing policy unique among distributions and some remarks by Caldera's Ransom Love that seemed designed to shoo away the general Linux user base, in any case mean that one of the oldest and best Linux distributions is no longer a player in the general desktop market. Too bad, though the company's reasons are understandable even if its way of going about it perhaps isn't.
-
Ransom Love speaks about UnitedLinux, SCO & Where He’s Going Now, Practical Technology (2002):
Love: So, what I did in those two months was work with the CEOs and what would become the Board of Managers to provide some guiding concepts, come up with the by-laws defining how new companies could join UnitedLinux and how everyone would work together and begin the search for a general manager. I did put my name in the ring.
-
Linux exec: This isn't revolution, ZDNet News UK, April 18, 2000, reporting on a Love keynote address at the Comdex/Spring 2000-Linux Business Expo:
Linux will thrive by offering open access, not through a too-strict demand that every part of the Linux infrastructure be opened, Love said.
"Some open-source licenses may go a little too far," he said. "It's one thing to facilitate open access, but another to demand it. That's what you are trying to get away from."
Update 2: More on Caldera and the GPL in this 1995 article from Linux Journal:While Caldera will be providing many commercial components, they have publicly promised to fully honor the GNU Public License, including providing full source code for all the GPL-licensed software they ship. The GPL is what has made Linux useful to them, and they say that it lowers and removes barriers for many small companies who want to compete in the software marketplace. They suggest that Linux will increase innovation in the software marketplace, and they want to push this along. They quote Ray Noorda as saying, “That's exactly what we are out to do—to grow [the whole Linux] industry.” Promoting Linux is good for everyone.
Caldera has instructed their public relations firm to promote Linux, as well as Caldera, believing that by giving Linux added exposure, the entire market will grow, benefiting everyone in it, including themselves. In addition, they will continue to contribute work on free software, doing their part to help keep Linux innovative and open. When they chose a business partner to build their distribution, they chose another company that licenses its software under the GPL, Red Hat Software.
And here's another Linux Journal article from 1995, ELF Is On the Way:
Nearly all the major Linux distributions have announced some support for ELF, and some have beta versions available on the Internet. Red Hat, Slackware, and Yggdrasil have each announced that alpha or beta level ELF-based distributions are available from their standard FTP sites. By the time you read this, all three expect to be shipping production-quality ELF-based distributions.
Debian has had ELF support for its standard distribution available to developers and all other interested parties for several months, and some of the debian developers are working on ELF issues. The current release is a.out-based, but users will be able to upgrade to ELF without re-installing the distribution. This in-place upgradability has been included in Debian for a long time, and has been well tested. Debian can be retrieved via FTP from ftp.debian.com and mirrors including tsx-11.mit.edu and its mirrors worldwide.
Red Hat's beta is available via FTP from ftp.pht.com, ftp.caldera.com, and other mirrors, and is being tested as of late August and early September. Red Hat has committed to a production-quality release in September to support the second preview release of the Caldera Network Desktop, which is built on top of Red Hat's distribution. Notice that Caldera distributed it from its ftp site. And note the a.out reference?
|
|
Authored by: bprice on Saturday, January 16 2010 @ 11:07 PM EST |
As if.
---
--Bill. NAL: question the answers, especially mine.[ Reply to This | # ]
|
|
Authored by: bprice on Saturday, January 16 2010 @ 11:08 PM EST |
With clickies, please.
---
--Bill. NAL: question the answers, especially mine.[ Reply to This | # ]
|
|
Authored by: bprice on Saturday, January 16 2010 @ 11:08 PM EST |
With the News Pick title in your comment title.
---
--Bill. NAL: question the answers, especially mine.[ Reply to This | # ]
|
|
Authored by: Anonymous on Saturday, January 16 2010 @ 11:54 PM EST |
The fact remains that what is really galling about SCO's predatory lawsuits is
that they intend to ask for first degree murder charges anytime someone else
does not dot an I or cross a T, but consider any slackness on their own side as
water under the bridge.
As has been noted, the courts preference to allow this is most unsettling.
[ Reply to This | # ]
|
|
Authored by: IMANAL_TOO on Sunday, January 17 2010 @ 02:32 AM EST |
Carnage4Life wrote
on Slashdot April 19 2000:
"ZDNet has an article on Ransom
Love's (Caldera CEO) speech at the Comdex/Spring 2000-Linux Business Expo. The
high points of his speech include his fears that the Linux revolution may be
silencing lots of others by its success; [the contention that] proprietary
software isn't all bad (Sun's Star Office is his example); Linux is as much a
proprietary system as any other since the GPL forces one to adhere to it's rules
just as proprietary licenses do; a brief description of the road map of
Caldera's Linux development in the future; and finally a few comments on what he
felt was the too-strict demand by some open source licenses that all code should
be opened." Some good points, but mainly a lot of unsurprising viewpoints
considering Caldera's outsider position in the actual Linux
Community.
Love's speech is heavily commented by the Slashdot
readers (all of which have very low numbers, as this was right after you could
register), e.g.:
In the article, Ransom Love also keeps spreading a
common misconception about Free Software Licenses. He claims that if you make
any modifications to Linux, the license demands that you distribute the changes.
That is patently false. What the license demands is that if you distribute a
modified version of Linux, you have to make the code to your modifications
available. Anyone can keep any changes they want a secret, as long as they
aren't distributing them. With fundimental misunderstandings like this, is it
any wonder people think of Caldera and Ransom Love as outsiders when it comes to
Linux.
So, the world doesn't change much, does
it?
--- ______
IMANAL
. [ Reply to This | # ]
|
|
Authored by: IMANAL_TOO on Sunday, January 17 2010 @ 04:10 AM EST |
Which GPL'd software did
Caldera distribute in 1998?
Date: Wed, 29 Jul
1998 18:53:33 +0200
From: Fredric Fredricson
X-Mailer: Mozilla 4.04
[en] (WinNT; I)
MIME-Version: 1.0
To: Evan Leibovitch
CC: Linux
Business Mailing List
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [linux-biz]
Re: Linux/Unix/NT comparison chart
X-Unsubscribe: send a blank message to
linux-biz-off@lege.com
X-Status:
Evan Leibovitch wrote:
>
> On Wed, 29 Jul 1998, Fredric Fredricson wrote:
>
> >
> I make it clear that the 'free' SCO is only for non-commercial use,
and
> > > one-user only. So it's not the same sense at all.
>
> I am sorry. I don't get what you mean. Maybe its me....
>
>
> > What _I_ mean is that I do not beleive that You can call SCO
and ask
> > them to send You their OS for free just because You are
non-commercial
> > user. I guess that You can download it for free,
but it is the same
> > with Linux. Maybe not with the complete Caldera
distribution but
> > it should be true for most of it. Or...?
>
> I'm totally missing Fredric's point. Can someone help me?
>
> Any UnixWare 7 media kit can be installed as a "free" version; you
just
> register at SCO's web site, and get a license that unlocks one
user.
> Alternately, you can get the media for essentailly the cost
of
> distribution.
OK! So when You got the SCO media You can install
SCO for free. Good.
As for Caldera, check
out:
http://www.caldera.com/products/openlinux/tryout.html
It sure looks
free to me. May not the _the complete distribution_
but unless Caldera lies
it is _a_ complete (whatever that means!)
distribution.
>
>
For more details, check http://www.sco.com/offers/freeUW7.html
>
> > > > If it is license cost it still does not make sense
since
> > > > Caldera OpenLinux (or at least the major part)
is free.
> > >
> > > Caldera OpenLinux Standard lists
for $199. If you have other info please
> > > let me know. For
many reasons I decided to take a specific 'snapshot' of
> > > a
Linux distribution just as I took a specific "Unix".
>
> > As
far as I understand the _License_ cost for Linux is zero.
>
>
Irrelevant. The license cost of Caldera Standard is $199. If I used
>
the Cheapbytes Red Hat Release that would have been different.
>
> > It is true that I need at least one set of CDs but I can install
it on
> > any number of computers.
>
> Same with the
Free UnixWare. You need a separately registered free license
> for each
computer, but can pass one media kit around.
>
> > This may not be
true for all of the Caldera Distribution but it is true
> > for most
part. (I am not really familiar with the Caldera Distribution.
> >
Afaik it may contain commercial sw).
>
> It absolutely
does.
I checked out Caldera OpenLinux
Standard
(http://www.caldera.com/doc/standard/appsoftw.html)
and it
seems like there are 10-15 packages distributed under
Caldera End-User
License and the rest is distributed under
GPL or similar
license.
What is the Caldera End-User
License? Perhaps that license relates itself to the GPL license, thus providing
with a stance from Caldera why Caldera provides this alternative license.
Perhaps they demonstrate how they understood the GPL at at the time, and that
they had had it analysed, perhaps in detail? Perhaps, but I have not seen it.
Has anyone else?
However, there something similar at
http://defcon.no/files/caldera-eula.php , called "Caldera Systems End-User
License Agreement", which reads, in selection:
"GPL Software"
consists of the following computer programs:
1. Linux packages as selected,
arranged and coordinated by Caldera Systems for inclusion in this OpenLinux
distribution. GPL Software is not owned by Caldera Systems. GPL Software is
distributed by Caldera Systems to Licensee for use by Licensee. GPL Software is
distributed under the terms of the GNU General Public License, Version 2, June
1991, a copy of which accompanies this OpenLinux Agreement. The GNU General
Public License governs the GPL Software and the copying, distribution and
modification of the GPL Software. GPL Software source code is included in the
GPL Software distributed to Licensee consistent with the requirements of the GNU
Public License.
and
All maintenance releases,
fixes, patches, work-around solutions, upgrades, and updates for or to the
Caldera Systems Software, Third Party Software or GPL Software made available by
Caldera Systems or its distributors, OEMs, VARs or other resellers to Licensee
shall be deemed part of the Caldera Systems Software, Third Party Software or
GPL Software as applicable, and shall be governed by this Agreement and the
license agreements referred to herein, unless a different license agreement is
provided with or made applicable to such maintenance releases, fixes, patches,
work-around solutions, upgrades, and updates.
It is my
perspective that Caldera had an extensive, broad and thorough understanding of
what the GPL did for Caldera and what Caldera could do for the
GPL.
--- ______
IMANAL
. [ Reply to This | # ]
|
|
Authored by: NZheretic on Sunday, January 17 2010 @ 06:21 AM EST |
(1:15:00) Linux distributions and fragmentation.
With: Brian Biles,
VP
Marketing, VA Linux Systems, Robert Bruce, President and
CEO, Walnut
Creek
CDROM, Ransom Love, President and CEO, Caldera, Cliff
Miller, CEO,
TurboLinux,
Stefan Wintermeyer, President, SuSE Linux AG.
Media Panel:
Bob Brown, News
Editor, Network World, April Jacobs, Senior
Editor,
Network World, Nick
Petreley, Editorial Director, LinuxWorld
Online
Publication. John Gallant, VP
and Editorial Director,
Network World,
Moderator
1h 9m into the
panel.
Question from audience:"This is for Caldera ( Ransom Love ):
Linux is protected by the GPL which means it's free software
and can be used
and re-used by others. If Caldera became
aware that Linux had been stolen, i.e.
someone had taken the
GPL'ed code and brought it into their proprietary
product
and resold it without also making that a GPL'ed product,
what would
Caldera Do?"
Ransom Love: "OK, let me just rephrase the question because
I'm
not sure I heard it clearly. If someone were to take the
GPL'ed software and
try to make it proprietary what would
Caldera Systems
do?"
"Exactly"
Ransom Love: "Well I think we would band together with
other
providers to protect the GPL. I think its critical and a
critical
component of what we do as well as other open
source licenses, like the QPL
and others. I think the key
here is that we would need to band and pool to
strive to
protect the license and insure that people are trying to
abide by
its terms, I think that is Key. All of us have
built a business on the fact
that we are collaborating
together and think that its important that we
continue to do
so."
I have emailed PJ the entire mp3.
[ Reply to This | # ]
|
|
Authored by: IMANAL_TOO on Sunday, January 17 2010 @ 06:46 AM EST |
H
ere is a guy who made public the end-user agreement of his copy of Caldera
OpenLinux 1.3 named "END-USER LICENSE AGREEMENT FOR CALDERA SYSTEMS OPENLINUX
AUG 1998". As for redistribution it
reads:
REDISTRIBUTION. All of the Software in this release
is distributed under
the GNU General Public License ("GNU GPL"), except for
DR-DOS, the NetWare
components, the LISA utility, StarOffice, Looking Glass, and
the BRU Backup
and Restore utility. The Software under GNU GPL may be freely
redistributed.
Except for the BRU Backup and Restore utility, all of the
Software may be
freely redistributed when packaged together. For specific
redistribution
rights, see the license for the package in
question.
So, it explicitly excludes DR-DOS and some
other software.
DR-DOS apparently had a different license, as seen from
the
Google cache of the Deltasoft homepage:
CALDERA
OPENDOS IS AVAILABLE FOR INSTALLATION FROM THIS FILE SET. IF YOU CHOOSE TO
INSTALL THIS SOFTWARE YOU ARE CONSENTING TO BE BOUND BY TERMS OF THIS AGREEMENT.
IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS AGREEMENT, DO NOT CONTINUE WITH
TH E INSTALLATION AND/OR RETURN THE COMPLETE PACKAGE TO CALDERA FOR A FULL
REFUND .
THIS DOWNLOAD, CDROM OR OTHER SUPPLIED MEDIA/DISTRIBUTION IS
PROVIDED WITHOUT TECHNICAL SUPPORT.
This Agreement has 4 parts. At
least two parts will apply to you. Part I applies if you have not purchased a
license to the accompanying software (the "Software"). Part II applies if you
have purchased a license to the Software. Part III applies to bi nary license
grants to the Software within the categories of Part I or Part II. Part IV
applies to source code license grants to the Software within said primary
categories. If you initially acquired a copy of the Software without purchasing
a license a nd you wish to purchase a license, contact Caldera, Inc. ("Caldera")
on the Internet at http:/www.caldera.com or call +1-800-850-7779.
PART
I -- TERMS APPLICABLE WHEN LICENSE FEES NOT (YET) PAID TO CALDERA (LIMITED
LICENSE FOR EVALUATION, EDUCATIONAL AND NON-PROFIT USE) ONLY.
Caldera
grants you a non-exclusive license to use the Software in source or binary form
free of charge if (a) you are a student, faculty member or staff member of an
educational institution (K-12, junior college, college or library), a staff
member of a r eligious organization, or an employee of an organization which
meets Caldera's criteria for a charitable non-profit organization; or (b) your
use of the Software is for the purpose of evaluating whether to purchase an
ongoing license to the Software. T he evaluation period for use by or on behalf
of a commercial entity is limited to 90 days; evaluation use by others is not
subject to this 90 day limit but is still limited to a reasonable period.
Government agencies (other than public libraries) are not considered
educational, religious, or charitable non-profit organizations for purposes of
this Agreement. If you are using the Software free of charge, you are not
entitled to support or telephone assistance. If you fit within the description
of a non- commercial use license, you may use the Software in the manner
described in Parts III and IV below under "Scope of Grant."
DISCLAIMER
OF WARRANTY FOR NON-COMMERCIAL USE.
Software obtained free of charge,
wether in source and binary forms, are provided on an "AS IS" basis, without
warranty of any kind, including without limitation the warranties of
merchantability, fitness for a particular purpose and non-infringement. The
entire risk as to the quality and performance of the Software is born by you.
Should the Software prove defective, you and not Caldera assume the entire cost
of any service and repair you may desire. In addition, the security mechanisms
implemented by C aldera software have inherent limitations, and you must
determine that the Software sufficiently meets your requirements. This
disclaimer of warranty constitutes an essential part of the agreement. SOME
JURISDICTIONS DO NOT ALLOW EXCLUSIONS OF AN IMPLIED WARRANTY, SO THIS DISCLAIMER
MAY NOT APPLY TO YOU AND YOU MAY HAVE OTHER LEGAL RIGHTS THAT VARY BY
JURISDICTION.
PART II -- TERMS APPLICABLE WHEN LICENSE FEES
PAID
GRANT. Subject to payment of applicable license fees, Caldera
grants to you a non-exclusive license to use the Software in binary and source
form and accompanying online documentation ("Documentation") in the manner
described in Parts III and IV below under "Scope of Grant."
LIMITED
WARRANTY FOR COMMERCIAL USE.
Caldera warrants that for a period of
ninety (90) days from the date of acquisition, the Software, if operated as
directed, will substantially achieve the functionality described in the
Documentation. Caldera does not warrant, however, that your use of the Software
will be uninterrupted or that the operation of the Software will be error-free
or secure. In addition, the security mechanisms implemented by Caldera software
have inherent limitations, and you must determine that the Software sufficiently
meets your requirements. Caldera also warrants that the media containing the
Software, if provided by Caldera, is free from defects in material and
workmanship and will so remain for ninety (90) days from the date you acquired
the Software. Caldera's sole liability for any breach of this warranty shall be,
in Caldera's sole discretion: (i) to replace your defective media; or (ii) to
advise you how to achieve substantially the same functionality with the Software
as described in the Documentation through a procedure different from that set
forth in the Documentation; or (iii) if the above remedies are demonstrated to
be impracticable, to refund the license fee you paid for the Software. Repaired,
corrected, or replaced Software and Documentation shall be covered by this
limite d warranty for the period remaining under the warranty that covered the
original Software, or if longer, for thirty (30) days after the date (a) of
shipment to you of the repaired or replaced Software, or (b) Caldera advised you
how to operate the Software so as to achieve the functionality described in the
Documentation. Only if you inform Caldera in writing of your problem with the
Software during the applicable warranty period and provide evidence of the date
you purchased a license to the Software will Caldera be obligated to honor this
warranty. Caldera will use reasonable commercial efforts to repair, replace,
advise or, for individual consumers, refund pursuant to the foregoing warranty
within 30 days of being so notified.
THIS IS A LIMITED WARRANTY AND IT
IS THE ONLY WARRANTY MADE BY CALDERA. CALDERA MAKES NO OTHER EXPRESS WARRANTY
AND NO WARRANTY OF NON-INFRINGEMENT OF THIRD PARTIES' RIGHTS. THE DURATION OF
IMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATION, WARRANTIES OF MERCHANTABILITY
AND OF FITNESS FOR A PARTICULAR PURPOSE, IS LIMITED TO THE ABOVE LIMITED
WARRANTY PERIOD; SOME JURISDICTIONS DO NOT ALLOW LIMITATIONS ON HOW LONG AN
IMPLIED WARRANTY LASTS, SO LIMITATIONS MAY NOT APPLY TO YOU. NO CALDERA DEALER,
AGENT, OR EMPLOYEE IS AUTHORIZED TO MAKE ANY MODIFICATIONS, EXTENSIONS, OR
ADDITIONS TO THIS WARRANTY. If any modifications are made to the Software by you
during the warranty period; if the media is subjected to accident, abuse, or
improper use; or if you violate the terms of this Agreement, then this warranty
shall immediately be terminated. This warranty shall not apply if the Software
is used on or in conjunction with hardware or software other than the unmodified
version of hardware and software with which the software was designed to be used
as described in the Documentation. THIS WARRANTY GIVES YOU SPECIFIC LEGAL
RIGHTS, AND YOU MAY HAVE OTHER LEGAL RIGHTS THAT VARY BY
JURISDICTION.
PART III -- TERMS APPLICABLE TO BINARY LICENSE
GRANTS
SCOPE OF GRANT.
For the binary license grants listed
above, you may:
* use the Software on any single computer;
* use the
Software on a network, provided that each person accessing the Software through
the network must have a copy licensed to that person;
* use the Software on
a second computer so long as only one copy is used at a time;
* copy the
Software for archival purposes, provided any copy must contain all of the
original Software's proprietary notices and license terms; or
* if you have
purchased multiple licenses (as in a 10 Pack or a 50 Pack, for instance) you may
make any number of copies of the Software (but not the documentation) up to the
number licensed (10 or 50, in the example), provided any copy must contain all
of the original Software's proprietary notices, marks and licenses. The number
of copies is the total number of copies that may be made for all platforms.
Additional copies of Documentation may be purchased.
* REDISTRIBUTION OF THE
SOFTWARE IS PERMITTED FOR NON-COMMERCIAL PURPOSES provided that the copyright
notices, marks and these terms and conditions in this document are duplicated in
all such forms and that the documentaiton, advertising materials, and other
materials related to such distribution and use acknowledge that the software was
developed by Caldera, Inc. Caldera's name may not be used to endorse or promote
products derived from this Software without specific prior written
permission.
You may not:
* permit concurrent use of the
Software without proper licenses;
* copy the Software other than as
specified above;
* rent, lease, grant a security interest in, or otherwise
transfer rights to the Software; or
* remove any proprietary notices,
licenses or labels on the Software.
PART IV -- TERMS APPLICABLE TO
SOURCE CODE GRANT
GRANT. Caldera grants you a non-exclusive license to
use the Software in source code form free of charge for personal, non-commercial
use. The Software in source code form may also be used for commercial
development purposes, provided a license is obtai ned from Caldera before any
products or derivative works are shipped for commercial gain that utilize the
Software , its components or derivative works.
For the source code
license grant, you may:
* use the Software on any single computer;
* use
the Software on a network, provided that each person accessing the Software
through the network agrees to the terms and conditions of this license
* use
the Software on as many computers as needed provided that each person accessing
the Software agrees to the terms and conditions of this license;
*
redistribute the Software for non-commerical purposes, provided any copy must
contain all of the original Software's proprietary notices, marks and license
terms. (Note: redistibution of derivative products for commercial gain is
permitted, provided a license is obtained before the derivative products are
exchanged for commercial gain)
* copy the Software for archival purposes,
provided any copy must contain all of the original Software's proprietary
notices, marks and license terms.
* modify, translate, compile, disassemble,
or create derivative works based on the Software provided that such
modifications are for non-commercial use and that such modifications are
provided back to Caldera except for those who have obtained the right from
Caldera in writing to retain such modifications; any modification, translation,
compilation, disassembly or derivative work used for commercial gain requires a
seperate license from Caldera;
You may not:
* permit other
individuals to use the Software except under the terms listed above;
* copy
the Software other than as specified above;
* rent, lease, grant a security
interest in, or otherwise transfer rights to the Software; or
* remove any
proprietary notices , licenses or labels on the
Software.
TITLE.
Title, ownership rights, and intellectual
property rights in the Software and all derivative works wether in binary and
source forms shall remain in Caldera and/or its suppliers unless otherwise
specificed in a seperate agreement with Caldera. The Softwar e is protected by
the copyright laws and treaties. Title and related rights in the content
accessed through the Software is the property of the applicable content owner
and may also be protected by applicable law. This License gives you no rights to
such content.
TERMINATION.
The license will terminate
automatically if you fail to comply with the limitations described herein.
On
termination, you must destroy all copies of the Software and
Documentation.
EXPORT CONTROLS.
None of the Software or
underlying information or technology may be exported or reexported (i) into (or
to a national or resident of) Cuba, Iraq, Libya, North Korea, Iran, Syria or any
other country to which the U.S. has embargoed goods; or (ii) to anyone on the
U.S. Treasury Department's list of Specially Designated Nationals or the U.S.
Commerce Department's Table of Denial Orders. By downloading or using the
Software, you are agreeing to the foregoing and you are representing and
warranting that you are not located in, under the control of, or a national or
resident of any such country or on any such list.
LIMITATION OF
LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, TORT, CONTRACT, OR
OTHERWISE, SHALL CALDERA OR ITS SUPPLIERS OR RESELLERS BE LIABLE TO YOU OR ANY
OTHER PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF
ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK
STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL
DAMAGES OR LOSSES. IN NO EENT WILL CALDERA BE LIABLE FOR ANY DAMAGES IN EXCESS
OF THE AMOUNT CALDERA RECEIVED FROM YOU FOR A LICENSE TO THE SOFTWARE, EVEN IF
CALDERA SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY
CLAIM BY ANY OTHER PARTY. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO
LIABILITY FOR DEATH OR PERSONAL INJURY TO THE EXTENT APPLICABLE LAW PROHIBITS
SUCH LIMITATION. FURTHERMORE, SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS LIMITATION AND
EXCLUSION MAY NOT APPLY TO YOU.
HIGH RISK ACTIVITIES.
The
Software is not fault-tolerant and is not designed, manufactured or intended for
use or resale as on-line control equipment in hazardous environments requiring
fail-safe performance, such as in the operation of nuclear facilities, aircraft
navigation or communication systems, air traffic control, direct life support
machines, or weapons systems, in which the failure of the Software could lead
directly to death, personal injury, or severe physical or environmental damage
("High Risk Activities"). Caldera and its suppliers specifically disclaim any
express or implied warranty of fitness for High Risk
Activities.
MISCELLANEOUS.
If the copy of the Software you
received was accompanied by a printed or other form of "hard-copy" End User
License Agreement whose terms vary from this Agreement, then the hard-copy End
User License Agreement governs your use of the Software. This Agreement
represents the complete agreement concerning this license and may amended only
by a writing executed by both parties. THE ACCEPTANCE OF ANY PURCHASE ORDER
PLACED BY YOU IS EXPRESSLY MADE CONDITIONAL ON YOUR ASSENT TO THE TERMS SET
FORTH HEREIN, AND NOT THOSE IN YOUR PURCHASE ORDER. If any provision of this
Agreement is held to be unenforceable, such provision shall be reformed only to
the extent necessary to make it enforceable. This Agreement shall be governed by
Utah law (except for conflict of law provisions). The application the United
Nations Conventio of Contracts for the International Sale of Goods is expressly
excluded.
U.S. GOVERNMENT RESTRICTED RIGHTS. Use, duplication or
disclosure by the Government is subject to restrictions set forth in
subparagraphs (a) through (d) of the Commercial Computer-Restricted Rights
clause at FAR 52.227-19 when applicable, or in subparagraph (c)(1)(ii) of the
Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, or
at 252.211-7015, or to Caldera's standard commercial license, as applicable, and
in similar clauses in the NASA FAR Supplement. Contractor/manufacturer is
Caldera, Inc. 633 South 550 East, Provo, UT 84606, U.S.A.
Download/Get OpenDOS
Password (accepting the above terms and conditions)
The DR-DOS
license apparently does not allow redistribution in the same fashion as the GPL
software products made available by Caldera.
--- ______
IMANAL
. [ Reply to This | # ]
|
|
Authored by: IMANAL_TOO on Monday, January 18 2010 @ 07:33 AM EST |
Sorry for the lengthy post. Here are some background information on the Caldera
OpenLinux distro, beginning in Berlin in 1996 with
the announcement of the 3rd International Linux
Conference:
3. International Linux Conference, 23. / 24.
May 1996
The 3rd International Linux Congress will be held in May
23./24.96 at the "Haus am Köllnischen Park" in Berlin ("Tagungszentrum Berlin
Mitte"). It follows the tradition of the Linux/Internet conference series
(Heidelberg 94 and Berlin 95) which has evolved into the most important meeting
for Linux-experts and -developers. The conference is a must for those who are
interested in Linux-technology and applications.
The main focus of the
forthcoming conference will be on current developments of Linux and its various
components. However, as Linux has become a well established and widespread
system, the development of applications and usage in commercial environments --
even for mission critical purposes -- will be another main conference topic.
Moreover, the Internet in the context of current Linux developments will be
covered by various talks and presentations.
Key speakers of the
conference will be Linus Torvalds, Theodore Tso and Allan Cox. According to the
growing commercial interest in Linux, a trade show will be part of the
conference, for all companies that offer products based on or using
Linux.
The conference will be organized by GUUG (Association of German
Unix Users) and supported by several companies (ASKnet, Fachbuchhandlung
Lehmanns, Lunetix, Thinking Objects) and publishers (Addison-Wesley, dpunkt,
Thomson/O'Reilly). Any profits from this event will be used to support
Free-Software-Projects.
The program of the 3rd International Linux
Conference:
Program for the Linux Conference 1996
We
are pleased to be able to offer you once again a great number of highly
qualified lectures on and around Linux.
Based on the needs and wishes
from last year´s participants and speakers we have improved the concept of the
Linux Conference:
* On both days of the Conference threre will be
two lectures taking place at the same time.
* The lectures will be foury
minutes each including discussion to follow. It will be up to the speaker to
decide how much time they wish to leave for the discussion. The chariman´s task
will be to modereate the discussion and make sure that the lecture will end in
time. There will be a break of five minutes between the lectures.
*
Should there be need for further discussion after a lecture we can offer you
another conference room where you can arrange another meeting. During the
Conference those meetings in the additional room will be announced on
information boards.
* This third room may of course be used for further
meetings, discussions, lectures ant other "Bird of a Feather Sessions" (BOFs)
that fall under the framework of the Conference but could not be integrated into
the present agenda. It is possible although not necessary, however, to announce
these extra offers even now.
* There will be an exposition of companies
offering products for or with Linux.
Lectures Thursday, May 23 1996
Lectures Friday, May 24 1996
The organization of the 3rd International Linux
Conference
Official organizer of the Linux Conference is the
German Unix Users Group, GUUG.
With support of the following
organizations:
* Addison Wesley Verlag
* ASKnet
*
dpunkt
* Interactive Networx
* J.F. Lehmanns
*
LunetIX
* O'Reilly
* Thinking Objects
Wait, what is LunetIX?!
Who or what is
actually Lunetix?
We are, in short, the authors and publisher of the
Linux user manual, and the initiators and organizers of the German Linux
Congress.
As a company, there is the "Martin Müller and Sebastian
baiting GbR" ever since 1992 when we sold the first beta versions of the book
together with a small Linux distribution. In the discount market with free
software, we are not entered, but instead we have dedicated ourselves mainly to
the two above mentioned projects. Duchaus successful as we can say with pride.
Our book is in spite of competition still on the bestseller lists of books and
computers are now find more than 30,000 books shelves. Congresses have
established themselves as the most important regular meeting of the
international development community.
To use all our expertise in Linux,
we have long been looking for ways to make Linux attractive to professional
users. Our support offer alone was not convincing enough to make the
breakthrough. Together with Caldera Linux, we now bring to the professional
market.
Lunetix is strict (still) do not put the company name, but our
registered trademark. The word we have to thank our friend Rebecca Forner to the
Linux and UNIX simply can not keep them straight.
We are taking steps
to start a limited company with which we may also operate officially under our
choice of names.
Our address is:
LunetIX
Müller und Hetze
GbR
Donaustr. 16
12043 Berlin
So, Caldera was involved?
Well, aptly enough there was a Bird of a Feather Session
Beside the fixed talks
we will have discussions about actual subjects.
This will give you the
change to discuss with the referents and other guys about the
subjects.
Here are some possible subjects for preparation.
*
Threads - Implementation in the Kernel and in libraries
* POSIX.4
Real Time Linux
* POSIX, XPG4, FIPS, UNIX95 - Linux and
Standardization
*
We are looking forward for proposals and
interesing subjects.
And, coincidentally the Caldera President and CEO Bryan Sparks not only participated in but also
moderated the Bird of a Feather Session discussions on POSIX, XPG4, FIPS, UNIX95
- Linux and Standardization:
POSIX, XPG4, FIPS,
UNIX95
Caldera Inc. would like to discuss the topic
How does
certification benefit Linux technologies? When will Linux certification be
completed?
Caldera President/CEO Bryan Sparks will present his
views and moderate a group discussion.
Linux technologies have created
a new niche in the computing industry. Many, many developers and vendors have
created and distributed Linuy technologies and Linux-based products that provide
stable, secure solutions that leverage the strenght of the Internet and Unix.
Linux technologies must now be riefined and meet the strict standards of X/Open
and other standard-setting organizations.
UNIX certification will allow
Linux technologies to be implemented by corporations and governments that
require software products that have passed rigid evaluation and certification
processes. Caldera is partnering with individuals and companies that share in
the vision of furthering the commercial acceptance of Linux technologies. The
combined efforts of these individuals and companies will allow Linux
technologies to become UNIX certified much sooner than if the efforts were made
independently.
Bryan Sparcs, President and CEO of Caldera will discuss
the company's accomplishments and future plans for obtaining multiple levels of
UNIX certification for Linux technologies and answer questions raised by those
in attendance.
Caldera made the following announcement on 23 May 2006, during the
conference:
"By developing and publishing source code
over the
Internet, Caldera and the Linux community are changing the way that
an
X/Open branded UNIX 95 operating system is developed and distributed,"
said
Bryan Sparks, President and CEO of Caldera, Inc. [...]
Caldera has also
retained the UNIX systems and Linux expertise of
engineers from Linux Support
Team (LST) of Erlangen, Germany, who
will spend the next few months integrating
technologies from Lasermoon,
Caldera's existing operating system, additional
Single UNIX Specification
APIs and Internet technologies, and LST's Linux 2.2
operating system
distribution, including the version 2.0 of the Linux kernel.
The resulting
combination of the Linux OS will be called Caldera Open Linux.
[...]
Caldera Open Linux, scheduled for release in Q3 1996,
will be
published freely with full source code via the Internet
to individuals and
organizations seeking stable, UNIX systems
solutions. [...]
Caldera
made this announcement from Linux Kongress in
Berlin, Germany, where the core of
Linux developers and vendors worldwide
meet each year to discuss accomplishments
and future plans for Linux
technologies.
So, "publishing
source code", "integrating technologies from Lasermoon, Caldera's existing
operating system, additional Single UNIX Specification APIs and Internet
technologies, and LST's Linux 2.2 operating system distribution, including the
version 2.0 of the Linux kernel", "Caldera Open Linux, scheduled for release in
Q3 1996, will be published freely with full source code via the Internet" are
statements which no longer matter? I don't think so, as Caldera did publish all this in November 27 1996, as
promised:
Caldera Releases Caldera OpenLinux (COL) Base 1.0 to
Manufacturing
First COL Stratified Product Runs on Intel-based PCs with
16 MB RAM
Provo, Utah November 27, 1996
Caldera Inc. today
announced the release to manufacturing of Caldera
OpenLinux (COL) Base, a
32-bit, Linux 2.x-based product forming the first
tier of the COL stratified
product line. COL Base provides Linux users and
first-time UNIX buyers with a
comprehensive and economical UNIX-based
system that can run on Intel-based PCs
including laptops with 16 MB of
RAM.
COL Base includes:
* Linux 2.x
kernel (A multi-tasking, multi-user, 32-bit kernel with firewall facilities and
comprehensive system utilities, complete Linux source code included on
CD-ROM.)
* Netscape Navigator 2.02 (The widely popular client software for
enterprise networks and the Internet.)
Looking Glass (A graphical user
interface with icon bar, drag and drop, comprehensive file typing, user-defined
configuration, and more.)
* MetroX (A commercial X11 server.)
*
CRiSPlite (A powerful, graphical text editor.)
* Caldera Solutions CD
(Fee-based, commercial, Linux software applications from Caldera and other
industry leaders.)
Note how Caldera stress that the Linux kernel
has the source code included by putting this first on the list. Bryan
sparks has later clarified his views on the GPL, in
detail:
First and foremost, the GPL is simply another software
license. Software is never really sold; it is just licensed to customers. A
customer agrees to the terms of a software license each time that customer
acquires and runs software.
That said, the GPL is not some oddity of
the software world. In fact, it embodies the best of both proprietary software
and open-source software by allowing companies to keep their own work while
using the incredibly stable and robust features of an open-source operating
system such as Linux. To further clarify inaccurate statements, the GPL never
requires a company to give away source code to its custom application
programs.
Allowing proprietary and GPL code to interact while keeping
the two separate is a fundamental process practiced by organizations around the
world. For example, if an application or driver runs in user space and makes
normal calls to the operating system, the proprietary source code is not
required to be licensed under the GPL but may be licensed under a proprietary
license if the author chooses.
Challengers of the GPL like to spread
fear about its "viral" effect. Yet what they fail to mention is that all
software licenses (even the Microsoft Windows license) have the same viral
effect as the GPL. The difference between a derivative of Microsoft code and a
derivative of GPL code is the final ownership of the code. Microsoft code and
derivatives assuredly go back to Microsoft and possibly benefit them with
profits.
GPL code and derivatives go back to the GPL and the public
domain and possibly benefit numerous individuals and organizations. This said,
the GPL clearly delineates an ability to use GPL code, and future derivatives of
that code, without threat of trademark infringement.
Bryan Sparks
preceded his fellow co-founder Ransom Love as the CEO at Caldera, and I think it
is clear that Caldera has understood the GPL from the beginning. That is clearly
how they "dared" use Linux in the first
place.
--- ______
IMANAL
. [ Reply to This | # ]
|
- "... it is clear that Caldera has understood the GPL from the beginning..." - Authored by: Anonymous on Monday, January 18 2010 @ 07:44 AM EST
- In 1995 - Authored by: IMANAL_TOO on Monday, January 18 2010 @ 08:05 AM EST
- In 1995 - Authored by: Anonymous on Monday, January 18 2010 @ 12:14 PM EST
- In 1995 - Authored by: Anonymous on Monday, January 18 2010 @ 12:41 PM EST
- In 1995 - Authored by: PJ on Monday, January 18 2010 @ 01:27 PM EST
- ELF, in 1995 - Authored by: IMANAL_TOO on Monday, January 18 2010 @ 02:23 PM EST
- ELF, in 1995 - Authored by: Anonymous on Monday, January 18 2010 @ 02:41 PM EST
- ELF, in 1995 - Authored by: Anonymous on Tuesday, January 19 2010 @ 01:51 AM EST
- ELF, in 1995 - Authored by: Anonymous on Tuesday, January 19 2010 @ 03:19 AM EST
- ELF, in 1995 - Authored by: PJ on Monday, January 18 2010 @ 03:29 PM EST
- In 1995 - Authored by: Anonymous on Monday, January 18 2010 @ 03:03 PM EST
- In 1995 - Authored by: PJ on Monday, January 18 2010 @ 02:30 PM EST
- That was Then, This is Now - Authored by: Anonymous on Monday, January 18 2010 @ 01:17 PM EST
- They understood? - Authored by: Anonymous on Wednesday, January 20 2010 @ 01:59 PM EST
|
Authored by: IMANAL_TOO on Tuesday, January 19 2010 @ 02:20 AM EST |
From the Ruby developer's page at
http://listlibrary.net/ruby-list/1996/10/00vKI0Qy
:
WATANABE Hirofumi
1996-10-01 18:05:46
���ա�ˡ��Ǥ�
.
�ޤĤ�Ȥ���:
: *
linux-ELF��a.out�򥳥�ѥ�ᦙ
3;뤷�Ƥ��ޤ����&
#65533;
�ɡ��Ǥ⤤��
5533;��ȤǤ���,
����� debug
�Τ�������줿
65533;Ȼפ��
�� echo "$host_os"
�� configure
�˻ĤäƤޤ�.
���
5533;Ʊ�� debug
���Ƥ��Τǵ��Ť
���. :-)
--
�錄�ʤ٤Ҥ�դ�
This message appeared in a previous month, was never archived, or was
lost.
matz@ca...jp (Yukihiro Matsumoto)
1996-10-01 19:15:49
In
message "[ruby-list:693] Re: ruby 0.99.2-960930 available"
on 96/10/01,
WATANABE Hirofumi
writes:
|
|���ա�ˡ��
Ǥ�.
|: *
linux-ELF��a.out�򥳥�ѥ�ᦙ
3;뤷�Ƥ��ޤ����&
#65533;
|
|�ɡ��Ǥ⤤��&
#65533;��ȤǤ���,
����� debug
�Τ�������줿
65533;Ȼפ��
|�� echo "$host_os"
�� configure
�˻ĤäƤޤ�.
���
956;ä��ġ�elisp�Υץ��
5533;�Ǥ�Ʊ�����Ȥ&
#65533;�ɤ������Ǥʏ
33;��
�͡��ޤ���
;�³���̵���ΤǼA
533;�������ľᦙ
3;����Ȥˤ��ޤ�
5533;礦��
|����Ʊ
65533;� debug
���Ƥ��Τǵ��Ť
���.
:-)
�ɤ���config.guess�Υ
057;�������autoconf�]
3;С�����󤬹��
65533;
���Τ��⤷��
956;���͡��ޤ���
;����Ͻ�����
Ƥ��Τ����㤤�
56;���
���ɡ�
�ޤĤ��
�椭�Ҥ� /:|)
2 messages in this thread
from ruby-list in 1996-10
No, it doesn't look any
better on the web page, or with any of the browser's I've tested. Still, this
page from 1996 does apparently talk about Linux, ELF and a.out, even if I cannot
see the relevance of it any more than that ELF was out for implementations in
Ruby.
--- ______
IMANAL
. [ Reply to This | # ]
|
|
Authored by: IMANAL_TOO on Tuesday, January 19 2010 @ 03:00 AM EST |
Did Linux have ELF before SCO or what?!
Some history:
Here is
a short excerpt from a long, detailed article from Linux Journal, April 1 1995:
"The ELF Object File Format: Introduction", :
Now
that we are on the verge of a public release of ELF file format compilers and
utilities, it is a logical time to explain the differences between a.out and
ELF, and discuss how they will be visible to the user. As long as I am at it, I
will also guide you on a tour of the internals of the ELF file format and show
you how it works. I realize that Linux users range from people brand new to Unix
to people who have used Unix systems for years—for this reason I will start with
a fairly basic explanation which may be of little use to the more experienced
users, because I would like this article to be useful in some way to as many
people as possible.
People often ask why we are bothering with a new
file format. A couple reasons come to mind—first, the current shared libraries
can be somewhat cumbersome to build, especially for large packages such as the X
Window System that span multiple directories. Second, the current a.out shared
library scheme does not support the dlopen() function, which allows you to tell
the dynamic loader to load additional shared libraries. Why ELF? The Unix
community seems to be standardizing this file format; various implementations of
SVr4 such as MIPS, Solaris, Unixware currently use ELF; SCO will reportedly
switch to ELF in the near future; and there are rumors of other vendors
switching to ELF
So, SCO didn't have ELF in April
1995.
The follow up article, "The ELF Object File Format by
Dissection", also by Eric Youngdale was published a month later also in Linux
Journal,
http://www.linuxjournal.com/article/1060 and .
Last
month, we reached a point where were beginning to dissect some real ELF files.
For this, I will use the readelf utility which I wrote when I was first trying
to understand the ELF format itself. Later on, it became a valuable tool for
debugging the linker as I added support for ELF. The sources to readelf should
be on tsx-11.mit.edu in pub/linux/packages/GCC/src or in
pub/linux/BETA/ibcs2.
So, Eric wrote this and added the
support for ELF himself. The article continues:
Finally, I should
mention something about the timetable. When we first got ELF to a point where it
was usable (last September), we decided to spend a relatively long period of
time testing it and shaking out all of the problems. Back then I felt that
roughly 4-to-6 months would allow people to test it thoroughly, plus we wanted
to give an opportunity for certain applications to be adapted for ELF (the most
recent versions of insmod and Wine now support ELF, for example). As I write
this, no firm date has been set for a public release, but it is possible that
ELF will be public by the time you read this.
In these articles I have
attempted to give you a guided introduction to the ELF file format. A lot of the
material I have covered is not of much practical value to most users (unless you
want to hack the linker), but my experience is that there are a lot of people
who are curious about how it all works, and I hope that I have provided enough
information to satisfy most people.
For more information about the ELF
file format, you can obtain the ELF specifications from a number of sources—you
can try ftp.intel.com in pub/tis/elf11g.zip. The specifications are also
available in a printed format. See SYSTEM V Application Binary Interface (ISBN
0-13-100439-5) and SYSTEM V Application Binary Interface, Intel386 Architecture
Processor Supplement (ISBN 0-13-104670-5).
Yes, he wrote it
himself, using the specification provided electronically by Intel and
specifications published in regular paper format with ISBN
numbers.
This was not any secret work, as indicated by an 1994
interview with Fred Kampen, available at
http://www.linuxjournal.com/article/2772 :
Linux Journal:
Do you have a vision of what the Linux community will look like in a few
years?
Fred: Depending on what some of the recent Linux projects
produce (I am talking about ELF/COFF, iBCS and Wine here), Linux users will
either continue to be semi-hackers like now, who use Linux for fun (as there
won't be any real applications) or standard things (mail, news etc.) or there
may come some sort of shift towards the “business” and “semi-business” class of
users, who use Linux systems for applications, like they would use a
“any-commercial-UNIX-here” now. Right now, it is hard to say what will
happen.
It is fairly obvious that by September 1994, ELF
was on it's way and usable, in Linux! And, SCO didn't have ELF in April
1995.
In light of this, did Linux have ELF in the open before SCO or
what?!
--- ______
IMANAL
. [ Reply to This | # ]
|
|
Authored by: IMANAL_TOO on Tuesday, January 19 2010 @ 08:51 AM EST |
It appears as if Caldera, through its Linux programme had access to ELF support
before SCO (Santa Cruz Operations, Inc., also known as OldSCO).
According
to a Linux Journal article from August 1st 1995, "ELF Released for Linux", at
http://www.linuxjournal.com/article/1139 :
The ELF tools
for Linux have just been publicly released, after months of testing. What does
that mean to the average Linux user? What is ELF, anyway?
ELF is a
advanced new binary file format for executables, libraries, and object files
(which are used to create libraries and executables). It is the native binary
file format of Unix System V Release 4, and is far more powerful and flexible
than the original binary file format used on Linux, which is often called
“a.out”.
And, according to the Operating Agreement
between Novell and SCO (available at
http://groklaw.net/pdf/Novell-173Ex2-3.pdf ) the deal between Novell and SCO
(Santa Cruz Operations, Inc., also known as OldSCO) was not finalized until
later, September 1995, when SCO formally had access to e.g. OpenServer Release 5
ELF binaries and UnixWare Release 2.1 ELF binaries. Before that, they belonged
to Novell as far as I can tell.
As it seems, Caldera had access to ELF
before SCO.
Doesn't all this make the entire ELF discussion moot and
void?
--- ______
IMANAL
. [ Reply to This | # ]
|
|
Authored by: Anonymous on Tuesday, January 19 2010 @ 11:14 AM EST |
The books "UNIX system V, release 4: programmer's reference manual" from 1990 by
AT&T (a very brief Google glimpse) and "Unix System V:
Understanding Elf Object Files and Debugging Tools (Programmer Collection)" from
1993 by Mary Lou Nohr (available at amazon.com) together probably give any well versed
reader what they need to implement ELF.
ATT&T's book
gets more than 1200 hits on Google and Mary Lou's book is described at
acm.org as:
UNIX System V Understanding ELF Object Files
and Debugging Tools details, in one place, the pieces of the compilation and
operating systems that provide information about the Executable and Linking
Format (ELF) object files: their formation, elements, structure, manipulation by
calls to ELF library functions, debugging, and their influence on active
processes. This book incorporates material from USL's: UNIX System V Release 4
Programming in Standard C, Programmer's Reference Manual: Operating System API,
User's Reference Manual/System Administrator's Reference Manual, System Files
and Devices Reference Manual, and Application Binary Interface. Combined in an
easy-to-use format, original source material and USL documentation, including
new examples, figures, tables, and explanatory material, enhances and simplifies
the complexities of programming. This Prentice Hall Open Systems Library book
provides programmers with the detailed and focused information they need in an
convenient format.
/The absolutely not a lawyer
parrot. Just didn't login.
[ Reply to This | # ]
|
- Some books - Authored by: PJ on Tuesday, January 19 2010 @ 12:02 PM EST
|
|
|
|