I agree with your premise that copyright can be detrimental to broader interests, and the case of "obsolete but historically interesting" software is a prime case in point. However, copyright holders can choose to make things readily available without placing them in the public domain; the 'Ancient UNIX' license is a great example. If they choose not to do so, the law does allow them recourse. I doubt they would consume the resources to execute on that against individuals who are running old software for non-commercial purposes; I suspect that those who commit such indiscretions wholesale may not be treated with such latitude.
And, IMHO, those who baldly advertise their general disdain of copyright law are pretty much asking for it. -- Ian
My opinions are my own, and do not necessarily represent my employer's opinions.
-----Original Message-----
From: Mirian Crzig Lennox [mailto:mirian@cosmic.com]
Sent: Thu 9/5/2002 4:56 PM
To: tuhs(a)minnie.tuhs.org
Cc:
Subject: Re: [TUHS] Ultrix...
On Wed, 4 Sep 2002 20:15:52 -0700, Ian King <iking(a)microsoft.com> wrote:
>"It is a problem only if you choose to honor copyright laws." I can
> only hope that others (dis)regard your property rights, as you
> (dis)regard the property rights of others. BTW, where do you live? I
> could use a new monitor or two....
It is possible to respect property rights and yet disagree (to the
point of disobedience) with how the concept has been lately twisted by
monied interests in the United States.
The purpose of copyright is not to be a form of property; if it were,
copyrights would not expire. The purpose of copyright is to enrich
the public domain by encouraging authors to publish their works, by
ensuring them exclusive right to profit from their work for a limited
time after which time *the work passes into the public domain*. This
is plainly stated in the U.S. Constitution as the basis for copyright
law: "To promote the progress of science and useful arts, by securing
for limited times to authors and inventors the exclusive right to
their respective writings and discoveries." [Article I, section 8].
In fact, the concept of "intellectual property" is a fairly recent
perversion, and the consequence has been a steady depletion of the
public domain. When a piece of software (and Ultrix is an excellent
example) is tied up in copyright long after it is of any value to
anyone beyond pure academic interest, nothing is added to anyone's
wealth, and society as a whole loses.
--Mirian
_______________________________________________
TUHS mailing list
TUHS(a)minnie.tuhs.org
http://minnie.tuhs.org/mailman/listinfo/tuhs
<nl>
> I guess my MACRO-11 implementation of C isn't good enough.
> (Well, it ain't mine, it's the normal DECUS C, but I'm hacked some at it.)
<nl><nl>
and to bring this full circle, do you know where DECUS C came from?
<nl><nl>
> From: Al Kossow <aek(a)spies.com>
> To: pups(a)tuhs.org
> Subject: Re: [pups] Bringing up the fist C compiler
> Content-ID: <9012_13188_1031248039_2(a)spies.com>
> Date: Thu, 5 Sep 2002 10:47:19 -0700
>
> <nl>
> > I guess my MACRO-11 implementation of C isn't good enough.
> > (Well, it ain't mine, it's the normal DECUS C, but I'm hacked some at i=
> t.)
> <nl><nl>
>
> and to bring this full circle, do you know where DECUS C came from?
> <nl><nl>
It is my understanding that it was a "clean room" reimplementation of
the 6th Edition Unix "cc" and "as".
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst(a)ucsd.edu
Peter Wrangell <pwrangell(a)bsdmercs.org> wrote:
> I am looking for a copy of Ultrix 4.5 preferably on TK70 tapes but any
> medium will do. I have a MicroVax 3300 that I would like to breath life
> into again.
I can't help you with 4.5, but I have the full V4.00 TK50 distribution and it
fully supports MV3300 with DSSI. The tape images are on my FTP site in:
ivan.Harhan.ORG:/pub/UNIX/thirdparty/Ultrix-32/ult400vaxdist-tk50
On the same site I also have full sources for V2.00 and V4.20. (I have no
sources for the version for which I have the dist, and no dists for the
versions for which I have the sources... I guess I need to bite the bullet and
compile V4.20 myself. Some day maybe.)
MS
About a thousand years ago, I recall hand-building programs for 8-bit microprocessors (in what we'd call embedded systems today). In many cases, I was the "assembler", writing directly in machine code which was then either keyed in through front-panel switches or burned into a PROM.... -- Ian
-----Original Message-----
From: Johnny Billquist [mailto:bqt@update.uu.se]
Sent: Thu 9/5/2002 5:05 AM
To: Tim Bradshaw
Cc: pups(a)minnie.tuhs.org
Subject: Re: [pups] Bringing up the fist C compiler
On Thu, 5 Sep 2002, Tim Bradshaw wrote:
> * Johnny Billquist wrote:
>
> > How? It was written, of course. In assembler. By that time, you already
> > had the assembler, an editor, and other commonly used system programs, so
> > it's just a case of the normal development cycle.
>
> Is this known or is it deduction?
[...]
Ah. Ok, now I understand what you're asking for.
You want to know what the first C was written in, and what that
compiler/assembler was written in/on, and so on...
No, I'm just deducting. Since the reference posted said that TMG was the
first higher level language implemented, it follows that it must have been
written in a low level language, namely assembler.
Admittedly, the PDP-7 TMG *could* have been written in some high level
language on some other machine using some tool that made a PDP-7
executable, so your guess is as good as mine.
But even though I cannot account for all steps, I can guarantee that at
the end of the chain, you *will* find assembler.
I guess my MACRO-11 implementation of C isn't good enough. :-)
(Well, it ain't mine, it's the normal DECUS C, but I'm hacked some at it.)
Johnny
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)update.uu.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
_______________________________________________
PUPS mailing list
PUPS(a)minnie.tuhs.org
http://minnie.tuhs.org/mailman/listinfo/pups
Greetings,
I am looking for a copy of Ultrix 4.5 preferably on TK70 tapes but any
medium will do. I have a MicroVax 3300 that I would like to breath life
into again. Unfortunately the version in the Archives is too old to be
of use and it seems that there is no DSSI support in NetBSD. I would be
willing to trade old computer parts in return(I have Old SGI, Dec PDP
and and Sun Stuff). Any help would be appreciated. Thanks.
-Peter
pwrangell(a)bsdmercs.org
On Wed, 4 Sep 2002, Dennis Ritchie wrote:-
> I'm not positive about the logo on our first PDP-11.
The picture of Dennis and Ken in front ASR-33's hints at a pdp11/20 logo
on the console. The 11/20 I have (built 29/1/71, SN 821) has just plain 'pdp11'.
The lead time on getting the machine was about 6 months. I suspect that the
/20 was added as other models were in the pipeline (/05,/45).
For a picture, see http://www.psych.usyd.edu.au/pdp-11/11_20.html
> Incidentally, the machine's handbook was a wonder.
Indead it was
The front cover is interesting, in that it shows a table top version of the
11/20. It was quite possible to run one just with paper tape and an ASR33 with
the reader/punch option. There was a similar option for the pdp8/e.
The only obvious change between the first and second edition handbooks was that
the latter changed the last page from a picture of a young lady in front of
a machine to a table of Unibus pin assignments.
> From: Dennis Ritchie <dmr(a)plan9.bell-labs.com>
> Subject: [pups] Unix and PDP11/20 (was PDP9?)
> Date: Wed, 4 Sep 2002 00:21:40 -0400
>
> I'm not positive about the logo on our first PDP-11.
The text accompanying the picture "Ken and Den" somewhere on your web site
says that the logo on your first PDP-11 was just "PDP-11" without the /20.
> On the earliest handbook I have, the front panel photo
> just shows "PDP11", though inside the handbook
> it does talk about the two models (11/10 and 11/20).
> Both had the same KA11 processor, but the basic
> 11/10 sported 1024Kw ROM memory plus a generous
> 128 words of RAM, while the 11-20 had
> 4096Kw core RAM, and the ASR33 Teletype was included.
> You could add more RAM to the 11/20.
I fear that you have suffered a "units slip" saying 1024Kw
and 4096Kw when you meant 1Kw and 4Kw respectively.
> Incidentally, the machine's handbook was a wonder.
> In 104 pages (each 5.25x8 inches), it described the whole
> system: not only the instruction set but the theory
> of the Unibus (including some logic diagrams) together with
> programming specifications for the TTY, the clock,
> and the paper tape reader.
>
> Dennis
Agreed, "PDP11 Handbook Second Edition" was a really good book
Occasionally I wonder if I ever had my hands on a "First Edition"
and threw it away when the second edition came out. Not knowing
that both the computer and the handbook would become classics.
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst(a)ucsd.edu
Hi,
I have a micro PDP11/73 equipped with an RD53, RX50 and a Cipher mag tape
drive (untested). The machine currently boots into TSX (although I don't
have usernames/passwords so no shell access).
I'd like to get BSD2.11 onto the machine. What is going to be the best
route? I assume that my chances of breaking through TSX security (so I can
use kermit) are small, so is vtserver going to be the easiest method?
Toby
Tobias Russell
Managing Director
Russell Sharpe Limited
The Tannery, Tannery Lane, Bramley, Surrey. GU5 0AJ England
Tel: +44 (1483) 894158
Fax: +44 (1483) 898932
Email: toby(a)russellsharpe.com
Carl Lowenstein:
I suppose the easiest break-in tool would be a floppy disk with a bootable
RT11 on it.
Or, if your goal is just to drain the machine's brain entirely
and start over, which is likely the case if you want to put 2.11
on it: dig up the standalone disk diagnostic (is XXDP easily
available somewhere these days?) and reformat the disk.
Norman Wilson
Toronto ON