From: dugo@xs4all.nl (Jacob Goense)
Subject: [TUHS] 386BSD on Bochs & Qemu...
Date: Tue, 4 May 2010 20:26:52 +0200 [thread overview]
Message-ID: <97c86725a66a6581c02553876124c880.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <20100426032303.GC15137@dereel.lemis.com>
On Mon, April 26, 2010 05:23 "Greg 'groggy' Lehey" <grog at lemis.com> wrote:
> 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.
Indeed, it can be argued that the statement refers to 386BSD Release 1.0
sec, not the 386BSD Reference CD-ROM as a whole, but it is hard to draw
a line, if any.
> 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.
Same issue here, would excluding eg. .book & .articles make the Release
incomplete or not?
> 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 .
The only thing I could find that makes some sort of demarcation is the
installer, which leaves some bits behind when doing a full install.
Without vehement arguing from stakeholders or copyright lawyers to the
contrary I assume the same and thank you for putting it up there.
/Jacob
next prev parent reply other threads:[~2010-05-04 18:26 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
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 [this message]
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=97c86725a66a6581c02553876124c880.squirrel@webmail.xs4all.nl \
--to=dugo@xs4all.nl \
/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).