Anyone here know if 4.4BSD supports the MicroVax 3400 series of machines? One
was given to me by my school (clearing out old equipment) and I would like to
get some pure BSD goodness on it again. Also, anyone know if it's possible to
make tapes under VMS?
Thanks in advance,
Rob Becker
Rob Becker <becker(a)ab.edu> wrote:
> Anyone here know if 4.4BSD supports the MicroVax 3400 series of machines?
>
> [...]
>
> get some pure BSD goodness on it again.
For VAXen you don't want 4.4BSD, you want 4.3BSD-Quasijarus, especially if you
want pure. Unfortunately, I haven't got the KA640 (3300/3400) support in there,
just KA650 (3500/3600) and KA655 (3800/3900). It would be trivial to add,
though, it just needs to be taught to look at the SIE in addition to the SID,
recognise the KA640, and don't try to touch the non-existent B-cache. This
wouldn't give you support for the on-board DSSI and Ethernet, but it'll run
with your Q-bus devices.
MS
In article by Milo Velimirovic:
> Warren,
> The license didn't survive the digestification process on the list --
> Would you be kind enough to send me a copy of the ancient-source.pdf
> directly or a URL to it?
>
> Thanks,
> Milo
Here it is,
Warren
http://www.tuhs.org/Archive/Caldera-license.pdf
All,
Amazing news. I have been negotiating with Caldera to release the
Ancient UNIX under a BSD-style license. Well, they got it done faster
than I expected. See attached license.
I'll start removing the username/password stuff on the Unix Archive soon.
Warren
On Jan 20, 18:45, Jochen Kunz wrote:
>
> Ahhhhh! My PDP 11 has this M8192 board with FPU but without ROMs...
> I thought that this is the "original" 11/73 CPU. But on this PDP is
> nothing "original". The BA23 was a MV II, the CPU was EPayed, the RAM
> board was given to me by a friend. (Many PC/XTs had to donate there RAM
> chips to fill it.)
About the best use I can think of for a PC/XT :-)
> I found the console SLU at the scrap yard, the Dilog
> ESDI controller was EPayd (in England BTW ;-) ) ... and I am still
> looking for a ROM card...
If you can find an MRV11-D (to put MXV11-B ROMs into) or an MVX11-B, that
would be the best option (and the only ones DEC supported). However, it
should be possible to put the code from MXV11-B ROMs into several 24-pin
2Kx8 EPROMs (2716 or equivalent), and put the EPROMs into a BDV11.
However, you'd want to modify the BDV11 for 22-bit operation (that's ECO
005).
> > The BA23 was only rated for one hard disk and either a TK50 or an
> RX50,
> I know. I once saw a MV II with a second RD54 in an external case. There
> was a real mess of wiring to get it and the internal RD54 work together
> on one RQDX3. Puting the TK50 out of the BA23 and mounting the second
> RD54 in the BA23 would have been much simpler. But not the DEC way of
> live. ;-)
Because old hard drives take a lot of current. The PSU and wiring loom
won't take a full backplane and two hard drives.
I did one of mine a different way. I have a BA11-N with the backplane
modified to be 22-bit. In it is an RQDX2 (or an RQDX3, depending on what's
been shuffled around this month), with a 50-way ribbon cable going to a DEC
box (used to be a TKZ50) which has a PSU, a hard drive, and an RX50. In
the box is also a small PCB I made to do the job of the distribution board
found in a BA123. Also in the BA11-N backplane is a modified BDV11, with a
pair of 28-pin EPROM sockets which normally hold microPDP-11/23 boot ROMs.
--
Pete Peter Turnbull
Network Manager
University of York
On Jan 19, 22:35, jkunz(a)unixag-kl.fh-kl.de wrote:
> Only the first 3 slots are Q/CD. The other 5 slots are Q/Q in serpentine
> bus grant wiring. Tony said that the memory should be in the first
> slot.
Lothar later said this is an H9276-A. That's a straight backplane, all
Q22/CD. It seems he has a BA11-S not a BA23 :-)
BTW, DEC normally recommended all comms and network cards go after the
memory, tapes next, then disks.
> AFAIK some 11/73 labeld boxen where sold with a 11/83 CPU in the first
> slot and the memory in the second.
It's the order of the boards (and the boot ROMs) that make it 11/73 or
11/83, not the circuit board. Though original 11/73s are 15MHz and
original 11/83s are 18MHz.
> AFAIK a 11/83 CPU can use QBus and (or?) PMI memory. If it is
> configured with QBus memory it is calld a "11/73". But keep in mind
> that there is a "real" 11/73 CPU (M8192 = KDJ11-A).
That's a dual-height board, CPU only, with no boot ROMs, LTC, or SLUs. It
was only sold as an OEM product or as an upgrade to 11/03 or 11/23 (not
11/23+ or microPDP-11/23) systems. Whilst it is a "real 11/73", it's no
more "real" than any other :-)
> Hmm. Are there Q/CD only BA23 backplanes?
No. There are straight Q/CD and serpentine Q/Q backplanes of the same size
but they're only used in other boxes (like BA11-N and BA11-S) or sold as
OEM units.
> I never saw a front panel like that, but your assumption sounds right.
> All my front panels have only one disk write protect / online switch.
The BA23 was only rated for one hard disk and either a TK50 or an RX50, but
the BA123 (which uses the same panels) was rated for up to 4 MSCP devices.
That's why the WP and ONLINE switches and LEDs are on a subassembly, so
you can add another one.
--
Pete Peter Turnbull
Network Manager
University of York
lcc is not public-domain nor GPL, but it is freely available for `personal
research and instructional use,' and in general there is no restriction as
long as you don't redistribute it for profit or resell it.
Here's the official scoop, as inscribed in ./CPYRIGHT in the lcc 3.6
distribution. It is possible that the terms have changed for newer
versions; I haven't been keeping track.
----
The authors of this software are Christopher W. Fraser and
David R. Hanson.
Copyright (c) 1991,1992,1993,1994,1995 by AT&T, Christopher W. Fraser,
and David R. Hanson. All Rights Reserved.
Permission to use, copy, modify, and distribute this software for any
purpose, subject to the provisions described below, without fee is
hereby granted, provided that this entire notice is included in all
copies of any software that is or includes a copy or modification of
this software and in all copies of the supporting documentation for
such software.
THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED
WARRANTY. IN PARTICULAR, NEITHER THE AUTHORS NOR AT&T MAKE ANY
REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY
OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.
lcc is not public-domain software, shareware, and it is not protected
by a `copyleft' agreement, like the code from the Free Software
Foundation.
lcc is available free for your personal research and instructional use
under the `fair use' provisions of the copyright law. You may, however,
redistribute lcc in whole or in part provided you acknowledge its
source and include this CPYRIGHT file. You may, for example, include
the distribution in a CDROM of free software, provided you charge only
for the media, or mirror the distribution files at your site.
You may not sell lcc or any product derived from it in which it is a
significant part of the value of the product. Using the lcc front end
to build a C syntax checker is an example of this kind of product.
You may use parts of lcc in products as long as you charge for only
those components that are entirely your own and you acknowledge the use
of lcc clearly in all product documentation and distribution media. You
must state clearly that your product uses or is based on parts of lcc
and that lcc is available free of charge. You must also request that
bug reports on your product be reported to you. Using the lcc front
end to build a C compiler for the Motorola 88000 chip and charging for
and distributing only the 88000 code generator is an example of this
kind of product.
Using parts of lcc in other products is more problematic. For example,
using parts of lcc in a C++ compiler could save substantial time and
effort and therefore contribute significantly to the profitability of
the product. This kind of use, or any use where others stand to make a
profit from what is primarily our work, requires a license agreement
with Addison-Wesley. Per-copy and unlimited use licenses are
available; for more information, contact
J. Carter Shanklin
Addison Wesley Longman, Inc.
2725 Sand Hill Rd.
Menlo Park, CA 94025
415/854-0300 x2478 FAX: 415/614-2930 jcs(a)aw.com
-----
Chris Fraser / cwfraser(a)microsoft.com
David Hanson / drh(a)cs.princeton.edu
$Revision: 1.3 $ $Date: 1996/09/30 13:55:00 $
On Jan 20, 12:44, jkunz(a)unixag-kl.fh-kl.de wrote:
> On 19 Jan, Pete Turnbull wrote:
>
> > Not the 54- number, that's only the PCB part. The backplane itself has
> >a model number; for a BA23 it should be H9728-A.
> "H9728-A"? The sticker on the two BA23 backplanes I have here says
> "H9278-A".
Typo.
--
Pete Peter Turnbull
Network Manager
University of York
On Jan 20, 2:05, lothar felten wrote:
> mine is about 40 inch high, 19 inch wide and
> as deep as
> the rl02 is. the "microcomputer interfaces
> 1983-84" shows
> some pictures of boxes: is might be the
> BA11-S
Sounds like you have what was a standard PDP-11/23 (or maybe 11/23+) system
in an office-type cabinet (H9642 or equivalent), with an RL02 in the top, a
stiffener panel, BA11-N or BA11-S box, a second RL02, and two blanking
plates at the bottom. Sometimes people moved the second RL02 down 3U and
put one blanking plate or an expansion box between the BA11 and the RL02.
As far as I remember, the only significant difference between a BA11-N and
a BA11-S is an uprated power supply, and a 22-bit backplane instead of an
18-bit one (but you can upgrade the 18-bit ones).
> on the backplane i found H9276-A.
> i don´t know what -A means, but it should be
> a Q22/CD
> so no serpentine?
Correct. There is a very similar backplane H9275-A which is all
serpentine, but not in a standard 11/23 box, as far as I remember. H9276-A
is for a BA11-S. BA11-N uses H9273.
> now i´ve got the numbers here:
> CPU: M8190-AE KDJ11-B
> MEM: M7551-CC MSVC11-QC
> RL02: M8061
> DELQA: M7516
> RQDX3: M7555
> DEQNA: M7546
OK. That should be fine, so long as there are no gaps in the A/B slots
(left side of backplane as you look into it from the back of the machine)
between the cards.
The original 11/23+ probably had an RQDX1 or RQDX2, and possibly an RLV11,
and certainly different memory.
> hmmm, this is really confusing, since i have
> AE can it take an FPU? maybe it has a fpu? what
> does the fpu look like?
The -AE means it's a later board, should be 18MHz, and should not only be
FPU-capable, it should actually have the FPJ-11 chip on it. -AD is the
same thing without the FPJ-11 fitted (it still does floating point ops,
just more slowly). If not, you'll probably find it easier to get a
replacement board with an FPU already on it, rather than get the FPU chip
on it's own.
> > However, the biggest difference between 11/83 and 11/73 is whether
> > memory is used as QBus memory, or PMI memory, which is faster. the
>
> so i should put in first memory then cpu.
To get the best performance, yes. It won't double the speed, or anything
like that, but it will go a bit faster.
> well it´s a BA11-S i suppose by now.
If it's an H9276 backplane and H7861 PSU, yes.
> a weird pdp.
Not quite factory-standard :-) But none the less good.
--
Pete Peter Turnbull
Network Manager
University of York
On Jan 19, 20:47, lothar felten wrote:
> hi there!
>
> well the pdp was once a pdp 11/23+ so
> enclosure and backplane should be
> the same as a 11/23 (ba 23).
If I were to be really picky, I'd say you meant microPDP-11/23. 11/23-plus
would mean a BA11-S enclosure with a different type of backplane :-)
> backplane should
> be Q22/CD configuration, but
> i´ll open the box and look for the 501-
> number to be sure.
Not the 54- number, that's only the PCB part. The backplane itself has a
model number; for a BA23 it should be H9728-A.
In an H9728-A the top three slots are Q22/CD-interconnect, and the rest are
Q22/Q22 serpentine (the 11/23-plus backplanes are different). When I
replied to your earlier email I assumed you just gave the order of the
boards, not the layout. The layout should be (reverse the positions of CPU
and memory if you wish):
---------KDJ11-B-CPU---------
---------MSV11-memory--------
------------RLV12------------
----RQDX3---- ----TQK50----
empty ----DEQNA----
I'm guessing you have a single memory board, probably an MSV11-Q (M7551),
and an RLV12 (M8061, one quad board) rather than an RLV11 (two quad boards)
-- if not, that makes a difference to the layout. I'm also guessing at a
DEQNA (M7504) rather than any other Ethernet controller, but it makes no
difference to the placement, so long as it's a dual-height board. If you
added another dual-height board it would go under the RQDX3 (M7555), the
next would go under that, and the next under the DELQA, etc. The
arrangement of the slots after the first three is called "serpentine" or
occasionally "zig-zag".
> on the back there
> is a sticker saying this is a 11/73. the
> cpu-board is a 11/83.(i´ll pass
> the number too).
All the KDJ11-B processors, whether 11/73 or 11/83, use the same printed
circuit board and module number. There were some differences about whether
an FPU could be fitted (due to an error on the original boards); those that
would not take an FPU were only sold as KDJ11-BC and all had 15MHz clocks.
Others with 15MHz clocks were sold as KDJ11-BB (upgradeable but FPU not
fitted). There are also some with 18MHz clocks, these were sold as
KDJ11-BE, -BF, or higher. Normally an 11/83 has a KDJ11-BE or higher
suffix. Early 11/73 are 15MHz. Just to add to the confusion, the -Bx
suffix actually refers to the EPROMs on the board, not the clock speed or
the FPU. The *only* difference between a normal KDJ11-BE or -BF or -BH is
the firmware in the EPROMs.
However, the biggest difference between 11/83 and 11/73 is whether the
memory is used as QBus memory, or PMI memory, which is faster. All of the
KDJ11-B boards can use PMI memory. Beware, not all quad memory boards are
PMI-capable, but all the 1MB and bigger ones that I can think of are.
> do all 11/83 use PMI ?
Yes. They will work with QBus memory instead (and if you put a PMI board
after the processor instead of before it, it will run as normal QBus
memory)
but then what you have is effectively an 11/73, not an 11/83.
> but the memory seems to work, or has
> the cpu board some memory on it?
No, there's no memory on the CPU board, but the memory you have is running
as QBus memory.
> when i picked up the box they booted it, i
> suppose this configuration was the
> way they used it there and should have
> worked.
> the RD54 controller has a 50pin ribboncable
> wich goes to a small board (wich
> was hanging on the backside) and a small
> frontpanel (from a 11/83 or 73) was
> hanging on it.
Literally "hanging"? Not fixed to the front of the BA23? Is this actually
a floor-standing (or possibly rack-mounting) BA23 with space for a TK50 and
a drive unit, or a rackmount BA11-S or BA11-N chassis with no space for
drives?
> it looks like
>
> *************
> * *'''''* O is a round hole (to hold a batch?)
> * O *'''''* '' is a big hole (power switch i suppose)
> * *'''''*
> *************
> * X B * X = run on/off ?(green led) B = reset ?
> * X X * X = write protect (red) X = online(green) for disk 0 ?
> * X X * X = write protect (red) X = online(green) for disk 1 ?
> *************
> X is a switch with led B is a button with led
> i never saw a pdp with this frontpanel
Neither have I. DEC used pushbuttons for the disk controls on microPDP-11
panels. Each section is separate, though; it sounds like someone has
replaced the pushbuttons or used third-party sub-panels. The round hole
(if this is an original DEC panel) is for the badge that says whether it's
a microPDP-11/23, microPDP-11/73, microPDP-11/83, microPDP-11/53, etc. The
rectangular hole is for the power switch in a BA23 or BA123 cabinet.
--
Pete Peter Turnbull
Network Manager
University of York
hi there!
well the pdp was once a pdp 11/23+ so
enclosure and backplane should be
the same as a 11/23 (ba 23). backplane should
be Q22/CD configuration, but
i´ll open the box and look for the 501-
number to be sure. on the back there
is a sticker saying this is a 11/73. the
cpu-board is a 11/83.(i´ll pass
the number too). do all 11/83 use PMI ? but
the memory seems to work, or has
the cpu board some memory on it?
when i picked up the box they booted it, i
suppose this configuration was the
way they used it there and should have
worked.
the RD54 controller has a 50pin ribboncable
wich goes to a small board (wich
was hanging on the backside) and a small
frontpanel (from a 11/83 or 73) was
hanging on it. it looks like
*************
* *'''''* O is a round hole (to hold a
batch?)
* O *'''''* '' is a big hole (power
switch i suppose)
* *'''''*
*************
* X B * X = run on/off ?(green led)
B = reset ?
* X X * X = write protect(red led) X
= online(green led) for disk 0 ?
* X X * X = write protect(red led) X
= online(green led) for disk 1 ?
*************
X is a switch with led B is a button with led
i never saw a pdp with this frontpanel, and
since there is nothing written on it,
i tried to compare with a picture found on
the web, but i´m not sure if i´m right.
can someone tell me if i´m right ?
i asked those guys from where i picked up the
box, but they told me that the last guy
using the pdp left some years ago, and in
1999 they just powered it off. this explains
also the small paper sticking on the pdp that
showed how to login and shutdown the box.
root password is written on it *g*.
tomorrow i´ll open the box again.
thanks for your fast response.
-- lothar
FWIW, I don't know about the tape error, but
that layout looks OK apart
>from the fact that if it's an 11/83, the
memory shold be in the first slot
and the CPU in the second. The essential
difference between an 11/73 and
an 11/83 is that the 11/83 uses PMI memory.
Assuming your backplane is the
right one, in a BA23 or BA123 box, and that
your memory is a single 4MB
board, you should swap them round, otherwise
what you actually have is an
11/73.
I assume your RD54 controller is a genuine
DEC RQDX3, so it's in the right
place. It's possible you have an old version
of the firmware on it, but it
should still work even if you do.
all the planes in the backplane are genuine
dec parts.
--
Pete
What enclosure? BA23? If yes you have empty
slots between the cards as
this box has 3 Q/CD slots on top and 5 Q/Q
slots below. Have a look at
the QBus HOWTO at
http://vaxarchive.sevensages.org/
--
tschuess,
Jochen
On Thu, Jan 17, 2002 at 08:36:05AM +0100, Lars Brinkhoff wrote:
> Hello,
>
> Is anyone using GCC to compile code for the PDP-11?
on the PDP or cross-compiled? (will gcc run under 2.11?)
--
Aaron J. Grier | "Not your ordinary poofy goof." | agrier(a)poofygoof.com
"Making people dance so hard their pants almost fall
off is kind of fun." -- David Evans
Johnny,
I have access to both RT-11 and RSTS/E systems here. I would be happy to
give the testing a shot. My preference would be RT first, and then if you
get no other takers, RSTS.
Regards,
Steve
> -----Original Message-----
> From: Johnny Billquist [SMTP:bqt@update.uu.se]
> Sent: Saturday, January 19, 2002 10:13
> To: SHOPPA(a)trailing-edge.com
> Cc: PUPS(a)minnie.tuhs.org
> Subject: Re: [pups] Re: GCC
>
> On Sat, 19 Jan 2002 SHOPPA(a)TRAILING-EDGE.COM wrote:
>
> > Johnny Billquist <bqt(a)update.uu.se> writes:
> > > DECUS C might be a better starting point.
> >
> > DECUS C is kind-of a funny case. Whereas most C compilers are
> > traditionally maintained and distributed as C source code, DECUS C
> > is distributed and maintained in PDP-11 assembly language.
>
> True.
>
> > For other C compilers, a significant milestone was when they were
> > rewritten in C and compiled themselves. DECUS C is the odd guy out
> because
> > it never tried to reach this milestone. In some sense this is a good
> thing,
> > because it lets you build it on a machine without any access to any C
> compiler.
>
> Which definitely is a good thing in this case. Since most systems don't
> have a C compiler anyway, the first compiler have to get down there
> someway, and MACRO-11 is the only language you *know* exist.
>
> I'm soon done with a cleanup of DECUS-C by the way. I've tried to collect
> all the different versions I can find, and incorporated my own fixes as
> well. This version will support I/D space correctly in RSX (which no other
> version except my in-house hacks have done), will have a working profiler
> again, and also supports RMS and DAP. Fun fun...
> I'm testing it right now, and most things looks like they are working like
> a charm.
> However, if someone have plenty of time, and an RSTS/E or RT-11 system
> around, I'd sure appreciate some help. I've tried to keep those parts
> up-to-date as well, but I cannot test, or fix broken things.
>
> This compiler have been a mess for many years now... About time it got
> some cleanup.
>
> Oh. And I don't know if Allan Baldwin (sp?) have some extra hacks in for
> his IP-stack, and I haven't even investigated.
> Anyone know?
>
> Johnny
>
> Johnny Billquist || "I'm on a bus
> || on a psychedelic trip
> email: bqt(a)update.uu.se || Reading murder books
> pdp is alive! || tryin' to stay hip" - B. Idol
>
> _______________________________________________
> PUPS mailing list
> PUPS(a)minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/pups
On Jan 19, 12:43, lothar felten wrote:
> i don´t know if this is a hardware (bus?)
> error, or maybe the tape is bad.
> the tapes i use are unused original dec TK50
> tapes, i made several ones, because i thought
> it might be a tape error, but
> all tapes are the same.
>
> hardware:
> PDP-11/83, 4megs of ram, TK50, two RD54
> (maxtor), two RL02 disks.
> qbus cards (top to bottom):
> *cpu (quad)
> *memory (quad)
> *controller for RL02 disks (quad)
> *controller for RD54 disks (double)
> *controller for TK50 (double)
> *network controller (double)
FWIW, I don't know about the tape error, but that layout looks OK apart
from the fact that if it's an 11/83, the memory shold be in the first slot
and the CPU in the second. The essential difference between an 11/73 and
an 11/83 is that the 11/83 uses PMI memory. Assuming your backplane is the
right one, in a BA23 or BA123 box, and that your memory is a single 4MB
board, you should swap them round, otherwise what you actually have is an
11/73.
I assume your RD54 controller is a genuine DEC RQDX3, so it's in the right
place. It's possible you have an old version of the firmware on it, but it
should still work even if you do.
> i didn´t find a kind of terminator, but i
> didn´t change the order of the
> cards since i picked the box up.
> there are no empty slots between the cards,
> and i´m not sure if the Qbus
> need a special terminator.
There normally isn't an extra terminator in an 11/73 or 11/83, unless you
add an expansion backplane.
--
Pete Peter Turnbull
Network Manager
University of York
Johnny Billquist <bqt(a)update.uu.se> writes:
> DECUS C might be a better starting point.
DECUS C is kind-of a funny case. Whereas most C compilers are
traditionally maintained and distributed as C source code, DECUS C
is distributed and maintained in PDP-11 assembly language.
For other C compilers, a significant milestone was when they were
rewritten in C and compiled themselves. DECUS C is the odd guy out because
it never tried to reach this milestone. In some sense this is a good thing,
because it lets you build it on a machine without any access to any C compiler.
Tim.
hi there,
maybe someone can help me installing 2.11BSD
on a PDP-11/83.
my problem:
the standalone disklabel-programm stops when
displaying the MSCP disk
information.
in the console ODT i write/see:
BOOT MU0
Starting system from mu0
83Boot from tms(0,0,0) at 0174500
:tms(0,1)
disklabel
Disk? ra(0,0)
d(isplay) D(efault) m(odify) w(rite) q(uit)?
d
type:MSCP
disk:RD54
flags:
bytes/sector: 512
sectors/reack: 17
tr
and then it just stops, right after "tr", but
the RUN led stays on.
when i try to disklabel a RL02 disk i get
invalid disk (for rl(0,1)) or a
system stop (for rl(0,0) with RUN led off).
i don´t know if this is a hardware (bus?)
error, or maybe the tape is bad.
the tapes i use are unused original dec TK50
tapes, i made several ones, because i thought
it might be a tape error, but
all tapes are the same.
hardware:
PDP-11/83, 4megs of ram, TK50, two RD54
(maxtor), two RL02 disks.
qbus cards (top to bottom):
*cpu (quad)
*memory (quad)
*controller for RL02 disks (quad)
*controller for RD54 disks (double)
*controller for TK50 (double)
*network controller (double)
i didn´t find a kind of terminator, but i
didn´t change the order of the
cards since i picked the box up.
there are no empty slots between the cards,
and i´m not sure if the Qbus
need a special terminator.
i made a TK50 boottape on my DECstation
5000/200. i got the software from
the pups archive, and made the tape with the
"maketape" program.
any idea welcome.
regards,
--lothar
I got Dennis' sixth edtion compiler to compile not long ago.
It's definitly not ANSI C, in fact it's not quite K&R C, but
I really like coding in it. My advice would be to start there.
Just check out the chapter on precidence parsing in the dragon book
before you work on the compiler.
Brantley Coile
In article by Mark E. Mallett:
> Somebody pointed me at this URL:
> http://minnie.tuhs.org/pipermail/pups/2000-January/000152.html
>
> and others where the question of the UNIX-based mallet was being
> discussed. It's me.. some time in the mid-80s I had submitted a
> number of entries to the calendar file and I had jokingly suggested
> that my birthday could also be included. And apparently it was.
>
> I enjoy seeing it pop up every August. I notice that some calendar
> files now actually explain it, which I think is a pity :-)
> --
> Mark E. Mallett | http://www.mv.com/users/mem/
> MV Communications, Inc. | http://www.mv.com/
> NH Internet Access since 1991 | (603) 629-0000 / FAX: 629-0049
I think a few people are going to be relieved to know the answer.
Can you tell us which versions of the calendar file actually explain
it, as I've not seen them.
Thanks for this,
Warren
I have been playing with a Qbus to IDE drive adapter for a while, and
with some free time this Christmas, I got around to working on it and
documenting it.
You can find information here: http://www.chd.dyndns.org/qbus_ide/
In summary, I have designed and built a Q22-Bus to ATA disk adapter and
written drivers for 2.11BSD on my microPDP-11/73. The adapter is PIO
only (for now) and the driver only works with LBA capable disks.
I posted this to the NetBSD/vax mailing list last week. If there is
sufficient interest, we might be able to get boards made. Someone is
writing a NetBSD driver and I have a 2.11BSD driver already.
-chuck
All,
Aharon Robbins just passed this on to me. Maybe some
of you are interested in this.
Warren
----- Forwarded message from Aharon Robbins -----
From: Aharon Robbins <arnold(a)skeeve.com>
To: wkt(a)tuhs.org
Subject: would any of this be useful to TUHS?
I am cleaning out my attic. What does that mean?? It means a lot of
AT&T documentation and software needs to find a home to avoid ending
in the dumpster. I have documentation and sfotware for the 6300+ and the
3B2. Some of it still in the original shrink-wrap.
And yes, this is on topic. I also have quite a bit of software and
documentation for the Unix-PC as well. Much of this still in the
original packaging. OS, Development sets, utilities. everything must
go. I also have three complete Unix-PC's and two without disks or
heads but with functional motherboards. At least all of this stuff
was functional the last time I actually turned any of them on. I have
one that I just fired up (that's already been claimed) to test it and
it works fine, so i assume the same is true of the others. I would
probably be willing to let all of them go at this point. Nice machines,
but my PDP's and VAXen need the room.
Now the only string. I will not ship any of this. it is located in
NEPA in the Scranton/Wilkes-Barre area and must be collected. And it
must be soon.
One person can claim it all and then ship it to others if they wish,
or people can email me asking for particular packages. First come,
first served. If you know of any other places where there might be
interest in the 3B2 or 6300+ stuff feel free to forward this message.
All the best.
bill
----- End of forwarded message from Aharon Robbins -----
But there's nothing like the rush of warmed, slighly phenolic air from
the cooling fans of an old minicomputer - I've noticed the furnace
doesn't kick on when the 11/34 is running. (Of course, when I flip on
the RM02s, the breaker trips....)
-- Ian
-----Original Message-----
From: Derrik Walker v2.0 [mailto:firebug@apk.net]
Sent: Monday, November 12, 2001 11:03 AM
To: Ian King
Cc: tuhs(a)tuhs.org
Subject: Re: [TUHS] HP 712& v6 or v7
On Monday, November 12, 2001, at 01:31 PM, Ian King wrote:
> Derrik, you're missing the point: what's the fun of doing it the easy
> way? :-) Seriously, though, I think you'd have a couple of serious
> problems: the assembly language components (which are not
> inconsiderable in V6) would need to be rewritten, and then there's
> also the question of whether you could find a sufficiently
> "undisciplined" C compiler to handle pre-ANSI C, to build the rest of
> the system.
>
Actually, I like playing with emulators - they use a LOT less power than
real computers :)
HP-UX comes with a REAL K&R c compiler that wont handle ANY ANSI stuff.
It's used to rebuild the kernel, but you can use it to build K&R C
programs too. That should be usable for the kernel C routines and
utilities. But as you pointed out, the assembly stuff you have to be
rewritten. Also, you'd have to deal with disk and tty drivers.
firebug(a)apk.net
http://junior.apk.net/~firebug
------------------------------------------------------------------------
---------------------------
Worriers may get all the glory, but it's engineers that build societies.
-- B`Elanna Torres, "Star Trek: Voyager"
Derrik, you're missing the point: what's the fun of doing it the easy
way? :-) Seriously, though, I think you'd have a couple of serious
problems: the assembly language components (which are not inconsiderable
in V6) would need to be rewritten, and then there's also the question of
whether you could find a sufficiently "undisciplined" C compiler to
handle pre-ANSI C, to build the rest of the system.
-- Ian, running UNIX 6th Ed. on a PDP-11/34a
-----Original Message-----
From: Derrik Walker v2.0 [mailto:firebug@apk.net]
Sent: Monday, November 12, 2001 8:29 AM
To: tuhs(a)tuhs.org
Subject: Re: [TUHS] HP 712& v6 or v7
On Tuesday, November 6, 2001, at 07:34 PM, Paul Hart wrote:
> On Sun, 4 Nov 2001, Mike Allison wrote:
>
>> Anyone tried/interested or successful in getting a copy of v6 or v7
>> up on a HP 9000 712?
>
> Are you sure it was ever ported to PA-RISC? As far as I am aware,
> PA-RISC
> (and the HP 9000 712) weren't developed until long after the days of
V6
> and V7 UNIX.
Wouldn't it be easier to just get the PDP-11 emulator from
gatekeeper.dec.com and compile it for HP-UX or Linux on the 712? I've
compiled it on Solaris 8, Linux, and Mac OS X, so it should compile just
fine under HP-UX.
Also, as far as I am aware ( and keep in mind, I am an HP-UX system
admin. ) HP-UX has only ever been System V. You can run HP-UX, Linux, or
NetBSD on a HP-9000/{800,700}.
- Derrik
firebug(a)apk.net
http://junior.apk.net/~firebug
------------------------------------------------------------------------
---------------------------
They seem to have learned the habit of cowering before authority even
when not actually threatened. How very nice for authority. I decided
not
to learn this particular lesson.
-- Richard Stallman
_______________________________________________
TUHS mailing list
TUHS(a)minnie.tuhs.org http://minnie.tuhs.org/mailman/listinfo/tuhs
Hi guys,
I'm working on a UNIX time-line database.
Its pretty basic atm - I've yet to hunt down the majority of SysV vendors
out there.
I'm currently looking for early releases, and V6/V7 offshoots (such as
PWB).
The data I'm looking for is vendor, strain, version, and date of release
(such as AIX, version 4.3.2, released 05/10/1998, SVR4, IBM etc)
Does anyone know of any sites that would give that kind of information for
the V6/V7 and earlier releases?
The database is currently at http://www.unixware.org.uk/test.php. There
isn't much to look at atm, I've yet to code the PHP interface, thought it
would be best to complete the database first though :-)
I'm hoping that, one day, it will contain a complete listing of all UNIX
releases, clones, and offshoots... well, I can dream ;-)
Regards,
Paul.
