On 2012-11-23 13:53, Bill Gunshannon wrote:
> In article <k8npdd$gja$
1...@iltempo.update.uu.se>,
> Johnny Billquist <
b...@softjar.se> writes:
>> On 2012-11-23 04:17, Bill Gunshannon wrote:
>>> In article <k8mnoc$587$
1...@iltempo.update.uu.se>,
>>> Johnny Billquist <
b...@softjar.se> writes:
>>>> On 2012-11-22 23:43, Bill Gunshannon wrote:
>>>>> In article <k8m7fp$vf2$
1...@iltempo.update.uu.se>,
>>>>> Johnny Billquist <
b...@softjar.se> writes:
>>>>>> On 2012-11-22 15:18, Bill Gunshannon wrote:
>>>>>>> I have an emulated 11/73 with 4M of memory, a DEQNA, a KDA50 with 4 RA81
>>>>>>> disks, an RQDX3 and an RXV21, and both TS11 and TK50 tapes.
>>>>>>
>>>>>> Nice setup.
>>>>>
>>>>> Yeah, sometimes you can actually do a lot more in emulation than you
>>>>> could ever hope for in real hardware.
>>>>
>>>> Mostly speed, though.
>>>> Question, though. Why not emulate an 11/93?
>>>
>>> Not in the list of supported CPU's. Can probably add the 83 and 93 later
>>> when I have everything set up to build a newer version. Looking at
>>> changing the partitioning scheme (at least for the RA81) as well. /usr
>>> is way to small even for their own distribution.
>>
>> Doh. They stopped Ultrix-11 too soon. :-)
>
> Yes, but then, some of us think they stopped the PDP-11 too soon, :-)
Indeed. But you can still buy a new PDP-11. Just go to Quickware
(
quickware.com), unless they somehow have forgotten that they are out of
business. :-)
The software side is way murkier, unfortunately. :-(
>>> But, as far as CPU goes what other than speed did the 93 really offer?
>>
>> TOY clock. Memory and serial ports on the same card as the CPU.
>
> Well, the TOY clock is nice if you have real hardware, but I have
> another solution. I am going to provide a utility to keep the time
> synched using an old RS-232 connected GPS receiver. I havr an old
> Delorme Earthmate and I figure there a thousands of them floating
> around. may even look on eBay and grab a few more. The rest are no
> big deal in hardware and pretty much meaningless in emulated systems.
> I meant the CPU itself. And, as I said, I think speed was pretty
> much it and that, too, doesn't have much meaning in an emulated
> system as I figure an 11/02 and an 11/93 process instructions at the
> same speed. Unless there is some throttling being done that I was
> not aware of.
Right. From a CPU point itself, there is no difference between an 11/53,
11/73, 11/83 or 11/93 (or even 11/84 and 11/94). They all use the J-11.
But I think it is relevant to talk about the system, and not the CPU.
The 11/73 is different than an 11/93, even though they use the same CPU,
and you are emulating an 11/73.
TOY is definitely nice. Having some other clock solves the same problem,
making it less important, yes.
>>>>> And another interesting note. There are Digital Copyrights in all
>>>>> the source files. There are no AT&T Copyrights in any of the source
>>>>> files and only a few BSD Copyrights, Am I the only one who doubts
>>>>> that DEC rewrote the whole operating system in a clean room environment?
>>>>
>>>> People were a bit more sloppy back then.
>>>
>>> Not so sure it was sloppy. Wasn't this also a major point in the BSDI-AT&T
>>> lawsuit? Hadn't AT&T taken all of UCB's Copyright notices out of the code
>>> they used, like networking?
>>
>> It was, and yes. But was the removal done because they tried to hide the
>> origins, and pretend the code was done by them, or just because they
>> just wanted uniform file headers, and noone really gave much thought to
>> whether this was formally ok to do or not?
>> I think the latter, and I think that was just sloppy. But I might be wrong.
>
> Well, I thought the AT&T case was that someone said "AT&T software only
> has AT&T Copyrights" so the others were very deliberately removed. I
> suspect it was quite the same with DEC. And people think nobody understands
> copyright today!!
I doubt we'll even know the truth of the matter, but if they tried to
pull that stunt intentionally, then they obviously failed miserably.
But I think your comment can be read the same as mine about having
uniform file headers. And such a thing could have been executed without
anyone really thinking about the legality of the issue.
I guess it depends on whether the headers were changed prior to, or
after the lawsuit started appearing on the horizon.
Since DEC never even had a lawsuit about it, and still changed all the
headers, I think I'm leaning towards the "sloppy" argument there.