The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: mike@ducky.net (Mike Haertel)
Subject: [TUHS] Re: Patches to improve 6th Edition
Date: Fri, 27 Dec 2002 23:07:46 -0800 (PST)	[thread overview]
Message-ID: <200212280707.gBS77kOc098669@ducky.net> (raw)

In article by Warren Toomey:
> P.S. Does anybody want to backport vi to 6th and 7th Edition?! :-)

The 2BSD tape contains vi source code that can *definitely* be built
on 7th edition (I've done it, it was easy) and supposedly can also
be used to build a 6th-edition "native" vi if you're willing to
backport the V7 C compiler (I haven't done that yet).

Since many people in 2BSD's time frame would not have had access
to V7 systems or V7-ish C compilers, the 2BSD tape also contains a
vi binary for V6 systems.

I think 2BSD was released around the same time as V7, and had an
assumption that many people would not yet have access to V7, and
so would want to use 2BSD as an add-on to V6 systems.

Since 6th edition didn't have environment variables, the 2BSD/V6
version of vi would get the terminal type from a file that mapped
hardwired serial lines to terminal type names.  I think it was
called /etc/htmp.

By the way, does anybody else think that vi should have been upgraded
to vii when V7 came out? :-)



             reply	other threads:[~2002-12-28  7:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-28  7:07 Mike Haertel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-08 13:42 Norman Wilson
2002-12-28 20:38 Wolfgang Helbig
2002-12-28  8:33 Wolfgang Helbig
2002-12-28  5:19 Brian S Walden
2002-12-28  2:58 John Holden
2002-12-27 20:58 [TUHS] V6: 50 bugs tape Mirian Crzig Lennox
2002-12-27 21:55 ` [TUHS] Re: Patches to improve 6th Edition Warren Toomey
2002-12-28  2:43   ` Greg Haerr

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=200212280707.gBS77kOc098669@ducky.net \
    --to=mike@ducky.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).