All,
I am still bashing away at my v7 a.out simulator, available at
ftp://minnie.cs.adfa.oz.au/apout_2.1.tar.gz. I'm having a *$(&(#(@ of a time
getting it to work 100% correctly.
At the moment, I can compile 30 to 40% of the programs in /usr/src/cmd. It
seems that the assember isn't being simulated correctly. Nearly all the
other programs work fine.
Does anybody have any PDP-11 asm programs (preferably v7 Unix .s files)
that give the user mode a damn good flogging, and catch instructions and
addressing modes that are not working correctly :-)
Thanks all,
Warren
From Dave Horsfall <dave(a)esi.COM.AU> Tue Nov 21
21:49:00 1995
Received: from eram.esi.com.au (dave@localhost) by
minnie.cs.adfa.oz.au (8.6.8/8.3) with ESMTP id WAA01901; Tue, 21 Nov 1995 22:46:42 +1100
Received: (from dave@localhost)
by eram.esi.com.au (8.6.12/ESI-HUB-2.0) id WAA10767; Tue, 21 Nov 1995 22:49:01 +1100
Date: Tue, 21 Nov 1995 22:49:00 +1100 (EST)
From: Dave Horsfall <dave(a)esi.COM.AU>
To: oldunix(a)minnie.cs.adfa.oz.au
Subject: Re: mknod device numbers
In-Reply-To: <9511202219.AA13088@dolphin>
Message-ID: <Pine.SUN.3.91.951121224148.10757A-100000(a)eram.esi.com.au>
X-Witty-Saying: "Mobius strip - see other side for instructions"
X-Disclaimer: "Me, speak for us?"
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Tue, 21 Nov 1995, Warren Toomey wrote:
Nobody, not even Dennis Ritchie, knows how to get a
license for any of these.
Hopefully, when the Unix source finishes its current migration to SCO and HP,
we can ask them for an answer.
Ah yes, the classic Catch-22...
"How do I do this?"
"You need a licence."
"How do I get a licence?"
"Nobody knows."
With apologies to Milo Minderbinder...
And in the meantime. those of us who can't quite lay our hands upon
that piece of paper will just have to wait until Something Can Be Done.
--
Dave Horsfall (VK2KFU) | dave(a)esi.com.au | VK2KFU @ VK2DAA.NSW.AUS.OC | PGP 2.6
Opinions expressed are mine. | D8 15 71 F9 26 C8 63 40 5E 63 5C 65 FC A0 22 99
From "Danny R. Brown"
<sysyphus(a)crl.com> Wed Nov 22 16:06:51 1995
Received: from
mail.crl.com by
minnie.cs.adfa.oz.au (8.6.8/8.3) with SMTP id RAA04567; Wed, 22 Nov 1995 17:12:03 +1100
Received: from
crl12.crl.com by
mail.crl.com with SMTP id AA21753
(5.65c/IDA-1.5 for <oldunix(a)minnie.cs.adfa.oz.au>) Tue, 21 Nov 1995 22:10:07
-0800
Received: by
crl12.crl.com id AA02825
(5.65c/IDA-1.5 for oldunix(a)minnie.cs.adfa.oz.au) Tue, 21 Nov 1995 22:06:51 -0800
Date: Tue, 21 Nov 1995 22:06:51 -0800 (PST)
From: "Danny R. Brown" <sysyphus(a)crl.com>
To: oldunix(a)minnie.cs.adfa.oz.au
Message-Id: <Pine.SUN.3.91.951121214923.2266B-100000(a)crl12.crl.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Greetings:
Woe is me.
I have been trying to resurrect Unix (BSD) on my venerable PDP-11/73.
It had an RL02, which has gone west.
It is running RT-11/TSX off an RD-54, and I would much like to run
BSD2.11 instead, for several reasons.
Now, I have several components of 2.11, and I'm trying to build a
bootable TK50 tape to install from. The problem is that I cannot
seem to assemble the tape files onto the tape using RT-11. It has
no 'dd' facility. At least, I thought it did, but every left-handed
syntax variation I have tried has resulted in "You can't do that"
-type errors, so I have given up.
This is really a simple problem. I would steal another RL02 if I could
build the tape from BSD2.9, but it doesn't support MSCP. So what I
need is either:
1. Someone who knows the secret to doing an addressable variable-
block-length transfer to a TMSCP device with RT-11; or
2. A bootable RL02 image of 2.11, wwhich would be a feat; or
3.A bootable RD5X image of same; or
4.A TK50, preferably the distribution tape.
(Yes, I put eggs in my beer).
All leads appreciated. I *do* have surplus Q-bus hardware (except
for RL02 drives).
Cheers!
BTW- how do I subscribe to this mailing list?
*************************************************************************
* A Personal Message from * BASILISK *
* Danny R. Brown * "Try our other fine flavors!" *
* ( sysyphus(a)crl.com ) * (404) 392-1691 *
* Pager:(404)397-0516 * LYNC host mode *
*************************************************************************
From "Steven M. Schultz"
<sms(a)wlv.iipo.gtegsc.com> Wed Nov 22 17:04:20 1995
Received: from
wlv.iipo.gtegsc.com by minnie.cs.adfa.oz.au (8.6.8/8.3) with ESMTP id SAA04683; Wed, 22
Nov 1995 18:05:23 +1100
Received: (from sms@localhost) by
wlv.iipo.gtegsc.com (8.6.10/8.6.12) id XAA12504; Tue, 21
Nov 1995 23:04:20 -0800
Date: Tue, 21 Nov 1995 23:04:20 -0800
From: "Steven M. Schultz" <sms(a)wlv.iipo.gtegsc.com>
Message-Id: <199511220704.XAA12504(a)wlv.iipo.gtegsc.com>
To: oldunix(a)minnie.cs.adfa.oz.au, sysyphus(a)crl.com
Danny -
From: "Danny R. Brown"
<sysyphus(a)crl.com>
Now, I have several components of 2.11, and I'm trying to build a
bootable TK50 tape to install from. The problem is that I cannot
Hmmm - does RT-11 have the ability/utilities to write 512 byte
records "bits as is" to tape? No labeling, no nothing.
seem to assemble the tape files onto the tape using
RT-11. It has
no 'dd' facility. At least, I thought it did, but every left-handed
syntax variation I have tried has resulted in "You can't do that"
Can you, using RT-11 do the equivalent of:
cat mtboot mtboot boot > file
dd if=file of=tapedrive bs=512
Basically what you want to do is have two copies of the tapeboot
block followed immediately by the boot program written to tape
using 512 byte records. Perhaps catenating the data together into
1 temp file first would help and then write that file out all at
one time.
Once you have that data on tape you have a bootable TK50. The
other images (mkfs, restor, etc) can be put on separate tapes if
need be and loaded one at a time.
That will require some interpolation of the setup/installation
documents but it shouldn't be too hard to figure out.
This is really a simple problem. I would steal another
RL02 if I could
build the tape from BSD2.9, but it doesn't support MSCP. So what I
Or TMSCP ;-(
4.A TK50, preferably the distribution tape.
(Yes, I put eggs in my beer).
Bletch (to eggs in beer) ;-)
TK50 tapes are excrutiatingly (sp) time consuming to write - I'm not
sure where the problem is (other than the TK50 being about as smart
and fast as a rock). Reading them isn't too bad, but to write a full
2.11 kit on TK50 took around 7 hours the last time I did it on a 11/73.
BTW- how do I subscribe to this mailing list?
Drop a line to Warren Toomey (wkt(a)csadfa.cs.adfa.oz.au)
Cheers and good luck.
Steven
From "Danny R. Brown"
<sysyphus(a)crl.com> Thu Nov 23 11:17:39 1995
Received: from
mail.crl.com by
minnie.cs.adfa.oz.au (8.6.8/8.3) with SMTP id MAA06264; Thu, 23 Nov 1995 12:26:57 +1059
Received: from
crl11.crl.com by
mail.crl.com with SMTP id AA29097
(5.65c/IDA-1.5 for <oldunix(a)minnie.cs.adfa.oz.au>) Wed, 22 Nov 1995 17:25:08
-0800
Received: by
crl11.crl.com id AA28493
(5.65c/IDA-1.5); Wed, 22 Nov 1995 17:17:40 -0800
Date: Wed, 22 Nov 1995 17:17:39 -0800 (PST)
From: "Danny R. Brown" <sysyphus(a)crl.com>
To: "Steven M. Schultz" <sms(a)wlv.iipo.gtegsc.com>
Cc: oldunix(a)minnie.cs.adfa.oz.au
Subject: Re: your mail
In-Reply-To: <199511220704.XAA12504(a)wlv.iipo.gtegsc.com>
Message-Id: <Pine.SUN.3.91.951122170747.28165A-100000(a)crl11.crl.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Tue, 21 Nov 1995, Steven M. Schultz wrote:
Danny -
From: "Danny R. Brown"
<sysyphus(a)crl.com>
Now, I have several components of 2.11, and I'm trying to build a
bootable TK50 tape to install from. The problem is that I cannot
Hmmm - does RT-11 have the ability/utilities to write 512 byte
records "bits as is" to tape? No labeling, no nothing.
------- snip ------
Can you, using RT-11 do the equivalent of:
cat mtboot mtboot boot > file
dd if=file of=tapedrive bs=512
First, I want to complement you on the excellent docs for 2.11BSD.
Second, I want to flame the people at DEC who decided that the
TK-50 MUST have a directory of some sort, and that various commands
which will work with other mag-tape devices will NOT work on the
TK-50 (under RT-11).
I am now going to plan B. I am going to scrounge up a proper reel-
to -reel magtape.
Anybody know where I can find one ? :=)
*************************************************************************
* A Personal Message from * BASILISK *
* Danny R. Brown * "Try our other fine flavors!" *
* ( sysyphus(a)crl.com ) * (404) 392-1691 *
* Pager:(404)397-0516 * LYNC host mode *
*************************************************************************
From Robin Birch <robin(a)falstaf.demon.co.uk> Thu
Nov 23 17:55:16 1995
Received: from
relay-4.mail.demon.net by minnie.cs.adfa.oz.au
(8.6.8/8.3) with SMTP id TAA06791; Thu, 23 Nov 1995 19:10:56 +1059
Received: from post.demon.co.uk by
relay-4.mail.demon.net id sg.ac28016;
23 Nov 95 8:09 GMT
Received: from falstaf.demon.co.uk by
relay-3.mail.demon.net id sg.aa25017;
23 Nov 95 8:07 GMT
Date: Thu, 23 Nov 1995 07:55:16 GMT
From: Robin Birch <robin(a)falstaf.demon.co.uk>
Reply-To: robin(a)falstaf.demon.co.uk
Message-Id: <143(a)falstaf.demon.co.uk>
To: sysyphus(a)crl.com, "Steven M. Schultz"(a)falstaf.demon.co.uk
Cc: oldunix(a)minnie.cs.adfa.oz.au
Subject: Re: Re: your mail
X-Mailer: FIMail V0.9d
X-User: Alpha Test Version Of FI-Mail, DisWin 1.5C:\WINSOCK\WINDIS
X-SMTP-Posting-Host: falstaf.demon.co.uk [Thu, 23 Nov 95 8:07:33 GMT]
X-SMTP-Posting-Host: post.demon.co.uk [Thu, 23 Nov 95 8:09:33 GMT]
First, I want to complement you on the excellent
docs for 2.11BSD.
Agreed, they are excellent, Steven did a wonderful job of continuing and
enhancing the docs that were completed for 2.10. They originally enabled
me to do a complete install, never having done one for anything other than
RSX and with zero UNIX experience. SO again, well done Steven.
Second, I want to flame the people at DEC who decided that the
TK-50 MUST have a directory of some sort, and that various commands
which will work with other mag-tape devices will NOT work on the
TK-50 (under RT-11).
Can you not write to the TK50 using system calls?. What you need to do is to
write a utility that does "raw" byte by byte writes to the tape. I can't
believe that this can't be done. If this can be done then images could be
written to the tape exactly as they appear on a standard 2.11 distribution
which could help you out.
Failing that, where are you?. Could one of the people close by who have 2.11
cut you a TK50?.
Cheers
Robin
--
---------------------------------------------------------------------------
| Robin Birch EMail robin(a)falstaf.demon.co.uk |
---------------------------------------------------------------------------
From Johnny Billquist <bqt(a)Minsk.DoCS.UU.SE> Thu
Nov 23 18:25:13 1995
Received: from sunic.sunet.se by minnie.cs.adfa.oz.au
(8.6.8/8.3) with ESMTP id TAA06805; Thu, 23 Nov 1995 19:25:22 +1100
Received: from Minsk.DoCS.UU.SE by sunic.sunet.se (8.6.8/2.03)
id JAA13839; Thu, 23 Nov 1995 09:25:15 +0100
Received: by Minsk.DoCS.UU.SE (Sun-4/630, SunOS 4.1.2)
with sendmail 5.61-bind 1.5+ida/ICU/DoCS id AA21643; Thu, 23 Nov 95 09:25:14 +0100
From: Johnny Billquist <bqt(a)Minsk.DoCS.UU.SE>
Date: Thu, 23 Nov 95 9:25:13 +0100 (MET)
Reply-To: bqt(a)Minsk.DoCS.UU.SE
To: "Danny R. Brown" <sysyphus(a)crl.com>
Cc: "Steven M. Schultz" <sms(a)wlv.iipo.gtegsc.com>,
oldunix(a)minnie.cs.adfa.oz.au
Subject: Re: your mail
In-Reply-To: Your message of Wed, 22 Nov 1995 17:17:39 -0800 (PST)
Message-Id: <CMM.0.90.0.817115113.bqt(a)Minsk.DoCS.UU.SE>
On Tue, 21 Nov 1995, Steven M. Schultz wrote:
Danny -
From: "Danny R. Brown"
<sysyphus(a)crl.com>
Now, I have several components of 2.11, and I'm trying to build a
bootable TK50 tape to install from. The problem is that I cannot
Hmmm - does RT-11 have the ability/utilities to write 512 byte
records "bits as is" to tape? No labeling, no nothing.
------- snip ------
Can you, using RT-11 do the equivalent of:
cat mtboot mtboot boot > file
dd if=file of=tapedrive bs=512
First, I want to complement you on the excellent docs for 2.11BSD.
Second, I want to flame the people at DEC who decided that the
TK-50 MUST have a directory of some sort, and that various commands
which will work with other mag-tape devices will NOT work on the
TK-50 (under RT-11).
I am now going to plan B. I am going to scrounge up a proper reel-
to -reel magtape.
Anybody know where I can find one ? :=)
I have a TU77 here in Sweden... :-)
And maybe Megan can answer for that "stupidity"...? :-)
Johnny
From "Danny R. Brown"
<sysyphus(a)crl.com> Mon Nov 27 15:45:23 1995
Received: from
mail.crl.com by
minnie.cs.adfa.oz.au (8.6.8/8.3) with SMTP id QAA00979; Mon, 27 Nov 1995 16:57:04 +1100
Received: from
crl14.crl.com by
mail.crl.com with SMTP id AA03371
(5.65c/IDA-1.5 for <oldunix(a)minnie.cs.adfa.oz.au>) Sun, 26 Nov 1995 21:55:08
-0800
Received: by
crl14.crl.com id AA17836
(5.65c/IDA-1.5 for oldunix(a)minnie.cs.adfa.oz.au) Sun, 26 Nov 1995 21:45:23 -0800
Date: Sun, 26 Nov 1995 21:45:23 -0800 (PST)
From: "Danny R. Brown" <sysyphus(a)crl.com>
To: oldunix(a)minnie.cs.adfa.oz.au
Subject: BSD211 Tape building
Message-Id: <Pine.SUN.3.91.951126212950.17682A-100000(a)crl14.crl.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Greetings:
I'm getting there. Now that I have a working(??) drive, more trouble.
The file size/# of records/block sizea aren't matching.
bytes, 512 -byte
Tape file Docs- #records, size PC RT11disk blocks
0 mtboot 1 512 512 1
boot 14 512 32462 64
1 disklabel * 23@ 512 or 1024 36191 71
2 mkfs 28 1024 31727 62
3 restor 27 1024 34066 67
4 icheck 26 1024 31356 62
* disklabel was quoted as two different bs in two different places.
I really think that my gunzipping is kosher- I do it in the PC
prior to ethernet-ing it to the PDP with no errors, and in fact
I unzipped one file on my unix host and beamed it down. It was the
same.
Anyway boot is too big or restor is to small, or something. Any ideas
whatis going on here?
Merry Christmas!
*************************************************************************
* A Personal Message from * BASILISK *
* Danny R. Brown * "Try our other fine flavors!" *
* ( sysyphus(a)crl.com ) * (404) 392-1691 *
* Pager:(404)397-0516 * LYNC host mode *
*************************************************************************
From "Steven M. Schultz"
<sms(a)wlv.iipo.gtegsc.com> Mon Nov 27 17:09:29 1995
Received: from
wlv.iipo.gtegsc.com by minnie.cs.adfa.oz.au (8.6.8/8.3) with ESMTP id SAA01218; Mon, 27
Nov 1995 18:10:55 +1059
Received: (from sms@localhost) by
wlv.iipo.gtegsc.com (8.6.10/8.6.12) id XAA21408; Sun, 26
Nov 1995 23:09:29 -0800
Date: Sun, 26 Nov 1995 23:09:29 -0800
From: "Steven M. Schultz" <sms(a)wlv.iipo.gtegsc.com>
Message-Id: <199511270709.XAA21408(a)wlv.iipo.gtegsc.com>
To: oldunix(a)minnie.cs.adfa.oz.au, sysyphus(a)crl.com
Subject: Re: BSD211 Tape building
Hi -
From: "Danny R. Brown"
<sysyphus(a)crl.com>
Greetings:
The file size/# of records/block sizea aren't matching.
I'm not sure what you mean by "not matching" - the sizes you list
below are correct. 'boot' is 32462 bytes, 'disklabel' is 36191
bytes,
'mkfs' is indeed 31727, and so on.
Tape file Docs- #records, size PC
RT11disk blocks
0 mtboot 1 512 512 1
boot 14 512 32462 64
1 disklabel * 23@ 512 or 1024 36191 71
2 mkfs 28 1024 31727 62
3 restor 27 1024 34066 67
4 icheck 26 1024 31356 62
* disklabel was quoted as two different bs in two different places.
ARRGH! That's a typo in the setup documents. Sorry 'bout that. I'll
updated the master copies and post a patch in comp.bugs.2bsd soon.
ALL of the executable programs (disklabel, icheck, mkfs, restor)
must be blocked at 1024 bytes per record on the tape.
I really think that my gunzipping is kosher- I do it
in the PC
Yep - it looks like the gunzip went ok - the byte sizes look correct.
Anyway boot is too big or restor is to small, or
something. Any ideas
whatis going on here?
You lost me there - what is too big or too small about them? The
record counts mentioned in the setup documents are examples - the
counts were accurate at one time, but then if a bug was fixed or a
feature added to boot or restor the number of records would change
slightly.
The various programs change size over time and the documents are not
updated if the record sizes change a little bit.
Oh - you need to have 2 copies of the 'mtboot' file at the front of
the tape. Why (I hear you ask)? Some boot roms actually read the
2nd copy!
The format of a boot tape is:
mtboot
mtboot
boot
<TM>
disklabel
<TM>
mkfs
<TM>
restor
<TM>
icheck
<TM>
<TM> = Tape Mark.
the first file (with mtboot,mtboot,boot) is blocked at 512 bytes, all
the other executables are blocked at 1024 (ignore the typo in the
setup docs).
Good Luck!
Steven Schultz
sms(a)wlv.iipo.gtegsc.com