The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jsteve@superglobalmegacorp.com (Jason Stevens)
Subject: [TUHS] b remnants?
Date: Fri, 14 Oct 2011 14:23:23 -0400	[thread overview]
Message-ID: <C1DCD24F4CD3E011B4240003FF08577C5B0A@EXCHANGE> (raw)

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

I didn't see it as immeditaly obvious on slackware 1.0 ... or SLS .. it very
well may have been some addon or something somehwere....

If anyone knew it's filename that'd go a long long way! :)

-----Original Message-----
From: Derrik Walker [mailto:lorddoomicus@mac.com]
Sent: Friday, October 14, 2011 12:36 PM
To: Gregg Levine
Cc: tuhs at minnie.tuhs.org
Subject: Re: [TUHS] b remnants?




On Oct 14, 2011, at 11:53 AM, Gregg Levine <gregg.drwho8 at gmail.com> wrote:

> On Fri, Oct 14, 2011 at 11:34 AM, Derrik Walker <lorddoomicus at mac.com>
wrote:
> > Many, many eons ago, in the early '90's, there was an implementation of
B
> > for Linux ( I believe it was written in C, ironically enough ).  I think
it
> > was part of a bigger collection of "ancient" software for Linux that use
to
> > be around in the early Slackware days.
> >
> > Alas, I have searched for it in the recent past, as I was thinking about
> > porting it to OS X for kicks, but it seems to have vanished.
> >
> > Having an B, implemented in a modern language for a modern OS would be
cool.
> >
>
>
> Hello!
> How early a time period for the Slackware Linux group? (Which is what
> I run.) There's a repository of older distributions on the Ibib site,
> and a more comprehensive one situated on a mirror in the UK.

It would have been around '92 or '93, back when Slackware really only
provided a very basic boot system, gcc, some fancy scripts, and a crap load
of tarballs to compile everything.  I'm not even sure it was part of the
Slackware collection, it might have been something someone added to the
server - I didn't build that computer.

It was an experimental system at CSU, where I was going to school at the
time - and the first actually Linux computer I ever had an account on.  One
of the older professors had a bunch of B code he got from someplace and put
the compiler on there to see if he could get it to build.  I remember he
also put f2c on there too as he had a tape full of Fortran code he wanted to
compile.

But, for all I know, he may have written the B compiler himself, but I seem
to remember him telling me about this collection of ancient software for
Linux that someone else had written, and he had gotten it up and running on
the experimental Linux system.  Just not sure how faulty my memory is.  I
just remember looking at B, and asking why he just doesn't covert it to C?

Funny thing was, some of the younger professors were complaining saying the
preferred their "REAL UNIX".

Unfortunately, he as long since retired.  And that Computer was retired when
they moved the main Student system from HPUX to Redhat in the late '90's.

- Derrik




             reply	other threads:[~2011-10-14 18:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14 18:23 Jason Stevens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-15 16:14 Jason Stevens
2011-10-15 16:41 ` Gregg Levine
2011-10-17 16:18   ` Al Kossow
2011-10-17 16:29     ` Gregg C Levine
2011-10-15  4:20 Jason Stevens
2011-10-15  4:37 ` Gregg Levine
2011-10-15  8:44 ` Michael Davidson
2011-10-14 14:52 A. P. Garcia
2011-10-14 15:34 ` Derrik Walker
2011-10-14 15:53   ` Gregg Levine
2011-10-14 16:35     ` Derrik Walker
2011-10-14 19:17       ` Jeremy C. Reed
2011-10-14 20:08   ` John Cowan
2011-10-14 18:06 ` Tim Newsham
2011-10-15  3:57 ` A. P. Garcia
2011-10-15  4:57   ` Andru Luvisi
2011-10-15  8:54   ` Michael Davidson
2011-10-15 14:12     ` Gregg Levine
2011-11-01 16:24   ` Tim Bradshaw
2011-10-15  6:20 ` Greg 'groggy' Lehey

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=C1DCD24F4CD3E011B4240003FF08577C5B0A@EXCHANGE \
    --to=jsteve@superglobalmegacorp.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).