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.)
In article by Jesper Nilsson:
> I'm thinking about getting myself a SCO Source license,
> but I'm worried that I might get "tainted" by this
> since my day job involves writing operating systems...
> My employer would not appreciate getting sued because of
> my hobbies...:-)
As long as you don't reuse tainted Unix source code in your job, you will
be ok. There are so many books covering the Unix kernel: Lions, Bach,
Goodheart, Vahalia etc., that any concerns other than source code reuse
are negligible.
That's my feelings, anyway.
Warren
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id LAA25583
for pups-liszt; Wed, 24 Feb 1999 11:46:21 +1100 (EST)
>From Greg Lehey <grog(a)lemis.com> Wed Feb 24 10:46:07 1999
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id LAA25578
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 24 Feb 1999 11:46:12 +1100 (EST)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA20195;
Wed, 24 Feb 1999 11:16:09 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.3/8.9.0) id LAA51811;
Wed, 24 Feb 1999 11:16:08 +1030 (CST)
Message-ID: <19990224111607.G93492(a)lemis.com>
Date: Wed, 24 Feb 1999 11:16:07 +1030
From: Greg Lehey <grog(a)lemis.com>
To: wkt(a)cs.adfa.edu.au, Unix Heritage Society <pups(a)minnie.cs.adfa.edu.au>
Subject: Re: SCO Source license tainting?
References: <Pine.LNX.4.05-df.9902231646390.8684-100000(a)bartlet.df.lth.se> <199902232152.IAA04722(a)henry.cs.adfa.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199902232152.IAA04722(a)henry.cs.adfa.edu.au>; from Warren Toomey on Wed, Feb 24, 1999 at 08:52:15AM +1100
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
On Wednesday, 24 February 1999 at 8:52:15 +1100, Warren Toomey wrote:
> In article by Jesper Nilsson:
>> I'm thinking about getting myself a SCO Source license,
>> but I'm worried that I might get "tainted" by this
>> since my day job involves writing operating systems...
>> My employer would not appreciate getting sued because of
>> my hobbies...:-)
>
> As long as you don't reuse tainted Unix source code in your job, you will
> be ok. There are so many books covering the Unix kernel: Lions, Bach,
> Goodheart, Vahalia etc., that any concerns other than source code reuse
> are negligible.
I think this relates to a spectre raised during the USL/BSDI wars.
Somebody suggested that anybody who had been exposed to AT&T source
code was ``tainted'' and could thus not legally develop competitive
systems. Somewhere I have a button that somebody brought back to me
from a USENIX, with the text ``mentally contaminated''.
Jesper, I don't think you need to worry about the problem. That kind
of restriction would be unenforceable.
Greg
--
See complete headers for address, home page and phone numbers
finger grog(a)lemis.com for PGP public key
Ken Wellsch has just uploaded a set of RX50 disk images containing
2.9BSD for the Pro 350 to the PUPS Archive. You can find them in
Distributions/ucb/2.9bsd4pro350-kcwellsc
He says:
I believe the RX50 is actually 80 tracks with 10 sectors per track,
thus yielding 800 blocks per disk. I think the first track is
reserved and thus Venix would not let me at it. Hopefully I have
not also lost additional information here too.
All the 34 disk images he sent in are 790 blocks long. Can anybody
tell us if we will need to recover track 0 to make these images useful?
At the very least, I've managed to find the pcreg.h file out of the
images (cat */*.rx50 | less -B), so I'm getting closer at recompiling
the 2.9/Pro kernel.
Cheers,
Warren
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id DAA23748
for pups-liszt; Wed, 24 Feb 1999 03:01:12 +1100 (EST)
>From Jesper Nilsson <jesper(a)df.lth.se> Wed Feb 24 02:00:54 1999
Received: from bartlet.df.lth.se (jesper(a)bartlet.df.lth.se [194.47.252.146])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id DAA23743
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 24 Feb 1999 03:01:02 +1100 (EST)
Received: from localhost (jesper@localhost)
by bartlet.df.lth.se (8.8.7/8.8.8) with ESMTP id RAA21777
for <pups(a)minnie.cs.adfa.edu.au>; Tue, 23 Feb 1999 17:00:54 +0100
Date: Tue, 23 Feb 1999 17:00:54 +0100 (CET)
From: Jesper Nilsson <jesper(a)df.lth.se>
To: PDP Unix Preservation Society <pups(a)minnie.cs.adfa.edu.au>
Subject: SCO Source license tainting?
Message-ID: <Pine.LNX.4.05-df.9902231646390.8684-100000(a)bartlet.df.lth.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Tjo!
I have a question that I hope someone can help me with:
I'm thinking about getting myself a SCO Source license,
but I'm worried that I might get "tainted" by this
since my day job involves writing operating systems...
My employer would not appreciate getting sued because of
my hobbies...:-)
Has anyone done research about this aspect of the license?
My goals are twofold, running an older Unix version on my PDP-11's,
and of course I want to peruse the source of the classic versions.
/^JN - Jesper Nilsson
--
I've heard of UNIseX, but I've never had it.
Jesper Nilsson -- jesper(a)df.lth.se
Yeah, I'm interested. Can you write up what changes the linux port entailed???
-Mike
At 07:10 PM 2/20/99 +0100, g4klx(a)g4klx.demon.co.uk wrote:
>Hello All
>
>A couple of weeks ago I hacked the program v7 from the bostic_tools to
>work under all sorts of different Unix versions. It worked great and
>allowed me to snoop around the V7 file system images from native Linux.
>Anyone who wants a copy can send me an e-mail.
>
>Anyway I had a few hours spare today, and decided to try adding the V7
>filesystem to the Linux kernel. Results so far are encouraging:
>
>
>g4klx:/usr/src/linux# ls -l /mnt
>total 333
>drwxrwxrwx 7 root root 224 Sep 22 1988 .
>drwxr-xr-x 19 root root 1024 Feb 14 11:55 ..
>drwxrwxr-x 2 3 3 2512 Sep 22 1988 bin
>-rwxr-xr-x 1 3 3 8986 Jun 8 1979 boot
>drwxrwxr-x 2 3 3 160 Sep 22 1988 dev
>drwxrwxr-x 2 3 3 336 Sep 22 1988 etc
>-rwxr-xr-x 1 daemon daemon 53302 Jun 8 1979 hphtunix
>-rwxr-xr-x 1 daemon daemon 52850 Jun 8 1979 hptmunix
>drwxrwxr-x 2 3 3 192 Sep 22 1988 lib
>drwxrwxr-x 2 root lp 96 Sep 22 1988 mdec
>-rwxr-xr-x 1 root daemon 50990 Jun 8 1979 rkunix
>-rwxr-xr-x 1 root daemon 51982 Jun 8 1979 rl2unix
>-rwxr-xr-x 1 daemon daemon 51790 Jun 8 1979 rphtunix
>-rwxr-xr-x 1 daemon daemon 51274 Jun 8 1979 rptmunix
>g4klx:/usr/src/linux# df
>Filesystem 1024-blocks Used Available Capacity Mounted on
>/dev/hda1 3031184 1920771 953665 67% /
>/dev/loop0 1919 1877 42 98% /mnt
>g4klx:/usr/src/linux#
>
>
>I am using the loop block device to allow me to mount a file as a block
>device, this saves me having to add a new partition to my disc. There
>should be no reason why it won't work with a true disc partition. The V7
>filesystem under Linux is read/write.
>
>Anyone interested ?
>
>Jonathan
>
>
>
>
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id NAA02555
for pups-liszt; Sun, 21 Feb 1999 13:29:44 +1100 (EST)
>From Warren Toomey <wkt(a)henry.cs.adfa.edu.au> Sun Feb 21 12:29:29 1999
Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id NAA02549
for <pups(a)minnie.cs.adfa.edu.au>; Sun, 21 Feb 1999 13:29:37 +1100 (EST)
Received: (from wkt@localhost)
by henry.cs.adfa.edu.au (8.9.1/8.9.1) id NAA08687;
Sun, 21 Feb 1999 13:29:29 +1100 (EST)
(envelope-from wkt)
From: Warren Toomey <wkt(a)henry.cs.adfa.edu.au>
Message-Id: <199902210229.NAA08687(a)henry.cs.adfa.edu.au>
Subject: Re: V7 filesystem work
In-Reply-To: <Pine.LNX.4.05.9902201906360.1385-100000(a)g4klx.agri.ch> from Jonathan Naylor at "Feb 20, 1999 7:10:45 pm"
To: g4klx(a)g4klx.demon.co.uk
Date: Sun, 21 Feb 1999 13:29:29 +1100 (EST)
Cc: pups(a)minnie.cs.adfa.edu.au
Reply-To: wkt(a)cs.adfa.edu.au
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
In article by Jonathan Naylor:
> Hello All
>
> A couple of weeks ago I hacked the program v7 from the bostic_tools to
> work under all sorts of different Unix versions. It worked great and
> allowed me to snoop around the V7 file system images from native Linux.
> Anyone who wants a copy can send me an e-mail.
>
> Anyway I had a few hours spare today, and decided to try adding the V7
> filesystem to the Linux kernel. Results so far are encouraging:
> I am using the loop block device to allow me to mount a file as a block
> device, this saves me having to add a new partition to my disc. There
> should be no reason why it won't work with a true disc partition. The V7
> filesystem under Linux is read/write.
>
> Anyone interested ?
I'd be happy to add any changes etc. into the Tools directory in the PUPS
Archive.
It's about time Unix could read the Unix filesystem again :-)
Ciao,
Warren
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id UAA05201
for pups-liszt; Sun, 21 Feb 1999 20:23:41 +1100 (EST)
>From Jonathan Naylor <g4klx(a)pop.agri.ch> Sun Feb 21 19:07:50 1999
Received: from biene.agri.ch (biene.agri.ch [212.28.128.41])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id UAA05195
for <pups(a)minnie.cs.adfa.edu.au>; Sun, 21 Feb 1999 20:23:21 +1100 (EST)
X-Internal-ID: 36B8327D0006E80C
Received: from g4klx.agri.ch (212.28.159.135) by biene.agri.ch (NPlex 2.0.119); Sun, 21 Feb 1999 10:23:16 +0100
Received: from localhost (g4klx@localhost)
by g4klx.agri.ch (8.8.8/8.8.8) with ESMTP id KAA00455;
Sun, 21 Feb 1999 10:07:51 +0100
X-Authentication-Warning: g4klx.agri.ch: g4klx owned process doing -bs
Date: Sun, 21 Feb 1999 10:07:50 +0100 (CET)
From: Jonathan Naylor <g4klx(a)pop.agri.ch>
X-Sender: g4klx(a)g4klx.agri.ch
Reply-To: g4klx(a)g4klx.demon.co.uk
To: Mike Allison <mallison(a)konnections.com>
cc: pups(a)minnie.cs.adfa.edu.au
Subject: Re: V7 filesystem work
In-Reply-To: <199902210203.TAA18682(a)mail.konnections.com>
Message-ID: <Pine.LNX.4.05.9902210957580.303-100000(a)g4klx.agri.ch>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Hello Mike and the list
On Sat, 20 Feb 1999, Mike Allison wrote:
> Yeah, I'm interested. Can you write up what changes the linux port entailed???
>
> -Mike
I assume you mean the standalone V7 FS program rather than the kernel V7
FS support ?
The code was written in old C, and from a modern C programmers point of
view, rather sloppily. The warnings from the compiler were terrible, so I
added function prototypes, and made the code more ANSI C like. Then I got
rid of a few bugs, in one place I remember a character pointer being
assigned to a character.
I then typedef'd the data types so I could use int8, int16 and int32 in
the code to make it more portable. I stopped using structure overlays onto
the raw data as that is messy and is not good for (a) byte ordering and
(b) structure packing. It also allowed me to stop using the original V7
file headers which would have made a public release of the code
problematic.
The data is extracted from the raw block data by using special
architecturally neutral functions into locally held structures. That is a
particular win with the block number in three bytes trick that is used in
the inode.
It has been tested on i386/Linux with both glibc 1.0 and glibc 2.0 and
Alpha/Linux, no changes were needed.
Then I added a few new commands to let me look at the superblock and
bootblocks and a few other bits.
Then I released it.
I have just sent a copy of the program to Warren for inclusion in the PUPS
tools section. Its not very big.
Work is progressing on the V7 filesystem in the Linux kernel. Anyone who
wants the patches for that should send me an e-mail. I hope to get it into
the mainstream kernel in the Linux 2.3 series.
Jonathan
Hello All
A couple of weeks ago I hacked the program v7 from the bostic_tools to
work under all sorts of different Unix versions. It worked great and
allowed me to snoop around the V7 file system images from native Linux.
Anyone who wants a copy can send me an e-mail.
Anyway I had a few hours spare today, and decided to try adding the V7
filesystem to the Linux kernel. Results so far are encouraging:
g4klx:/usr/src/linux# ls -l /mnt
total 333
drwxrwxrwx 7 root root 224 Sep 22 1988 .
drwxr-xr-x 19 root root 1024 Feb 14 11:55 ..
drwxrwxr-x 2 3 3 2512 Sep 22 1988 bin
-rwxr-xr-x 1 3 3 8986 Jun 8 1979 boot
drwxrwxr-x 2 3 3 160 Sep 22 1988 dev
drwxrwxr-x 2 3 3 336 Sep 22 1988 etc
-rwxr-xr-x 1 daemon daemon 53302 Jun 8 1979 hphtunix
-rwxr-xr-x 1 daemon daemon 52850 Jun 8 1979 hptmunix
drwxrwxr-x 2 3 3 192 Sep 22 1988 lib
drwxrwxr-x 2 root lp 96 Sep 22 1988 mdec
-rwxr-xr-x 1 root daemon 50990 Jun 8 1979 rkunix
-rwxr-xr-x 1 root daemon 51982 Jun 8 1979 rl2unix
-rwxr-xr-x 1 daemon daemon 51790 Jun 8 1979 rphtunix
-rwxr-xr-x 1 daemon daemon 51274 Jun 8 1979 rptmunix
g4klx:/usr/src/linux# df
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/hda1 3031184 1920771 953665 67% /
/dev/loop0 1919 1877 42 98% /mnt
g4klx:/usr/src/linux#
I am using the loop block device to allow me to mount a file as a block
device, this saves me having to add a new partition to my disc. There
should be no reason why it won't work with a true disc partition. The V7
filesystem under Linux is read/write.
Anyone interested ?
Jonathan
<DELQA is not 68k, The DEUNA is. The DELQA is a cost reduced version
<(less buggy too) of the DEQNA and is largely logically the same as the
<DEQNA.
Memory parity exception... Eat foot time.
DELQA M7516 is 68k and lance chip... had to pull mine to check. The M7504
however I am correct as I pulled one down from the shelf before dining on
foot. Oh and the reson I forgot it's 68k, was the DELQA is far more
reliable! that and I only open the BA123 one a year to check the fans and
clean dust. It just don't break. ;)
Allison
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id NAA19969
for pups-liszt; Fri, 19 Feb 1999 13:36:31 +1100 (EST)
>From Tim Shoppa <SHOPPA(a)trailing-edge.com> Fri Feb 19 12:36:11 1999
Received: from timaxp.trailing-edge.com (trailing-edge.wdn.com [198.232.144.27])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with SMTP id NAA19961
for <PUPS(a)MINNIE.cs.adfa.OZ.AU>; Fri, 19 Feb 1999 13:36:21 +1100 (EST)
Received: by timaxp.trailing-edge.com for PUPS(a)MINNIE.cs.adfa.OZ.AU;
Thu, 18 Feb 1999 21:36:11 -0500
Date: Thu, 18 Feb 1999 21:36:11 -0500
From: Tim Shoppa <SHOPPA(a)trailing-edge.com>
To: PUPS(a)MINNIE.cs.adfa.OZ.AU
Message-Id: <990218213611.202000b8(a)trailing-edge.com>
Subject: Re: DEQNA (was was Re: 2.9BSD: mbuf.h)
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
><The replacement ethernet controller was the DELQA, which was a complete
><redesign and used a 68000 processor.
>The DELQA was not 68000.
Hate to turn this into a "no it isn't, yet it is" sequence, but all
my DELQA's have prominent 68000's on 'em.
> The board was far to small for that
No, it isn't. The 68000 is the quad pack, and is smaller than either
of the two custom gate arrays that does the Q-bus handshaking.
Tim.
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id OAA20047
for pups-liszt; Fri, 19 Feb 1999 14:07:20 +1100 (EST)
>From Warren Toomey <wkt(a)henry.cs.adfa.edu.au> Fri Feb 19 13:06:14 1999
Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id OAA20040
for <pups(a)minnie.cs.adfa.oz.au>; Fri, 19 Feb 1999 14:07:11 +1100 (EST)
Received: (from wkt@localhost)
by henry.cs.adfa.edu.au (8.9.1/8.9.1) id OAA02230;
Fri, 19 Feb 1999 14:06:14 +1100 (EST)
(envelope-from wkt)
From: Warren Toomey <wkt(a)henry.cs.adfa.edu.au>
Message-Id: <199902190306.OAA02230(a)henry.cs.adfa.edu.au>
Subject: Re: 2.9BSD: mbuf.h
In-Reply-To: <006401be5baa$06ce3da0$33d1b7c7@eric-edwards> from Eric Edwards at "Feb 18, 1999 8:48:59 pm"
To: eekg(a)ix.netcom.com (Eric Edwards)
Date: Fri, 19 Feb 1999 14:06:14 +1100 (EST)
Cc: pups(a)minnie.cs.adfa.oz.au (Unix Heritage Society)
Reply-To: wkt(a)cs.adfa.edu.au
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
In article by Eric Edwards:
> I'm not sure if anyone mentioned this, but you can build a working 2.9
> kernel (sans network) from the sources by just commenting out the references
> to the networking include files. I think there is an offending reference in
> syslocal.c also.
>
> Eric Edwards
> eekg(a)ix.netcom.com
> mag(a)csh.rit.edu
What is happening is that `make depend' invokes a script which finds
#includes in the source code, and builds a make dependency. However,
it's not very intelligent, and doesn't ignore:
#ifdef INET
#include <stuff>
when INET isn't defined. :-) This bites on several C files.
You just have to hand-prune the Makefile after make depend :-)
This is 2.9BSD, BTW, ignore if you're not using it.
Ciao!
Warren
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id VAA21635
for pups-liszt; Fri, 19 Feb 1999 21:20:30 +1100 (EST)
>From Johnny Billquist <bqt(a)Update.UU.SE> Fri Feb 19 20:19:31 1999
Received: from Zeke.Update.UU.SE (IDENT:2026@Zeke.Update.UU.SE [130.238.11.14])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id VAA21630
for <pups(a)minnie.cs.adfa.oz.au>; Fri, 19 Feb 1999 21:20:14 +1100 (EST)
Received: from localhost (bqt@localhost)
by Zeke.Update.UU.SE (8.8.8/8.8.8) with SMTP id LAA26451;
Fri, 19 Feb 1999 11:19:33 +0100
Date: Fri, 19 Feb 1999 11:19:31 +0100 (MET)
From: Johnny Billquist <bqt(a)Update.UU.SE>
To: Allison J Parent <allisonp(a)world.std.com>
cc: pups(a)minnie.cs.adfa.oz.au
Subject: Re: Venix (was Re: 2.9BSD: mbuf.h)
In-Reply-To: <199902190157.AA29020(a)world.std.com>
Message-ID: <Pine.VUL.3.93.990219111730.26158A-100000(a)Zeke.Update.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
On Thu, 18 Feb 1999, Allison J Parent wrote:
> <You obviously knows more about this than I do. :-)
> <However, as I said, atleast the DELQA have an M68K...
> <And the DEQNA is old, yes...
>
> DELQA is not 68k, The DEUNA is. The DELQA is a cost reduced version
> (less buggy too) of the DEQNA and is largely logically the same as the
> DEQNA.
Really? I have a DELQA sitting right in front of me, and when I look at
it, the large chip definitely says M68000. What could that be then?
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
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id VAA21652
for pups-liszt; Fri, 19 Feb 1999 21:23:04 +1100 (EST)
>From Johnny Billquist <bqt(a)Update.UU.SE> Fri Feb 19 20:22:35 1999
Received: from Zeke.Update.UU.SE (IDENT:2026@Zeke.Update.UU.SE [130.238.11.14])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id VAA21647
for <pups(a)minnie.cs.adfa.oz.au>; Fri, 19 Feb 1999 21:22:50 +1100 (EST)
Received: from localhost (bqt@localhost)
by Zeke.Update.UU.SE (8.8.8/8.8.8) with SMTP id LAA26532;
Fri, 19 Feb 1999 11:22:37 +0100
Date: Fri, 19 Feb 1999 11:22:35 +0100 (MET)
From: Johnny Billquist <bqt(a)Update.UU.SE>
To: Allison J Parent <allisonp(a)world.std.com>
cc: pups(a)minnie.cs.adfa.oz.au
Subject: Re: DEQNA (was was Re: 2.9BSD: mbuf.h)
In-Reply-To: <199902190214.AA14211(a)world.std.com>
Message-ID: <Pine.VUL.3.93.990219112030.26158B-100000(a)Zeke.Update.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
On Thu, 18 Feb 1999, Allison J Parent wrote:
> <The replacement ethernet controller was the DELQA, which was a complete
> <redesign and used a 68000 processor.
>
> The DELQA was not 68000. The board was far to small for that and had to be
> Qbus dual width and compatable with DEQNA. I have a few of them in my vaxen
> too. The Unibus versions DEUNA and the later DELUA were 68k and very good.
Hate to disagree with you, Alison. The the DELQA really is 68000, take a
peek inside yourself. It is a dual-width too...
And the DEUNA is T-11, while the DELUA is 68000.
I have never bothered plugging in any DEUNAs myself, since DELUAs are
pretty common, and they atleast are pretty good. Never had any problems
with any of them.
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
<I'm sorry. I didn't mean to imply that you were wrong, just that I was.
Not an argument, just posting to the group what went private by error.
<Never looked carefully at RQDX?, but the DELQA uses an M68K, that much I
<*do* know. (As do the DELUA)
Having two Qbus VAXen and several Qbus PDP-11s it's old turf. Also I worked
for DEC Engineering. that and I've done a lot of hardware level work on my
systems (repaired dead boards) so the designs are more familair.
<You obviously knows more about this than I do. :-)
<However, as I said, atleast the DELQA have an M68K...
<And the DEQNA is old, yes...
DELQA is not 68k, The DEUNA is. The DELQA is a cost reduced version
(less buggy too) of the DEQNA and is largely logically the same as the
DEQNA.
<> The DEUNA is quite different.
<
<Obviously. But it is also pretty old. Not as buggy though, which should
<have been a clue. :-)
Also The DELUA.
Allison
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id MAA19690
for pups-liszt; Fri, 19 Feb 1999 12:59:39 +1100 (EST)
>From "Eric Edwards" <eekg(a)ix.netcom.com> Fri Feb 19 11:48:59 1999
Received: from dfw-ix2.ix.netcom.com (dfw-ix2.ix.netcom.com [206.214.98.2])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id MAA19683
for <pups(a)minnie.cs.adfa.edu.au>; Fri, 19 Feb 1999 12:59:27 +1100 (EST)
Received: (from smap@localhost)
by dfw-ix2.ix.netcom.com (8.8.4/8.8.4)
id TAA22942; Thu, 18 Feb 1999 19:58:39 -0600 (CST)
Received: from roc-ny1-19.ix.netcom.com(199.183.209.51) by dfw-ix2.ix.netcom.com via smap (V1.3)
id rma022871; Thu Feb 18 19:58:23 1999
Message-ID: <006401be5baa$06ce3da0$33d1b7c7@eric-edwards>
From: "Eric Edwards" <eekg(a)ix.netcom.com>
To: "maximum entropy" <entropy(a)zippy.bernstein.com>,
<pups(a)minnie.cs.adfa.edu.au>
Subject: Re: 2.9BSD: mbuf.h
Date: Thu, 18 Feb 1999 20:48:59 -0500
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
I'm not sure if anyone mentioned this, but you can build a working 2.9
kernel (sans network) from the sources by just commenting out the references
to the networking include files. I think there is an offending reference in
syslocal.c also.
Eric Edwards
eekg(a)ix.netcom.com
mag(a)csh.rit.edu
-----Original Message-----
From: maximum entropy <entropy(a)zippy.bernstein.com>
To: pups(a)minnie.cs.adfa.edu.au <pups(a)minnie.cs.adfa.edu.au>
Date: Tuesday, February 16, 1999 11:36 PM
Subject: 2.9BSD: mbuf.h
>"make unix" failed:
>Make: Don't know how to make /usr/include/sys/mbuf.h. Stop.
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id NAA19762
for pups-liszt; Fri, 19 Feb 1999 13:14:46 +1100 (EST)
>From maximum entropy <entropy(a)zippy.bernstein.com> Tue Feb 16 23:36:00 1999
Received: from europe.std.com (europe.std.com [199.172.62.20])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id NAA19757
for <pups(a)minnie.cs.adfa.oz.au>; Fri, 19 Feb 1999 13:14:38 +1100 (EST)
Received: from world.std.com by europe.std.com (STD1.2/BZS-8-1.0)
id VAA07685; Thu, 18 Feb 1999 21:14:33 -0500 (EST)
Received: by world.std.com (TheWorld/Spike-2.0)
id AA14211; Thu, 18 Feb 1999 21:14:32 -0500
Date: Thu, 18 Feb 1999 21:14:32 -0500
From: allisonp(a)world.std.com (Allison J Parent)
Message-Id: <199902190214.AA14211(a)world.std.com>
To: pups(a)minnie.cs.adfa.oz.au
Subject: Re: DEQNA (was was Re: 2.9BSD: mbuf.h)
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
<The DEQNA uses a Intel 8751 (an EPROM version of 8051 family). I suspect th
<it may deal with the programming protocol and the ring buffers. The
<chip with the F (with bars top and bottom of the letter) is probably
<Fujitsu.
Correct on both cases.
<These boards had a fairly bad reputation for lockups and dropped packets.
<There was a 20+ wire ECO along with a PAL chip (with 8 of the pins cut off
<soldered on top of another chip.
Actually there were revs A->n and each rev had a step. The last one was
N-11... it was marginal. Good one tended to be good and the bad were PITA.
Also they tended to fail far often than MTBF predictions.
<The replacement ethernet controller was the DELQA, which was a complete
<redesign and used a 68000 processor.
The DELQA was not 68000. The board was far to small for that and had to be
Qbus dual width and compatable with DEQNA. I have a few of them in my vaxen
too. The Unibus versions DEUNA and the later DELUA were 68k and very good.
They were partly the reason why 730s and 750s were used for routers long
after they were replaced for other tasks.
Allison
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id NAA19811
for pups-liszt; Fri, 19 Feb 1999 13:23:12 +1100 (EST)
| Just for the sake of being picky... the DEQNA is based on an Intel
| microcontroller chip (something 8085-ish, I think). The ethernet chipset
| seems to be Fairchild (it's certainly got a big F on it.)
|
The DEQNA uses a Intel 8751 (an EPROM version of 8051 family). I suspect that
it may deal with the programming protocol and the ring buffers. The
chip with the F (with bars top and bottom of the letter) is probably
Fujitsu.
These boards had a fairly bad reputation for lockups and dropped packets.
There was a 20+ wire ECO along with a PAL chip (with 8 of the pins cut off)
soldered on top of another chip.
The replacement ethernet controller was the DELQA, which was a complete
redesign and used a 68000 processor.
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id LAA19489
for pups-liszt; Fri, 19 Feb 1999 11:41:28 +1100 (EST)
>From Johnny Billquist <bqt(a)Update.UU.SE> Fri Feb 19 10:41:03 1999
Received: from Zeke.Update.UU.SE (IDENT:2026@Zeke.Update.UU.SE [130.238.11.14])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id LAA19484
for <pups(a)minnie.cs.adfa.oz.au>; Fri, 19 Feb 1999 11:41:18 +1100 (EST)
Received: from localhost (bqt@localhost)
by Zeke.Update.UU.SE (8.8.8/8.8.8) with SMTP id BAA05467;
Fri, 19 Feb 1999 01:41:06 +0100
Date: Fri, 19 Feb 1999 01:41:03 +0100 (MET)
From: Johnny Billquist <bqt(a)Update.UU.SE>
To: Allison J Parent <allisonp(a)world.std.com>
cc: pups(a)minnie.cs.adfa.oz.au
Subject: Re: Venix (was Re: 2.9BSD: mbuf.h)
In-Reply-To: <199902190022.AA25325(a)world.std.com>
Message-ID: <Pine.VUL.3.93.990219013735.1502E-100000(a)Zeke.Update.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Hi, Alison.
> <You might not be totally out. I also thought the DEQNA was T-11 based,
> <since the DEUNA is. :-)
>
> I have a DEQNA in front of me. There is a micro and that is a 8751 8bitter.
> The big chip is a LSI ASIC that is a linked list DMA controller. No t-11.
I'm sorry. I didn't mean to imply that you were wrong, just that I was.
> The RQDXn(n={1,2,3} uses a t-11. The DELQA also does not use a T-11.
Never looked carefully at RQDX?, but the DELQA uses an M68K, that much I
*do* know. (As do the DELUA)
> Both use lots of logic in PALs and ASICs to perform several state machines
> needed for eithenet. At the time of development there were few complete
> and fast enough chipsets for eithernet. The DEQNA is mid 80s design and
> quite old.
You obviously knows more about this than I do. :-)
However, as I said, atleast the DELQA have an M68K...
And the DEQNA is old, yes...
> The DEUNA is quite different.
Obviously. But it is also pretty old. Not as buggy though, which should
have been a clue. :-)
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
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id MAA19674
for pups-liszt; Fri, 19 Feb 1999 12:57:56 +1100 (EST)
<> I'm going to give up as I seem to remember nothing anymore... sigh.
<> Allison also sent e-mail saying the DEQNA is not T-11 based. I guess
<> I'm thinking of an RQDX3. I've had no place to unpack my old iron in
<> over three years and certainly miss being able to pick up the part in
<> question before foaming at the mouth spouting nonsense. Many apologies
<> for suggesting such major inaccuracies. -- Ken
<>
<> P.S. Allison describe the DEQNA as a state-driven device with PALs
<> (I think) and that "big F" may the the gate array also mentioned.
<
<You might not be totally out. I also thought the DEQNA was T-11 based,
<since the DEUNA is. :-)
I have a DEQNA in front of me. There is a micro and that is a 8751 8bitter.
The big chip is a LSI ASIC that is a linked list DMA controller. No t-11.
The RQDXn(n={1,2,3} uses a t-11. The DELQA also does not use a T-11.
Both use lots of logic in PALs and ASICs to perform several state machines
needed for eithenet. At the time of development there were few complete
and fast enough chipsets for eithernet. The DEQNA is mid 80s design and
quite old.
The DEUNA is quite different.
Allison
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id LAA19476
for pups-liszt; Fri, 19 Feb 1999 11:40:24 +1100 (EST)
My local computer junk store has a VaxMate for sale. I'm not sure of the
model -- It has a DB-25 serial port, 10-base-2 ethernet, and a phone-jack
like printer port on the back, as well as an internal ST-225 hard drive
and a 5.25 inch floppy drive.
Anyway, when I turn it on it tries to boot up -- the graphical slider
thing on the screen gets about 90% of the way across and it displays the
number 83, which I assume is an eeror code since the number changes if you
boot it up with no keyboard. Anyone know what the 83 means or where I can
get a list of VaxMate error codes? Also, how intelligent is this machine
compared to a terminal? Will it actually run a Vax operating system or
does it need a server?
--------------------------------------------------------
"...color flashing thunder crashing dynamite machine..."
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id KAA19267
for pups-liszt; Fri, 19 Feb 1999 10:25:25 +1100 (EST)
>From Johnny Billquist <bqt(a)Update.UU.SE> Fri Feb 19 09:24:43 1999
Received: from Zeke.Update.UU.SE (IDENT:2026@Zeke.Update.UU.SE [130.238.11.14])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id KAA19259
for <pups(a)minnie.cs.adfa.oz.au>; Fri, 19 Feb 1999 10:25:14 +1100 (EST)
Received: from localhost (bqt@localhost)
by Zeke.Update.UU.SE (8.8.8/8.8.8) with SMTP id AAA02756;
Fri, 19 Feb 1999 00:24:44 +0100
Date: Fri, 19 Feb 1999 00:24:43 +0100 (MET)
From: Johnny Billquist <bqt(a)Update.UU.SE>
To: Ken Wellsch <kcwellsc(a)math.uwaterloo.ca>
cc: James Lothian <simul8(a)simul8.demon.co.uk>, pups(a)minnie.cs.adfa.oz.au
Subject: Re: Venix (was Re: 2.9BSD: mbuf.h)
In-Reply-To: <199902181846.NAA05766(a)math.uwaterloo.ca>
Message-ID: <Pine.VUL.3.93.990219002351.1502D-100000(a)Zeke.Update.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
On Thu, 18 Feb 1999, Ken Wellsch wrote:
> I'm going to give up as I seem to remember nothing anymore... sigh.
> Allison also sent e-mail saying the DEQNA is not T-11 based. I guess
> I'm thinking of an RQDX3. I've had no place to unpack my old iron in
> over three years and certainly miss being able to pick up the part in
> question before foaming at the mouth spouting nonsense. Many apologies
> for suggesting such major inaccuracies. -- Ken
>
> P.S. Allison describe the DEQNA as a state-driven device with PALs
> (I think) and that "big F" may the the gate array also mentioned.
You might not be totally out. I also thought the DEQNA was T-11 based,
since the DEUNA is. :-)
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
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id LAA19430
for pups-liszt; Fri, 19 Feb 1999 11:22:47 +1100 (EST)
