Rico Pajarola <rp(a)servium.ch> wrote:
> I installed 4.3-quasijarus on simh [...]
> I have been unable to boot it directly from it's 'own'
> filesystem.
>
> here's what I see, complete transcript at the end
> > >>>boot dua0
> > (BOOT/R5:0 DUA0)
> >
> >
> >
> > 2..
> > -DUA0
> > HALT instruction, PC: 00000C1A (MOVL (R11),SP)
My ability to help you here will be limited because you are using simh rather
than a real VAX. The real KA655 console ROM does not issue halt messages like
the above, its halt message have a different form (the one prescribed by DEC
STD 032-0, VAX Architecture Standard). The last message above does not exist on
any real VAX made by DEC.
> that's obviously not what I want. I tried all combinations of
> installboot and disklabel -B I can think of, both in netbsd and
> quasijarus, and all lead to the same result.
>
> Can anybody tell me the exact incantations necessary to install
> the bootblocks for quasijarus0a [...]
This seems like a simh problem, or, more probably since you can boot That Other
OS successfully, a problem with your installation of 4.3BSD-Quasijarus0a masked
by a simh problem. You've got a halt inside VMB that happened after VMB had
successfully opened the boot device but before it accepted a valid bootblock.
What happens on a real KA655 is as follows: the console copies VMB from the
EPROM to RAM and transfers control to it, which is accompanied by the display
of 2.. on the console and on the CPU module LEDs. At that point the VAX is
unhalted, i.e., the RUN indicator on the front panel lights up. VMB thus runs
as user code and tries to perform the bootstrap. As VMB successfully opens the
boot device using its built-in drivers, it displays the device name in VMS
format on the console. Then if it finds and accepts a valid bootblock it
displays 1.. on the console and on the CPU module LEDs. Finally it transfers
control to the bootblock accompanied by 0.. display. If something goes wrong
and VMB gives up, it prints its own error message on the console and then
executes a HALT instruction to return to the console prompt. The HALT
instruction halts the VAX (the RUN indicator on the front panel goes out) and
invokes the console, which prints the halt message followed by the >>> prompt
as prescribed by DEC STD 032-0.
It looks like you are seeing VMB fail for some reason and halt, giving you the
(not compliant with DEC STD 032-0) halt message from simh. However, you are not
seeing VMB's error message which on a real KA655 will always appear before the
halt message from the console. This is a simh problem, it obviously does not
fully and properly emulate the real KA655 here. I cannot help you past this
point as I only support real VAX hardware. There is probably something wrong
with your bootblock as your emulated VAX's VMB is not accepting it while
accepting the one on DUA1 from That Other OS, but your poor emulator prevents
you from seeing what the problem is.
> So far I have not been able to boot any other VAX operating system
> from the TUHS archive, the netbsd bootloader cannot load ultrix32m,
> 32v and 3bsd.
I don't know / don't care much about That Other OS and its bootloader, but the
format of the VAX unix/vmunix kernel image and its boot interface has remained
absolutely unchanged from 32V through 4.3BSD-Quasijarus0a inclusive (but see
below about VAX model support). DEC has extended the boot interface in Ultrix,
but it's completely backward compatible: as the Ultrix bootloader starts the
kernel with a calls instruction, it passes one argument (calls $1) whereas
traditional Bell/Berkeley UNIX had zero (calls $0). A traditional kernel will
simply ignore this argument, while the Ultrix kernels checks for its presence
(thanks to the wonderful VAX architecture and its procedure call standard that
allows a procedure to determine its argument count) and lives without it if
it's absent. (That argument is a pointer to a structure with useful info,
however, and I plan to adopt this extension in 4.3BSD-Quasijarus1.)
> I have not yet had time to try any of the other 4.x
> bsds, but I assume they'd have the same problem as quasijarus0a.
4.3BSD-Quasijarus0 was the first release to support KA650/655, so don't bother
trying earlier ones. (Although you could try 4.3-Reno if that's what you like.)
> I don't
> have ultrix/vax media to do it right
You can get the complete TK50 distribution (tape images) of Ultrix V4.00 for
VAX on my FTP site ivan.Harhan.ORG in /pub/UNIX/thirdparty/Ultrix-32. I have
full sources for it there too.
> Ultrix 4.3 gives me:
> > 466788+254256+177476+[36984+34990] total=0xecfa2
OK, so the kernel has been loaded successfully.
> > machine check 82: vap 82000004 istate1 7c000c00 istate2 c070fe pc 80001c61 psl 41f0008
> > r0=8000000c, r1=8000167c, r2=0, r3=211bd0dd, r4=0, r5=dd274
> > panic: mchk
Since Ultrix V4.3 perfectly supports the KA655 CPU, this again must be a case
of simh misemulating it.
My advice to you is to get a real VAX.
MS
P.S. You may want to subscribe to the Quasijarus mailing list, send a request
to quasijarus-request(a)ifctfvax.Harhan.ORG.
I installed 4.3-quasijarus on simh, and I managed to boot indirectly
by putting the kernel as /quasijarus0a in the netbsd root filesystem,
and then booting it from the netbsd bootloader with 'boot quasijarus0a
-a'. I have been unable to boot it directly from it's 'own'
filesystem.
here's what I see, complete transcript at the end
> >>>boot dua0
> (BOOT/R5:0 DUA0)
>
>
>
> 2..
> -DUA0
> HALT instruction, PC: 00000C1A (MOVL (R11),SP)
that's obviously not what I want. I tried all combinations of
installboot and disklabel -B I can think of, both in netbsd and
quasijarus, and all lead to the same result.
Can anybody tell me the exact incantations necessary to install
the bootblocks for quasijarus0a, or does anybody who has installed
quasijarus0a have a session transcript? any idea what I might be
doing wrong?
So far I have not been able to boot any other VAX operating system
from the TUHS archive, the netbsd bootloader cannot load ultrix32m,
32v and 3bsd. I have not yet had time to try any of the other 4.x
bsds, but I assume they'd have the same problem as quasijarus0a.
I have tried ultrix-4.3 (also from the netbsd bootloader, I don't
have ultrix/vax media to do it right), but it does not work either.
If anybody can help me with this, thanks in advance
Rico Pajarola
The following transcript shows how I boot it (first the way it
fails, then the way it works):
> VAX simulator V2.9-9
> sim> show c
> VAX simulator configuration
>
> CPU, 32768KB
> TLB, 2 units
> TLB0, 8KW
> TLB1, 8KW
> ROM, 128KB
> NVR, 1KB
> SYSD, 2 units
> SYSD0
> SYSD1
> QBA
> TTI
> TTO
> CSI
> CSO, not attached
> CLK
> PTR, address=20001F68-20001F6F, not attached
> PTP, address=20001F68-20001F6F, not attached
> LPT, address=20001F4C-20001F4F, not attached
> RQ, address=20001468-2000146B, 4 units
> RQ0, 159334KB, attached to 4.3-quasijarus0a.rd54.dsk, write enabled, RD54
> RQ1, 622932KB, attached to ../netbsd-vax/netbsd-vax.ra82.dsk, write enabled, RA82
> RQ2, 409KB, not attached, write enabled, RX50
> RQ3, 409KB, not attached, write enabled, RX50
> RL, disabled
> TS, disabled
> DZ, disabled
> sim> boot cpu
>
>
> KA655-B V5.3, VMB 2.7
> Performing normal system tests.
> 40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
> 24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
> 08..07..06..05..04..03..
> Tests completed.
> >>>boot dua0
> (BOOT/R5:0 DUA0)
>
>
>
> 2..
> -DUA0
> HALT instruction, PC: 00000C1A (MOVL (R11),SP)
> >>>boot dua1
> (BOOT/R5:0 DUA1)
>
>
>
> 2..
> -DUA1
> 1..0..
>
>
> >> NetBSD/vax boot [Aug 19 2001 05:57:49] <<
> >> Press any key to abort autoboot 3
> > boot quasijarus0a -a
> 327204+103384+130352+[29436+24084] total=0x96220
> 4.3 BSD Quasijarus UNIX #0: Sat Oct 2 22:15:38 CDT 1999
> msokolov@luthien:/usr/src/sys/GENERIC
> real mem = 33521664
> SYSPTSIZE limits number of buffers to 80
> avail mem = 31697920
> using 80 buffers containing 655360 bytes of memory
> MicroVAX 3000, ucode rev 6
> uda0 at uba0 csr 172150 vec 774, ipl 15
> uda0: version 3 model 3
> uda0: DMA burst size set to 4
> ra0 at uda0 slave 0: RD54, size = 311200 sectors
> ra1 at uda0 slave 1: vaxnetbsd, size = 1216665 sectors
> ra2 at uda0 slave 2: floppy
> ra3 at uda0 slave 3: floppy
> lp0 at uba0 csr 177514 vec 200, ipl 14
> root device? ra0
> WARNING: clock gained 14 days -- CHECK AND RESET THE DATE!
> erase ^?, kill ^U, intr ^C
> #
from this point on, it works as expected.
Ultrix 4.3 gives me:
> 466788+254256+177476+[36984+34990] total=0xecfa2
> machine check 82: vap 82000004 istate1 7c000c00 istate2 c070fe pc 80001c61 psl 41f0008
> r0=8000000c, r1=8000167c, r2=0, r3=211bd0dd, r4=0, r5=dd274
> panic: mchk
>
> dumping to dev ffffffff, offset 0
> dump machine check 80: vap 78302077 istate1 fb000c00 istate2 c070fd pc 8004eb57 psl 41f0000
> r0=78302073, r1=0, r2=0, r3=211bd0dd, r4=22, r5=80
> panic: mchk
>
> HALT instruction, PC: 8000165B (XFC)
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
Does anyone know how many of the V5, V6, V7, 2BSD, 2.11BSD, etc. filesystems are
implemented in some current unix implementations, NetBSD, Linux, etc. Seems like
that could be useful when playing with simh.
-chuck
On Mon, 6 May 2002 tuhs-request(a)minnie.tuhs.org wrote:
> From: Warren Toomey <wkt(a)minnie.tuhs.org>
>
> Sven, you might want to look at this:
> http://minnie.tuhs.org/cgi-bin/pups.cgi?article=2170
>
> From: Stuart Norris <norris(a)euler.mech.eng.usyd.edu.au>
>
> I have hacked together a version of a Unix 5th (and 6th)
> Edition filesystem for Linux. It is read only, and was written for
> Linux 2.0 on an x86 and so will require a little work to install on
> other systems and newer kernels, but it is fun to be able to mount
> old disk images.
The source code is sitting on
http://www.esc.auckland.ac.nz/People/Staff/Norris/src/u5e-0.2.tar.gz
and the INTRO file contains a description of the filesystem. I don't think
it works with current Linux kernels (I havn't touched it for a long while),
so it might be easiest to start afresh using the minix filesystem module
as a start.
Briefly, the filesystem is like
--
* Block size: 512
* General layout:
Block 0 boot block
Block 1 super block
Blocks 2 -> isize-1 inodes
Blocks isize -> fsize-1 data blocks
* Byte ordering of "short" (16 bit entities) is little endian 0 1
* Byte ordering of "long" (32 bit entities) is PDP-11 2 3 0 1
* Inode on disk: "short"
0 means non-existent
1 root dir
* Maximum number of hard links to a file: 256
* Super-block location: bytes 512-1023
* Super-block layout:
unsigned short s_isize; /* size in blocks of I list */
unsigned short s_fsize; /* size in blocks of entire volume */
unsigned short s_nfree; /* number of in core free blocks (0-100) */
unsigned short s_free[100]; /* in core free blocks */
unsigned short s_ninode; /* number of in core I nodes (0-100) */
unsigned short s_inode[100];/* in core free I nodes */
char s_flock; /* lock during free list manipulation */
char s_ilock; /* lock during I list manipulation */
char s_fmod; /* super block modified flag */
char s_ronly; /* mounted read-only flag */
unsigned long s_time; /* current date of last update */
* Inode layout:
unsigned short i_mode; /* access permissions */
unsigned char i_nlink; /* number of links to file */
unsigned char i_uid; /* owner */
unsigned char i_gid; /* group */
unsigned char i_size0; /* size of file */
unsigned short i_size1;
unsigned short i_addr[8];/* address of blocks */
unsigned long i_atime; /* time of last access */
unsigned long i_mtime; /* time of last modification */
* Regular file data blocks are organized as
if (010000 bit set)
the file is large:
i_addr[] contains indirect blocks
else
the file is small:
* Inode size 32, 16 inodes per block
* Directory entry on disk
unsigned short inode;
char name[14];
* Dir entry size 16, 32 dir entries per block
* There are no symbolic links
--
Stuart Norris s.norris(a)auckland.ac.nz
Bioengineering Institute, University of Auckland hm: +(64 9) 307 0006
http://www.esc.auckland.ac.nz/People/Staff/Norris wk: +(64 9) 373 7599 x3055
I've just obtained a box of tapes, some of which might be of interest here.
- UNIX/32V V1.0 (w/ typed Bell Labs label): one 2400' 800bpi tape
- Ultrix-32M V1.1 distribution: one 2400' dump tape
- Ultrix-32 & 32M V1.1 Sources: two 2400' 1600bpi tar tapes (2 copies each)
- BSD4.1 distribution: one 2400' 1600bpi tape
- UNIX V5 (handwritten label dated Feb 7 1977): one 2400' tape
- one 400' tape with missing identification label but a typed Bell
Labs notice
- backup of 2 RKs: V6 UNIX master and V6 UNIX additional source:
one 400' 800bpi tape
- C Release 29/9/80 (handwritten): one 2400' tape
- several backup tapes from a V7 system
- several other tapes that appear to be other UNIX system backups
I don't have a 9-track drive, so I can't say that these will be readable (or
even that they haven't been bulk-erased), but I do believe that they have at
least been stored well so far. If any of these look like they could contain
things currently missing from the archives, then I do of course want to make
them available to someone who can try to read them.
--
Kevin Schoedel
schoedel(a)kw.igs.net
Hi,
I'm currently working on an implementation of the Unix 6th Edition's
filesystem for Linux. I think earlier Unix filesystems should be very
similar to it. I would like to implement them, too, but I don't have
exact descriptions of them (for the 6th Edition I've the Lions Book;
there is not much about the actual filesystem architecture in it, but
it should be enough - together with the code ;-).
Please send me descriptions, specifications and everything else
you've about the early Unix filesystems. Also filesystem images are
very welcome as I can use them to test my implementation.
My e-mail account can only handle attachments <3000KB. Please
compress or split the files if they are bigger than 3000KB.
Thank you
Sven
>exact descriptions of them (for the 6th Edition I've the Lions Book;
>there is not much about the actual filesystem architecture in it, but
>it should be enough - together with the code ;-).
You might want to run V6 or V5 on a simulator. For one you can "see"
the filesystem and you can read the man pages, especially fs(5).
Wolfgang
> From: Mike Haertel <mike(a)ducky.net>
> To: tuhs(a)tuhs.org
> Subject: Re: [TUHS] Some tapes
> Date: Fri, 3 May 2002 01:13:55 -0700 (PDT)
>
> I'd also like to point out that the 4.1BSD distribution tape would
> be a nice addition to the TUHS archive. Right now 4.0, 4.1, and
> 4.1[abc] distributions are still missing.
These are available from Kirk McKusick on his 4-CD collection, no?
It'd be good to have them in w/the other stuff all in one place, but
it's not like they aren't available...
Arnold
I'd also like to point out that the 4.1BSD distribution tape would
be a nice addition to the TUHS archive. Right now 4.0, 4.1, and
4.1[abc] distributions are still missing.
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.
Hi all,
This is a general announcement :)
I have been working on getting to know the format used by the Ultrix-32
"setld" tapes for system (boot) tapes, and I am happy to announce that I
can now create bootable TK50 tapes from any valid Ultrix-32 CD-ROM dist
kit.
Once I get my stuff here sorted out (I am in the midst of redoing all my
computer stuff...) I will post the HOWTO (in PDF format, no less !) and
associated files on my web server.
I was able to successfully install Ultrix-32/VAX V4.5 on a MicroVAX 3300
with TK50 tape and no errors.
Next project is to get the V4.4 or V4.5 source to add CPU support for the
4000 series, and, eventually, add DSSI support for the SHAC chipset.
Anyone have pointers to source kits newer than V4.2 ?
Cheers,
Fred
--
InterNetworking, Network Security and Communications Consultants
MicroWalt Corporation (Netherlands), Postbus 8, 1400 AA 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.
Bleh, sorry for the blank post... notes went schitzo....
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 :)
Regards,
Paul.
Frank Wortner <frank(a)wortner.com>
Sent by: pups-admin(a)minnie.tuhs.org
04/03/2002 04:31
To: <asmodai(a)unixware.org.uk>, <pups(a)minnie.tuhs.org>
cc:
Subject: Re: [pups] Interesting PDP/Xenix History
on 4/2/02 5:38 PM, asmodai(a)unixware.org.uk at asmodai(a)unixware.org.uk
wrote:
I wrote to SCO/Caldera a while back about this one... Here's a quote
from the mail I got in reply:
"XENIX will never be released under any license, as it is too full of
Microsoft copyrights...?
Well, there?s always the possibility that Microsoft could see fit to make
a ?hobby? PDP/11 XENIX license available. Why not?
--
Frank
"Don't Blame Me."
* Eeyore, "Winnie the Pooh"
Frank Wortner <frank(a)wortner.com>
Sent by: pups-admin(a)minnie.tuhs.org
04/03/2002 04:31
To: <asmodai(a)unixware.org.uk>, <pups(a)minnie.tuhs.org>
cc:
Subject: Re: [pups] Interesting PDP/Xenix History
on 4/2/02 5:38 PM, asmodai(a)unixware.org.uk at asmodai(a)unixware.org.uk
wrote:
I wrote to SCO/Caldera a while back about this one... Here's a quote
from the mail I got in reply:
"XENIX will never be released under any license, as it is too full of
Microsoft copyrights...?
Well, there?s always the possibility that Microsoft could see fit to make
a ?hobby? PDP/11 XENIX license available. Why not?
--
Frank
"Don't Blame Me."
* Eeyore, "Winnie the Pooh"
I wrote to SCO/Caldera a while back about this one... Here's a quote
from the mail I got in reply:
"XENIX will never be released under any license, as it is too full of
Microsoft copyrights, and "sanitizing" the source to remove such code
would render the product useless, and would be a MASSIVE undertaking."
Looks like we wont get Xenix in source format unless Microsoft want us to
have it.
Regards,
Paul.
"The major difference between a thing that might go wrong and a thing that
cannot possibly go wrong is that when a thing that cannot possibly go
wrong goes wrong it usually turns out to be impossible to get at or
repair" - Hitchhikers Guide to the Galaxy
Robert Tillyard <rob(a)vetsystems.com>
Sent by: pups-admin(a)minnie.tuhs.org
03/25/2002 10:38
To: pups(a)minnie.tuhs.org
cc:
Subject: Re: [pups] Interesting PDP/Xenix History
Frank Wortner wrote:
>
> 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
Would SCO->Caldera have copies of this? SCO did the Intel port of Xenix
so they would probably have started with the PDP source. Would tapes be
copyright to Microsoft?
I doubt that they would release the source for the Intel version as it
is still in use today although I don't think that SCO/Caldera will sell
it anymore.
Rob.
_______________________________________________
PUPS mailing list
PUPS(a)minnie.tuhs.org
http://minnie.tuhs.org/mailman/listinfo/pups
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.
