From: jcapp@anteil.com (Jim Capp)
Subject: [TUHS] SVR4 x86 -- Sources
Date: Mon, 11 Jul 2011 08:53:02 -0400 (EDT) [thread overview]
Message-ID: <19113151.8438.1310388782327.JavaMail.root@zimbraanteil> (raw)
In-Reply-To: <CAHfSdrU9vK2uZqz4+9XxkqQiy7evcad4iWgbDgBtKXu90nvvUg@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
Michele,
Some time ago, SCO made its source code available under an "Ancient UNIX" license. That is also very close to SVR4. I don't have the details at hand, but perhaps someone on this list does.
Is there a reason you need to see the source code specifically for SVR4?
Cheers,
Jim
----- Original Message -----
From: "Michael Kerpan" <madcrow.maxwell@gmail.com>
To: "Michele Ghisolfo" <ghisolfo.m at gmail.com>
Cc: TUHS at minnie.tuhs.org
Sent: Monday, July 11, 2011 8:42:45 AM
Subject: Re: [TUHS] SVR4 x86 -- Sources
On Mon, Jul 11, 2011 at 6:29 AM, Michele Ghisolfo <ghisolfo.m at gmail.com> wrote:
> Hi,
>
> I'm currently reading J. Lion's commentary of Unix Code Level Six. It
> is the most useful commentary to operating system kernel I have ever
> read.
>
> It would be really useful to also have the source code of SVR4 kernel
> for Intel x86. Does anyone have that?
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
OpenSolaris is derived from SVR4 and much of the userland stuff is
still quite similar to the original release. Sadly, System V as a
whole is still regarded as a commercial product and no source is
available. If you want the source code for a decent early-90s Unix
implementation, I'd take a look at 4.4BSD. It's not SVR4, but it's
from the same era and has many of the same abilities.
Mike
_______________________________________________
TUHS mailing list
TUHS at minnie.tuhs.org
https://minnie.tuhs.org/mailman/listinfo/tuhs
next prev parent reply other threads:[~2011-07-11 12:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 10:29 Michele Ghisolfo
2011-07-11 12:42 ` Michael Kerpan
2011-07-11 12:53 ` Jim Capp [this message]
2011-07-14 17:42 ` Al Kossow
2011-07-14 17:46 ` Jason Stevens
2011-07-15 4:10 ` Random832
2011-07-15 4:22 ` John Cowan
2011-07-12 7:54 ` Wesley Parish
2011-07-12 9:53 ` Nick Downing
2011-07-19 23:17 ` Doug McIntyre
2011-07-20 0:42 ` Larry McVoy
2011-07-20 3:16 ` John Cowan
2011-07-20 4:04 ` Warner Losh
2011-07-12 9:57 ` Nick Downing
2011-07-12 11:22 ` Tim Bradshaw
2011-07-12 11:54 ` Nick Downing
2011-07-11 12:50 ` Sergio Aguayo
[not found] ` <4E1B6A45.40607@laposte.net>
2011-07-11 19:50 ` Michele Ghisolfo
2011-07-11 21:56 ` Jason Stevens
2011-07-11 20:08 ` Michele Ghisolfo
2011-07-11 22:56 ` Warren Toomey
2011-07-12 13:04 ` Milo Velimirović
2011-07-12 13:07 ` Jason Stevens
[not found] <1310385759.2145.18.camel@localhost.localdomain>
2011-07-11 14:09 ` Sergio Aguayo
2011-07-12 13:24 Norman Wilson
2011-07-12 15:11 Michele Ghisolfo
2011-07-12 23:26 ` Larry McVoy
2011-07-13 0:23 ` Jason Stevens
2011-07-13 13:25 ` Arno Griffioen
2011-07-13 2:48 ` John Cowan
2011-07-13 3:07 ` Larry McVoy
2011-07-14 17:37 ` Al Kossow
2011-07-15 4:30 ` Warren Toomey
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=19113151.8438.1310388782327.JavaMail.root@zimbraanteil \
--to=jcapp@anteil.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).