The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] Illumos )
Date: Wed, 31 Dec 2014 22:28:35 +1300 (NZDT)	[thread overview]
Message-ID: <1420018115.54a3c1c32faaa@www.paradise.net.nz> (raw)
In-Reply-To: <20141231062219.GA21046@mcvoy.com>

Illumos is a branch (or fork: I'm not sure which word is most appropriate here)
of OpenSolaris: if my memory serves me right (always a bit ask) it's a
debianized OpenSolaris
http://wiki.illumos.org/display/illumos/illumos+Home

OpenIndiana is another such project
http://openindiana.org/

and I think there are some other OpenSolaris branch/fork tree available, but i
don't know anything about them. Their primary importance, 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 ...

Wesley Parish

Quoting Larry McVoy <lm at mcvoy.com>:

> Yo Jacob,
> 
> I'm ex-sun but I don't know too much about Illumos. Care to give us 
> the summary of why I might care about it?
> 
> On Wed, Dec 31, 2014 at 01:16:00AM -0500, Jacob Ritorto wrote:
> > Hey, thanks, Derrik.
> > I don't mess with Linux much (kind of an Illumos junkie by trade ;),
> but
> > I bet gcc would. I did out of curiosity do it with the Macintosh cc
> (Apple
> > LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)) and it
> throws
> > warnings about our not type-defining functions because you're
> apparently
> > supposed to do this explicitly these days, but it dutifully goes on
> to
> > assume int and compiles our test K&R stuff mostly fine. It does
> > unfortunately balk pretty badly at the naked returns we initially
> had,
> > though. Wish it didn't because it strikes me as being beautifully
> simple..
> > 
> > thx again for the encouragement!
> > jake
> > 
> > 
> > On Wed, Dec 31, 2014 at 1:02 AM, Derrik Walker v2.0
> <dwalker at doomd.net>
> > wrote:
> > 
> > > On Wed, 2014-12-31 at 00:44 -0500, Jacob Ritorto wrote:
> > >
> > > >
> > > > P.S. if anyone's bored enough, you can check out what we're up to
> at
> > > > https://github.com/srphtygr/dhb. I'm trying to get my 11yo kid to
> > > > spend a little time programming rather than just playing video
> games
> > > > when he's near a computer. He'a actually getting through this
> stuff
> > > > and is honestly interested when he understands it and sees it work
> --
> > > > and he even spotted a bug before me this afternoon! Feel free to
> > > > raise issues, pull requests, etc. if you like -- I'm putting him
> > > > through the git committing and pair programming paces, so outside
> > > > interaction would be kinda fun :)
> > > >
> > > >
> > > > P.P.S. We're actually using 2.11bsd after all..
> > > >
> > > I'm curious, will gcc on a modern Linux system compile K&R c?
> > >
> > > Maybe when I get a little time, I might try to see if I can compile
> it
> > > on a modern Fedora 21 system with gcc.
> > >
> > > BTW: Great job introducing him to such a classic environment. A few
> > > years ago, my now 18 year old had expressed some interest in
> graphics
> > > programming and was in awe over an SGI O2 I had at the time, so I
> got
> > > him an Indy. He played around with a bit of programming, but
> > > unfortunately, he lost interest.
> > >
> > > - Derrik
> > >
> > >
> > > _______________________________________________
> > > TUHS mailing list
> > > TUHS at minnie.tuhs.org
> > > https://minnie.tuhs.org/mailman/listinfo/tuhs
> > >
> 
> > _______________________________________________
> > TUHS mailing list
> > TUHS at minnie.tuhs.org
> > https://minnie.tuhs.org/mailman/listinfo/tuhs
> 
> 
> -- 
> ---
> Larry McVoy 	 lm at mcvoy.com http://www.mcvoy.com/lm 
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuh s
>  




  reply	other threads:[~2014-12-31  9:28 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 [this message]
2014-12-31 13:13   ` John Cowan
2014-12-31 17:42     ` Diomidis Spinellis
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=1420018115.54a3c1c32faaa@www.paradise.net.nz \
    --to=wes.parish@paradise.net.nz \
    /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).