From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] 386BSD on Bochs & Qemu...
Date: Mon, 26 Apr 2010 13:23:03 +1000 [thread overview]
Message-ID: <20100426032303.GC15137@dereel.lemis.com> (raw)
In-Reply-To: <5a7c3451f8bbb8efaaa6b9c809214a55.squirrel@webmail.xs4all.nl>
On Sunday, 25 April 2010 at 11:28:29 +0200, Jacob Goense wrote:
>>> It got me curious about where 386BSD ended though. Did anyone save
>>> the 386BSD Reference CD-ROM Release 1.0 from /dev/null?
>>
>> Yes, I have a copy. It was pretty much useless. All the
>> documentation was in some Microsoft format, and I couldn't read it.
>> Unfortunately Dr Dobbs has a copyright on it, or I could upload it for
>> the curious.
>
> That's about what I understood from as well from reading this column
> at http://www.cfcl.com/rdm/tin/P/199503.shtml
>
> "The 386BSD release CD-ROM includes a mixture of BSD and Jolitz code,
> articles, and what have you. The files are hyperlinked with a global
> glossary and index to illustrate the structure and interdependence in
> the discussion of the system files.
>
> Consequently, the CD-ROM release is not freeware, as a whole, though
> many parts of it are freely redistributable. In particular, the system
> itself will be available at certain "official" Internet sites,
> still(unfortunately) to be determined at press time."
>
> and I have dug around long enough to assume that 15 years later it is
> still TBD where to get just the system.
OK, I mounted the CD-ROM and looked for copyright statements. The
only one I found was /COPYRGHT.TXT, a modified 8 paragraph BSD license
with \r\n line delimiters, attached.
Arguably it only applies to the OS sources, but it's the only license
I can see. It probibits commercial distributions, but the important
clause from our point of view is:
* 5. Non-commercial distribution of the complete source and/or binary
* release at no charge to the user (such as from an official Internet
* archive site) is permitted.
I was going to take out just the source tree, but another clause
states:
* 7. Non-commercial and/or commercial distribution of an incomplete,
* altered, or otherwise modified source and/or binary release is not
* permitted.
Since this is the only copyright statement, I assume that this means I
can put up the entire CD image, but not just part of it, so that's
what I've done. It's at http://www.lemis.com/grog/src/386BSD-1.0.bz2 .
If anybody finds anything that indicates that it shouldn't be made
available, please let me know and I'll pull it.
Greg
--
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. See
http://www.lemis.com/grog/email/signed-mail.php for more details.
If your Microsoft MUA reports problems, please read
http://tinyurl.com/broken-mua
-------------- next part --------------
386BSD Release 1.0
Copyright
/*
* Copyright (c) 1989-1994 William F. Jolitz, TeleMuse.
* All Rights Reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this
* software must display the following acknowledgement:
* This software is a component of "386BSD" developed by
* William F. Jolitz, TeleMuse.
* 4. Neither the name of the developer nor the name "386BSD"
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
* 5. Non-commercial distribution of the complete source and/or binary
* release at no charge to the user (such as from an official Internet
* archive site) is permitted.
* 6. Commercial distribution and sale of the complete source and/or binary
* release on any media, including that of floppies, tape, or CD-ROM, or
* through a per-charge download such as that of a BBS, is not permitted
* without specific prior written permission.
* 7. Non-commercial and/or commercial distribution of an incomplete,
* altered, or otherwise modified source and/or binary release is not
* permitted.
* 8. Non-commercial and/or commercial incorporation and distribution of
* any components, programs, files, and other modules derived from the
* source and/or binary release is not permitted without specific prior
* written permission, except where stated by the author as in the
* copyright disclaimer of the source code component, program, file, or
* other module in question.
*
* 386BSD WAS DEVELOPED BY WILLIAM F. JOLITZ.
* 386BSD IS INTENDED FOR RESEARCH AND EDUCATIONAL PURPOSES.
* THIS SOFTWARE SHOULD NOT BE CONSIDERED TO BE A COMMERCIAL PRODUCT.
* THE DEVELOPER URGES THAT USERS WHO REQUIRE A COMMERCIAL PRODUCT
* NOT MAKE USE OF THIS WORK.
*
* FOR USERS WHO WISH TO UNDERSTAND THE 386BSD SYSTEM DEVELOPED
* BY WILLIAM F. JOLITZ, WE RECOMMEND THE USER STUDY WRITTEN
* REFERENCES SUCH AS THE "PORTING UNIX TO THE 386" SERIES
* (BEGINNING JANUARY 1991 "DR. DOBBS JOURNAL", USA AND BEGINNING
* JUNE 1991 "IX MAGAZIN", FORMERLY "UNIX MAGAZIN", GERMANY) BY
386BSD Copyright 1 August 1994
* WILLIAM AND LYNNE JOLITZ, THE "386BSD REFERENCE CD-ROM" KERNEL SOURCE
* ANNOTATIONS AND OTHER 386BSD MATERIALS AND WRITINGS BY WILLIAM & LYNNE
* JOLITZ, AS WELL AS OTHER BOOKS ON UNIX AND THE ON-LINE 386BSD
* USER MANUAL BEFORE USE. A BOOK DISCUSSING THE INTERNALS OF 386BSD
* RELEASE 1.0 ENTITLED "386BSD FROM THE INSIDE OUT" IS PENDING.
*
* THIS SOFTWARE IS PROVIDED BY THE DEVELOPER ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE DEVELOPER BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
* ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
* OF SUCH DAMAGE.
*
* Any questions regarding this copyright notice may be directed to:
* Lynne Greer Jolitz
* 386BSD Release 1.0
* c/o Dr. Dobbs Journal
* 411 Borel Avenue
* San Mateo, California 94402 USA
* +1-510-420-0174 (FAX)
*
*/
386BSD Copyright 2 August 1994
\x1a
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20100426/5c77bf4c/attachment.sig>
next prev parent reply other threads:[~2010-04-26 3:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 5:12 Jason Stevens
2010-04-17 19:10 ` Natalia Portillo
2010-04-18 1:12 ` Jason Stevens
2010-04-24 14:28 ` Jacob Goense
2010-04-24 18:06 ` Jason Stevens
2010-04-24 20:59 ` Tom Ivar Helbekkmo
2010-04-25 2:29 ` Greg 'groggy' Lehey
2010-04-25 9:28 ` Jacob Goense
2010-04-25 17:32 ` Carl Lowenstein
2010-04-25 17:36 ` Jason Stevens
2010-04-26 3:23 ` Greg 'groggy' Lehey [this message]
2010-04-26 5:22 ` Jason Stevens
2010-05-04 19:37 ` Jacob Goense
2010-05-04 19:41 ` Natalia Portillo
2010-05-04 18:26 ` Jacob Goense
2010-04-26 7:03 ` Wesley Parish
2010-04-26 8:07 ` Greg 'groggy' Lehey
2010-04-26 9:33 ` Wesley Parish
2010-04-26 17:52 ` Jason Stevens
2010-04-28 2:30 ` Cyrille Lefevre
2010-04-30 7:58 ` [TUHS] UniFlex Jose R. Valverde
2010-04-30 15:38 ` Brad Spencer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100426032303.GC15137@dereel.lemis.com \
--to=grog@lemis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).