HI!
After a week or so of trying, I finally got 2.11BSD to recognize a KFQSA
in a PDP-11/73. The problem seems to be that 2.11BSD sets an MSCP packet
length of 64 bytes, but the KFQSA must have this field set to 60 bytes.
There is some confusion about if the header is part of the packet or
not. For the KFQSA, it is not included in the length. After that, life
is good........
Unfortunately I trashed my 2.11BSD installation in the process. :-( I
did a backup I think.....
Anyway, KFQSA modules are not that expensive and RF drives are pretty
cheap, so it is another solution to the lack of disk drives for QBus
PDPs. As long as you have a VAX for configuration. A 390MB RF71 is a
useful size for 2.11BSD.
After I get things put back together, I will send off a patch to sms for
the next release.... :-)
-chuck
on 3/23/02 11:26 PM, Warren Toomey at wkt(a)minnie.tuhs.org wrote:
> In article by Martin Crehan:
>> From a thread on Slashdot about Microsoft's Ancient History w/Unix
>> http://slashdot.org/articles/02/03/23/1422243.shtml?tid=130
>>
>> First Unix/Xenix (Score:1)
>> by presearch on Saturday March 23, @01:58PM (#3213453)
>> (User #214913 Info)
>
> I've left a comment in the thread asking if they would
> donate a copy of the tape's contents to our Archive.
I also remember running PDP/11 Xenix. The article is basically correct,
although Microsoft (or HCR) did add a working paging system that enabled
simulation of split I&D on small PDP/11s like the 11/23, 11/34, and 11/40.
I also remember that my copy of the installation document had been printed
by Microsoft's PDP/10 (referred to as the "Microsoft Heating Plant" :-) in
the printout). I wish I still had the tape and that printout. Sigh ...
--
Frank
"I don't hold with all this washing. This modern Behind-the-ears nonsense."
* Eeyore, "Winnie the Pooh"
Hello,
I'm writing a new networking protocol into the Linux kernel. I have to find the place in which the multiplexing of the incoming packets are done and sent to the initial handling functions of the appropriate protocols, according to the protocol types (x25,ax25,ip,appletalk,etc...). I think net_rx_action function does this. (version 2.4.8). W
Why does it searches two lists, why 2 lists (ptype_all-ptype_base)?
Second, what is the mission of dev_add_pack dev_remove pack functions in net/core/dev.h. I've heard they deal with protocols. But I am not sure.
Anyone interested in or know any person who knows about???
Arda...
---------------------------------
Yahoo! Mail -- Une adresse @yahoo.fr gratuite et en français !
From a thread on Slashdot about Microsoft's Ancient History w/Unix
http://slashdot.org/articles/02/03/23/1422243.shtml?tid=130
First Unix/Xenix (Score:1)
by presearch on Saturday March 23, @01:58PM (#3213453)
(User #214913 Info)
In 1979 all that existed of Xenix was a silver brochure from Microsoft
but there was no distribution. I wanted it to run it/sell it, seeing that
you could do the timesharing thing just like back at college, except
without a giant machine behind glass. I contacted the then tiny
Microsoft, asked, begged, pleaded but they had nothing to sell.
After multiple inquiries, they finally told me that they didn't have
Xenix yet, but they expected it to arrive shortly. Arrive? From where?
I was told, from Human Computing Resources (HCR) in Toronto.
Ahh, interesting. So I called HCR somehow got them to commit
to an early delivery. After a few weeks, and several dollars, the
day came. MS wanted a PDP-11 and 68000 version and was
only after the PDP-11 distro, I was 1 week ahead in the queue
from Microsoft. So, as I was told from HCR, I had the first Xenix
distribution in the US, ahead of Microsoft. I ran it on a LSI-11/23
with insanely expensive 256Kb of memory and a giant 20Mb
drive from Charles River Data Systems. It also had 2 eight inch
floppies (errrtt, clunk, clunk, errrrttt), and 2 four port serial cards
that each ran a VT100. The distro came on a 9-track tape (which
I still have) and the take drive was this weird, front loading thing
where you loaded the tape in the front like a big floppy and it
auto threaded the tape (sometimes). As I remember, it seemed
pretty fast, I'd start up stuff on all of the terminals, just to do it.
Of course, it wasn't that fast but at the time....
The Unix itself was a more or less pure Unix v7. The only thing,
as I remember that made is Xenix, was the boot message and
the captions on the man pages. There was no vi at that time,
the editor of choice was "ed". It did have a nice /usr/games
and I got a Zork for it from a friend.
We ended up selling a few of the boxes. The company was
called MSD. The only record of such is in a 1981 (Jan?) issue
of Byte with our little ad in the back. And that's the story of the
first commercial Unix sold in the US.
I am trying to get a KFQSA to work with 2.11BSD on a pdp-11. It always
fails with an error in the SA register during the transition between
STEP 3 and STEP 4 of the initialization sequence.
The SA register ends up with the value 101513. The error bit is set and
I think that the rest is an error code. I can't find a reference to
describe these error codes.
An RQDX3 and a CQD-223 in the same machine initialize fine. The KFQSA
initializes in an MVIII using NetBSD 1.5.
I have looked over the initialization code from NetBSD, Ultrix-32,
4.4BSD, Ultrix-11, and 2.11BSD. The values being sent, are all very
similar. One difference is that the VAXen OS use polling during the
init, and the pdp-11 code uses interrupts.
Any suggestions or comments about the MSCP 4 step init and how it works
on the KFQSA?
A pointer to error code reference would be great too.
-chuck
Hi there,
The pdp 11/44 is working with a minimal configuration!
Thanks to Bill Gunshannon and Milo Velmimirovic.
The M7090 CIM is now doing RS 232 and gives me output (i get the console
prompt >>>) the backplane only contains memory and the cpu-cards.
The connector M9202 connects the two planes. I tried to boot the RL11 with
one of my RL02's but i didn't work, i guess this is because i don't have a
UNIBUS terminator. is it possible to make one myself ? i could make a
dual-sided PCB. or is it possible that the backplane itself is terminated
(like small qbus-systems have)?
>> "DRU-11 CA" parallel DMA.
>
>Looks like it's a parallel interface module. Are there two 40-pin BERG
>headers on the board?
yes there are two 40 pin connectors. so it's a interface, i guess i don't
use this...
i guess i might use the Ethernet cards, the SMD-diskcontroller and the
RL11. does anyone have the pinout of the M7792/M7793 Ethernet-controller ?
i also still have no idea what those cards might be:
> Ramtek 508295/508297 (has a 50 pin connector)
> Eikonix 821-015cs (handwritten: 785-283)(has two 50 pin connectors)
if anyone has a spare unibus-controller for ciphertapes (pertec-interface),
please contact me.
-- regards, lothar.
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
hi,
i never used rsync, so sorry for my question, but i have some
problems ...
1) i can't find any CD image in the "Mirroring" directory
2) launching
rsync -avuz --exclude 'CD_IMAGE.*' minnie.tuhs.org::UA_Mirroring Mirroring
as explained in http://www.tuhs.org/mirroring.html give me no result ...
no files nor dir. are written and the rsync exit without any kind of
error ...
what's wrong ?
we at freaknet medialab really want to mirror the site and distribute
the 2 CD package :)
tnx all,
--
[asbesto : freaknet medialab : GPG key available on keyservers ]
[MAIL ATTACH SPAM HTML WORD and msgs larger than 150K >/dev/null ]
[http://www.freaknet.org/~asbesto : http://kyuzz.org/radiocybernet]
My first unibus-pdp...
I picked up the box this weekend, without any additional equipment or
information.
They also told me is is configured for a 20 mA current loop, but i don't
have a working current loop term. is there a easy way of converting 20mA
current loop to RS-232 ?
I found a posting in classiccmp that says M7090 might be configured for
RS232 or current loop(i don't know if they meant the MUX or the CIM M7090
or both), is there a way to find out without blowing things up ? i do have
a VT420, maybe i can do current loop <-> rs422 ?
i didn't power up the box yet, first i'd like to connect the correct
console and check the configuration. maybe reduce the configuration to
RL11, DEUNA and disk-controller? another problem is the media, i'd like to
install 2.9BSD, but how ? i still hope that one of those unidentified cards
turns out to be a ciphertape-controller (Pertec-interface for my second
cipher F880).
any help, information or link is very welcome.
-- regards, lothar
This is the actual configuration:
<-power supply / frontpanel->
M 7090 - - - - dual height KD11-Z 11/44 console interface module
- - - - - - empty (this is where the optional CIS belongs)
------M 7093------ hex height FP11-F 11/44 floating point module
------M 7094------ hex height KD11-Z 11/44 data path module
------M 7095------ hex height KD11-Z 11/44 control module
------M 7096------ hex height KD11-Z 11/44 multifunction module
------M 7097------ hex height KK11-B 11/44 4-Kword cache module
------M 7098------ hex height KD11-Z 11/44 UNIBUS interface
------M 8743------ hex height MS11-PB 1-Mbyte ECC RAM (-BH)
- - - - - - empty
------M 7486------ hex height UDA52 Controller for SDI disk drives (UDA
SI)
------M 7485------ hex height UDA50-A UNIBUS to radial disk interface
------M 7762------ hex height RL11 RL01/02 disk controller
M 9202 ---M 8729-- dual height M9202 / quad height M8729 no info.
M 9202 - - - - empty (badge says hex SPC slot)
- - - - - - empty
- - - - - - empty
- - - F - - empty, F is a bus grant continuity (single height)
------SC4110------ hex height
------M 7814------ hex height DZ11-C 8-line 20mA data MUX, 50 to
100-Kbaud
------M 7792------ hex height see below
------M 7793------ hex height see below
- - --Ramtek--- quad height no info
- - - - - -
addition to descriptions:
M7485-YA UDA50-A UNIBUS to radial disk interface PR board with blasted
ROMs
M7792 DEUNA port module, UNIBUS to ethernet microprocessor. (1 of 2)
M7793 DEUNA link module, M7792 to ethernet bus line unit. (2 of 2)
i don't have any reliable description for the M8729, i found a with google:
"DRU-11 CA" parallel DMA.
the SC4110 (Emulex) is probably a SMD disk controller, at least the heavy
disk was attached to it.
there are two cards for which i found nothing:
Ramtek 508295/508297 (has a 50 pin connector)
Eikonix 821-015cs (handwritten: 785-283)(has two 50 pin connectors)
while cleaning the box i found three bus grant continuity cards (single
height). it is possible they fell out during transport.
i've read akos varga's unibus basics, but i still can't tell if this is a
valid configuration. i found a badge on top of the box, which says the
M8729 is in a SPC slot and the "second" part of the M9202 is in a hex. SPC
slot.
Warren wrote :-
>I think the phrase `successor systems' covers PWB, as PWB is derived
>from 6th Edition. Yes, I suppose we could ask for Mini-UNIX, PWB,
>Mert, RT and TS also to be added to the list.
I'd really like to get my hands on MERT, but past correspondence from DMR
suggests that it was probably never released outside the labs. So, are there
any tapes lying about?
Any hints on making the v7_rk05_1145 boot image work with Ersatz11 v3
demo?
John Perkins Willis
Software Engineer/Database Architect
Ariel Technologies
(505) 524-6860
jwillis(a)arielusa.com
In article by Fred N. van Kempen:
> Isn't PWB more closely related to USG and/or Sys III ?
> --f
SysIII is related to PWB and TS, which means both PWB and TS came
before SysIII and so are covered by the Caldera license.
I still have a number of PWB `things' in the archive: supposed releases,
parts of releases, etc. I need to sit down one day and try to reconstitute
a canonical release set from these bits and pieces.
Warren
In article by Lars Buitinck:
> ftp://minnie.tuhs.org/UnixArchive/COPYRIGHTS
> says "See Caldera-license.pdf for [Caldera's] license conditions
> for thrse [sic] systems," where "these systems" includes PWB.
> The Caldera license doesn't even mention PWB. It's (apparently)
> still illegal to copy PWB (unless they consider it a version of
> V6?). I don't think they'll prosecute you for it (:-) but I'd
> change it anyway.
> Lars
I think the phrase `successor systems' covers PWB, as PWB is derived
from 6th Edition. Yes, I suppose we could ask for Mini-UNIX, PWB,
Mert, RT and TS also to be added to the list.
Cheers,
Warren
P.S I'll fix thrse at least :)
hi all, here's asbesto from FreakNet Medialab in Catania, Italy.
our pdp11/34 is still alive !!!
the local mayor and the municipalty shutted down electric power in our
old place. now we have a new place for our computers (here in italy
we have a really bad politic situation so the municipalty hate us)
the pdp11 was so cutted in parts and mounted again, and it seem
working ... only a weird sound come from the rl01 disk when working.
it SEEM the sound of the disk head "touching" the disk .. maybe ?
the disk is ok and a copy test of all files is working.
any idea ? :)
p.s. soon i will ask HELP to install any kind of UNIX on this pdp11/34:
we have no tape. only 8" floppy disks and the rl01 (and, of course, serial
port for terminal & printer)
sorry for my bad english, i'm very tired now
to know more about us, http://www.freaknet.org
gabriele "asbesto"
Hi,
On 03/03/2002 01:47:34 AM PST "Steven M. Schultz" wrote:
>
> Glad to hear you're current and are not seeing 'df' weirdness. You
> may want to upgrade P11 to 2.9 though - that would, I think, have
> fixed that problem before you saw it ;)
No, wouldn't :-)
I used 2.10a all the time.
regards,
chris
On Mon, Jan 28, 2002 at 10:03:45PM +0100, Jonathan Naylor wrote:
> With so much open source code out there, it'd be a relatively simple
> task to find C code for IDE disc access and such like. I would even
> suggest getting older Linux code from the 2.0.x days as its likely to
> be a little less complex, while still being stable.
Linux!? why not one of the three BSD-licensed BSD-derived Net/Free/Open
BSDs? keep it "in the family" so to speak. :)
--
Aaron J. Grier | "Not your ordinary poofy goof." | agrier(a)poofygoof.com
"[...] I generally haven't found IDM guys to be very good
live acts, most of them just sit down at their laptop and
tweak reaktor." -- Brandon Daniel
Howdy -
> From: Christian Groessler <cpg(a)aladdin.de>
> I just last week installed v6 from tape image. I have to admit, I like
> working boot images more :-) (Since I only have an emulator and not
An emualtor of course would use an emulated tape image ;) That's
how I typically install. There are instructions and sources to
the program to create the 'virtual tape' from the dump and tar files.
> the real thing, I don't have the need to physically transfer the stuff.)
I keep forgetting that not everyone has a SCSI<->Qbus adaptor :)
(it was _expensive_ at the time but gosh, after 10 years the initial
$ pain is long long gone and I've gotten a lot of use out of it)
> Hmm, I just did this now, but I have to admit, I only browsed the
> instructions of most of them. I followed the instructions of 412/413
> because I feared I'd forget to update init before rebooting the new kernel.
Yes, screwing up 'init' is, to put it mildly, catastrophic. During
the development and testing of that set of updates I did render my
system unbootable. Thankfully I had a spare OS installed on the
SCSI Zip drive - I just booted from "DU 1" and put back a working
'init' (turns out that a 100MB Zip disk can contain a *full* 2.11BSD
system - not a lot of space left, but it includes all sources and
will boot).
> But otherwise I applied all patches to 442, and then rebuilt the
> kernel, rebooted, and did "make build; make installsrc". Seemed to work.
That's fantastic to hear!
> I noticed 2 patches, which patched /usr/src/sys/GENERIC/Makefile, but
> this is a generated file I think. At least it wasn't present, because
Yes and No. YES - it is generated by running './config' in /sys/conf.
NO - it's an integral part of the OS as distributed.
> I removed /usr/src/sys/GENERIC.
You really didn't want to do that ;)
The Make* files for custom kernels will (100% guaranteed) diverge
from the defaults. That's expected. The GENERIC kernel is a special
case though. When changes are made to the Make* files (overlay sizes
change for example) the patches will not attempt to find and "fix"
any locally created kernels - but the guarantee has always been that
the GENERIC kernel _will_ build, thus the patches presume that the
/sys/GENERIC directory hasn't been removed. Indeed the kernel patches
usually suggest rebuilding GENERIC.
It is a Good Idea (saved my system a couple times) to keep a known
good working _non_networking kernel (i.e. GENERIC) in /genunix. That
way if you are tinkering around (or a bad patch ends up in /unix) you
have something to boot. Many is the time (during development, testing
of course) that I've had to rely on a /genunix to get the system
back alive.
Glad to hear you're current and are not seeing 'df' weirdness. You
may want to upgrade P11 to 2.9 though - that would, I think, have
fixed that problem before you saw it ;)
Cheers,
Steven Schultz
sms(a)2bsd.com
Hi,
On 02/28/2002 08:53:34 AM PST "Steven M. Schultz" wrote:
>
>> From: Christian Groessler <cpg(a)aladdin.de>
>> > Look at the /VERSION file. The first or second line will have
>> > the patchlevel. That file's updated by each patch.
>>
>> I have 400. I assume www.2bsd.com contains the newest patches? So 442
>> is the latest?
>
> It _might_ be easier to create an install tape from the files in
> the 2.11 portion of the PUPS archive - I think that was updated
> to about patchlevel 432 or so. There is documentation on how to
> create a boot tape, etc from the compressed files.
I just last week installed v6 from tape image. I have to admit, I like
working boot images more :-) (Since I only have an emulator and not
the real thing, I don't have the need to physically transfer the
stuff.)
> On the other hand it might be instructive/interesting/whatever to
> apply the 42 updates manually - just be sure to read the instructions
> that come with each one :)
Hmm, I just did this now, but I have to admit, I only browsed the
instructions of most of them. I followed the instructions of 412/413
because I feared I'd forget to update init before rebooting the new
kernel.
But otherwise I applied all patches to 442, and then rebuilt the
kernel, rebooted, and did "make build; make installsrc". Seemed to
work.
I noticed 2 patches, which patched /usr/src/sys/GENERIC/Makefile, but
this is a generated file I think. At least it wasn't present, because
I removed /usr/src/sys/GENERIC.
regards,
chris
> From: Nutech <repro(a)nutechgroup.net>
> To: pups(a)minnie.tuhs.org
> Subject: [pups] PDP 11
> Date: Sun, 24 Feb 2002 01:27:40 +0530
>
> I post this message with hope that someone out there can help me with a
> problem I have at hand.
>
> My company recently bought a preowned printing machine, which uses a
> PDP11/73 BA23
> connected to a VT240 terminal to control the functions of the machine.
> Needless to say that we are unable to make the PDP run since we have no
> knowledge of the machine and have no one to look upto for guidance..
>
> While we are able to power on the PDP, the VT240 is dead.
Problems like this are much more easily solved in person than by email
correspondence. Why not tell everyone where you are physically located,
and perhaps someone nearby can help.
The VT240 could be replaced by any of several terminals, or even by a PC
running a terminal emulation program.
carl
carl lowenstein marine physical lab u.c. san diego
clowenstein(a)ucsd.edu
This must be a FAQ but I couldn't find the answer anywhere.
I have some 2.11BSD disk images that I want to copy large files onto on a
NetBSD box. Can someone please point me to a tool that can do it?
These are disk images that I use with p11. For various reasons, using p11
simulated tape drive isn't an option. I use kermit to inject small files into
the running p11 + 2.11BSD. It takes many minutes to 300KB. It takes much,
much more time to copy 12MB.
David Talmage
Hi -
> From: Christian Groessler <cpg(a)aladdin.de>
> > Look at the /VERSION file. The first or second line will have
> > the patchlevel. That file's updated by each patch.
>
> I have 400. I assume www.2bsd.com contains the newest patches? So 442
> is the latest?
Wow, that is quite old.
A faster link is at FTP.TO.GD-ES.COM (that's a T-1 vs the ISDL
link I have at home).
It _might_ be easier to create an install tape from the files in
the 2.11 portion of the PUPS archive - I think that was updated
to about patchlevel 432 or so. There is documentation on how to
create a boot tape, etc from the compressed files.
On the other hand it might be instructive/interesting/whatever to
apply the 42 updates manually - just be sure to read the instructions
that come with each one :)
Cheers,
Steven
Warren,
Does the archive contain any Venix images that are not in "tdo" format? I
have been unsuccessful in creating the floppies using that method. If I
could get an image from "dd", I could use my VAX or PDP to create images for
my Pro-380.
Thanks,
-Steve Davidson
Hi,
On 02/27/2002 03:25:22 PM PST "Steven M. Schultz" wrote:
>
>Hello again -
>
>> From: Christian Groessler <cpg(a)aladdin.de>
>> Regarding the patchlevels, how do I find out which patchlevel my
>> system is at?
>
> Look at the /VERSION file. The first or second line will have
> the patchlevel. That file's updated by each patch.
I have 400. I assume www.2bsd.com contains the newest patches? So 442
is the latest?
regards,
chris
Hello again -
> From: Christian Groessler <cpg(a)aladdin.de>
> > Mmmm, I wonder if the problems you were having were caused by
> > /dev not being correctly populated.
>
> Maybe. I noticed they're missing and recreated them by hand. Perhaps I
> made a mistake there.
It would be easy enough to do - or perhaps a critical one was
left out. Filesystems without device nodes can be moved
with a 'tar' pipeline but the root filesystem is special.
> It's a problem of the p11 emulator I use. I got a patch off-list which
> fixed it. It was some signed/unsigned thing.
Ah ha!
> Regarding the patchlevels, how do I find out which patchlevel my
> system is at?
Look at the /VERSION file. The first or second line will have
the patchlevel. That file's updated by each patch.
Cheers,
Steven