Greg Lehey <grog(a)lemis.com> wrote:
> Now you mention this, I seem to remember that BSDI registered the name
> BSD as a trade mark, so you wouldn't be able to even if you wanted to.
That's nonsense. You can't trademark something that isn't even yours. BSDI has
no rights whatsoever to the code copyrighted by the Regents of University of
California. The BSD license agreement explicitly allows unrestricted
modification and distribution of modified versions. Incrementing the version
number is one of the most natural operations a developer modifying the system
can do. If I were to use CSRG's final 1995 code as my starting point, I would
indeed call my system 4.5BSD, and I would have the full right to do so. The
only reason I do not and cannot call my system 4.5BSD, 5BSD, or whatever is
because I'm tmachining the SCCS tree back to 1988, nullifying 4.4BSD.
Michael Sokolov
TUHS 4BSD Coordinator
4.3BSD-* Maintainer
Quasijarus Project Principal Architect & Developer
Phone: 440-449-0299 or 216-217-2579
ARPA Internet SMTP mail: mxs46(a)k2.scl.cwru.edu
TUHS WWW page: http://minnie.cs.adfa.edu.au/TUHS/
Quasijarus WWW page: http://minnie.cs.adfa.edu.au/Quasijarus/
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id TAA14866
for pups-liszt; Tue, 26 Jan 1999 19:49:29 +1100 (EST)
>From Greg Lehey <grog(a)lemis.com> Tue Jan 26 18:49:16 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 TAA14861
for <pups(a)minnie.cs.adfa.edu.au>; Tue, 26 Jan 1999 19:49:21 +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 TAA05782;
Tue, 26 Jan 1999 19:19:17 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id TAA94514;
Tue, 26 Jan 1999 19:19:16 +1030 (CST)
Date: Tue, 26 Jan 1999 19:19:16 +1030
From: Greg Lehey <grog(a)lemis.com>
To: Michael Sokolov <mxs46(a)k2.scl.cwru.edu>
Cc: pups(a)minnie.cs.adfa.edu.au
Subject: Re: 4.4BSD
Message-ID: <19990126191916.A66239(a)freebie.lemis.com>
References: <199901260840.DAA03267(a)skybridge.scl.cwru.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901260840.DAA03267(a)skybridge.scl.cwru.edu>; from Michael Sokolov on Tue, Jan 26, 1999 at 03:40:40AM -0500
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 Tuesday, 26 January 1999 at 3:40:40 -0500, Michael Sokolov wrote:
> Greg Lehey <grog(a)lemis.com> wrote:
>
>> Now you mention this, I seem to remember that BSDI registered the name
>> BSD as a trade mark, so you wouldn't be able to even if you wanted to.
>
> That's nonsense. You can't trademark something that isn't even
> yours.
You can trademark anything that hasn't already been trademarked.
> BSDI has no rights whatsoever to the code copyrighted by the Regents
> of University of California.
Of course they have. The rights are described in the Berkeley
License.
> The BSD license agreement explicitly allows unrestricted
> modification and distribution of modified versions.
Precisely.
Greg
--
See complete headers for address, home page and phone numbers
finger grog(a)lemis.com for PGP public key
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id UAA15026
for pups-liszt; Tue, 26 Jan 1999 20:54:41 +1100 (EST)
Thor Lancelot Simon <tls(a)rek.tjls.com> wrote:
> I frankly consider this to be silly, somewhat presumptious, and, for myself,
> at least, a waste of time. But if it's something _you_ want to do, I
> encourage you to do it, I suppose.
You may believe whatever you want, but I will only remark that several very
prominent VAX hardware gurus (some of them on this list) support my work very
eagerly. Whatever you or the NetBSD gang may believe, my True UNIX is the only
UNIX system that is really a VAX OS and can truly drive a VAX the way it's
supposed to be driven.
> All that I ask is that you not touch the value of the "BSD" symbol which is
> exposed to the userland C namespace. The chaos which would ensue should
> a "later" version of BSD appear which didn't support the full 4.4BSD feature
> set is horrifying to contemplate.
Don't worry, I'm not planning on doing that. Although I do not consider 4.4BSD
to be True UNIX, I do acknowledge that it exists, and I do respect the laws of
arithmetics and sequential numbering, so I don't plan on using numbers like
4.5BSD or 5BSD. Instead, I follow CSRG's own convention of calling 4.3-followup
systems 4.3BSD-BlahBlahBlah, just like they did with 4.3BSD-Tahoe.
> Despite the great temptation to do so, neither the NetBSD nor the FreeBSD
> project have taken up the mantle of CSRG [...]
Excellent! This gives me the luxury of being free from competitors.
> History is history.
Yes, history is history, and I respect it as such. I'm not trying to abuse my
write access to the 4BSD collection and maliciously modify some preserved tape
image without anyone's knowledge. However, there is nothing in the world that
prevents a developer from creating a new version of system from an old one. If
there is an SCCS file with deltas ranging from 1.1 to 7.16, there is absolutely
nothing in the world preventing a developer with legitimate authorized write
access to that file from checking in delta 7.17. I am a legitimate authorized
Berkeley UNIX developer (actually the principal one at the present time). My
title as the principal maintainer has been legitimized and blessed by the
previous CSRG maintainer.
> Pretending
> to be an organization which doesn't exist...
First of all, I didn't say "I'm CSRG", I said that I am CSRG's legitimate and
authorized successor. Second, there is nothing in the words "Computer Systems
Research Group" that is limited to Berkeley. Any group of researchers could
conceivably come up with that name. However, doing that would be extremely
confusing, therefore, I don't want to do that.
> [...] gets very little useful work done.
Check out the Quasijarus features page:
http://minnie.cs.adfa.edu.au/Quasijarus/features.html
So far the list is not that long, but keep in mind that the work started less
than a month ago.
Michael Sokolov
TUHS 4BSD Coordinator
4.3BSD-* Maintainer
Quasijarus Project Principal Architect & Developer
Phone: 440-449-0299 or 216-217-2579
ARPA Internet SMTP mail: mxs46(a)k2.scl.cwru.edu
TUHS WWW page: http://minnie.cs.adfa.edu.au/TUHS/
Quasijarus WWW page: http://minnie.cs.adfa.edu.au/Quasijarus/
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id TAA14823
for pups-liszt; Tue, 26 Jan 1999 19:27:01 +1100 (EST)
Dear VAX users,
Due to the storm of protests, the method of distribution of VAX EPROM upgrades
has changed from the PUPS archive to direct uuencoded E-mail. If you require an
EPROM upgrade for your VAX in order to run a UNIX software distribution
obtained from me, please contant me via ARPA Internet SMTP mail and I will send
you the EPROM image, compressed and uuencoded. I currently have the images for
KA650-B V1.2 and KA42 SCSI/MFM daughterboard.
The VAX odds and ends directory in the PUPS archive will still contain the
soft-loaded microcode files and booters, which have already been freely
distributed with different VAX UNIX systems (either 4.3BSD-* or BSD
derivatives like MIT's Athena-4.3BSD).
Michael Sokolov
TUHS 4BSD Coordinator
4.3BSD-* Maintainer
Quasijarus Project Principal Architect & Developer
Phone: 440-449-0299 or 216-217-2579
ARPA Internet SMTP mail: mxs46(a)k2.scl.cwru.edu
TUHS WWW page: http://minnie.cs.adfa.edu.au/TUHS/
Quasijarus WWW page: http://minnie.cs.adfa.edu.au/Quasijarus/
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id TAA14811
for pups-liszt; Tue, 26 Jan 1999 19:26:42 +1100 (EST)
Let's look at things from the practical viewpoint, OK? One of my goals is to
establish a repository containing the latest available microcode revision for
every machine supported by my UNIX system. Why? As you may remember from our
extensive phone discussions, UNIX is quite picky about which hardware to run
on. In many cases (on a 730, for example), UNIX won't boot if the firmware is
below the minimum required revision. I know for sure that this is the case on
730, 8200, and if James Lothian's WCS changes get integrated, 750. It will also
be the case on BabyVAXen when I get around to supporting them. Now, so far I
haven't heard any reports of UNIX refusing to boot on KA650s with early
microcode revisions, but one may come in at some point. Since my KA650 runs
UNIX right now, I know for sure that at least my version of the firmware is
UNIX-friendly. By making it available to other 4.3BSD-Quasijarus users (note
that keeping the microcode repository within the PUPS archive has the advantage
of giving the images out only to Ancient UNIX enthusiasts, i.e., only to those
who really need them), I can make sure that the greatest possible number of
people can benefit from my 4.3BSD-Quasijarus work.
Come on, removing the KA650 from the list of CPUs for which I make microcode
updates available won't change anything. I will still have to carry a ragbag of
DEC-copyrighted bits and pieces in order to make my OS project successful. Soon
UNIX will require a copy of VMB.EXE in order to boot from MSCP disks and TMSCP
tapes on large VAXen. Yes, there is one distributed with the machine itself,
but it's too old. UNIX requires a very recent version, and if I want my OS to
be viable, there will simply be no other choice but to distribute VMB.EXE. Or
look at BI-bus machines. There were two different BI network cards made, DEBNA
and DEBNI. They have the same hardware, but different EPROMs. DEBNA is the
older one and DEBNI is the newer one. They have completely different software
interfaces, and DEBNI is a lot simpler to program. Right now UNIX doesn't
support any BI network cards. Suppose I decide to add this support. Given how
hard it is to find documentation, write drivers, and test them, what do you
think, will I welcome the idea of writing two drivers instead of one? Rather
than spend months hunting for a BVP manual and writing a DEBNA driver, it's
much easier to write a driver for DEBNI only (much simpler software interface)
and tell DEBNA users to upgrade their boards to DEBNI. The catch is, if you are
getting your 8200 or whatever for free, you don't get to choose which network
card to use, you take what you can find. But with me keeping the repository of
all important EPROM images and microcode patch files, the poor DEBNA user can
just download the image, borrow an EPROM blaster, and run his free VAX with a
UNIX-supported DEBNI!
The thing of it is, all this hardware is orphaned. If you have a DEBNA and want
to upgrade it to DEBNI to run UNIX, or if you have KA650 V1.1 and want to
upgrade it to V1.2 to run UNIX, if you call COMPAQ and ask them for a firmware
upgrade they'll laugh at you. If DEC still existed and supported this stuff it
would be a different story, but with all this hardware orphaned, the poor VAX
UNIX users have no one to turn to for microcode upgrades and troubleshooting
support except the VAX UNIX maintainer, i.e., me.
Michael Sokolov
TUHS 4BSD Coordinator
4.3BSD-* Maintainer
Quasijarus Project Principal Architect & Developer
Phone: 440-449-0299 or 216-217-2579
ARPA Internet SMTP mail: mxs46(a)k2.scl.cwru.edu
TUHS WWW page: http://minnie.cs.adfa.edu.au/TUHS/
Quasijarus WWW page: http://minnie.cs.adfa.edu.au/Quasijarus/
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id PAA14104
for pups-liszt; Tue, 26 Jan 1999 15:43:26 +1100 (EST)
>From Thor Lancelot Simon <tls(a)rek.tjls.com> Tue Jan 26 14:43:10 1999
Received: from mail1.panix.com (mail1.panix.com [166.84.0.212])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id PAA14099
for <pups(a)minnie.cs.adfa.edu.au>; Tue, 26 Jan 1999 15:43:16 +1100 (EST)
Received: from panix7.panix.com (root(a)panix7.nyc.access.net [166.84.0.232])
by mail1.panix.com (8.8.8/8.8.8/PanixM1.3) with ESMTP id XAA13322
for <pups(a)minnie.cs.adfa.edu.au>; Mon, 25 Jan 1999 23:43:11 -0500 (EST)
Received: (from tls@localhost) by panix7.panix.com (8.8.8/8.7.1/PanixN1.0) id XAA02557 for pups(a)minnie.cs.adfa.edu.au; Mon, 25 Jan 1999 23:43:10 -0500 (EST)
Date: Mon, 25 Jan 1999 23:43:10 -0500
From: Thor Lancelot Simon <tls(a)rek.tjls.com>
To: pups(a)minnie.cs.adfa.edu.au
Subject: Re: 4.4BSD
Message-ID: <19990125234310.A1809(a)rek.tjls.com>
Reply-To: tls(a)rek.tjls.com
References: <199901260323.WAA03123(a)skybridge.scl.cwru.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901260323.WAA03123(a)skybridge.scl.cwru.edu>; from Michael Sokolov on Mon, Jan 25, 1999 at 10:23:32PM -0500
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
On Mon, Jan 25, 1999 at 10:23:32PM -0500, Michael Sokolov wrote:
> Thor Lancelot Simon <tls(a)rek.tjls.com> wrote:
>
> > It would be nice to have the pre-4.4 (was it 4.4-alpha?) and 4.4BSD
> > distributions, as shipped by CSRG, in the archive.
>
> See my previous posting.
>
> > What would be even nicer would be the entire system as of the last
> > time it was touched -- the AT&T-encumbered system which would correspond
> > to the free 4.4BSD-Lite2 distribution which was the last public output
> > from CSRG.
>
> You'll get exactly this if you order Marshall Kirk McKusick's CSRG Archives
> CD-ROM set. The last CD-ROM is the image of CSRG's master /usr/src as it
> existed on the last second of CSRG's existence, one hour after the 4.4BSD-Lite2
> tape was pressed.
>
> > Did anyone ever build a distribution of such a system?
>
> You mean binary distribution? Well, the machine the master /usr/src was stored
> on ran this system presumably, so I guess the binaries you want existed at some
> point. Whether they have been preserved anywhere is an entirely different
> matter.
>
> > Is it feasible
> > to do so now?
>
> I suppose so. The best way to do it would probably be to bootstrap from the
> 4.4BSD tape and then recompile the system from the new source tree.
>
> > I don't have a firm grasp on which architectures would
> > actually compile and run as of that point in the SCCS files -- would
> > VAX, using the old VM system?
>
> I also have a very vague idea of what exactly can 4.4BSD-* run on. But
> definitely not VAX or Tahoe. There is no old VM in the 4.4BSD-* tree, and the
> kernel architecture has changed so much between 4.3BSD and 4.4BSD that back-
> porting it is not something I would volunteer to do.
>
> > I'd assume hp300 would work, since it
> > was the primary development platform, right?
>
> Yes.
>
> > Had the LBL SPARC port been integrated?
>
> Yes.
>
> You know, if your interest is in resurrecting CSRG, my advice to you is not to
> bother with 4.4BSD-*, but to join Quasijarus Project instead. The break point
My interest is not in "resurrecting CSRG". If I were into that kind of thing
I'd just join Jews For Jesus. My interest is pretty much purely historical.
> in the history of CSRG was in late 1988. Everything after that is so far from
> True UNIX that I have decided to put a big X over it, turn the Universe clock
> back to that point (using my SCCS Time Machine), declare all of CSRG's
> post-1988 work "not really CSRG", and declare myself CSRG's true successor.
>
> If you look at my mail signature, you'll see that I'm the new official
> maintainer of Berkeley UNIX and the principal architect of its further
> development, known as Quasijarus Project. As far as I am concerned, 4.4BSD
> never existed except as a "side branch" from True UNIX, and the last True UNIX
> release from CSRG was 4.3BSD-Tahoe. I picked it up from that point and now I'm
> maintaining and developing it just as CSRG did until 1988. I am the true
> successor of true CSRG. If you want CSRG, here I am.
I frankly consider this to be silly, somewhat presumptious, and, for myself,
at least, a waste of time. But if it's something _you_ want to do, I
encourage you to do it, I suppose.
All that I ask is that you not touch the value of the "BSD" symbol which is
exposed to the userland C namespace. The chaos which would ensue should
a "later" version of BSD appear which didn't support the full 4.4BSD feature
set is horrifying to contemplate.
Despite the great temptation to do so, neither the NetBSD nor the FreeBSD
project have taken up the mantle of CSRG and mucked around with that symbol,
nor released "4.5BSD" "5BSD", or the like. History is history. Pretending
to be an organization which doesn't exist... gets very little useful work
done. At least that's my personal take on it.
I think you'd find a substantial number of people who thought that the
"True UNIX" line ran through either SunOS 4 or 9th and 10th Edition, were
you to take a poll of as many wizards as you could summon. But it's a silly
thing to argue about, which is why I'll assert no position at all on that
issue. Similarly, I have no interest in arguing about Common LISP
versus Scheme or vi versus Emacs. Please don't tempt me with a discussion
of X versus MGR or C versus C++ and I'll avoid lecturing at you about
_my_ religious hot buttons. :-)
--
Thor Lancelot Simon tls(a)rek.tjls.com
"And where do all these highways go, now that we are free?"
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id PAA14164
for pups-liszt; Tue, 26 Jan 1999 15:57:16 +1100 (EST)
>From Greg Lehey <grog(a)lemis.com> Tue Jan 26 14:56:59 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 PAA14158
for <pups(a)minnie.cs.adfa.edu.au>; Tue, 26 Jan 1999 15:57:06 +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 PAA04633;
Tue, 26 Jan 1999 15:27:04 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id PAA93369;
Tue, 26 Jan 1999 15:26:59 +1030 (CST)
Date: Tue, 26 Jan 1999 15:26:59 +1030
From: Greg Lehey <grog(a)lemis.com>
To: Thor Lancelot Simon <tls(a)rek.tjls.com>
Cc: pups(a)minnie.cs.adfa.edu.au
Subject: Re: 4.4BSD
Message-ID: <19990126152659.I66239(a)freebie.lemis.com>
References: <199901260323.WAA03123(a)skybridge.scl.cwru.edu> <19990125234310.A1809(a)rek.tjls.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <19990125234310.A1809(a)rek.tjls.com>; from Thor Lancelot Simon on Mon, Jan 25, 1999 at 11:43:10PM -0500
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 Monday, 25 January 1999 at 23:43:10 -0500, Thor Lancelot Simon wrote:
> On Mon, Jan 25, 1999 at 10:23:32PM -0500, Michael Sokolov wrote:
>> in the history of CSRG was in late 1988. Everything after that is so far from
>> True UNIX that I have decided to put a big X over it, turn the Universe clock
>> back to that point (using my SCCS Time Machine), declare all of CSRG's
>> post-1988 work "not really CSRG", and declare myself CSRG's true successor.
>>
>> If you look at my mail signature, you'll see that I'm the new official
>> maintainer of Berkeley UNIX and the principal architect of its further
>> development, known as Quasijarus Project. As far as I am concerned, 4.4BSD
>> never existed except as a "side branch" from True UNIX, and the last True UNIX
>> release from CSRG was 4.3BSD-Tahoe. I picked it up from that point and now I'm
>> maintaining and developing it just as CSRG did until 1988. I am the true
>> successor of true CSRG. If you want CSRG, here I am.
>
> All that I ask is that you not touch the value of the "BSD" symbol which is
> exposed to the userland C namespace. The chaos which would ensue should
> a "later" version of BSD appear which didn't support the full 4.4BSD feature
> set is horrifying to contemplate.
>
> Despite the great temptation to do so, neither the NetBSD nor the FreeBSD
> project have taken up the mantle of CSRG and mucked around with that symbol,
> nor released "4.5BSD" "5BSD", or the like. History is history. Pretending
> to be an organization which doesn't exist... gets very little useful work
> done. At least that's my personal take on it.
Now you mention this, I seem to remember that BSDI registered the name
BSD as a trade mark, so you wouldn't be able to even if you wanted to.
Greg
--
See complete headers for address, home page and phone numbers
finger grog(a)lemis.com for PGP public key
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id QAA14191
for pups-liszt; Tue, 26 Jan 1999 16:01:14 +1100 (EST)
>From Greg Lehey <grog(a)lemis.com> Tue Jan 26 15:01:02 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 QAA14186
for <pups(a)minnie.cs.adfa.edu.au>; Tue, 26 Jan 1999 16:01:04 +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 PAA04650;
Tue, 26 Jan 1999 15:31:02 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.2/8.9.0) id PAA93393;
Tue, 26 Jan 1999 15:31:02 +1030 (CST)
Date: Tue, 26 Jan 1999 15:31:02 +1030
From: Greg Lehey <grog(a)lemis.com>
To: Michael Sokolov <mxs46(a)k2.scl.cwru.edu>
Cc: pups(a)minnie.cs.adfa.edu.au
Subject: Licensed microcode (was: KA650-B V1.2 CPU EPROM image)
Message-ID: <19990126153102.J66239(a)freebie.lemis.com>
References: <199901260450.XAA03161(a)skybridge.scl.cwru.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199901260450.XAA03161(a)skybridge.scl.cwru.edu>; from Michael Sokolov on Mon, Jan 25, 1999 at 11:50:33PM -0500
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 Monday, 25 January 1999 at 23:50:33 -0500, Michael Sokolov wrote:
> Let's look at things from the practical viewpoint, OK?
I think one aspect of a practical viewpoint is to acknowledge that
there are laws relating to proprietary code. It's not practical to
break these laws, no matter what you may think of them.
> One of my goals is to establish a repository containing the latest
> available microcode revision for every machine supported by my UNIX
> system.
Fine. Then negotiate with the owners of the microcode. I'd guess
that it wouldn't be as difficult as with the AU licenses. But don't
endanger others with your views on legality.
Greg
--
See complete headers for address, home page and phone numbers
finger grog(a)lemis.com for PGP public key
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id RAA14415
for pups-liszt; Tue, 26 Jan 1999 17:25:56 +1100 (EST)
>From Rick Copeland <rickgc(a)calweb.com> Wed Jan 13 16:13:50 1999
Received: from mail.calweb.com (mail.calweb.com [209.210.251.12])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id RAA14409
for <pups(a)minnie.cs.adfa.edu.au>; Tue, 26 Jan 1999 17:25:47 +1100 (EST)
Received: by mail.calweb.com (8.8.6/8.8.6) with SMTP id WAA16989;
Mon, 25 Jan 1999 22:25:39 -0800 (PST)
X-SMTP: helo rick from rickgc(a)calweb.com server @sac2-110.calweb.com ip 207.211.93.110 user=rickgc
Message-Id: <3.0.32.19990112221347.006a9f90(a)pop.calweb.com>
X-Sender: rickgc(a)pop.calweb.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Tue, 12 Jan 1999 22:13:50 -0800
To: mxs46(a)k2.scl.cwru.edu (Michael Sokolov), pups(a)minnie.cs.adfa.edu.au
From: Rick Copeland <rickgc(a)calweb.com>
Subject: Re: 4.4BSD
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
No problem!
At 09:35 PM 1/25/99 -0500, Michael Sokolov wrote:
>emanuel stiebler <emu(a)ecubics.com> wrote:
>
>> Hi all,
>> why this version isn't in the pups archive ?
>
>Generally it's my job as the TUHS 4BSD coordinator to ensure the completeness
>of TUHS 4BSD collection, but right now I can't do anything, since Rick
Copeland
>has Marshall Kirk McKusick's tapes, not me.
>
>Rick, would you please decide whether or not you are interested in reading
>_ALL_ of Marshall Kirk McKusick's tapes? If you are, please read them. If
not,
>please return them to Kirk so that someone more industrious and motivated can
>take a stab at them (I have Kirk's OK).
>
>Michael Sokolov
>TUHS 4BSD Coordinator
>4.3BSD-* Maintainer
>Quasijarus Project Principal Architect & Developer
>Phone: 440-449-0299 or 216-217-2579
>ARPA Internet SMTP mail: mxs46(a)k2.scl.cwru.edu
>TUHS WWW page: http://minnie.cs.adfa.edu.au/TUHS/
>Quasijarus WWW page: http://minnie.cs.adfa.edu.au/Quasijarus/
>
>
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id SAA14579
for pups-liszt; Tue, 26 Jan 1999 18:31:22 +1100 (EST)
Thor Lancelot Simon <tls(a)rek.tjls.com> wrote:
> It would be nice to have the pre-4.4 (was it 4.4-alpha?) and 4.4BSD
> distributions, as shipped by CSRG, in the archive.
See my previous posting.
> What would be even nicer would be the entire system as of the last
> time it was touched -- the AT&T-encumbered system which would correspond
> to the free 4.4BSD-Lite2 distribution which was the last public output
> from CSRG.
You'll get exactly this if you order Marshall Kirk McKusick's CSRG Archives
CD-ROM set. The last CD-ROM is the image of CSRG's master /usr/src as it
existed on the last second of CSRG's existence, one hour after the 4.4BSD-Lite2
tape was pressed.
> Did anyone ever build a distribution of such a system?
You mean binary distribution? Well, the machine the master /usr/src was stored
on ran this system presumably, so I guess the binaries you want existed at some
point. Whether they have been preserved anywhere is an entirely different
matter.
> Is it feasible
> to do so now?
I suppose so. The best way to do it would probably be to bootstrap from the
4.4BSD tape and then recompile the system from the new source tree.
> I don't have a firm grasp on which architectures would
> actually compile and run as of that point in the SCCS files -- would
> VAX, using the old VM system?
I also have a very vague idea of what exactly can 4.4BSD-* run on. But
definitely not VAX or Tahoe. There is no old VM in the 4.4BSD-* tree, and the
kernel architecture has changed so much between 4.3BSD and 4.4BSD that back-
porting it is not something I would volunteer to do.
> I'd assume hp300 would work, since it
> was the primary development platform, right?
Yes.
> Had the LBL SPARC port been integrated?
Yes.
You know, if your interest is in resurrecting CSRG, my advice to you is not to
bother with 4.4BSD-*, but to join Quasijarus Project instead. The break point
in the history of CSRG was in late 1988. Everything after that is so far from
True UNIX that I have decided to put a big X over it, turn the Universe clock
back to that point (using my SCCS Time Machine), declare all of CSRG's
post-1988 work "not really CSRG", and declare myself CSRG's true successor.
If you look at my mail signature, you'll see that I'm the new official
maintainer of Berkeley UNIX and the principal architect of its further
development, known as Quasijarus Project. As far as I am concerned, 4.4BSD
never existed except as a "side branch" from True UNIX, and the last True UNIX
release from CSRG was 4.3BSD-Tahoe. I picked it up from that point and now I'm
maintaining and developing it just as CSRG did until 1988. I am the true
successor of true CSRG. If you want CSRG, here I am.
BTW, it's not just that I suddenly declared myself to be the new CSRG. I earned
this title, not just assumed it. Marshall Kirk McKusick himself (the previous
maintainer of CSRG) acknowledges me as the new principal maintainer and
architect. Oh, and he doesn't even object to my decision to undo all of his and
others' 1988-1995 work with the SCCS Time Machine. He said himself in a private
E-mail that he would love to see the golden old non-bloated system resurrected.
I have used the term "True UNIX" several times in this message. Let me explain
what I mean. While others may view the history of UNIX as a tree (you hear
about UNIX history tree diagrams all the time), I view it as a straight line.
The straight line of _mainstream_ True UNIX development looks like this:
V6 (Bell) -> V7 (Bell) -> 32V (Bell) -> 3BSD (UCB) -> 4.0BSD (UCB) -> 4.1BSD
(UCB) -> 4.2BSD (UCB) -> 4.3BSD (UCB) -> 4.3BSD-Tahoe (UCB) ->
4.3BSD-Quasijarus0 (Michael Sokolov) -> future Quasijarus releases (Michael
Sokolov).
For each release the responsible entity is indicated in parentheses. There are
several things worth noting here. Notice how after V7 and 32V the torch of True
UNIX development moves from Bell to UCB, never to return to Bell again. This is
because everything Bell did after that (System V and such) deviates from the
True UNIX ideology and loses the True UNIX torch. In late 1970s or early 1980s
UCB picks up this torch and carries it until 1988. In 1988 UCB starts deviating
from True UNIX too with the evil spirit of POSIX and everything, and loses the
torch. The torch was laying on the ground from that point until the 27th of
December 1998 when I picked it up with the 4.3BSD-Quasijarus0 release. Now I'm
carrying it into the next millennium.
Check out the Quasijarus Project WWW page referenced in my mail signature.
Michael Sokolov
TUHS 4BSD Coordinator
4.3BSD-* Maintainer
Quasijarus Project Principal Architect & Developer
Phone: 440-449-0299 or 216-217-2579
ARPA Internet SMTP mail: mxs46(a)k2.scl.cwru.edu
TUHS WWW page: http://minnie.cs.adfa.edu.au/TUHS/
Quasijarus WWW page: http://minnie.cs.adfa.edu.au/Quasijarus/
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id OAA13519
for pups-liszt; Tue, 26 Jan 1999 14:17:20 +1100 (EST)
<> Get that out of there fast, it's copyrighted firmware!
<
<The PUPS archive already contains some PDP-11 boot/diag/etc. odds and ends.
<not have VAX ones too?
Yes but, not copyrighted firmware. The KA650 B V1.2 firmware is not
released or granted publication that I know of and the straw horse of,
"well, PDP-xx is here" is not the issue.
<BTW, there is a long tradition of shipping DEC odds and ends with UNIX. Jus
<look at pcs750.bin, or at DEC-contributed device drivers in 4.3BSD, or at t
There is a distinct difference between DEC contributed and the KA650 rom
image.
<fact that if you do a strings(1) on 4.3BSD /genvmunix, you'll see DEC's
<copyright and the word "ULTRIX" in a whole bunch of places. Ancient UNIX an
<Ancient DEC live together very well. Please don't separate them. If our gro
<(PUPS/TUHS) loves and cares for Ancient UNIX, we should also love and care
<Ancient DEC.
It is neither the point nor applicable. It's a specious arguement in an
attempt to not respect the copyrighted firmware on the CPU card that is
not distributed. The fact that DEC and unix go well is not the issue
either.
<And finally, some of the files in my odds-ends directory were originally
<recovered from some BSD distribution (the ULTRIX rabads program, which desp
<its DEC copyright, ULTRIX origin, and binary-only nature came with some BS
<distributions).
I doubt that the KA650 bootrom image was in there as original distribution.
If the system is a KA650 it would be available on the system and if it is
not it's meaningless. My comment earlier was directly and specifically
aimed at the KA650 B V1.2 Eprom image.
The problem is that failure to respect the copyrights and ownerships of
any code, especially firmware could lead to vendors taking a future
hostile stance to the work of PUPS. That would be very undesireable.
Allison
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id PAA14043
for pups-liszt; Tue, 26 Jan 1999 15:37:02 +1100 (EST)
emanuel stiebler <emu(a)ecubics.com> wrote:
> Hi all,
> why this version isn't in the pups archive ?
Generally it's my job as the TUHS 4BSD coordinator to ensure the completeness
of TUHS 4BSD collection, but right now I can't do anything, since Rick Copeland
has Marshall Kirk McKusick's tapes, not me.
Rick, would you please decide whether or not you are interested in reading
_ALL_ of Marshall Kirk McKusick's tapes? If you are, please read them. If not,
please return them to Kirk so that someone more industrious and motivated can
take a stab at them (I have Kirk's OK).
Michael Sokolov
TUHS 4BSD Coordinator
4.3BSD-* Maintainer
Quasijarus Project Principal Architect & Developer
Phone: 440-449-0299 or 216-217-2579
ARPA Internet SMTP mail: mxs46(a)k2.scl.cwru.edu
TUHS WWW page: http://minnie.cs.adfa.edu.au/TUHS/
Quasijarus WWW page: http://minnie.cs.adfa.edu.au/Quasijarus/
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id OAA13461
for pups-liszt; Tue, 26 Jan 1999 14:09:52 +1100 (EST)
allisonp(a)world.std.com (Allison J Parent) wrote:
> Get that out of there fast, it's copyrighted firmware!
The PUPS archive already contains some PDP-11 boot/diag/etc. odds and ends. Why
not have VAX ones too?
But if too many people start complaining, I'll just move the entire odds-ends
directory to one of my friend's _anonymous_ FTP site.
BTW, there is a long tradition of shipping DEC odds and ends with UNIX. Just
look at pcs750.bin, or at DEC-contributed device drivers in 4.3BSD, or at the
fact that if you do a strings(1) on 4.3BSD /genvmunix, you'll see DEC's
copyright and the word "ULTRIX" in a whole bunch of places. Ancient UNIX and
Ancient DEC live together very well. Please don't separate them. If our group
(PUPS/TUHS) loves and cares for Ancient UNIX, we should also love and care for
Ancient DEC.
And finally, some of the files in my odds-ends directory were originally
recovered from some BSD distribution (the ULTRIX rabads program, which despite
its DEC copyright, ULTRIX origin, and binary-only nature came with some BSD
distributions).
Michael Sokolov
TUHS 4BSD Coordinator
4.3BSD-* Maintainer
Quasijarus Project Principal Architect & Developer
Phone: 440-449-0299 or 216-217-2579
ARPA Internet SMTP mail: mxs46(a)k2.scl.cwru.edu
TUHS WWW page: http://minnie.cs.adfa.edu.au/TUHS/
Quasijarus WWW page: http://minnie.cs.adfa.edu.au/Quasijarus/
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id MAA13004
for pups-liszt; Tue, 26 Jan 1999 12:22:35 +1100 (EST)
>From "emanuel stiebler" <emu(a)ecubics.com> Tue Jan 26 11:21:38 1999
Received: from biz1.mailsrvcs.net (biz1.gte.net [207.115.153.50])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id MAA12999
for <pups(a)minnie.cs.adfa.edu.au>; Tue, 26 Jan 1999 12:22:27 +1100 (EST)
Received: from p2350 ([208.250.164.80]) by biz1.mailsrvcs.net
(Post.Office MTA v3.1.2 release (PO203-101c) ID# 0-40549L5000S0)
with ESMTP id AAA24603 for <pups(a)minnie.cs.adfa.edu.au>;
Mon, 25 Jan 1999 19:22:21 -0600
From: "emanuel stiebler" <emu(a)ecubics.com>
To: <pups(a)minnie.cs.adfa.edu.au>
Subject: 4.4BSD
Date: Mon, 25 Jan 1999 18:21:38 -0700
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1161
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID: <19990126012214.AAA24603@p2350>
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Hi all,
why this version isn't in the pups archive ?
cheers,
emanuel
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id NAA13171
for pups-liszt; Tue, 26 Jan 1999 13:05:32 +1100 (EST)
>From Thor Lancelot Simon <tls(a)rek.tjls.com> Tue Jan 26 12:05:12 1999
Received: from mail2.panix.com (mail2.panix.com [166.84.0.213])
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id NAA13165
for <pups(a)minnie.cs.adfa.edu.au>; Tue, 26 Jan 1999 13:05:22 +1100 (EST)
Received: from panix7.panix.com (root(a)panix7.nyc.access.net [166.84.0.232])
by mail2.panix.com (8.8.8/8.8.8/PanixM1.3) with ESMTP id VAA17162
for <pups(a)minnie.cs.adfa.edu.au>; Mon, 25 Jan 1999 21:05:12 -0500 (EST)
Received: (from tls@localhost) by panix7.panix.com (8.8.8/8.7.1/PanixN1.0) id VAA23416 for pups(a)minnie.cs.adfa.edu.au; Mon, 25 Jan 1999 21:05:12 -0500 (EST)
Date: Mon, 25 Jan 1999 21:05:12 -0500
From: Thor Lancelot Simon <tls(a)rek.tjls.com>
To: pups(a)minnie.cs.adfa.edu.au
Subject: Re: 4.4BSD
Message-ID: <19990125210512.A22884(a)rek.tjls.com>
Reply-To: tls(a)rek.tjls.com
References: <19990126012214.AAA24603@p2350>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <19990126012214.AAA24603@p2350>; from emanuel stiebler on Mon, Jan 25, 1999 at 06:21:38PM -0700
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
On Mon, Jan 25, 1999 at 06:21:38PM -0700, emanuel stiebler wrote:
> Hi all,
> why this version isn't in the pups archive ?
>
> cheers,
> emanuel
It would be nice to have the pre-4.4 (was it 4.4-alpha?) and 4.4BSD
distributions, as shipped by CSRG, in the archive.
What would be even nicer would be the entire system as of the last
time it was touched -- the AT&T-encumbered system which would correspond
to the free 4.4BSD-Lite2 distribution which was the last public output
from CSRG.
Did anyone ever build a distribution of such a system? Is it feasible
to do so now? I don't have a firm grasp on which architectures would
actually compile and run as of that point in the SCCS files -- would
VAX, using the old VM system? I'd assume hp300 would work, since it
was the primary development platform, right? Had the LBL SPARC port
been integrated?
--
Thor Lancelot Simon tls(a)rek.tjls.com
"And where do all these highways go, now that we are free?"
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id NAA13220
for pups-liszt; Tue, 26 Jan 1999 13:21:38 +1100 (EST)
<I have added the EPROM image from my KA650-B V1.2 CPU to the VAX firmware
<collection in Distributions/4bsd/odds-ends in the PUPS archive.
Get that out of there fast, it's copyrighted firmware!
Allison
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id MAA12960
for pups-liszt; Tue, 26 Jan 1999 12:11:38 +1100 (EST)
Dear PUPS/TUHS members,
I have added the EPROM image from my KA650-B V1.2 CPU to the VAX firmware
collection in Distributions/4bsd/odds-ends in the PUPS archive.
Sincerely,
Michael Sokolov
Phone: 440-449-0299
ARPA Internet SMTP mail: mxs46(a)k2.scl.cwru.edu
