The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] SunOS vs Linux
Date: Tue, 10 Jan 2017 12:02:45 +0100	[thread overview]
Message-ID: <5874bf55.S65Cf/vLEnr+muVU%schily@schily.net> (raw)
In-Reply-To: <CACwAiQ=OLbvque4Jg_byK9c7O+h7_3zav40euCzDzCGfKT2tug@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3433 bytes --]

Rico Pajarola <rp at servium.ch> wrote:

> Now stop picking on Joerg already. Not every university was invested in
> Unix. In practice Unix source was pretty much unobtainable if you happened
> to live outside of the "Unix bubble".
>
> I grew up and went to school/university in Switzerland, and getting access
> to UNIX source was nothing but a crazy pipe dream at the time. I don't even
> know if my university had a source license (I can't imagine they didn't),
> but in any case it wasn't something that they would let you use as a normal
> student. None of my inquiries at the time resulted in anything that would
> allow me to get access to Unix source. If the university had it, this
> wasn't public information, and they didn't share. I couldn't prove that my
> university had a license, and I had no way to get the actual bits. This was
> the 90ies btw.

Well, I did not say that it was easy and that every university did have source 
access, but universities that had people who have been interested in UNIX did 
usually try to get source access.

It did take time to get it and I remember that TU-Berlin received the Svr2 
sources when AT&T launched Svr3.

In order to get SunOS source code, you needed to have a AT&T source license and 
another from Sun. This was close to impossible for a smaller company......

On the other side, Sun did give away parts of the SunOS source that was not 
based on AT&T code. If you have been a big OEM (and H.Berthold AG was a big 
OEM) you received what Sun believed was helpful for business. I e.g. received 
the keyboard driver in spring 1986 and I wrote the enhancements to support 155 
keys from the Berthold keyboard and to switch layouts for different languages.

In January 1986, I received a one sheet of paper description for a SCSI VME 
board that was made of a DMA chip and a few PALs. I wrote a SCSI driver and we 
demonstrated a SCSI interface to our high resolution scanner at the "Drupa"
fair in April 1986 in Düsseldorf. The demo used a diskless client machine as I 
could either bind the Sun SCSI framework into the kernel or mine and then we 
could no longer access disks. 

Sun mamagers attended that fair and a few weeks later, I had access to the Sun 
SCSI driver framework and to Matthew Jacobs - the architect of that code. This 
resulted in my "scg" driver, the first SCSI pass through driver that I used to
e.g. format disks while the kernel was running. Sun at that time had to boot a 
standalone program for disk formatting, but Sun did take my idea after I 
explained it to Matthew Jacobs.

Even with these connections, I was not able to get a AT&T source license for a 
complete SunOS kernel source. This was because IIRC the AT&T license did cost 
200000 $ for non-university entities and H.Berthold AG would not spend that 
much money for a source license. Here Horst Winterhoff helped and asked Bill 
Joy whether he could give me the sources for my dimploma thesis.

So you are right, you had to be somehow connected to the right people to get 
source access. But people who have been interested usually have been 
connected...even though the world was harder to explore these days.

Jörg

-- 
 EMail:joerg at schily.net                  (home) Jörg Schilling D-13353 Berlin
       joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/


  reply	other threads:[~2017-01-10 11:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 17:08 Clem Cole
2017-01-06  2:32 ` ron minnich
2017-01-06  3:56 ` Dan Cross
2017-01-06  3:58   ` Larry McVoy
2017-01-06 14:27   ` Clem Cole
2017-01-07  2:58     ` Greg 'groggy' Lehey
2017-01-07  3:09       ` Warner Losh
2017-01-07  3:13         ` Larry McVoy
2017-01-07  3:12       ` Larry McVoy
2017-01-08 16:28   ` Angus Robinson
2017-01-08 18:02     ` Kay Parker   
2017-01-08 20:51       ` Clem cole
2017-01-09  3:00         ` Greg 'groggy' Lehey
2017-01-09  6:32           ` Arno Griffioen
2017-01-09  8:27             ` Wesley Parish
2017-01-09 13:07             ` Joerg Schilling
2017-01-09 15:57             ` Clem Cole
2017-01-09 16:08               ` ron minnich
2017-01-09 17:40                 ` Dan Cross
2017-01-09 17:32               ` Rico Pajarola
2017-01-10 11:02                 ` Joerg Schilling [this message]
2017-01-08 22:52     ` Wesley Parish
2017-01-09 19:45   ` Jacob Goense
2017-01-08  6:10 Kirk McKusick
2017-01-08 14:52 ` Ron Natalie

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=5874bf55.S65Cf/vLEnr+muVU%schily@schily.net \
    --to=schily@schily.net \
    /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).