I've assembled some notes from old manuals and other sources
on the formats used for on-disk file systems through the
Seventh Edition:
http://www.cita.utoronto.ca/~norman/old-unix/old-fs.html
Additional notes, comments on style, and whatnot are welcome.
(It may be sensible to send anything in the last two categories
directly to me, rather than to the whole list.)
There were ports of PCC to the 8086, Z8000, and 68000 done by
MIT's Laboratory for Computer Science. This might be a more
historically correct place to start.
Jonathan Engdahl:
Consider lcc, the Princeton C compiler. It's much smaller than gcc, and ANSI
compliant.
lcc's a good compiler; it has become cc in my own peculiar Ancient UNIX
environment. But my environment is on VAXes, not PDP-11s; the lcc I use
probably cannot be compiled to a core compiler binary of less than about
180KB, of which 136KB is text, and that is without any real code generators.
(For those who know lcc: I am using a slightly-hacked-up lcc 3.6; the
180KB binary includes just the symbolic and null code generators, not
the enormous one I ended up with for the VAX.)
On the other hand, it is probably easier to split lcc into overlays or
multiple passes to make it fit on a PDP-11 than to do the same to gcc;
and lcc works fine as a cross-compiler. And it's a good solid ANSI
compiler; enough so that it is a little annoying to use it on heritage
code (it grumbles, correctly, if a function returns no value and wasn't
declared void), and helpful or very painful (depending on your point of
view) when used on really old code that is sleazy about mixing types of
pointers in procedure arguments, or reusing one structure as part of another,
or the like. I had an interesting time a few months ago getting an old
version of tbl to compile cleanly and produce correct results under lcc;
the program contained some ancient constructs that are truly remarkable
to look back on, especially for those of us who started out programming
that way and learned better the hard way ...
If I were going to work with PDP-11s, I would probably use lcc as a
cross-compiler myself, after writing or snitching a code generator of
course.
Norman Wilson
Hi,
rsync doesn't seem to work anymore for some time, now, any idea ?
$ rsync -avz --password-file=.passwd au2496@minnie.tuhs.org::UA_Root .
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(151)
same results w/ rsync -avz minnie.tuhs.org::UA_Root .
Cyrille.
--
Cyrille Lefevre mailto:cyrille.lefevre@laposte.net
In article by Dave Horsfall
> On Thu, 18 Apr 2002, Wolfgang Helbig wrote
>
> > I tried the latest simulator from Bob Supnik, Simh V2.9-6.
> > It simulates DZ11 multiline controllers. Are they supported in UNIX V6.
>
> Not natively, no. Back at Uni of NSW, we did several drivers, getting
> better each time, but I think the sources are lost to antiquity (unless
> someone happens to have those old tapes).
Would AUSAM have any DZ11 drivers? There are several AUSAM tapes in
the Unix Archive, and AUSAM was a deriative of V6.
How about
PDP-11/Distributions/unsw/1/record0.gz dz.c 12999 1978 01 24
PDP-11/Distributions/unsw/4/record0.gz dz.c 13416 1979 08 01
PDP-11/Distributions/unsw/6/record0.gz dz.c 6532 1979 10 30
PDP-11/Distributions/unsw/81/record0.gz dz.c 4761 1979 12 20
PDP-11/Distributions/unsw/83/record0.gz dz.c 4761 1979 08 22
PDP-11/Distributions/unsw/92/92.gz dz.c 7457 1981 09 16
Cheers all,
Warren
> I guess the closest would be the DH-11
The DZ and DH are totally different beasts. The DZ had a 256 word input silo
and interrupt per output character, while the DH was DMA.
There is certainly support for DZ's in V7. It shouldn't be too hard to back port
it to V6
Hi
I tried the latest simulator from Bob Supnik, Simh V2.9-6.
It simulates DZ11 multiline controllers. Are they supported in UNIX V6.
If not, which of the supported ones are closest to DZ11, so I would write
a driver for them.
TIA
Wolfgang
Since I'm no longer employed, I don't have access to any Unix or Windows
boxes to run a PDP/11 emulator. I do have my home computer: a G4 Mac
running MacOS 9.1. Are there any precompiled PDP/11 emulator binaries out
there? I've found a nice PDP/8 emulator, but so far the PDP/11 has eluded
me. I'd like to be able to boot up PDP/11 Unix when the nostalgia urge hits
me.
Oh, BTW, if you know of any jobs in the New York City (NY, NY USA) area for
a 20-year veteran system administrator, I'd love to hear from you!
--
Frank
"They haven't got Brains, any of them, only grey fluff that's blown into
their heads by mistake, and they don't Think."
* Eeyore, "The House at Pooh Corner"
If you want to play with Harti's p11
running 2.11BSD, you can telnet to
madison.onespeeddave.com on any of
ports 10001 through 10006.
I'll give you an account if you
want one. Just tell me what
userid and initial password you
want. Also tell me what you'll do
with your account.
This flavor of the emulator is
running without a tape drive and
a network interface card.
FWIF, madison is a 96MB P2-333 running NetBSD.
Paul,
> Bleh, sorry for the blank post... notes went schitzo....
*smile*
> If MS can release WinCE source, then they would probably do
> the same for XENIX.... both PDP/11 and the x86 version perhaps...
> Its not like we want the source... just a tape image would do me :)
> Perhaps there is someone in MS who knows of XENIX's existance and
> can help.... I'll have a word with a friend of mine who works
> there :)
Yeah, I agree. I personally think MS would release Xenix, as it no
longer has any commercial value whatsoever to them. The hardest part
might be finding people within who know about it, and who can point
us in the right (legalese) direction. Once MS signs off on it, the
people at SC(O)aldera won't have a problem with releasing the tapes.
Cheers,
Fred
InterNetworking en Network Security Consultant
MicroWalt Corporation (Netherlands), Korte Heul 95, 1403 ND BUSSUM
Phone +31 (35) 6980059 FAX +31 (35) 6980215 http://WWW.MicroWalt.NL/
Dit bericht en eventuele bijlagen is uitsluitend bestemd voor de
geadresseerde. Openbaarmaking, vermenigvuldiging, verspreiding aan
derden is niet toegestaan. Er wordt geen verantwoordelijkheid
genomen voor de juiste en volledige overbrenging van de inhoud van
dit bericht, noch voor de tijdige ontvangst ervan.
