Just a quick question. Was the `dc' command introduced with one of the
BSD releases or did it exist in an earlier version of Unix like the 6th or
7th Edition?
-brian.
--- Brian Chase | bdc(a)world.std.com | http://world.std.com/~bdc/ -----
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id DAA27477
for pups-liszt; Tue, 26 Oct 1999 03:20:12 +1000 (EST)
Brian Chase asked:
> Just a quick question. Was the `dc' command introduced with one of the
> BSD releases or did it exist in an earlier version of Unix like the 6th or
> 7th Edition?
I see it on the System III and Version 7 systems. I don't see it in V6 distro
however.
Cheers,
-skots
--
Scott G. Akmentins-Taylor InterNet: staylor(a)mrynet.com
MRY Systems staylor(a)mrynet.lv
(Skots Gregorijs Akmentins-Teilors -- just call me "Skots")
----- Labak miris neka sarkans -----
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id EAA27681
for pups-liszt; Tue, 26 Oct 1999 04:03:31 +1000 (EST)
>From Eric Fischer <enf(a)pobox.com> Tue Oct 26 04:15:15 1999
Received: from csadfa.cs.adfa.edu.au (csadfa.cs.adfa.edu.au [131.236.21.6])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id EAA27677
for <pups(a)minnie.cs.adfa.edu.au>; Tue, 26 Oct 1999 04:03:25 +1000 (EST)
Received: from 216-80-13-97.d.enteract.com (216-80-13-90.d.enteract.com [216.80.13.90])
by csadfa.cs.adfa.edu.au (8.9.0/8.9.0) with ESMTP id EAA09243
for <pups@minnie@cs.adfa.oz.au>; Tue, 26 Oct 1999 04:03:21 +1000 (EST)
Received: (from eric@localhost)
by 216-80-13-97.d.enteract.com (8.9.3/8.9.3) id NAA25814;
Mon, 25 Oct 1999 13:15:15 -0500 (CDT)
(envelope-from eric)
Date: Mon, 25 Oct 1999 13:15:15 -0500 (CDT)
Message-Id: <199910251815.NAA25814(a)216-80-13-97.d.enteract.com>
From: Eric Fischer <enf(a)pobox.com>
To: bdc(a)world.std.com
Subject: Re: When did the `dc' command first appear?
In-Reply-To: <Pine.SGI.4.04.9910250931400.1849-100000(a)world.std.com>
References: <Pine.SGI.4.04.9910250931400.1849-100000(a)world.std.com>
Cc: pups@minnie@cs.adfa.oz.au
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Brian D. Chase writes,
> Just a quick question. Was the `dc' command introduced with one of the
> BSD releases or did it exist in an earlier version of Unix like the 6th or
> 7th Edition?
It appears in the First Edition manual, and according to A Quarter
Century of Unix, it's even older than that. "There was also a version
of dc, desk calculator, a very very early program. That was actually
the first program that ran on the PDP-11. It ran standalone before
there was an operating system." (p. 35)
eric
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id EAA27847
for pups-liszt; Tue, 26 Oct 1999 04:24:20 +1000 (EST)
>From Mark Green <mark(a)cs.ualberta.ca> Tue Oct 26 04:23:48 1999
Received: from scapa.cs.ualberta.ca (root(a)scapa.cs.ualberta.ca [129.128.4.44])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id EAA27843
for <pups(a)minnie.cs.adfa.oz.au>; Tue, 26 Oct 1999 04:24:12 +1000 (EST)
Received: (from localhost user: 'mark' uid#150 fake: goodfare.cs.ualberta.ca)
by scapa.cs.ualberta.ca id <S433932AbPJYSXv>;
Mon, 25 Oct 1999 12:23:51 -0600
Subject: Re: When did the `dc' command first appear?
In-Reply-To: <Pine.SGI.4.04.9910250931400.1849-100000(a)world.std.com> from Brian D Chase at "Oct 25, 1999 09:34:40 am"
From: Mark Green <mark(a)cs.ualberta.ca>
To: bdc(a)world.std.com (Brian D Chase)
Date: Mon, 25 Oct 1999 12:23:48 -0600 (MDT)
Cc: pups(a)minnie.cs.adfa.oz.au
X-Mailer: ELM [version 2.4ME+ PL53 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <19991025182355Z433932-29789+188(a)scapa.cs.ualberta.ca>
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
> Just a quick question. Was the `dc' command introduced with one of the
> BSD releases or did it exist in an earlier version of Unix like the 6th or
> 7th Edition?
>
I think it was in 6th, but thats straining my memory a bit.
--
Dr. Mark Green mark(a)cs.ualberta.ca
Professor (780) 492-4584
Director, Research Institute for Multimedia Systems (RIMS)
Department of Computing Science (780) 492-1071 (FAX)
University of Alberta, Edmonton, Alberta, T6G 2H1, Canada
Hi everyone,
I have already posted this program to the PUPS list back in December 1998, but
people are asking for it again, and also there are people on the Quasijarus
list and not on the PUPS list who want it, so I'm posting it again, to both
lists.
This program can read a tape on a UNIX box without the user having to know
anything about its format. This program automatically determines how many files
are on the tape, what is the record size for each, and whether there are any
oddities such as partial records. It saves each tape file into a separate disk
file and produces a log of everything found on the tape.
It's a simple C program and should compile and run on virtually any UNIX or
UNIX-like system. The original version was written by one guy I met on another
list once and then it was significantly enhanced by me. I include it below as
a uuencoded 'compress -s'ed tarball.
--
Michael Sokolov Harhan Computer Operation Facility
Special Agent 615 N GOOD LATIMER EXPY #4
International Free Computing Task Force DALLAS TX 75204-5852 USA
Phone: +1-214-824-7693
ARPA INET: msokolov(a)meson.jpsystems.com
Enclosure: uuencoded cptape.tar.Z:
begin 644 cptape.tar.Z
M'Z'M6&U3&S<0YJOU*P0T@PW&^,`X&3NF0PBT:0G,0-(WFNF(.YU]PUER[^08
MFO#?N[LZ^>X<4MK.0#[D=B;#25KMR[-O<EZ+*QE&L5QZ0/+:[6ZGPY<X]]K=
M'?S+.[NTMN1UGG+>[>[L[NZTM[UM8FOO+O'V0QKE:)H:D7"^-+Y..]U_X'L[
M#,X?PYY'IE6V"A%XG64!#W7"_8D1$\E6&3M]\<.@-A:1:FEV?G:0??N,'1P=
M[W]W/JAMGC)FV7NU;^K`WF`UW^?VDV]J)XM]:3<K^@R='>Z_?'WXL#KNJ7^O
MLUVH_YVGR-;>[5;U_QAD"Y0G4@0I%YP6D>):29Z.M&GR22S\2`VY%/[('E.C
MB)31P)_*B4B$D3R(TBM&)T(%/-;#(5XR(^2$IC(6)M**BTL]-:#,UTG`T^@O
MF;9<`R%%,OTW>NR)$F,9\#7\;BFUUN2SD4PD4XI'*2DV,[T91,/(P.T_IU*9
M2,1<3<>7,N$Z)!82!'81.^JL@^^!]*.QB!DFAD$O9I$9\;;7:/$W(YG:6P!6
M(KD/N!FP(K(B_&F2(a)!XP$EPT.KEI\2-HJ&84I0PX4ZW(2D5PHV3!E9R1YB9!
M/M/3..`*\8KCFTP\<,T%4H..3)/Y`0=@X(OP3J8J:[4\3/08C4DD0'LREV0/
M(:2HX%+2#9&"N#C6L[0WC\)F3.98%Y^G$\!"Q'N,$;CYAL,8@^#`3(1U!0!\
M'_F@S/(27$TN6\-6DVW!V99*QJ:-8(*0613'N9]W!99<IJQ8C!9#U\N7YK:O
MV:@)'D>I00L!ACRM4GM*5N?)R)RFUM<SK^Q$?U@=]_3_W=UNN]#_V\BVW?6J
M_O\8M+7.^+IK#YO<UY.;8IE`X4S5E=(SY0HEEFIH1G!IB['52/GQ-,"^8()(
MMT9[A:W05R8N;\DD40M<Z4VZ194.NVPU@.*%-GCRXNU1C9X&J".D-=^#5?E>
MI/U,@U1!%#(&PX(/I=$3P^N-/I/71B;0&$<0X'78%,EPOHFLL!6IH(E_P;)^
MKA_4G;_Z[=":T-UYUJEMK?-]'_VGJ:;Y&,99O=-H\K&XMGA=QMJ_LFVD!@2@
M8C<Y/SA_1>>I:UP_[?^"S=/K_MC*&+?(<!9H!+^._3L$HV"$(BX-<LIN]MG1
MJ^-#OIX=]=D'AA9"`IO(ASBET5!!$R1_+Z=A*).+S)-W?>*<L\0:W+`!5=J>
MD1J0JB<PGP:\O7`#CR"@<.+E_$:C4;@BG;`$+NS$%\_NU$CST4>,`&P\1HCJ
M_?[<E(V-!O_`:L1\>6-DBH,2>&N4.=:LVOP`UOAG#IGUN>G"!QE0@^2IY_S/
M>9ODH^H)B-1)?67^_%E!?CQ)I)E"AGA]6D'D<7YCS(3B=`E#5KOE,H:W0%G!
M8%#0@$<.T8;=@A,RR8]U*NL(7P-.:KA=M`D>29.I#4>/$R\91SSR.C)UCY:W
M\&^20"#"^LH;<&,LDBL8M#`4H6QI*JX^:6]/?U<K31<_NI=];VRX11YS4G%K
M_Z!_N=E@4'J'&H3/&I?!5A"2093!`4`21JF&)T,@C'#M!AYH".BGZ4*XSI+(
M&*DP"1RHRW>@ZG`X=X^VW/]F<<;W^).XA$@SPQ5H'D?R!S7-B]#RA)F6;+O)
M5X[^NY8[5*69W+R`0#1U192\$#W,&@@6O9E*-]K=;G=NN>4:\$WO_@1#29]-
ML$)^>#;,ME2S?*GE-0T[A9K]-),6BG%Y4.@')2.S4/XL$@61[#E@5P'3<F9C
M4>(F"46XRR(a)[4_,H+.#N$JH0YMJG,?X?=MRO^C;+YV)CFR=&EO.PC5^V4>3M
MK23(N5"ZMUR(1,.6QUV!)^&EXO7ZME#S-N=*F=KU+9Z%]H1E-7UR^N;L</_@
M^\.7N&O=HGF&+\LZC%P??J(DP_=VD.&ZS^Q$7L=M-\3PT"_,$C?DZ`?&@)^\
M/3ZVIZ416#JQ]V@8W'4QGZ,<RR+?!&?#>&AC0)NS$8JNUWW8L\^)@A^0$'%O
MI=%`D`]/CPC>%'Y-P.^3ND\K7T#36XO7>A:]LB/N&6*##0&Z@F]X=HAI;'KN
M[K?NKC6-&G61/XN&M1:CG[GP\6/VID'CT&1HL1[9Y+(:WFG`"SY,4S'$VK</
MOPOXV9?9^8Y`@B3&O*!>L-WH+^HK^)0-;!>.$'M%\1QTS5;<*%[.*ZT\AHL"
M,V?S/E1R=R&^&)(+Z_2[?H$C(*S!E")_DY_^<?;R].3X5^B6F5<TI;,;U"[1
MGWFY@`1Z\=G_%G&EDV/CE;')RN@S3[D^E,>7?N]75%%%%554444555111155
/5%%%7Q_]#6D82E<`*```
`
end
Howdy -
> From: pups(a)mrynet.com (PUPS mailing list)
>
> Has anyone successfully booted either the System III
> (...Distributions/usdl/SysIII/) or Ultrix (...Distritutions/dec/Ultrix*)
> tape images? I don't have a real PDP-11 any more, however both the
I don't know what the problem with Ultrix is but I suspect
your trouble with System-III is similar to what I wasted a couple
days on eons ago
Spent a fruitless couple days trying to get Sys-III going on a 11/44
only to have it dawn on me that Sys-III didn't have *any* UMR support
except for the DH-11 - thus an 11/70 with MASSBUS devices was the
only thing Sys-III would run on.
As far as I know no effort was put into Sys-III to deal with 22
bit machines that didn't have a MASSBUS (a la 11/70). PERHAPS
that is what is biting you? Feels likely. I know that no effort
was put in to supporting UMRs on 22bit systems such as the 11/44.
The Supnik and Begemot emulators offer up a ~kdj-11 (11/53, 73, ...)
and not an 11/70 so it could be that Sys-III is trying to do
something 11/70'ish that KDJ-11 based systems don't offer.
Steven Schultz
sms(a)moe.2bsd.com
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id NAA00889
for pups-liszt; Thu, 21 Oct 1999 13:39:50 +1000 (EST)
>From "P.BASKER" <basker(a)protocol.ece.iisc.ernet.in> Thu Oct 21 13:04:09 1999
Received: from uumail-relay-blr.ernet.in (uumail-relay-blr.ernet.in [202.141.1.17])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id NAA00885
for <pups(a)minnie.cs.adfa.edu.au>; Thu, 21 Oct 1999 13:39:39 +1000 (EST)
Received: from ece.iisc.ernet.in (ece.iisc.ernet.in [144.16.64.2])
by uumail-relay-blr.ernet.in (8.9.0/8.9.0) with SMTP id JAA05114
for <pups(a)minnie.cs.adfa.edu.au>; Thu, 21 Oct 1999 09:13:26 +0530
Received: from protocol.ece.iisc.ernet.in by ece.iisc.ernet.in (4.1/SMI-4.1)
id AA29573; Thu, 21 Oct 99 09:09:06+0530
Received: from localhost (basker@localhost)
by protocol.ece.iisc.ernet.in (8.8.7/8.8.7) with SMTP id IAA24170
for <pups(a)minnie.cs.adfa.edu.au>; Thu, 21 Oct 1999 08:34:09 +0530
Date: Thu, 21 Oct 1999 08:34:09 +0530 (IST)
From: "P.BASKER" <basker(a)protocol.ece.iisc.ernet.in>
Reply-To: "P.BASKER" <basker(a)protocol.ece.iisc.ernet.in>
To: pups(a)minnie.cs.adfa.edu.au
Subject: assembler?
In-Reply-To: <199910210259.TAA16059(a)moe.2bsd.com>
Message-Id: <Pine.LNX.3.96.991021082828.24006A-100000(a)protocol.ece.iisc.ernet.in>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Hi ,
Im interested in a PDP-11 assembler that has the MACRO-11 syntax,
I got a book, "Introduction to Computer Systems using the PDP-11 and
Pascal" by McEwans, Thought it would be nice to have the assembler to
check out. I hope the assembler is a load and go assembler cum simulator.
I want to check out some PDP-11 assembly on my linux machine.
Does anyone remember a program called "apout" I think that might work for
cross development (learning).
Bye
P.Basker
Research Program Asst, ECE Dept IISc, India
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id OAA01039
for pups-liszt; Thu, 21 Oct 1999 14:03:45 +1000 (EST)
>From Warren Toomey <wkt(a)cs.adfa.edu.au> Thu Oct 21 14:02:36 1999
Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id OAA01035
for <pups(a)minnie.cs.adfa.edu.au>; Thu, 21 Oct 1999 14:03:38 +1000 (EST)
Received: (from wkt@localhost)
by henry.cs.adfa.edu.au (8.9.2/8.9.3) id OAA00539;
Thu, 21 Oct 1999 14:02:36 +1000 (EST)
From: Warren Toomey <wkt(a)cs.adfa.edu.au>
Message-Id: <199910210402.OAA00539(a)henry.cs.adfa.edu.au>
Subject: Re: assembler?
In-Reply-To: <Pine.LNX.3.96.991021082828.24006A-100000(a)protocol.ece.iisc.ernet.in> from "P.BASKER" at "Oct 21, 1999 8:34: 9 am"
To: basker(a)protocol.ece.iisc.ernet.in
Date: Thu, 21 Oct 1999 14:02:36 +1000 (EST)
Cc: pups(a)minnie.cs.adfa.edu.au (Unix Heritage Society)
Reply-To: wkt(a)cs.adfa.edu.au
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
In article by P.BASKER:
> Hi ,
> Im interested in a PDP-11 assembler that has the MACRO-11 syntax,
> I got a book, "Introduction to Computer Systems using the PDP-11 and
> Pascal" by McEwans, Thought it would be nice to have the assembler to
> check out. I hope the assembler is a load and go assembler cum simulator.
> I want to check out some PDP-11 assembly on my linux machine.
>
> Does anyone remember a program called "apout" I think that might work for
> cross development (learning).
> Bye
Yes, I wrote Apout. It runs user-mode programs from V5, V6, V7, 2.9BSD
and 2.11BSD. So if you could find an assembler for any of these systems
which met your requirements, and produced .o files which could be linked
using the normal Unix linker, you'd be okay.
However, I haven't heard of a Unix assembler with MACRO-11 syntax, and
Apout only runs PDP-11 Unix binaries. So you probably would be better
off with a full emulator running a DEC OS with MACRO-11.
Cheers,
Warren
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id RAA01742
for pups-liszt; Thu, 21 Oct 1999 17:06:23 +1000 (EST)
>From Wilko Bulte <wilko(a)yedi.iaf.nl> Thu Oct 21 09:01:53 1999
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id RAA01732
for <pups(a)minnie.cs.adfa.edu.au>; Thu, 21 Oct 1999 17:06:09 +1000 (EST)
Received: from yedi.iaf.nl (uucp@localhost)
by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id IAA21266;
Thu, 21 Oct 1999 08:51:13 +0200 (MET DST)
Received: (from wilko@localhost)
by yedi.iaf.nl (8.9.3/8.9.3) id BAA44603;
Thu, 21 Oct 1999 01:01:53 +0200 (CEST)
(envelope-from wilko)
From: Wilko Bulte <wilko(a)yedi.iaf.nl>
Message-Id: <199910202301.BAA44603(a)yedi.iaf.nl>
Subject: Re: booting archived Sys III and Ultrix 3.x images
In-Reply-To: <199910202028.NAA49448(a)mrynet.com> from PUPS mailing list at "Oct 20, 1999 1:28:36 pm"
To: pups(a)mrynet.com (PUPS mailing list)
Date: Thu, 21 Oct 1999 01:01:53 +0200 (CEST)
Cc: pups(a)minnie.cs.adfa.edu.au
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-pgp-info: PGP public key at 'finger wilko(a)freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
As PUPS mailing list wrote ...
> Has anyone successfully booted either the System III
> (...Distributions/usdl/SysIII/) or Ultrix (...Distritutions/dec/Ultrix*)
> tape images? I don't have a real PDP-11 any more, however both the
Ultrix-11 V3.1 works just fine on my 11/83. I supplied the binary images
to PUPS from the .5" reel tape ;-) So, yes it can work. My PDP is now
running 2.11BSD btw.
--
| / o / / _ Arnhem, The Netherlands - Powered by FreeBSD -
|/|/ / / /( (_) Bulte WWW : http://www.tcja.nlhttp://www.freebsd.org
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id AAA03366
for pups-liszt; Fri, 22 Oct 1999 00:56:31 +1000 (EST)
Has anyone successfully booted either the System III
(...Distributions/usdl/SysIII/) or Ultrix (...Distritutions/dec/Ultrix*)
tape images? I don't have a real PDP-11 any more, however both the
Begemot P11 and the Supnik emulators produce the following on a
generated boot disk:
#0=unixhptm
ka6 = 1535
aps = 141774
pc = 1476 ps = 30010
trap type 0
ka6 = 1535
aps = 141666
pc = 113444 ps = 30300
trap type 0
panic: trap
The Ultrix images both fail to actually boot from tape, as they
quit after reading the first boot block. Thus I am unable get as
far as being able to generate a disk image for booting.
I'm somewhat confident that my tape image booting and system generation
procedures used with the Supnik emulator are working properly, since I
successfully generate disk systems from both the V7 (Bostic) and
the 2.11BSD boot-tape images.
Any info and interest of others gleefully appreciated :)
-skots
--
Scott G. Akmentins-Taylor InterNet: staylor(a)mrynet.com
MRY Systems staylor(a)mrynet.lv
(Skots Gregorijs Akmentins-Teilors -- just call me "Skots")
----- Labak miris neka sarkans -----
Hi.
I have been given a Bull DSP 2/300 system. The machine is running B.O.S.
version 02.00.12. The machine boots and runs fine and I cal login as Root
and look around the system. The problem I have is that the B.O.S. operating
system is a Unix look-a-like and I can find no-one who actually knows
anything about the box. Most Unix commands work but, being a VMS guy, I
can't run the machine like my Digital MV 2's. Does anyone know anything
about these machines? I particularly want to have a bash at programming the
machine. It appears to have C (This should be fun. I've not touched C for 12
years!)
Also. I have two Digital Micro Vax 2's. The both have hardware problems in
that a) One machine has a system disk which will not come up to speed and b)
The other has a corrupted system_primitives.exe on VMS 5.5-H and so I can't
run either of them! Anyone know where I can get spares which are pre-loaded?
I really would appreciate any help or advice/ pointers etc that anyone can
give.
Rusel Broadway
Senior Systems Analyst
DDI: 01206-25-5745
********************** N O T I C E *********************************
This information transmitted is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged
material. Any review , retransmission, dissemination or other use of,
or taking of any action in reliance upon, this information by persons
or entities other than the intended recipient is prohibited.
If you received this error, please contact the sender and delete all
copies of the message.
This footnote also confirms that this email message has been swept for
the presence of computer viruses, however we cannot guarantee that this
message is free from such problems.
**********************************************************************
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id FAA17930
for pups-liszt; Sun, 17 Oct 1999 05:02:44 +1000 (EST)
>From James Lothian <simul8(a)simul8.demon.co.uk> Sun Oct 17 05:11:03 1999
Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id FAA17926
for <pups(a)minnie.cs.adfa.edu.au>; Sun, 17 Oct 1999 05:02:35 +1000 (EST)
Received: from simul8.demon.co.uk ([212.228.120.103])
by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1)
id 11cZ66-000Dz5-0C
for pups(a)minnie.cs.adfa.edu.au; Sat, 16 Oct 1999 19:02:30 +0000
Message-ID: <3808CDC7.210BC969(a)simul8.demon.co.uk>
Date: Sat, 16 Oct 1999 20:11:03 +0100
From: James Lothian <simul8(a)simul8.demon.co.uk>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: pups(a)minnie.cs.adfa.edu.au
Subject: Re: vtserver
References: <199910141836.LAA21478(a)moe.2bsd.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Hmm.. I seem to remember, from when I was thinking about rolling my own
11 OS a few years ago, that the /34 differs from most of the other
mid-range
11s in automatically restoring the CPU registers on a page fault. I
think I
picked this up from the differences table in the /04, /34 & /60 CPU
handbook.
(This was unfortunately no use at all to me, as I've got a /40 not a
/34.)
Of course, that was a while ago and I might be wrong.
James
"Steven M. Schultz" wrote:
>
> Hi -
>
> > From: Wilko Bulte <wilko(a)yedi.iaf.nl>
>
> I will be doing some more research on this when I get home from
> work tonight.
>
> > I once had Ultrix-11 3.1 running on a dual RK05 11/34. What I'd call a
> > very minimal system ;-) But it ran
>
> That is because DEC put the extra effort into supporting non-split I/D
> machines. The "stock" V7 really wanted a 11/70. In fact there was a
> chapter in the back of one of the manuals/books detailing what it took
> to get V7 running on an 11/40 (it was a non-trivial project).
>
> Several things conspire against V7 and later on 11/34 (or 35, 40, 60,
> etc). The two most notable ones are the limited address space,
> everything (drivers, data structures, general kernel code) must fit
> in 56kb instead of 120kb - (8kb reserved for the I/O page) and lack
> of instruction restart on MMU faults.
>
> I'll take a look at the V7 layout later but my memory is that it
> wanted an 11/70.
>
> Steven Schultz
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id FAA18139
for pups-liszt; Sun, 17 Oct 1999 05:47:02 +1000 (EST)
>From "Steven M. Schultz" <sms(a)moe.2bsd.com> Sun Oct 17 05:42:14 1999
Received: from moe.2bsd.com (0(a)MOE.2BSD.COM [206.139.202.200])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id FAA18135
for <pups(a)minnie.cs.adfa.edu.au>; Sun, 17 Oct 1999 05:46:53 +1000 (EST)
Received: (from sms@localhost)
by moe.2bsd.com (8.9.0/8.9.0) id MAA18843
for pups(a)minnie.cs.adfa.edu.au; Sat, 16 Oct 1999 12:42:14 -0700 (PDT)
Date: Sat, 16 Oct 1999 12:42:14 -0700 (PDT)
From: "Steven M. Schultz" <sms(a)moe.2bsd.com>
Message-Id: <199910161942.MAA18843(a)moe.2bsd.com>
To: pups(a)minnie.cs.adfa.edu.au
Subject: Re: vtserver
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Hi -
> From: James Lothian <simul8(a)simul8.demon.co.uk>
>
> Hmm.. I seem to remember, from when I was thinking about rolling my own
> 11 OS a few years ago, that the /34 differs from most of the other
> mid-range 11s in automatically restoring the CPU registers on a page fault. I
It's not the automatically restoring that is the problem - the /34, /40
(/60, etc) lack the MMU registers that record by how much the cpu
registers have incremented/decremented at the time an instruction has
faulted. SSR1 and SSR2 located at 0177574 and 0177576 respectively.
From the module which handles the instruction restart (mch_backup.s):
* 11/40 version of backup, for use with no SSR1 and SSR2. Actually SSR1
* usually exists for all processors except the '34 and '40 but always
* reads as zero on those without separate I&D ...
What is a dozen lines of code if those registers exist turns into
over 300 lines and even then there is no guarantee (fortunately the
C compiler does not generate the sequences that can not be handled)
it will work.
What's instruction restart used for? The most common case is growing
the stack. The stack for a process starts out small and then kernel
will automatically extend it downwards IF an instruction faults when
accessing the stack area:
sub $N,sp
mov $xxx, XX(sp)
mov -(r4), X(sp)
for dealing with local variables in a function. The other case
is when calling a function:
mov (r0)+, -(sp)
mov $xxx, -(sp)
jsr pc, function
If the reference to (sp) is made and the instruction faults the
kernel will determine if the current stack needs to be extended. It
will then restart the faulted instruction - but to do that it needs
to know what other registers ('r0', 'r4', etc...) might have been
already changed so that it can back out those changes before
restarting the instruction.
In the case of the 11/44, 70, 73, etc there are MMU registers that
will record the fact that "R0" or "r4" or whatever was changed by
2 or not. On the /34 and /40 that capability does not exist and
the kernel can not _always_ guarantee things will work. MOST of the
time it will but...
Interestingly enough there is a difference between the KDJ-11 (11/73)
family and the other 11s which have the SSR1, and 2. From the
bug report and fix for 2.11BSD (update #150):
"The problem is that the KDJ-11 processes the double word store
of the 'movfi' differently than the 11/44 or 11/70. On other
systems (such as the 11/44) the first word is stored successfully
at 0175000 then the program faults when trying to access 0174776
but SP is left at 0174776 with SSR1 (memory management
status register 1) indicating that 'sp' was decremented by 4. The
kernel adjusts 'sp', grows the stack and restarts the instruction.
The 'movfi' then completes successfully.
On a KDJ-11 cpu the story is different. The fault is generated
as expected BUT 'SP' IS STILL 0175002! The kernel sees that 'sp'
is still within the "valid stack region" and DOES NOT grow the
stack at all. SSR1 indicates that no registers were modified
so the kernel does no adjustment of 'sp'. The instruction is
NOT restarted and a SIGSEGV signal is sent to the program.
The problem appears to be only when doing FP instructions, fixed point
operations do not experience any difficulty. The instruction
"cmp -(sp),-(sp)" for example is handled correctly."
Steven Schultz
sms(a)moe.2bsd.com
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id GAA18253
for pups-liszt; Sun, 17 Oct 1999 06:08:29 +1000 (EST)
>From "Steven M. Schultz" <sms(a)moe.2bsd.com> Sun Oct 17 06:07:04 1999
Received: from moe.2bsd.com (0(a)MOE.2BSD.COM [206.139.202.200])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id GAA18248
for <pups(a)minnie.cs.adfa.edu.au>; Sun, 17 Oct 1999 06:08:01 +1000 (EST)
Received: (from sms@localhost)
by moe.2bsd.com (8.9.0/8.9.0) id NAA19063
for pups(a)minnie.cs.adfa.edu.au; Sat, 16 Oct 1999 13:07:04 -0700 (PDT)
Date: Sat, 16 Oct 1999 13:07:04 -0700 (PDT)
From: "Steven M. Schultz" <sms(a)moe.2bsd.com>
Message-Id: <199910162007.NAA19063(a)moe.2bsd.com>
To: pups(a)minnie.cs.adfa.edu.au
Subject: Re: vtserver
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
> From: Warren Toomey <wkt(a)cs.adfa.edu.au>
> > To: Kirk Davis <kbd(a)ndx.net>
> > Do you know of anyone that has used it on a /34? I've punched in the
> > bootstrap and ran it. It loads the boot file from my Linux system.
> > It appears to call it but it halts somewhere in the 70000-70040 region.
> > Nothing comes up on the console. Looks like the memory is over written
> > with the same values over and over again in this area. Any thoughts?
> >
> Sorry for the delay Kirk. It could be that the V7 bootstrap expects
> split I/D, or a different I/O mapping then what's provided on the /34.
>
> I'll punt this to the PUPS mailing list. I have a suspicion that
> you won't be able to install V7, but you should be able to install V6
> or 2.9BSD instead.
I _think_ I know what the problem is...
While the /34 (and /40, etc) can run a stripped down V7 (the necessary
mch.s code exists for example) the kernels that come with the
distribution are split I&D kernels. /hptmunix, etc are all split I/D
executables. Thus you'll be able to toggle in the bootstrap and
get /boot loaded but then fault when loading and/or trying to execute
the kernel.
As I recall the usual way to get Unix on to a /23, 34,etc was to
have a 11/70 around to do the build on, then stage/create the media
(usually an RL02 or similar) on the 70 and sneakernet the pack over
to the /34.
At least that is how it was done when we shoehorned V7 into an 11/23.
Of course we "cheated" in that we had a fellow around who made the
necessary changes to the assembler/compiler/linker to handle kernel
overlays (preceeded the use of them in 2BSD by several years). Thus
we could run a larger kernel than a pure/stock V7. It was an
"interesting" experience running V7 on an 11/23 (maxed out with 248kb
of memory which was fairly expensive at the time). There was just
enough memory left after the kernel was loaded for a couple user
processes. Thus as the '#' prompt you would run "ls" the shell ('sh')
would get swapped out, the 'ls' would run, and then 'sh' would get
swapped back in. Uh, slowed things down just a _little_ bit :-)
Steven Schultz
sms(a)moe.2bsd.com
Mahlzeit
As Warren Toomey wrote ...
> Sorry for the delay Kirk. It could be that the V7 bootstrap expects
> split I/D, or a different I/O mapping then what's provided on the /34.
I'm 99% sure, that it's V7 which I have running (for lower values
of running, because one drive is dead and the power supply needs
to be replaced) on my 11/34A with 128kB RAM and two RL01. I think
I wanted to install V6, but installed V7 because of the RL01 drivers.
I stripped V7 down, so I only needed one RL01 disk pack (I have only
two.) and transfered the disk image via kermit.
I want to install 2.11BSD on my M70 with 512kB RAM (No, more RAM is
to expensive here. 1MB for over US$500.) and a 120MB ST506-type disk,
but had not much time. I want to avoid the way of the disk image,
because I have no BSD installed for the emulator and don't know,
if the transfere of slices of the disk image would be successfull.
(The RT-11 only handles 32MB "disks".) I think the best way would
be to boot from a 2.11BSD floppy and install it via serial port.
(TU-58 emu? Are there 1.2MB 2.11BSD floppies somewhere?)
Mahlzeit
endergone Zwiebeltuete
--
insanity inside
On Wed, Oct 06, 1999 at 11:19:54PM -0700, Kirk Davis wrote:
> Warren,
> I've been checking out your vtserver program. It's a great idea
> and it's been fun to play with. I'm bringing up a /34 and have been
> collecting parts for it for a few months. I've got it set up with
> a few RL02's on it. Few questions for you:
>
> Do you know of anyone that has used it on a /34? I've punched in the
> bootstrap and ran it. It loads the boot file from my Linux system.
> It appears to call it but it halts somewhere in the 70000-70040 region.
> Nothing comes up on the console. Looks like the memory is over written
> with the same values over and over again in this area. Any thoughts?
>
> I'm working on getting a source license from SCO. I'd love to hack on
> this with you if you are interested in any help.
Sorry for the delay Kirk. It could be that the V7 bootstrap expects
split I/D, or a different I/O mapping then what's provided on the /34.
I'll punt this to the PUPS mailing list. I have a suspicion that
you won't be able to install V7, but you should be able to install V6
or 2.9BSD instead.
Cheers,
Warren
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id DAA02824
for pups-liszt; Fri, 15 Oct 1999 03:40:02 +1000 (EST)
>From Wilko Bulte <wilko(a)yedi.iaf.nl> Fri Oct 15 03:18:02 1999
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id DAA02811
for <pups(a)minnie.cs.adfa.edu.au>; Fri, 15 Oct 1999 03:39:52 +1000 (EST)
Received: from yedi.iaf.nl (uucp@localhost)
by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA01702;
Thu, 14 Oct 1999 19:15:18 +0200 (MET DST)
Received: (from wilko@localhost)
by yedi.iaf.nl (8.9.3/8.9.3) id TAA01066;
Thu, 14 Oct 1999 19:18:02 +0200 (CEST)
(envelope-from wilko)
From: Wilko Bulte <wilko(a)yedi.iaf.nl>
Message-Id: <199910141718.TAA01066(a)yedi.iaf.nl>
Subject: Re: vtserver
In-Reply-To: <19991014163422.C41213(a)henry.cs.adfa.edu.au> from Warren Toomey at "Oct 14, 1999 4:34:43 pm"
To: wkt(a)cs.adfa.edu.au (Warren Toomey)
Date: Thu, 14 Oct 1999 19:18:02 +0200 (CEST)
Cc: kbd(a)ndx.net, pups(a)minnie.cs.adfa.edu.au
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-pgp-info: PGP public key at 'finger wilko(a)freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
As Warren Toomey wrote ...
> On Wed, Oct 06, 1999 at 11:19:54PM -0700, Kirk Davis wrote:
> > Warren,
> > I've been checking out your vtserver program. It's a great idea
> > and it's been fun to play with. I'm bringing up a /34 and have been
> > collecting parts for it for a few months. I've got it set up with
> > a few RL02's on it. Few questions for you:
> >
> > Do you know of anyone that has used it on a /34? I've punched in the
> > bootstrap and ran it. It loads the boot file from my Linux system.
> > It appears to call it but it halts somewhere in the 70000-70040 region.
> > Nothing comes up on the console. Looks like the memory is over written
> > with the same values over and over again in this area. Any thoughts?
> >
> > I'm working on getting a source license from SCO. I'd love to hack on
> > this with you if you are interested in any help.
>
> Sorry for the delay Kirk. It could be that the V7 bootstrap expects
> split I/D, or a different I/O mapping then what's provided on the /34.
>
> I'll punt this to the PUPS mailing list. I have a suspicion that
> you won't be able to install V7, but you should be able to install V6
> or 2.9BSD instead.
I once had Ultrix-11 3.1 running on a dual RK05 11/34. What I'd call a
very minimal system ;-) But it ran
--
| / o / / _ Arnhem, The Netherlands - Powered by FreeBSD -
|/|/ / / /( (_) Bulte WWW : http://www.tcja.nlhttp://www.freebsd.org
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id EAA03106
for pups-liszt; Fri, 15 Oct 1999 04:38:33 +1000 (EST)
>From "Steven M. Schultz" <sms(a)moe.2bsd.com> Fri Oct 15 04:36:52 1999
Received: from moe.2bsd.com (0(a)MOE.2BSD.COM [206.139.202.200])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id EAA03102
for <pups(a)minnie.cs.adfa.edu.au>; Fri, 15 Oct 1999 04:38:25 +1000 (EST)
Received: (from sms@localhost)
by moe.2bsd.com (8.9.0/8.9.0) id LAA21478;
Thu, 14 Oct 1999 11:36:52 -0700 (PDT)
Date: Thu, 14 Oct 1999 11:36:52 -0700 (PDT)
From: "Steven M. Schultz" <sms(a)moe.2bsd.com>
Message-Id: <199910141836.LAA21478(a)moe.2bsd.com>
To: wilko(a)yedi.iaf.nl, wkt(a)cs.adfa.edu.au
Subject: Re: vtserver
Cc: kbd(a)ndx.net, pups(a)minnie.cs.adfa.edu.au
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Hi -
> From: Wilko Bulte <wilko(a)yedi.iaf.nl>
I will be doing some more research on this when I get home from
work tonight.
> I once had Ultrix-11 3.1 running on a dual RK05 11/34. What I'd call a
> very minimal system ;-) But it ran
That is because DEC put the extra effort into supporting non-split I/D
machines. The "stock" V7 really wanted a 11/70. In fact there was a
chapter in the back of one of the manuals/books detailing what it took
to get V7 running on an 11/40 (it was a non-trivial project).
Several things conspire against V7 and later on 11/34 (or 35, 40, 60,
etc). The two most notable ones are the limited address space,
everything (drivers, data structures, general kernel code) must fit
in 56kb instead of 120kb - (8kb reserved for the I/O page) and lack
of instruction restart on MMU faults.
I'll take a look at the V7 layout later but my memory is that it
wanted an 11/70.
Steven Schultz
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id GAA03622
for pups-liszt; Fri, 15 Oct 1999 06:04:30 +1000 (EST)
Anybody here interested in helping?
Greg
----- Forwarded message from Christoph Kaeder <hh-city(a)lehmanns.de> -----
> Delivered-To: freebsd-questions(a)freebsd.org
> Date: Thu, 30 Sep 1999 23:53:14 +0200
> Organization: Lehmanns Fachbuchhandlung
> X-Mailer: Mozilla 4.03 [de] (Win95; I)
> To: freebsd-questions(a)FreeBSD.ORG
> X-Loop: FreeBSD.ORG
> Precedence: bulk
>
> Hello.
>
> Lehmanns bookshop in Germany will print a
> Unix-Freeware-Calender in
> postersize and give it away for FREE (300.000 copies /
> 4-colour!).
>
> The calendar will include over 100 remarkable days from the
> History of Unix, Linux, Freeware and Open Source.
>
>
> Would you like to add some remarkable days from the
> FreeBSD-History?
> Release days or ...
>
>
> - calendar-home : http://www.lob.de/cal0
> - first look (JPEG): http://www.lob.de/cal1
> - a detail: http://www.lob.de/cal2
> - form to add your remarkable days: http://www.lob.de/cal3
>
> And if you agree we would like to add the FreeBSD Daemon on
> this calender beside the Tux, TeX-Lion, Perl Camel ...
>
> Do you agree to this and can you send us a Tif or JPEG?
> We need it with 300 dpi, 4-colour, about 1 inch high
>
> Thanks.
> Christoph Kaeder
> --
>
> * - * - * - * - * - * - * - * - * - * - * - * - * - * - * -
> * -- *
> Lehmanns Fachbuchhandlung fuer Informatik, Medizin und
> Psychologie
> Hermannstrasse 17 / 20095 Hamburg / GERMANY /
> hh-city(a)lehmanns.de
> Telefon 040 - 336384 / Fax 040-338955 / International:
> 0049-40-...
> http://www.lob.de / Mo - Fr von 10 bis 20 und Sa von 10 bis
> 16 Uhr
> * - * - * - * - * - * - * - * - * - * - * - * - * - * - * -
> * -- *
>
>
> To Unsubscribe: send mail to majordomo(a)FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
----- End forwarded message -----
--
See complete headers for address, home page and phone numbers
finger grog(a)lemis.com for PGP public key
In article by Lord Isildur:
> hello,
>
> alas, i do not have an account on the PUPS Archive machine! could i have one?
> i remember vaguely something about requiring pgp-signed stuff, and i dont
> use pgp, and so dont have a public (or any other) key.
> isildur
Here's the policy for the machine holding the PUPS Archive:
+ People with UNIX source licenses can get at least
guest FTP access to the archive, with S/Key as the
authentication mechanism.
+ People with UNIX source licenses, and who either
help to maintain the archive, or who have volunteered
to distribute the archive, can get ssh access to the
machine.
+ No telnet access, no e-mail. The box runs with `reserved
tolerance' from the real system administrators :-)
If you fall into either category, and can prove you have a UNIX source
license, then I can either PGP e-mail you, or fax you, the access
details.
Apologies for the cross-post to the 3 old UNIX-related mailing lists!
Cheers,
Warren
In article by johna(a)babel.apana.org.au:
> Hi Warren,
> I have a set (11 I think) of manuals for the Unisys 5000 / 7000 series
> which I'd be happy to give away. Not sure if they are of historical
> interest (too recent, perhaps) or if it was a landmark computer ...
>
> Anyway, I'd be happy to donate them to the Unix archive if you're
> interested. I'm in Sydney, North Ryde, and would be happy to pass them
> on next time we're in earshot of each other
Actually, your email made me think: if I collect _erverything_ offered to
me, then I _will_ run out of room soon.
So, how about the idea of a register? You tell me what you have & your
contact details. I put up a web page with the stuff, your name, and
your contact details if you are happy.
Then, if people want access to them, they can contact you. Or, if you'd
rather not have your contact details on the web, they can contact me.
And if you feel like getting rid of them, you can email me and I'll see
if anybody wants them.
Let me know what you think. P.S I'm cc'ing this to the PUPS mail list
for similar comments.
Cheers,
Warren
Hi -
> From: Dave Horsfall <dave(a)fgh.geac.com.au>
> Do you recall the PC-board hack on the sep-ID machines that changed
No, I do not recall seeing a PCB hack (hacking on an 11/70 was
frowned upon ;))
> the MFPI instruction to do something that was expressly prohibited?
But I do know what that 'something' was. In "user" or "supervisor"
mode MPFI functioned as "MFPD" - a user program could not read its own
I(nstruction) space. Only for "kernel" mode did MFPI access the
I space.
> Something about allowing a user program to access something else, for
> some obscure hack or other...
It was aimed at providing "execute only" code - a program could "run"
but not "read" its code space.
This caused problems though if trap handlers (floating point exception
handling comes to mind) needed to retrieve the faulted instruction
for inspection/analysis. Thus in 2BSD there is a system call that
programs can issue to request the KERNEL to do the 'mfpi' for them
and return the value.
Steven Schultz
sms(a)moe.2bsd.com
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id TAA10091
for pups-liszt; Thu, 9 Sep 1999 19:48:18 +1000 (EST)
>From Johnny Billquist <bqt(a)Update.UU.SE> Thu Sep 9 19:58:19 1999
Received: from Zeke.Update.UU.SE (IDENT:2026@Zeke.Update.UU.SE [130.238.11.14])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id TAA10087
for <pups(a)minnie.cs.adfa.edu.au>; Thu, 9 Sep 1999 19:48:09 +1000 (EST)
Received: from localhost (bqt@localhost)
by Zeke.Update.UU.SE (8.8.8/8.8.8) with SMTP id LAA22975;
Thu, 9 Sep 1999 11:58:20 +0200
Date: Thu, 9 Sep 1999 11:58:19 +0200 (MET DST)
From: Johnny Billquist <bqt(a)Update.UU.SE>
To: Warren Toomey <wkt(a)cs.adfa.edu.au>
cc: Unix Heritage Society <pups(a)minnie.cs.adfa.edu.au>
Subject: Re: Diff between 11/20 and 11/45?
In-Reply-To: <199909062356.JAA12397(a)henry.cs.adfa.edu.au>
Message-ID: <Pine.VUL.3.93.990909115534.22939A-100000(a)Zeke.Update.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
On Tue, 7 Sep 1999, Warren Toomey wrote:
> These executables were written for a PDP-11/20. Are there any significant
> USER-MODE differences between the 11/20 and later PDP-11 models? I'm
> thinking missing instructions, different addressing mode behaviour etc.
As far as I can remember, there aren't any huge differences. However, some
stuff behave differently in the 11/20. On the other hand, some stuff
behave differently in just about every implementation...
Condition flags on some instructions specifically. And the 11/20 might
have had some limitations on using the PC which differed as well.
I have a processor handbook for the "modern" -11s, which has a chart with
all differences between different models. I started writing it down, to
place in the PDP-11 FAQ, but haven't come that far yet...
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
Are, I was afraid of that. The KE11-A wasn't a real CPU option, but
was a peripheral that sat on the Unibus
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id KAA03506
for pups-liszt; Wed, 8 Sep 1999 10:58:18 +1000 (EST)
>From Tim Shoppa <SHOPPA(a)trailing-edge.com> Wed Sep 8 11:12:00 1999
Received: from timaxp.trailing-edge.com (timaxp.trailing-edge.com [63.73.218.130])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with SMTP id KAA03501
for <PUPS(a)MINNIE.CS.ADFA.edu.AU>; Wed, 8 Sep 1999 10:58:10 +1000 (EST)
Received: by timaxp.trailing-edge.com for PUPS(a)MINNIE.CS.ADFA.edu.AU;
Tue, 7 Sep 1999 21:12:00 -0400
Date: Tue, 7 Sep 1999 21:12:00 -0400
From: Tim Shoppa <SHOPPA(a)trailing-edge.com>
To: PUPS(a)minnie.cs.adfa.edu.au
Message-Id: <990907211200.2020016c(a)trailing-edge.com>
Subject: Re: Diff between 11/20 and 11/45?
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
>These executables were written for a PDP-11/20. Are there any significant
>USER-MODE differences between the 11/20 and later PDP-11 models? I'm
>thinking missing instructions, different addressing mode behaviour etc.
Well, first of all, there is no "User mode" on the 11/20 unless you have
a KT11 installed. Everything is kernel mode with no KT11. Maybe the
executables are trying to go out and directly bang on the console CSR's,
the switch register, or the interrupt vectors themselves?
11/20's also frequently had the EAE (Extended Arithmetic Element)
installed, to make up for the fact that there was no multiply, divide,
or multiple shift instructions in the native instruction set (and
wouldn't be until the EIS came along.) The EAE was a peripheral
living in I/O space (773000-777316); you wrote the operands to the EAE
locations and read the results later. You can put a EAE in a machine
with EIS, but generally you only did this if you had some binaries without
sources using the EAE (I know of several sites running 11/24's and 11/44's
with EAE's today)
There are many other differences, especially dealing with "funny" address
modes. Generally, folks like me who have to code so that something works
across all the -11's know better than to do these things, but back when
there was *only* the 11/20 some folks didn't know any better and used
them anyway.
First, we have instructions that use the same register as source
and destination, with an auto-increment one or the other:
1. OPR R,(R)+ on an 11/20 increments R before it's used as a source
operand. On an 11/45 the initial contents of R are used.
2. Same thing for OPR R,-(R).
3. JMP (R)+ or JSR reg,(R)+ increments R before putting it in the PC
on the 11/20; on the 11/45 R isn't incremented until after the old
value is put in the PC.
4. On an 11/20, JMP %R traps to 4; on an 11/45, JMP %R traps to 10
5. On an 11/20, SWAB does not change the V flag; on every other machine,
SWAB clears V. (In the 11/20 processor handbook, it *says* that SWAB
clears the V flag, but that's not the way the machine actually worked!)
6. On an 11/20, R0-R7 can be used by the program at addresses 177700-
177717; on any other machine, they can't be used that way and will
result in a non-existent memory (NXM) trap. This can be used for some
neat tricks where you run code out of the registers (which of course
is quite non-portable!)
There's lots more differences, having to do with T bits and interrupt
handling, but I don't know if you're getting that far... and these
aren't things that you have to worry about in user mode, anyway.
--
Tim Shoppa Email: shoppa(a)trailing-edge.com
Trailing Edge Technology WWW: http://www.trailing-edge.com/
7328 Bradley Blvd Voice: 301-767-5917
Bethesda, MD, USA 20817 Fax: 301-767-5927
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id LAA03564
for pups-liszt; Wed, 8 Sep 1999 11:03:51 +1000 (EST)
>From Dave Horsfall <dave(a)fgh.geac.com.au> Wed Sep 8 11:15:48 1999
Received: from caveman.geac.com.au (caveman.geac.com.au [203.30.73.2])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with SMTP id LAA03558
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 11:03:40 +1000 (EST)
Received: (qmail 4832 invoked from network); 8 Sep 1999 11:21:32 +1000
Received: from trowel.geac.com.au (203.1.26.189)
by caveman.geac.com.au with SMTP; 8 Sep 1999 11:21:32 +1000
Received: (qmail 27748 invoked from network); 8 Sep 1999 11:29:48 +1000
Received: from fgh.geac.com.au (202.6.67.163)
by trowel.geac.com.au with SMTP; 8 Sep 1999 11:29:49 +1000
Received: from localhost (dave@localhost)
by fgh.geac.com.au?r with ESMTP id LAA21756
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 11:15:48 +1000
X-Envelope-From: dave(a)horsfall.org
X-Envelope-To: <pups(a)minnie.cs.adfa.edu.au>
X-Authentication-Warning: fgh.geac.com.au: dave owned process doing -bs
Date: Wed, 8 Sep 1999 11:15:48 +1000 (EST)
From: Dave Horsfall <dave(a)fgh.geac.com.au>
X-Sender: dave@fgh
To: PDP Unix Preservation Society <pups(a)minnie.cs.adfa.edu.au>
Subject: Re: Diff between 11/20 and 11/45?
In-Reply-To: <199909070604.XAA04723(a)mpl.ucsd.edu>
Message-ID: <Pine.GSO.4.10.9909081103330.19899-100000@fgh>
X-No-Archive: Yes
X-Witty-Saying: "Tesseract - Enter at own risk"
X-Disclaimer: "Me, speak for us?"
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
On Mon, 6 Sep 1999, Carl Lowenstein wrote:
> The first genuine user-mode difference that I remember coming across was
> an incompatibility in the result of
>
> MOV SP, -(SP)
Anything involving the same register as src and dst in this way was,
err, different...
And I have an annotation that the JSR does not behave as documented.
Unlike page 91, the sequence is not (tmp) <- (dst) / v(SP) <- reg /
reg <- PC / PC <- (tmp). The first ISP code is not present i.e. the
SP is decremented first, not saved, and the last is PC <- (dst).
> It isn't really clear to me why one would want to use this particular
> instruction, however it turned out to hang both BASIC and FOCAL at the
> time. A zero-length patch wasn't too hard to figure out.
Some sort of frame pointer linking, on an architecture that didn't
have separate frame pointers (like the Vax)?
--
Dave Horsfall VK2KFU dave(a)geac.com.au Ph: +61 2 9978-7493 Fx: +61 2 9978-7422
Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, Australia
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id LAA03594
for pups-liszt; Wed, 8 Sep 1999 11:05:14 +1000 (EST)
>From Tim Shoppa <SHOPPA(a)trailing-edge.com> Wed Sep 8 10:48:50 1999
Received: from timaxp.trailing-edge.com (timaxp.trailing-edge.com [63.73.218.130])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with SMTP id LAA03588
for <PUPS(a)MINNIE.CS.ADFA.edu.AU>; Wed, 8 Sep 1999 11:05:07 +1000 (EST)
Received: by timaxp.trailing-edge.com for PUPS(a)MINNIE.CS.ADFA.edu.AU;
Tue, 7 Sep 1999 20:48:50 -0400
Date: Tue, 7 Sep 1999 20:48:50 -0400
From: Tim Shoppa <SHOPPA(a)trailing-edge.com>
To: PUPS(a)minnie.cs.adfa.edu.au
Message-Id: <990907204850.202001b4(a)trailing-edge.com>
Subject: Re: Diff between 11/20 and 11/45?
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
> MOV SP, -(SP)
>
>It isn't really clear to me why one would want to use this particular
>instruction
"MOV SP" is often-used shorthand for "MOV some-non-zero-value", since no
sane implementation would ever have a zero in the SP. So this would
put a non-zero value on top of the stack (perhaps as a flag, to be
cleared by CLR (SP) when ready) - at least on machines where this was legal!
On which machine does this fail, BTW? On a 11/15, 11/20, 11/23, 11/35
or 11/40 this ought to work, decrementing SP by two before putting it on
the stack, and on the 11/03, 11/04, 11/05, 11/10, 11/34, and 11/45
SP is decremented by two before being put on the stack, according to my
notes.
--
Tim Shoppa Email: shoppa(a)trailing-edge.com
Trailing Edge Technology WWW: http://www.trailing-edge.com/
7328 Bradley Blvd Voice: 301-767-5917
Bethesda, MD, USA 20817 Fax: 301-767-5927
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id LAA03973
for pups-liszt; Wed, 8 Sep 1999 11:47:41 +1000 (EST)
>From Dave Horsfall <dave(a)fgh.geac.com.au> Tue Sep 7 14:13:30 1999
Received: from caveman.geac.com.au (caveman.geac.com.au [203.30.73.2])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with SMTP id LAA03969
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 11:47:34 +1000 (EST)
Received: (qmail 24470 invoked from network); 7 Sep 1999 14:18:39 +1000
Received: from trowel.geac.com.au (203.1.26.189)
by caveman.geac.com.au with SMTP; 7 Sep 1999 14:18:39 +1000
Received: (qmail 12323 invoked from network); 7 Sep 1999 14:26:41 +1000
Received: from fgh.geac.com.au (202.6.67.163)
by trowel.geac.com.au with SMTP; 7 Sep 1999 14:26:41 +1000
Received: from localhost (dave@localhost)
by fgh.geac.com.au?r with ESMTP id OAA21437
for <pups(a)minnie.cs.adfa.edu.au>; Tue, 7 Sep 1999 14:13:31 +1000
X-Envelope-From: dave(a)horsfall.org
X-Envelope-To: <pups(a)minnie.cs.adfa.edu.au>
X-Authentication-Warning: fgh.geac.com.au: dave owned process doing -bs
Date: Tue, 7 Sep 1999 14:13:30 +1000 (EST)
From: Dave Horsfall <dave(a)fgh.geac.com.au>
X-Sender: dave@fgh
To: PDP Unix Preservation Society <pups(a)minnie.cs.adfa.edu.au>
Subject: Re: Diff between 11/20 and 11/45?
In-Reply-To: <199909062356.JAA12397(a)henry.cs.adfa.edu.au>
Message-ID: <Pine.GSO.4.10.9909071404290.19123-100000@fgh>
X-No-Archive: Yes
X-Witty-Saying: "Tesseract - Enter at own risk"
X-Disclaimer: "Me, speak for us?"
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
On Tue, 7 Sep 1999, Warren Toomey wrote:
> I've got a few working. cat works. ls and date run, but sort of give
> strange outputs.
What sort of strange output? My guess is that kernel-wise, date-handling
would have changed.
> These executables were written for a PDP-11/20. Are there any significant
> USER-MODE differences between the 11/20 and later PDP-11 models? I'm
> thinking missing instructions, different addressing mode behaviour etc.
Ummm... No floating point (all emulated), and I seem to recall that
it didn't even have multiply/divide; could this be the problem? The
/20 was certainly a subset of the "classic" 11. No memory management,
but users won't see that. Also had some quirks, long-forgotten.
My experience is based on the GT-40, which was basically a /20 with a
graphics processor attached to it (which had a mean Lunar Lander game!).
--
Dave Horsfall VK2KFU dave(a)geac.com.au Ph: +61 2 9978-7493 Fx: +61 2 9978-7422
Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, Australia
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id OAA04594
for pups-liszt; Wed, 8 Sep 1999 14:30:23 +1000 (EST)
>From Carl Lowenstein <cdl(a)mpl.ucsd.edu> Wed Sep 8 14:43:16 1999
Received: from mpl.ucsd.edu (chiton.ucsd.edu [192.135.238.128])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id OAA04581
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 14:29:58 +1000 (EST)
Received: (from cdl@localhost)
by mpl.ucsd.edu (8.8.8+Sun/8.8.8) id VAA07676
for pups(a)minnie.cs.adfa.edu.au; Tue, 7 Sep 1999 21:43:16 -0700 (PDT)
Date: Tue, 7 Sep 1999 21:43:16 -0700 (PDT)
From: Carl Lowenstein <cdl(a)mpl.ucsd.edu>
Message-Id: <199909080443.VAA07676(a)mpl.ucsd.edu>
To: pups(a)minnie.cs.adfa.edu.au
Subject: Re: Diff between 11/20 and 11/45?
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
> From owner-pups(a)minnie.cs.adfa.edu.au Tue Sep 7 18:24 PDT 1999
> Date: Tue, 7 Sep 1999 17:49:36 -0700 (PDT)
> From: "Steven M. Schultz" <sms(a)moe.2bsd.com>
> To: pups(a)minnie.cs.adfa.edu.au
> Subject: Re: Diff between 11/20 and 11/45?
>
> > From: Carl Lowenstein <cdl(a)mpl.ucsd.edu>
> >
> > MOV SP, -(SP)
>
> Similarily
>
> MOV R0,(R0)+
>
> won't work as expected on some 11s. I suspect that the even less
> likely case of "mov pc,-(pc)" won't work either :-)
>
> > It isn't really clear to me why one would want to use this particular
> > instruction, however it turned out to hang both BASIC and FOCAL at the
>
> Fairly common when setting up call frames, etc. You want the
> address of where the arguments start and since they're pushed on the
> stack 'sp' is the value you want.
>
> There's a comment in 2BSD (I think it came from V7) where mention is
> made that "we can't do sp,-(sp) because it won't work on the 11/40".
>
> > time. A zero-length patch wasn't too hard to figure out.
>
> Hmmm, interesting. The workaround I saw took an extra instruction.
Abbreviated due to fading memory over the years, but refreshed by some
of the current discussion. The patch was zero-length but involved more
than the one instruction. Something similar to:
MOV SP, -(SP) MOV SP, R0
MOV (sP), R0 MOV R0, -(SP)
The net result being that the initial value of SP is now both in R0 and
on the stack. Without doing both a SRC and DST operation on SP in the
same instruction, which is the thing that is incompatible across different
processor hardware.
carl
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id OAA04681
for pups-liszt; Wed, 8 Sep 1999 14:51:11 +1000 (EST)
>From Carl Lowenstein <cdl(a)mpl.ucsd.edu> Wed Sep 8 15:03:09 1999
Received: from mpl.ucsd.edu (chiton.ucsd.edu [192.135.238.128])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id OAA04676
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 14:50:06 +1000 (EST)
Received: (from cdl@localhost)
by mpl.ucsd.edu (8.8.8+Sun/8.8.8) id WAA08055
for pups(a)minnie.cs.adfa.edu.au; Tue, 7 Sep 1999 22:03:09 -0700 (PDT)
Date: Tue, 7 Sep 1999 22:03:09 -0700 (PDT)
From: Carl Lowenstein <cdl(a)mpl.ucsd.edu>
Message-Id: <199909080503.WAA08055(a)mpl.ucsd.edu>
To: pups(a)minnie.cs.adfa.edu.au
Subject: Re: Diff between 11/20 and 11/45?
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
> Date: Tue, 7 Sep 1999 14:13:30 +1000 (EST)
> From: Dave Horsfall <dave(a)fgh.geac.com.au>
> To: PDP Unix Preservation Society <pups(a)minnie.cs.adfa.edu.au>
> Subject: Re: Diff between 11/20 and 11/45?
> X-No-Archive: Yes
>
> On Tue, 7 Sep 1999, Warren Toomey wrote:
>
> > I've got a few working. cat works. ls and date run, but sort of give
> > strange outputs.
>
> What sort of strange output? My guess is that kernel-wise, date-handling
> would have changed.
It occurs to me that really early Unix used a time word in PDP-11 ticks,
not seconds. So it ran out of time a lot sooner than 2038, like maybe
only a year after it started, at 60 ticks per second, 31.5 Megaseconds per
year. This information was gleaned from a Mt.Xinu calendar from a few
years ago.
carl
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id PAA04812
for pups-liszt; Wed, 8 Sep 1999 15:28:58 +1000 (EST)
>From "Steven M. Schultz" <sms(a)moe.2bsd.com> Wed Sep 8 15:40:58 1999
Received: from moe.2bsd.com (0(a)MOE.2BSD.COM [206.139.202.200])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id PAA04808
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 15:28:46 +1000 (EST)
Received: (from sms@localhost)
by moe.2bsd.com (8.9.0/8.9.0) id WAA17669
for pups(a)minnie.cs.adfa.edu.au; Tue, 7 Sep 1999 22:40:58 -0700 (PDT)
Date: Tue, 7 Sep 1999 22:40:58 -0700 (PDT)
From: "Steven M. Schultz" <sms(a)moe.2bsd.com>
Message-Id: <199909080540.WAA17669(a)moe.2bsd.com>
To: pups(a)minnie.cs.adfa.edu.au
Subject: Re: Diff between 11/20 and 11/45?
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Howdy -
> From: Carl Lowenstein <cdl(a)mpl.ucsd.edu>
> Abbreviated due to fading memory over the years, but refreshed by some
> of the current discussion. The patch was zero-length but involved more
It has been a long long ('quad'? ;)) time since I first encountered
the problem.
> than the one instruction. Something similar to:
>
> MOV SP, -(SP) MOV SP, R0
> MOV (SP), R0 MOV R0, -(SP)
Ah, thank you for bringing that memory back to the front of the brain!
If R0 is available for that then yes indeed that'll do the trick very
nicely.
> on the stack. Without doing both a SRC and DST operation on SP in the
> same instruction, which is the thing that is incompatible across different
> processor hardware.
The 11/45 (and 70) behave as "expected" as do the KDJ-11 systems
(11/73, etc) so unless a person had an 11/40 (or a /20) around it
would be fairly easy to get bit by the "feature".
When it comes time for MMU "features" I know of one difference between
the KDJ-11 and the other members that had an MMU (11/44, /70, etc). Was
fun tracking it down but not something I'd want to do again ;)
Steven
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id QAA04962
for pups-liszt; Wed, 8 Sep 1999 16:17:43 +1000 (EST)
>From Dave Horsfall <dave(a)fgh.geac.com.au> Wed Sep 8 16:29:16 1999
Received: from caveman.geac.com.au (caveman.geac.com.au [203.30.73.2])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with SMTP id QAA04957
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 16:17:35 +1000 (EST)
Received: (qmail 10263 invoked from network); 8 Sep 1999 16:34:56 +1000
Received: from trowel.geac.com.au (203.1.26.189)
by caveman.geac.com.au with SMTP; 8 Sep 1999 16:34:56 +1000
Received: (qmail 1789 invoked from network); 8 Sep 1999 16:43:20 +1000
Received: from fgh.geac.com.au (202.6.67.163)
by trowel.geac.com.au with SMTP; 8 Sep 1999 16:43:20 +1000
Received: from localhost (dave@localhost)
by fgh.geac.com.au?r with ESMTP id QAA24887
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 16:29:17 +1000
X-Envelope-From: dave(a)horsfall.org
X-Envelope-To: <pups(a)minnie.cs.adfa.edu.au>
X-Authentication-Warning: fgh.geac.com.au: dave owned process doing -bs
Date: Wed, 8 Sep 1999 16:29:16 +1000 (EST)
From: Dave Horsfall <dave(a)fgh.geac.com.au>
X-Sender: dave@fgh
To: PDP Unix Preservation Society <pups(a)minnie.cs.adfa.edu.au>
Subject: Re: Diff between 11/20 and 11/45?
In-Reply-To: <199909080540.WAA17669(a)moe.2bsd.com>
Message-ID: <Pine.GSO.4.10.9909081618240.19899-100000@fgh>
X-No-Archive: Yes
X-Witty-Saying: "Tesseract - Enter at own risk"
X-Disclaimer: "Me, speak for us?"
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
On Tue, 7 Sep 1999, Steven M. Schultz wrote:
> > MOV SP, -(SP) MOV SP, R0
> > MOV (SP), R0 MOV R0, -(SP)
>
> Ah, thank you for bringing that memory back to the front of the brain!
> If R0 is available for that then yes indeed that'll do the trick very
> nicely.
Yep, I remember that now! Often thought it was odd, but it worked
on all platforms.
The convention was that R0/1 were scratch (used to return results)
and R2/3/4 had to be saved (they were the caller's first three register
variables). R5 was used as a frame pointer (?) and R6/7 you know
better as SP/PC.
> The 11/45 (and 70) behave as "expected" as do the KDJ-11 systems
> (11/73, etc) so unless a person had an 11/40 (or a /20) around it
> would be fairly easy to get bit by the "feature".
We had 40s, and used to dream of owning a 70... I learned a lot about
porting Edition 6 to the /23, /60, etc.
> When it comes time for MMU "features" I know of one difference between
> the KDJ-11 and the other members that had an MMU (11/44, /70, etc). Was
> fun tracking it down but not something I'd want to do again ;)
Do you recall the PC-board hack on the sep-ID machines that changed
the MFPI instruction to do something that was expressly prohibited?
Something about allowing a user program to access something else, for
some obscure hack or other...
--
Dave Horsfall VK2KFU dave(a)geac.com.au Ph: +61 2 9978-7493 Fx: +61 2 9978-7422
Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, Australia
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id UAA05921
for pups-liszt; Wed, 8 Sep 1999 20:30:43 +1000 (EST)
>From Wim Fournier <hsmade(a)dds.nl> Wed Sep 8 20:41:32 1999
Received: from amber.dds.nl (amber.dds.nl [194.109.21.10])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id UAA05917
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 20:30:34 +1000 (EST)
Received: from feline.dds.nl (feline.dds.nl [194.109.20.19])
by amber.dds.nl (8.9.3/8.9.1) with ESMTP id MAA25230
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 12:39:41 +0200 (MET DST)
Received: from fatima.dds.nl (hsmade(a)fatima.dds.nl [194.109.20.21])
by feline.dds.nl (8.9.3/8.9.1) with SMTP id MAA16806
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 12:41:33 +0200 (MET DST)
Date: Wed, 8 Sep 1999 12:41:32 +0200 (MET DST)
From: Wim Fournier <hsmade(a)dds.nl>
To: pups(a)minnie.cs.adfa.edu.au
Subject: Newbie question
Message-ID: <Pine.GSO.3.90.990908123352.21899B-100000(a)fatima.dds.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Hi,
I am the happy owner of a pdp-11/94. I've got it from our local telecom
provider (kpn). As I am not a specialist on these machines, I would like
to ask some questions:
- My pdp won't accept mains... when I supply power it doesn't do
anything.. I've heard it could be something with the power-supply not
being closed.. but I cannot find what it is.. it's fully closed.
- I've got sdi / tu80 and an other diskcontroller... What type of disks
can I use to boot from?? (disks = floppy / tape / harddrive)
- What about the 2 connectors at the back.. 1 has 3 pins and can be
connected to the mains regulator (or something (a box for switching the
mains)) an other one has got 2 pins and no info...
- Is there some info on hardware to connect at the diverse controllers
(modem / serial??)
GreetZz
Wim Fournier
hsmade(a)dds.nl
> From: Warren Toomey <wkt(a)cs.adfa.edu.au>
> Subject: Diff between 11/20 and 11/45?
> To: pups(a)minnie.cs.adfa.edu.au (Unix Heritage Society)
> Date: Tue, 7 Sep 1999 09:56:09 +1000 (EST)
>
> Dennis Ritchie has unearthed some really old Unix a.out
> executables from around 1st Edition - 2nd Edition period: see
> Distributions/research/1973_stuff in the PUPS Archive.
>
> These executables were written for a PDP-11/20. Are there any significant
> USER-MODE differences between the 11/20 and later PDP-11 models? I'm
> thinking missing instructions, different addressing mode behaviour etc.
There's a good table in the back of the more recent micro-11 manuals.
The first genuine user-mode difference that I remember coming across was
an incompatibility in the result of
MOV SP, -(SP)
It isn't really clear to me why one would want to use this particular
instruction, however it turned out to hang both BASIC and FOCAL at the
time. A zero-length patch wasn't too hard to figure out.
carl
carl lowenstein marine physical lab u.c. san diego
{decvax|ucbvax} !ucsd!mpl!cdl cdl(a)mpl.ucsd.edu
clowenstein(a)ucsd.edu
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id KAA03173
for pups-liszt; Wed, 8 Sep 1999 10:13:57 +1000 (EST)
There is huge difference between the machines, but not backwards!
The 11/20 doesn't have :-
EIS instructions like div, mul, ash etc
FPU instructions like fmul ...
MMU no memory management of any sort, 56Kb memory, 8Kb I/O page
and hence no user modes, 16 bit addressing
So a program written for a 11/20 should work untouched on an 11/45 except for
some very minor (and ugly) instruction sequences involving using the same
register for both source and destination eg mov r2,-(r2), or jmp (r2)+.
The behaviour of the trace trap and T bit is also different.
There is a list of differences some some of the PDP/11 handbooks (perhaps the
latter architecture book).
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id KAA03319
for pups-liszt; Wed, 8 Sep 1999 10:38:29 +1000 (EST)
>From Dave Horsfall <dave(a)fgh.geac.com.au> Wed Sep 8 10:50:39 1999
Received: from caveman.geac.com.au (caveman.geac.com.au [203.30.73.2])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with SMTP id KAA03314
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 10:38:20 +1000 (EST)
Received: (qmail 4222 invoked from network); 8 Sep 1999 10:56:15 +1000
Received: from trowel.geac.com.au (203.1.26.189)
by caveman.geac.com.au with SMTP; 8 Sep 1999 10:56:15 +1000
Received: (qmail 27184 invoked from network); 8 Sep 1999 11:04:35 +1000
Received: from fgh.geac.com.au (202.6.67.163)
by trowel.geac.com.au with SMTP; 8 Sep 1999 11:04:35 +1000
Received: from localhost (dave@localhost)
by fgh.geac.com.au?r with ESMTP id KAA21475
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 10:50:40 +1000
X-Envelope-From: dave(a)horsfall.org
X-Envelope-To: <pups(a)minnie.cs.adfa.edu.au>
X-Authentication-Warning: fgh.geac.com.au: dave owned process doing -bs
Date: Wed, 8 Sep 1999 10:50:39 +1000 (EST)
From: Dave Horsfall <dave(a)fgh.geac.com.au>
X-Sender: dave@fgh
To: PDP Unix Preservation Society <pups(a)minnie.cs.adfa.edu.au>
Subject: Re: KE11-A! (was Diff between 11/20 and 11/45?)
In-Reply-To: <199909070110.LAA12638(a)henry.cs.adfa.edu.au>
Message-ID: <Pine.GSO.4.10.9909081049430.19899-100000@fgh>
X-No-Archive: Yes
X-Witty-Saying: "Tesseract - Enter at own risk"
X-Disclaimer: "Me, speak for us?"
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
On Tue, 7 Sep 1999, Warren Toomey wrote:
> I also see that unit 1 lives at 777300 - 777316, and the date a.out
> executable does this:
Yep; I read through my own 11/20 handbook, and I remembered that
EAE weirdness.
--
Dave Horsfall VK2KFU dave(a)geac.com.au Ph: +61 2 9978-7493 Fx: +61 2 9978-7422
Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, Australia
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id KAA03361
for pups-liszt; Wed, 8 Sep 1999 10:43:07 +1000 (EST)
>From "Steven M. Schultz" <sms(a)moe.2bsd.com> Wed Sep 8 10:49:36 1999
Received: from moe.2bsd.com (0(a)MOE.2BSD.COM [206.139.202.200])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id KAA03354
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 8 Sep 1999 10:42:59 +1000 (EST)
Received: (from sms@localhost)
by moe.2bsd.com (8.9.0/8.9.0) id RAA15948
for pups(a)minnie.cs.adfa.edu.au; Tue, 7 Sep 1999 17:49:36 -0700 (PDT)
Date: Tue, 7 Sep 1999 17:49:36 -0700 (PDT)
From: "Steven M. Schultz" <sms(a)moe.2bsd.com>
Message-Id: <199909080049.RAA15948(a)moe.2bsd.com>
To: pups(a)minnie.cs.adfa.edu.au
Subject: Re: Diff between 11/20 and 11/45?
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
> From: Carl Lowenstein <cdl(a)mpl.ucsd.edu>
> The first genuine user-mode difference that I remember coming across was
> an incompatibility in the result of
>
> MOV SP, -(SP)
Similarily
MOV R0,(R0)+
won't work as expected on some 11s. I suspect that the even less
likely case of "mov pc,-(pc)" won't work either :-)
> It isn't really clear to me why one would want to use this particular
> instruction, however it turned out to hang both BASIC and FOCAL at the
Fairly common when setting up call frames, etc. You want the
address of where the arguments start and since they're pushed on the
stack 'sp' is the value you want.
There's a comment in 2BSD (I think it came from V7) where mention is
made that "we can't do sp,-(sp) because it won't work on the 11/40".
> time. A zero-length patch wasn't too hard to figure out.
Hmmm, interesting. The workaround I saw took an extra instruction.
Steven Schultz
sms(a)moe.2bsd.com
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id KAA03462
for pups-liszt; Wed, 8 Sep 1999 10:53:48 +1000 (EST)
Hi all,
Dennis Ritchie has unearthed some really old Unix a.out
executables from around 1st Edition - 2nd Edition period: see
Distributions/research/1973_stuff in the PUPS Archive.
[ Actually, I suspect his dates are a year off: they should be 1972 ]
I've printed off the 1st Ed manuals from Dennis' web page, and I'm
attempting to get my a.out emulator, Apout, to run these old binaries.
I've got a few working. cat works. ls and date run, but sort of give
strange outputs.
These executables were written for a PDP-11/20. Are there any significant
USER-MODE differences between the 11/20 and later PDP-11 models? I'm
thinking missing instructions, different addressing mode behaviour etc.
There is no source code with these binaries, so I can't use that to help
debug the emulator. I do have the following processor handbooks:
PDP-11 /20 /15 /R20 1972
PDP-11 /45 1973
PDP-11 /04 /34 /45 /55 /60 1978-79
I just thought I'd ask for pointers here before I hit them for details.
Cheers,
Warren
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id LAA27104
for pups-liszt; Tue, 7 Sep 1999 11:10:31 +1000 (EST)
>From Warren Toomey <wkt(a)cs.adfa.edu.au> Tue Sep 7 11:10:25 1999
Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id LAA27099
for <pups(a)minnie.cs.adfa.edu.au>; Tue, 7 Sep 1999 11:10:25 +1000 (EST)
Received: (from wkt@localhost)
by henry.cs.adfa.edu.au (8.9.2/8.9.3) id LAA12638
for pups(a)minnie.cs.adfa.edu.au; Tue, 7 Sep 1999 11:10:25 +1000 (EST)
From: Warren Toomey <wkt(a)cs.adfa.edu.au>
Message-Id: <199909070110.LAA12638(a)henry.cs.adfa.edu.au>
Subject: KE11-A! (was Diff between 11/20 and 11/45?)
To: pups(a)minnie.cs.adfa.edu.au (Unix Heritage Society)
Date: Tue, 7 Sep 1999 11:10:25 +1000 (EST)
Reply-To: wkt(a)cs.adfa.edu.au
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Hi all,
I've just answered my own question. Reading thru the 11/20
processor handbook, I see the section on the extended arithmetic element,
KE11-A, which is ``an option to perform multiplication, division,
multiple position shifts and normalization significantly faster than
software routines''.
I also see that unit 1 lives at 777300 - 777316, and the date a.out
executable does this:
230: TRAP 15 time syscall
232: MOV #177770,@#177314
240: MOV #47432,@#177300
246: ADD #5,@#177304
254: MOV #7,@#177300
262: MOV @#177302,@#177304
270: MOV #5,@#177306
276: ADD #40622,@#177304
304: MOV @#177304,320
. . .
So it looks like I need to add KE11-A support to my emulator :-)
Cheers,
Warren
The sub-disks that one divide real disks into on UNIX systems are usually
called `partitions' these days. But that's not what they were originally
called on UNIX:
- V7 hp(4) and rp(4) refer to `sections' and `pseudo-disks'. 32V hp(4)
refers to `portions' and `pseudo-disks.' Later Research UNIX manuals,
once Section 4 was being edited again, settled on `sections.'
- System V Release 5.0 (the most recent system for which I have the device
driver part of the manual) also refers just to `sections.' (So far as I
can remember, this convergence was a coincidence; I think I'm the one who
decided to use `sections' on the Research side, and I think I did so just
because it was the more graceful of the historic cases, though my memory
is not clear.)
- 3BSD and 4.0BSD follow 32V; in 4.1BSD, the term `partition' appears as well.
The System V preference for `section' lives on in the device naming scheme
on System-V-derived, but the documentation even on those systems just says
`partition' these days.
It looks to me like `partition' came in from the Berkeley world. Does anyone
on the list remember where it came from? Was the new term introduced on
purpose, or did it just creep in in the way language usually changes?
Norman Wilson
Occasional pursuer of arcana
For any MSCP disk, the proper way to find out how many sectors there are
is to ask the disk. The `unit online' command (which has to be used anyway,
to tell the controller to connect to the disk) reports the unit size in
sectors; the `get unit status' command reports the number of sectors per
track, tracks per group, and groups per cylinder. (The term `group' here
is MSCP-speak which I've never really understood; the idea seems to be that
groups are collections of cylinders that can be switched between with relatively
little time penalty, whereas switching between even adjacent cylinders is more
expensive.)
Beware, however, that modern disks usually don't have a fixed number of
sectors per track; the tracks furthest from the spindle have more sectors,
so that more of the disk surface can be used without too much density
variation. Such `zoned' disks weren't common (maybe they didn't even exist)
when the MSCP spec was first written; maybe the RA92 is new enough that it
has zones.
I've never been convinced that worrying in great detail about track and
cylinder sizes gains much performance anyway, but that's another story.
Hi,
I wonder, does anyone know for sure what is the user capacity of an RA92 in
blocks? I'm now updating disktab(5) and the driver tables in 4.3BSD-Quasijarus
to cover new RA disks, and I can't figure out the user capacity of RA92 in
blocks. For all other RA disks with no exceptions (all RA8x, all RA7x, and
RA90) the user capacity in blocks is exactly equal to the number of cylinders
multiplied by the number of heads multiplied by the number of sectors, i.e., no
funny reserved sectors or tracks or anything like that. Looking in the
disktab(5) from Ultrix V4.2 I see a perfect match between the geometry and the
partition sizes for all disks except RA92. The RA92 entry indicates 3279
cylinders, 13 heads, and 69 sectors per track, but partition c is listed as
2940951 blocks instead of 3279*13*69=2941263 blocks. Does anyone know for sure
whether the user capacity of an RA92 is 2940951 blocks, 2941263 blocks, or
something else altogether?
--
Michael Sokolov
Special Agent
International Free Computing Task Force
ARPA Internet SMTP mail: msokolov(a)meson.jpsystems.com
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id KAA17754
for pups-liszt; Sun, 5 Sep 1999 10:41:13 +1000 (EST)
Hi,
Having solved the RA72 problem and the KDA50 problem, I'm ready to attack the
next problem. :-( This time the TK50. I have a very odd problem with it. When I
first power up the VAX, everything works fine. I can read tapes, restore dumps,
etc. Then after some uptime (apparently something heat-related) it starts
behaving very oddly. Tapes with 512-byte records still read just fine, but
trying to read a tape with 10240-byte records (such as a UNIX filesystem dump
tape) results in the controller returning a hard error indication of "record
data truncated". This is so odd that I first thought it was a software problem,
but it isn't, because this happens identically under 4.3BSD-Quasijarus0 and
Ultrix V4.0, whose TMSCP drivers are completely different. The fact that the
problem occurs only after some uptime suggests some kind of overheat, which
would normally be a very low-level physical problem, but the record size
dependence suggests something high-level, more likely the controller than the
drive. This MicroVAX is still under the dealer's warranty (I just bought it on
Monday), so if this is a bad drive or controller, I can replace it, which which
of the two is it? Has anyone ever seen this problem before? Does anyone know
whether it is the drive or the controller that's bad? TIA.
--
Michael Sokolov
Special Agent
International Free Computing Task Force
ARPA Internet SMTP mail: msokolov(a)meson.jpsystems.com
P.S. The temperature in the machine room is 70F. Not the best for a machine
room, but the best you'd ever expect for an office, and I think the VAX has no
right to go on strike at 70F.
V7M was the DEC distribution of V7 (pre Ultrix days). Fred Canter did
most of the work, along with Jerry Brenner and Armando Stettner. It
supported non ID space machines, and some of the newer DEC hardware.
My manual lists it as working with :-
CPUS:- 11/23, 34, 44, 45/50/55, 60 and 70
Disks:- RL02, RK06, RK07, RM02/3, RP04/5
Tapes:- TU10, TE10, TU16, TE16, TS11
There was a strip down of V6 called Miniunix that would run on machines
without memory management, such at the 11/20, 05, 10 and 35/40 (without MMU
option). It required a full 56Kb machine, used the first 28Kb for the kernel
and swapped the last 28Kb for each process. Pipes worked by using a temporary
inode to store the data and swapping the processes. It was realllllllll slow.
The was also a similar version for 11/03's. I remember that there was an early
bug in that updates would always rewrite open inodes (last access time had
changed). You could physically wear out a floppy disk, since it was forever
rewriting the sector with the inode for the console terminal.
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id QAA00853
for pups-liszt; Thu, 2 Sep 1999 16:07:04 +1000 (EST)
>From Carl Lowenstein <cdl(a)mpl.ucsd.edu> Thu Sep 2 16:06:50 1999
Received: from mpl.ucsd.edu (chiton.ucsd.edu [192.135.238.128])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id QAA00845
for <pups(a)minnie.cs.adfa.edu.au>; Thu, 2 Sep 1999 16:06:56 +1000 (EST)
Received: (from cdl@localhost)
by mpl.ucsd.edu (8.8.8+Sun/8.8.8) id XAA06196
for pups(a)minnie.cs.adfa.edu.au; Wed, 1 Sep 1999 23:06:50 -0700 (PDT)
Date: Wed, 1 Sep 1999 23:06:50 -0700 (PDT)
From: Carl Lowenstein <cdl(a)mpl.ucsd.edu>
Message-Id: <199909020606.XAA06196(a)mpl.ucsd.edu>
To: pups(a)minnie.cs.adfa.edu.au
Subject: Re: V7M
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
> Subject: Re: V7M
> cc: pups(a)minnie.cs.adfa.edu.au
> Date: Wed, 01 Sep 1999 16:44:29 -0700
> From: Kirk McKusick <mckusick(a)flamingo.mckusick.com>
>
> My recollection is that V7M stood for V7-mini. It was a
> striped down version of V7 that was designed to run on
> the very low-end PDP-11's (like the 11/20).
Well, actually the M was for Modified. Particularly modified to work
with some more DEC peripherals.
What ran on 11/20's was Mini-Unix, which was a stripped-down 6th
Edition. By the way I'm not sure that the PUPS archive has a Mini-Unix
tape. I have one, although it has not been read since the days when I
had an 11/20.
carl
carl lowenstein marine physical lab u.c. san diego
{decvax|ucbvax} !ucsd!mpl!cdl cdl(a)mpl.ucsd.edu
clowenstein(a)ucsd.edu
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id QAA00913
for pups-liszt; Thu, 2 Sep 1999 16:11:58 +1000 (EST)
>From Warren Toomey <wkt(a)cs.adfa.edu.au> Thu Sep 2 16:09:16 1999
Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id QAA00907
for <pups(a)minnie.cs.adfa.edu.au>; Thu, 2 Sep 1999 16:11:51 +1000 (EST)
Received: (from wkt@localhost)
by henry.cs.adfa.edu.au (8.9.2/8.9.3) id QAA00770;
Thu, 2 Sep 1999 16:09:16 +1000 (EST)
From: Warren Toomey <wkt(a)cs.adfa.edu.au>
Message-Id: <199909020609.QAA00770(a)henry.cs.adfa.edu.au>
Subject: Re: V7M
In-Reply-To: <199909020606.XAA06196(a)mpl.ucsd.edu> from Carl Lowenstein at "Sep 1, 1999 11: 6:50 pm"
To: cdl(a)mpl.ucsd.edu (Carl Lowenstein)
Date: Thu, 2 Sep 1999 16:09:16 +1000 (EST)
Cc: pups(a)minnie.cs.adfa.edu.au
Reply-To: wkt(a)cs.adfa.edu.au
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
In article by Carl Lowenstein:
> Well, actually the M was for Modified. Particularly modified to work
> with some more DEC peripherals.
>
> What ran on 11/20's was Mini-Unix, which was a stripped-down 6th
> Edition. By the way I'm not sure that the PUPS archive has a Mini-Unix
> tape. I have one, although it has not been read since the days when I
> had an 11/20.
> carl
Yep, it's in Distributions/usdl/Mini-Unix. It's not in the research/
dir because it was not done in the labs, but elsewhere.
Cheers,
Warren
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id SAA00659
for pups-liszt; Thu, 2 Sep 1999 18:07:17 +1000 (EST)
>From Anders Magnusson <ragge(a)ludd.luth.se> Thu Sep 2 18:05:23 1999
Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id SAA00643;
Thu, 2 Sep 1999 18:05:30 +1000 (EST)
Received: from father.ludd.luth.se (ragge(a)father.ludd.luth.se [130.240.16.18])
by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id KAA22337;
Thu, 2 Sep 1999 10:05:25 +0200
From: Anders Magnusson <ragge(a)ludd.luth.se>
Received: (ragge@localhost) by father.ludd.luth.se (8.6.11/8.6.11) id KAA11504; Thu, 2 Sep 1999 10:05:24 +0200
Message-Id: <199909020805.KAA11504(a)father.ludd.luth.se>
Subject: Re: KDA50 woes
To: quasijarus(a)minnie.cs.adfa.edu.au
Date: Thu, 2 Sep 1999 10:05:23 +0200 (MET DST)
Cc: pups(a)minnie.cs.adfa.edu.au, quasijarus(a)minnie.cs.adfa.edu.au
In-Reply-To: <9909020115.AA00610(a)meson.jpsystems.com> from Michael Sokolov at "Sep 1, 99 08:15:23 pm"
X-Mailer: ELM [version 2.4ME+ PL15 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
> Hi,
>
> I wonder, does anyone here know anything about the KDA50? I've solved my RA72
>
Well, something I think... :-)
[...]
>
> So my questions to the folks are: First, is my understanding of the situation
> correct? Second, what can be done about it? I guess as a temporary solution I
> can remove this problematic IPL autodetection code and hard-code the IPL of my
> KDA50, but what is it? Is the IPL set with switches on the KDA50 or how? And
> what do the KDA50 switches do in the first place? Does anyone know? TIA.
>
The IPL autodetect code has seemed to me as unneccessary. You know that
the KDA50 will always interrupt at spl5, so you can hard-code it in
the interrupt driver and nuke the autodetect code. The same with the
other drivers that can be on Qbus:
if (uh->uh_type == QBA)
spl5();
-- Ragge
Hi,
I wonder, does anyone here know anything about the KDA50? I've solved my RA72
problem (as it turns out, if there is no control panel connected, the drive
assumes normal operation, i.e., spin up, go on-line, enable port A, no write
protect, and the unit number between 0 and 7 is set by the switches on the
right side of the drive), but now I have a different problem: I can't get UNIX
(4.3BSD-Quasijarus of course) to recognize the KDA50, although it worked fine
on my Webster ESDI controller back in Ohio, and others have also reported
successfully booting it on different controllers. By inserting a few debugging
printouts in the uda driver, I have determined that it fails the udaprobe(). I
know very little about UDA50/KDA50 registers, so I may be wrong, but it looks
to me that the code is trying to do the following. It diddles the controller
registers to make it start the initialization. Then apparently it expects the
controller to interrupt and set some status bits in some register. However,
because of Q-bus's odd interrupt protocol and the need to determine the IPL of
the controller, the procedure is done non-trivially. First it does an spl6(),
disabling all interrupts except BR7 (which these controllers apparently don't
use). Then it does the register diddling and testing with these interrupts
disabled. It allows the CPU to field the interrupt only when the register bits
indicate that the operation has been performed and the interrupt has been
posted. Apparently the assumption is that the controller will post the
interrupt and then set the right bits in the right registers without waiting
for the CPU to field the interrupt. Also apparently the KDA50 is different and
doesn't set those bits until the interrupt is fielded, breaking this code.
So my questions to the folks are: First, is my understanding of the situation
correct? Second, what can be done about it? I guess as a temporary solution I
can remove this problematic IPL autodetection code and hard-code the IPL of my
KDA50, but what is it? Is the IPL set with switches on the KDA50 or how? And
what do the KDA50 switches do in the first place? Does anyone know? TIA.
--
Michael Sokolov
Special Agent
International Free Computing Task Force
ARPA Internet SMTP mail: msokolov(a)meson.jpsystems.com
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id PAA00399
for pups-liszt; Thu, 2 Sep 1999 15:09:20 +1000 (EST)
>From Kirk McKusick <mckusick(a)flamingo.McKusick.COM> Thu Sep 2 09:44:29 1999
Received: from knecht.sendmail.org (knecht.sendmail.org [209.31.233.160])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id PAA00395
for <pups(a)minnie.cs.adfa.edu.au>; Thu, 2 Sep 1999 15:09:13 +1000 (EST)
Received: from flamingo.McKusick.COM (root(a)flamingo.mckusick.com [209.31.233.178])
by knecht.sendmail.org (8.9.3/8.9.3) with ESMTP id RAA20755;
Wed, 1 Sep 1999 17:54:11 -0700 (PDT)
Received: from flamingo.McKusick.COM (mckusick(a)localhost.concentric.net [127.0.0.1])
by flamingo.McKusick.COM (8.9.3/8.9.0) with ESMTP id QAA29309;
Wed, 1 Sep 1999 16:44:35 -0700 (PDT)
Message-Id: <199909012344.QAA29309(a)flamingo.McKusick.COM>
To: wkt(a)cs.adfa.edu.au
Subject: Re: V7M
cc: pups(a)minnie.cs.adfa.edu.au
In-reply-to: Your message of "Mon, 09 Aug 1999 09:41:23 +1000."
<199908082341.JAA83043(a)henry.cs.adfa.edu.au>
Date: Wed, 01 Sep 1999 16:44:29 -0700
From: Kirk McKusick <mckusick(a)flamingo.McKusick.COM>
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
My recollection is that V7M stood for V7-mini. It was a
striped down version of V7 that was designed to run on
the very low-end PDP-11's (like the 11/20).
Kirk McKusick
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id PAA00533
for pups-liszt; Thu, 2 Sep 1999 15:27:01 +1000 (EST)
>From "Steven M. Schultz" <sms(a)moe.2bsd.com> Thu Sep 2 15:25:35 1999
Received: from moe.2bsd.com (0(a)MOE.2BSD.COM [206.139.202.200])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id PAA00528
for <pups(a)minnie.cs.adfa.edu.au>; Thu, 2 Sep 1999 15:26:54 +1000 (EST)
Received: (from sms@localhost)
by moe.2bsd.com (8.9.0/8.9.0) id WAA04996
for pups(a)minnie.cs.adfa.edu.au; Wed, 1 Sep 1999 22:25:35 -0700 (PDT)
Date: Wed, 1 Sep 1999 22:25:35 -0700 (PDT)
From: "Steven M. Schultz" <sms(a)moe.2bsd.com>
Message-Id: <199909020525.WAA04996(a)moe.2bsd.com>
To: pups(a)minnie.cs.adfa.edu.au
Subject: Re: V7M
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
> From: Kirk McKusick <mckusick(a)flamingo.McKusick.COM>
>
> My recollection is that V7M stood for V7-mini. It was a
> striped down version of V7 that was designed to run on
> the very low-end PDP-11's (like the 11/20).
Hmmm, interesting. My memories dredge up the 'M' as meaning
"Modified". Don't recall it ever being touted as 11/20 capable
56kb, no MMU would be a wee bit too mini I'd think - was there ever
a V7 that could run without an MMU? If there was I've completely
forgotten about it.
Steven Schultz
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id PAA00770
for pups-liszt; Thu, 2 Sep 1999 15:59:45 +1000 (EST)
Hi,
I wonder, does anyone know how to set the unit number on an RA72 manually,
without the RA7x control panel? I need to put two RA72s in a BA123, I have the
skidplates under the drives, the KDA50 and the right internal SDI cables, but
this is a BA123, so I don't have that RA7x control panel they put in 3500/3600
skunk boxes. I know that on RF drives if you don't have that panel connector,
the drive has its own switches or jumpers to set the DSSI node number, and I'm
sure that the same is true for the SDI unit number on RA7x drives. There is a
pack of 3 DIP switches on the right side of the RA72, is that the unit number?
If so, is bit 0 on the left or on the right? Is 1 up or down? TIA.
--
Michael Sokolov
Special Agent
International Free Computing Task Force
ARPA Internet SMTP mail: msokolov(a)meson.jpsystems.com
