The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: (Andrzej Popielewicz)
Subject: [TUHS] /usr/bin/bs on HPUX?
Date: Fri, 09 Jan 2009 11:51:38 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

John Cowan pisze:
> Lord Doomicus scripsit:
>> I was poking around an HP UX system at work today, and noticed a  
>> command I've never noticed before ... /usr/bin/bs.
>> I'm sure it's been there for a long time, even though I've been an  
>> HPUX admin for more than a decade, sometimes I'm just blind ... but  
>> anyway ....
>> I tried to search on google ... it looks like only HPUX, AIX, and  
>> Maybe AU/X has it.  Seems to be some kind of pseudo BASIC like  
>> interpreter.
> That's just what it is.  Here are the things I now know about it.
> 0.  The string "bs" gets an awful lot of false Google hits, no matter
> how hard you try.
> 1.  "bs" was written at AT&T, probably at the Labs, at some time between
> the release of 32V and System III.  It was part of both System III and
> at least some System V releases.
> 2.  It was probably meant as a replacement for "bas", which was a more
> conventional GW-Basic-style interpreter written in PDP-11 assembly
> language.  (32V still had the PDP-11 source, which of course didn't work.)
> 3.  At one time System III source code was available on the net,
> including bs.c and bs.1, but apparently it no longer is.  I downloaded
> it then but don't have it any more.
> 4.  I was able to compile it under several Unixes, but it wouldn't run:
> I think there must have been some kind of dependency on memory layout,
> but never found out exactly what.
> 5. I remember from the man page that it had regular expressions, and
> two commands "compile" and "execute" that switched modes to storing
> expressions and executing them on the spot, respectively.  That eliminated
> the need for line numbers.
> 6. It was apparently never part of Solaris.
> 7. It was never part of any BSD release, on which "bs" was the battleships
> game.
> 8. I can't find the man page on line anywhere either.
> 9. The man page said it had some Snobol features.  I think that meant
> the ability to return failure -- I vaguely remember an "freturn" command.
> 10.  99 Bottles of Beer has a sample bs program at
> .
> 11. If someone sends me a man page, I'll consider reimplementing it as
> Open Source.
You will find public domain basic interpreter in Coherent archive mwcbbs


lynx gopher://

It is for pdp11, vax, coherent , motorola etc.


  reply	other threads:[~2009-01-09 10:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10  0:30 Lord Doomicus
2008-12-10  9:45 ` Tim Bradshaw
2008-12-10 14:29 ` Jason Stevens
2008-12-10 18:08 ` John Cowan
2009-01-09 10:51   ` Andrzej Popielewicz [this message]
     [not found]   ` <>
2019-09-30 19:29     ` [TUHS] capturing history of bs(1) command / programming language Dave Plonka
2008-12-17 14:27 [TUHS] /usr/bin/bs on HPUX? Jose R. Valverde
2008-12-17 15:39 ` John Cowan
2008-12-17 16:14   ` lyricalnanoha
2008-12-17 16:35     ` John Cowan
2008-12-17 23:55       ` Lord Doomicus

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \

* 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).