The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dds@aueb.gr (Diomidis Spinellis)
Subject: [TUHS] Illumos )
Date: Wed, 31 Dec 2014 19:42:23 +0200	[thread overview]
Message-ID: <54A4357F.9040703@aueb.gr> (raw)
In-Reply-To: <20141231131335.GA26926@mercury.ccil.org>

On 31/12/2014 15:13, John Cowan wrote:
> Wesley Parish scripsit:
>
>> [The] primary importance [of Solaris forks], from my POV, is that they
>> keep the POSIX space open for experimentation: a Linux monoculture's
>> as deadening as a MS Windows monoculture or a \[choose your own poison\]
>> monoculture ...
>
> Well, BSD does that.  But Solaris is the only descendant of System V for
> which we have source, which means that in non-Posix cases it can give
> us helpful information how the original Unix code fared after leaving
> the Labs.  By comparison, both Linux and BSD are clones.

Thank you for stressing the importance of Solaris as a Unix descendant 
for which source code is available.  It's a pity that we don't have 
public source code for the Solaris versions 2.1 to 10, so there's a 15 
year gap between System V R4 and the first release of Open Solaris.

I don't agree that BSD systems are a clone of Unix.  There are bits in 
them that were written at Bell Labs.  The earliest example I've found up 
to now comes from timezone.c, and was written at least 36 years ago 
(1979-01-10 14:58:45).

Compare the 7th Edition implementation of timezone()

http://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/libc/gen/timezone.c

with lines 110-128 of the current FreeBSD _tztab() implementation.

https://github.com/freebsd/freebsd/blob/master/lib/libc/gen/timezone.c

(How did I find it?  For the past six months I've been running git blame 
on various tags of https://github.com/dspinellis/unix-history-repo.)

Happy new year everybody!

-- 
Diomidis Spinellis      http://www.spinellis.gr



  reply	other threads:[~2014-12-31 17:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-31  6:22 Larry McVoy
2014-12-31  9:28 ` Wesley Parish
2014-12-31 13:13   ` John Cowan
2014-12-31 17:42     ` Diomidis Spinellis [this message]
2014-12-31 20:32       ` Clem Cole
2014-12-31 20:36         ` Larry McVoy
2014-12-31 22:19           ` Jacob Ritorto
2014-12-31 22:42             ` Larry McVoy
2014-12-31 22:50               ` Larry McVoy
2015-01-01  1:17                 ` Larry McVoy
2015-01-01  1:34                   ` Erik E. Fair
2015-01-05 12:02               ` Tim Bradshaw
2015-01-05 17:04                 ` Jacob Ritorto
2015-01-06  4:54                   ` Andy Kosela
2015-01-06 11:10                     ` Kurt H Maier
2015-01-06 15:37                   ` Tim Bradshaw
2015-01-09  9:23                     ` Jose R. Valverde
2015-01-06 21:58                   ` Clem Cole
2015-01-06 22:02                     ` [TUHS] pre-FSCK days Ronald Natalie
2015-01-07  1:53                     ` [TUHS] Illumos ) Dave Horsfall
2015-01-07 16:26                       ` Clem Cole
2015-01-07 18:32                         ` scj
2015-01-16  8:40                       ` [TUHS] sync; sync; sync; halt (was: Re: Illumos )) Tom Ivar Helbekkmo
2015-01-16 13:39                         ` random832
2015-01-16 14:14                           ` Brantley Coile
2014-12-31  9:46 ` [TUHS] Illumos ) arnold

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=54A4357F.9040703@aueb.gr \
    --to=dds@aueb.gr \
    /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).