The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wobblygong@gmail.com (Wesley Parish)
Subject: [TUHS] Various Unix
Date: Wed, 20 Dec 2017 21:25:22 +1300	[thread overview]
Message-ID: <CACNPpeaXOzoKRdPd3wDNHG7PA4hooQxoNU-NC0_YeaXFDSZOWA@mail.gmail.com> (raw)
In-Reply-To: <20171219171345.59efbf33@cnb.csic.es>

I've just dropped in to the QNX Foundry27 FAQ page:
https://community.qnx.com/sf/wiki/do/viewPage/projects.community/wiki/FAQ

" I want to access the source code, how can I?#
QSS classifies proprietary QNX source code as either Open (available
to anyone under an open source license), Accessible (available to
registered users on the QNX Source project), or Restricted (please
contact your QSS Sales or Support contact to request access).

Source code is available through the SVN Web interface. To do so,
access the desired project, select its 'Source Code' section, select
the repository, select 'View Commits', then select 'Browse
Repository'.

Registered members can access the Subversion repository using any
Subversion client application. Such a client is offered as part of the
QNX Momentics IDE.



Is this open source?#

Simple answer is 'no'. But the complete answer is 'sometimes' since
each Foundry27 project is free to expose its technology under its
sponsor's own licensing terms. As an example, some of the BSPs
delivered as part of the BSPs and Drivers project are published under
the terms of the Apache 2.0 license; these are clearly open source.
The QSS components delivered as part of the QNX Operating System
project can be considered very close to open within the QNX
development community with access to Restricted code; their source is
published, the binaries are available, the source code can be modified
and even redistributed to other QSS licensed developers. More details
are available at the Community Redistribution page at
http://licensing.qnx.com/.  "

FWIW

Wesley Parish

On 12/20/17, Jose R. Valverde <jrvalverde at cnb.csic.es> wrote:
> Before we had to phase out our FTP server, I kept on it several
> versions of UNIX clones and related OS that were mostly not on TUHS.
> This post is to remember some of these systems. Many of these were
> open sourced or widely available at some time and were related to UNIX
> one way or another. I may not have the latest versions or all the
> versions, but at least I do keep something.
>
> The following ones have been open sourced at some point in time (I
> believe):
>
> 	ChorusOS
> 	Coherent
> 	EXOS
> 	L4
> 	Lunix
> 	MaRTE-OS
> 	Mach
> 	OpenBLT
> 	OpenSolaris
> 	Sprite	(I also own the original distribution CD)
> 	Trix
> 	UniFlex
> 	agnix
> 	amoeba
> 	bkunix
> 	bsd386
> 	hurd
> 	iunix
> 	jaluna-c5
> 	lsx-unix
> 	mini-unix
> 	minix
> 	omu
> 	opensolaris
> 	starunix
> 	thix
> 	from tliquest.net/local/unix: uzi and various other bits
> 	tme
> 	tropix
> 	tunix
> 	unix-v8
> 	unix-wega
> 	uzi
> 	xhomer
> 	xinu
> 	xv6
> 	yoctix
>
> Plus several archaic CDs with early versions of Linux,
> Open/Free/NetBSD, (Walnut Creek, InfoMagic, etc. CD/ROMs)
> and even the Beowulf/Extreme Linux CDs (plus I must keep around the
> mirror we hosted for a long time of the Beowulf site). The hobbyist CDs
> for OpenSolaris 8 (and I believe 9) with sources. Oh, and
> MOSIX/OPENMOSIX.
>
>
> In addition, I have many other sources whose Copyright status I'm not
> aware of, but which are interesting for archival purposes.
>
> Regarding QNX, yes, it was open sourced (at least for hobbyist use, I
> have to check the license) for several distributions. I ported some
> bioinformatics software and kept for some time a distribution
> repository, and I'm pretty certain I must have the sources as well as
> the virtual machines. I'll try to verify the licenses to see if it can
> be redistributed, although I doubt they can. Oh, and I also own the
> mentioned famous 3.5" diskette. I think I digitized it long ago. Would
> have to check.
>
> Off the Net, it has been possible, one time or another, to recover
> executables and, sometime, even sources, of many systems. Archive.org
> has -I believe- a copy of a once famous repo of abandonware with
> binaries of SCO, System V, AIX, etc...
>
> I know that AIX, ATT systemV vI, II, III and IV, Solaris V6, Tru64,
> OSF-1, Dynix, Ultrix 11, BSDI, Ultrix-32 etc... have been out there at
> some time or another in source code format, and binaries of IRIX, Lisa,
> QNX, A/UX, xenix...
>
> Some years ago, I had more free time and could test many systems on
> emulators, and built images and accompanying scripts ready ti run. I
> also made some tools to be able to transfer data in and out of old
> unix versions (so I could edit the software off the virtual machine
> while back-porting a screen editor to V6, v5, etc... with only vt100
> support).
>
> Not UNIX-related, I also keep copies of many other ancient operating
> systems and software and hardware emulators.
>
>
> Well, as I said at the beginning, everything that I had, I should still
> keep while the hard disks continue spinning. If there is any
> interest in adding any of these to TUHS, I can try to find a way to
> send it all.
>
> If I find time to browse through everything, I would like to upload all
> the source code to GitHub (at least anything that's redistributable).
> If I find the time...
>
> But, Warren, if you are interested in anything, let me know and I'll
> find a way to give you access.
>
> 				 j
>
> --
> 		Scientific Computing Service
> 	Solving all your computer needs for Scientific
> 			Research.
>
> 		http://bioportal.cnb.csic.es
>


      reply	other threads:[~2017-12-20  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 16:13 Jose R. Valverde
2017-12-20  8:25 ` Wesley Parish [this message]

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=CACNPpeaXOzoKRdPd3wDNHG7PA4hooQxoNU-NC0_YeaXFDSZOWA@mail.gmail.com \
    --to=wobblygong@gmail.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).