> Date: Sun, 8 Jun 2003 10:59:44 +1000
> From: Warren Toomey <wkt(a)tuhs.org>
> To: The Unix Heritage Society <tuhs(a)tuhs.org>
> Subject: Re: [TUHS] a question re pdp11 unix7
>
> On Sat, Jun 07, 2003 at 05:29:30PM +0000, zmkm zmkm wrote:
> > just a quick question about pdp11 unix7 , what's the pg command on unix7 ?
> > , like later versions of unix was pg as in ( ls -l | pg ) .
>
> lp ? :-)
> Warren
I think I remember being able to use the hardware Scroll Lock on a
VT05 terminal with some variety of Unix, perhaps late 6th Edition.
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst(a)ucsd.edu
Hi all
just a quick question about pdp11 unix7 , what's the pg command on unix7 ? ,
like later versions of unix was pg as in ( ls -l | pg ) .
tks in advance for the infos.
rgs to all
zmkm
_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
I've located a paper which describes the system, which I've put
up along with the disc image in www.spies.com/aek/solo
I'll see about extracting all of the files.
http://www.pbs.org/cringely/pulpit/pulpit20030605.html
Technician, Steal Thyself
SCO, Not IBM, May Have Put Unix Code Into Linux Instead?
By Robert X. Cringely
There is something about institutional memory, the way organizations do or
don't remember things. Covering IBM back in the Opel and Akers eras, I noticed
a very interesting thing about the way that company handled internal
information, which was through the use of plausible deniability. There was a
difference at IBM between knowing something and having it be known that you
knew something. So when an IBMer would say he didn't know a fact or the answer
to my question, it didn't always mean he lacked the information. It could just
as easily have meant that he/she hadn't been BRIEFED on the information.
Anything learned at the water cooler wasn't real. I wonder, then, how they
handle institutional memory issues at SCO, our subject for the last couple
weeks, because reality seems not to even be involved. Can it be that the very
crime SCO is accusing IBM of committing could have been done, instead, by SCO
itself? I think so.
Remember, SCO is suing IBM for stealing bits of Unix and putting those bits
inside Linux. How IBM is supposed to have done that remains a mystery, because
the only version of Linux that includes any IBM authorship claim is for the
S/390 mainframes, and even that wasn't written by IBM. According to folks who
did the work, it was done under contract to IBM by SuSE Linux AG, the German
Linux vendor. IBM provided the hardware and some access to IBM mainframe
engineers, but 98 percent of the work was done by SuSE. At Linuxworld 2000, IBM
didn't even help with the install or configuration of Linux on the S/390 they
loaned SuSE for the show.
Where, then, did IBM get those Unix parts it is supposed to have stolen? They
certainly didn't come from IBM's version of Unix, AIX, which bears little
internal similarity to any other Unix. I think the parts may have come from
SCO, itself.
Here is where institutional memory ought to come into play but doesn't seem to
be. Remember that the motto of the combined Caldera and SCO was "Unifying Unix
with Linux for Business." It is very possible that SCO's Linux team added
UnixWare and OpenServer code to Linux. They then sent their Linux developers
to SuSE when United Linux was formed. Soon after that, CEO Ransom Love
departed. Now the SCO management is scouring the UnixWare, OpenServer and
Linux code bases and says that they are finding cut-and-pasted code. Chances
are that their former employees put it there.
"Open Unix 8 is the first step in implementing the vision of the pending new
company," said Ransom Love, president and CEO of Caldera Systems in a company
press release way back when. "It combines the heritage of Unix with the
momentum of Linux, and will be our premiere product for data intensive
applications like database, email and supply chain management. The
incorporation of the Linux application engine into the UnixWare kernel
essentially redefines the direction of the product, and motivates a new brand
identity -- Open Unix."
But wait, there's more! Here is what Ransom Love said to ZDNet around the same
time:
ZDNet: What does the future hold for your unified Linux/Unix platform?
Love: "When we talk about unifying Unix and Linux, the two have a huge amount
in common. A lot of people are running their businesses on Unix, while Linux
has a tremendous population on Web servers and other front-end servers. So we
are taking both and combining them into one platform."
So SCO/Caldera spent two years "unifying" Unix and Linux and is now outraged to
find some of their intellectual property in Linux. Well duh! That's exactly
what they said they were going to do.
But does it even matter? As I noted last week, Novell retained the Unix
patents and copyrights when it sold whatever it sold to SCO back in 1995. The
best SCO can claim, given that Novell won't pursue a copyright or patent claim
against IBM, is that IBM is in violation of its Unix license agreement.
WHAT license agreement?
That SCO/Novell deal from 1995 gets murkier and murkier when you add in the
claims of The Open Group, a consortium that acquired the Unix trademark from
Novell at the same time SCO wasn't acquiring the Unix copyrights or patents.
"IBM's ability to call AIX a Unix system is due to its license from The Open
Group," says the group's marketing vice-president Graham Bird. "This license
requires IBM (and all other licensees) to warrant that it's certified products
conform with the Single Unix Specification. So, SCO cannot yank IBM's right to
call their certified products Unix, I'm delighted to say."
If SCO doesn't own the copyrights or patents, and it doesn't even have a
sublicensing agreement with the organization that owns the trademark, what
rights could they possibly intend to deny IBM as of June 13th?"
Nobody really knows.
There is an easy solution to this problem, one that I wouldn't be at all
surprised is in the works. SCO is angling to be acquired by IBM in an
out-of-court settlement. Certainly, IBM can afford to buy the Unix copyrights
and patents from Novell and I think Novell would sell them. That would bring
everything but the Unix trademark under the same roof. And I don't think IBM
really cares that much about the Unix trademark. They care much more about the
Linux trademark. So let's say IBM buys up all these rights for a few hundred
million dollars, then puts the whole package under the General Public License,
essentially making Unix into an Open Source product.
Why would IBM do something like that? They'd do it to sell more computers.
People forget that IBM is mainly a hardware and services company. By putting
Unix under the GPL they would become heroes to the programmers and system
admins and end up selling even more hardware and services. Remember, IBM
already invested $1 billion in Linux and claimed to have made that money back
within a year. Buying SCO and the Novell IP could be viewed as just the next
step of that very smart investment.
[...snip unrelated sections...]
__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
Warren did:
> > $ zcat tape1.tar.gz | strings | grep -i copyr | uniq -c | sort -rn
On Thu, Jun 05, 2003 at 11:35:53AM -0700, Kenneth Stailey wrote:
> why did you run "uniq -c | sort" and not "sort | uniq -c" ?
Because it was late. I really should have done
$ zcat tape1.tar.gz | strings | grep -i copyr | sort | uniq -c | sort -rn:
56 /* Copyright (c) 1979 Regents of the University of California */
20 c/* Copyright (c) 1979 Regents of the University of California */
6 Copyright \fB\^\s+8\v'.25m'\(co\v'-.25m'\s-8\|\fP1983 Western Electric Company, Incorporated.
6 "\001c\bO", /*copyright*/
4 Portions of this document were copyrighted
4 PAIR('c','o'), 0336, /*copyright*/
2 x/* Copyright (c) 1979 Regents of the University of California */
2 t/* Copyright (c) 1979 Regents of the University of California */
2 e/* Copyright (c) 1979 Regents of the University of California */
2 copyright
2 0153, /*copyright*/
2 .\" Portions of this document were copyrighted
2 'co', 0336, /*copyright*/
2 "\033\016O\b#\033\017", /*copyright*/
2 "\003(c)", /*copyright*/
2 "\001\0338c\0339", /*copyright*/
2 * Copyright 1975 Bell Telephone Laboratories, Incorporated
2 /* Copyright 1976, Bell Telephone Laboratories, Inc.,
There, that's better :-)
Warren
I came across this:
cm.bell-labs.com/cm/cs/who/dmr/bsdi/930303.ruling.txt
17 U.S.C. 101. Version 32V source code has now been distributed,
without notice, to literally thousands of licensees.
Consequently, Plaintiff can have no valid copyright on 32V unless
it can fit within one of the statutory or common law escape
provisions.
The three statutory escape provisions are listed in
section 405(a). These provisions relieve a copyright owner from
the harsh consequences of noticeless publication if the owner
(i) omitted the notice from a "relatively small number of copies;"
(ii) registers the work within five years of publication, and then
makes a "reasonable effort" to add notices to the noticeless copies
already distributed; or (iii) proves that a third party omitted,
notice in violation of an express agreement in writing 17 U.S.C
405(a)(1)-(3).
Plaintiff cannot avail itself of any of these provisions.
Notice was omitted from thousands of copies of 32V; no contractual
agreements require the licensees to affix notice;
Plaintiff failed to copyright 32V until 1992, well over five years
after 32V was published; and Plaintiff has not yet made reasonable
efforts to add notices to the many noticeless publications of 32V.
Consequently, Plaintiff must try to fit within the common-law
doctrine of limited publication.
and I felt like asking a few questions in relation to Sys III - was it
copyrighted? When? And has SCO's publication of said Sys III on its Ancient
Unix web site created the presumption that SCO has no further interest in Sys
III?
Wesley Parish
--
Mau e ki, "He aha te mea nui?"
You ask, "What is the most important thing?"
Maku e ki, "He tangata, he tangata, he tangata."
I reply, "It is people, it is people, it is people."
http://news.com.com/2100-1016_3-1013229.html
Contract illuminates Novell, SCO spat
By Stephen Shankland
Staff Writer, CNET News.com
June 4, 2003, 3:01 PM PT
A 1995 contract sheds light on the conflicting Unix ownership claims by Novell
and SCO Group, with SCO receiving broad rights to the operating system but
Novell retaining copyrights and patents.
According to a copy of the contract obtained by CNET News.com, Novell sold "all
rights and ownership of Unix and UnixWare" to the SCO Group's predecessor, the
Santa Cruz Operation. However, the asset purchase agreement, filed with the
Securities and Exchange Commission, specifically excludes "all copyrights" and
"all patents" from the purchase.
"This agreement is kind of murky...You end up with a lot of questions, to put
it mildly," said Mark Radcliffe, an intellectual property attorney with law
firm Gray Cary.
While the contract squarely leaves the copyright with Novell, a section that
gives to SCO "all claims...against any parties relating to any right, property
or asset included in the (Unix) business" could be interpreted to give SCO the
right to enforce the copyright, Radcliffe said. "The question is, even though
(Novell) didn't assign the intellectual property (to SCO), did (Novell) assign
the rights to enforce the patents and copyrights?"
The Unix ownership issue is central to a debate about whether companies can be
taken to court for using Linux. On May 14, SCO claimed in letters sent to 1,500
of the world's largest companies that using Linux could open them to legal
liability because Unix source code has been copied into Linux.
That copying, if proven and illegal, could violate Unix copyrights and the
independent spirit of the open-source movement that creates Linux, but the
contract indicates SCO won't have a simple time relying on Unix copyrights in
such a case.
A week after SCO's letter, Novell said it never sold SCO the Unix copyrights
and patents and that SCO's actions could bring legal action on itself. "We
believe it unlikely that SCO can demonstrate that it has any ownership interest
whatsoever in those copyrights," Novell Chief Executive Jack Messman said in a
letter to SCO.
The Unix ownership debate grew from SCO's $1 billion lawsuit against IBM,
alleging Big Blue breached its contract with SCO and misappropriated SCO's
trade secrets by moving Unix intellectual property into Linux. IBM denies the
claims.
SCO didn't immediately respond to questions about how the contract supports its
claims to rights of copyright enforcement, but company Chief Executive Darl
McBride last week said the contract had "conflicting statements."
"It doesn't make sense. How would you transfer the product but not have the
copyright attached? That would be like transferring a book but only getting the
cover," McBride said.
Novell continues to disagree with SCO. "It's pretty clear that patents and
copyrights were excluded and not included in the business as it's described (in
the contract), so we don't believe SCO would have copyright and patent
enforcement rights," Hal Thayer, vice president of communications for Novell,
said Wednesday.
Novell is basing future operating system products on Linux, and open-source
advocates say they are reassured by Messman's words that the company won't
press its own copyright claims. "Novell is an ardent supporter of Linux and the
open-source development community," Messman has said.
"It's difficult to imagine any scenario in which we'd bring Unix copyright
infringement action against Linux users. We certainly don't have any plans to
do any such thing...and we wouldn't have undertaken this whole call to SCO to
prove their claims if that was the road we wanted to pursue," Thayer said.
The 1995 contract appears to give Novell the edge in the copyright debate, said
John Ferrell, an intellectual property attorney with Carr and Ferrell, who
reviewed the contract.
"This would support Novell's contention that SCO does not own the copyrights
and does not have the right to litigate" a copyright infringement case, Ferrell
said. However, he said, the contract does indicate SCO could pursue a case that
a Unix licensee breached its contract.
But the contract is odd, Ferrell said. "It's very unusual to have the transfer
of a software program and not have the rights of copyright transferred as
well," he said.
SCO vehemently argues that it has copyright enforcement rights, but in any
case, it doesn't need the Unix copyright to go after Linux users.
"I think it's perfectly clear we have the rights to enforce copyright claims,"
McBride said in an interview after Novell challenged SCO's Linux actions. But
more likely than a copyright case, would be one based on breach of contract, he
said.
"The letter went to 1,500 large companies around the world, the majority of
which all have (Unix) System V licenses with us...We do have sublicense
rights," McBride said. "They sign up for the fact that they will not
misappropriate the code." The sublicenses come through Unix purchases made with
direct Unix licensees such as Silicon Graphics, Hewlett-Packard and IBM, he
said.
But the absence of copyright and patent claims in SCO's lawsuit against IBM is
telling, Gray Cary's Radcliffe said. Copyright and patent claims can make a
strong case.
"If they had the rights to enforce the copyrights, how come that didn't show up
in the IBM suit?" Radcliffe asked. "It's very weird they would bring a lawsuit
on trade secret (misappropriation) and unfair competition and not put in
copyrights and patents. Those are the strongest rights. Particularly with IBM,
you don't go out and say, 'I'm not going to take the elephant-hunting rifle
with me, I'm just going to take my .22-caliber.'"
SCO has said it has the option to include copyright claims later. But while
it's said Unix code was copied into Linux, it hasn't yet said who it believes
is responsible. SCO says it will show proof of the copying later this month to
some neutral parties.
SCO's suit mentions concepts and methods, but not copyrights: "It is not
possible for Linux to rapidly reach Unix performance standards for complete
enterprise functionality without the misappropriation of Unix code, methods or
concepts to achieve such performance and coordination by a larger developer
such as IBM."
Radcliffe said copying methods and concepts are much weaker evidence than
copying code. "If they did enough due diligence to figure out there were
concepts there, how the heck did they miss that there was actual code copying?"
he asked.
__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
There's an old joke:
If the law is against you, argue the facts.
If the facts are against you, argue the law.
If both are against you, call the other attorney names.
It's possible this is an elaborate tactic to step on IBM's feet until IBM apologizes - see "The Mouse That Roared". It could be that the issues are so convoluted, the SCO folks are very crafty (and think they can irritate Big Blue enough that IBM will pay them to go away). But it is indeed possible that they are really this clueless. There are many examples of businesses that once held pre-eminent positions, layed low by bonehead business decisions.
In any event, baseless lawsuits are a common business tool these days. And in a country where you can become independently wealthy by spilling coffee in your lap, and you can lose the popular vote by a large margin but be appointed to the highest office in the land by your daddy's Supreme Court - is any legal maneuver really a surprise anymore?
I printed out my "ancient UNIX" license (I got a no-charge license), I'm not erasing my RK05s yet. :-) -- Ian
NOTE: The above is my personal ranting, and should not be construed to reflect the policies or opinions of my employer.
________________________________
From: tuhs-admin(a)minnie.tuhs.org on behalf of Larry McVoy
Sent: Thu 5/29/2003 7:42 PM
To: tuhs(a)minnie.tuhs.org
Subject: [TUHS] Re: TUHS digest, Vol 1 #159 - 12 msgs
> SCO is blustering more and more as the open source community exposes
> them for the fruads that they have become.
In the for what it is worth department, I happen to know that this
stuff is more complex than it seems. For instance, I am pretty sure
that ATT should have won their lawsuit over the BSD stuff and if you
doubt that I'd suggest that you go compare the UFS code against the 32v
or v7 code. bmap() is a good place to look. Any suggestions that that
was completely rewritten are patently false, at least in my opinion.
I'm a file system guy, I've done a lot of work in UFS, I'm intimately
familiar with the code. In fact, I defended UFS against LFS when Kirk
wouldn't (LFS is a friggin' joke, any file system hacker knows that the
allocation policy is 90% of the file system).
I do not have knowledge of the code it is that SCO says infringes. And I
think that SCO is about as astute as I am in terms of public relations
(we both tend to be our own worst enemies and I thought I was without
peer in that department :-) But I suspect that there is at least some
merit to what they are claiming. I have to believe that nobody is stupid
enough to have zero data and jump out in public like they are doing.
That's just way too far over the top. Anything is possible I guess,
but doesn't it seem just a little unlikely that a corporation would
commit that public a suicide? I'll probably be proved wrong but I'm
a CEO, running a small company, much smaller than SCO, and there is
no way I'd stick my neck out that far with no data to back it up.
I'd like to think I'm smarter than they are but I tend to doubt it,
they have more experience.
--
---
Larry McVoy lm at bitmover.comhttp://www.bitmover.com/lm
_______________________________________________
TUHS mailing list
TUHS(a)minnie.tuhs.org
http://minnie.tuhs.org/mailman/listinfo/tuhs
> SCO is blustering more and more as the open source community exposes
> them for the fruads that they have become.
In the for what it is worth department, I happen to know that this
stuff is more complex than it seems. For instance, I am pretty sure
that ATT should have won their lawsuit over the BSD stuff and if you
doubt that I'd suggest that you go compare the UFS code against the 32v
or v7 code. bmap() is a good place to look. Any suggestions that that
was completely rewritten are patently false, at least in my opinion.
I'm a file system guy, I've done a lot of work in UFS, I'm intimately
familiar with the code. In fact, I defended UFS against LFS when Kirk
wouldn't (LFS is a friggin' joke, any file system hacker knows that the
allocation policy is 90% of the file system).
I do not have knowledge of the code it is that SCO says infringes. And I
think that SCO is about as astute as I am in terms of public relations
(we both tend to be our own worst enemies and I thought I was without
peer in that department :-) But I suspect that there is at least some
merit to what they are claiming. I have to believe that nobody is stupid
enough to have zero data and jump out in public like they are doing.
That's just way too far over the top. Anything is possible I guess,
but doesn't it seem just a little unlikely that a corporation would
commit that public a suicide? I'll probably be proved wrong but I'm
a CEO, running a small company, much smaller than SCO, and there is
no way I'd stick my neck out that far with no data to back it up.
I'd like to think I'm smarter than they are but I tend to doubt it,
they have more experience.
--
---
Larry McVoy lm at bitmover.comhttp://www.bitmover.com/lm
