From: Clem Cole <clemc@ccc.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] vi in v7
Date: Sat, 25 Jul 2020 10:45:09 -0400 [thread overview]
Message-ID: <CAC20D2OYXpGUO-sAcePk0HevQ3AWUxshrj4=iEBXFT3-QZ-nNA@mail.gmail.com> (raw)
In-Reply-To: <fa23316b-c755-4182-0982-84104657d8f2@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
2BSD was the BSD for V7. It was >>not<< a 'distro' as 3.0 and later 2.XBSD
became. It is just a set of programs and kernel patches that were built
up at UCB. This was the way different sites released things in those
days. The "read me" files should tell you what is there and you pick the
binaries (if you have them) and install them as is and/or recompile from
the makefiles on a case by case basis.
Clem
On Sat, Jul 25, 2020 at 10:35 AM Will Senn <will.senn@gmail.com> wrote:
> On another front. I know I've asked this before in v6, and possibly
> related to v7, but I can't find the notes anywhere. vi doesn't come with
> v7. So, has anybody put it on v7 in simh? I saw a thread sometime back
> where vi on v7 wasn't the main topic, where Warren? I think it was, said
> he'd done it and it was "easy." I don't suppose there are any notes laying
> around telling how this might be accomplished?
>
> I do see vi in 2bsd.tar, I don't suppose there is a 'how to install 2bsd
> on v7" note around either?
>
> Thanks,
>
> Will
>
> --
> GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
>
>
[-- Attachment #2: Type: text/html, Size: 1941 bytes --]
next prev parent reply other threads:[~2020-07-25 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 14:34 Will Senn
2020-07-25 14:45 ` Clem Cole [this message]
2020-07-25 15:36 ` Warner Losh
2020-07-26 0:06 ` Dave Horsfall
2020-07-26 0:13 ` Warner Losh
2020-08-01 7:54 ` Dave Horsfall
2020-08-01 12:15 ` Clem Cole
2020-08-01 14:33 ` Warner Losh
2020-08-01 15:41 ` Clem Cole
2020-07-26 0:41 ` Clem Cole
2020-07-26 0:16 Noel Chiappa
2020-07-26 0:39 ` Adam Thornton
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='CAC20D2OYXpGUO-sAcePk0HevQ3AWUxshrj4=iEBXFT3-QZ-nNA@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=tuhs@minnie.tuhs.org \
--cc=will.senn@gmail.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).