The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: b4@gewt.net (Cory Smelosky)
Subject: [TUHS] 4.1BSD Networking
Date: Mon, 16 Jun 2014 08:53:59 -0400 (EDT)	[thread overview]
Message-ID: <alpine.OSX.2.00.1406160847210.15321@melanie.local> (raw)

Hello all, recent subscriber to this list...but some might 
recognise me.

I'm currently fighting (and mostly succeeding) with getting a pure 
4.3BSD-Tahoe install rolling in a VAX simulator (all my tape drives are 
currently nonfunctional or I'd fire up a real II or III).  Still in the 
middle of compiling (I know there are easier ways...but I like the feeling 
of doing it purely "from scratch"...feels more historically accurate).

Anyways, while waiting for the compile I ended up with a working 4.1c 
installation and I began poking around its source tree (I also did a 
little bit of poking at the CSRG discs).  I stumbled upon the fact 4.1c 
supports the DMC (which SIMH git now emulates!) and I see it's also still 
in src/old on some versions of 4.3 (I wonder if it'll still build...). 
Looking at the source is immensely confusing...does anyone have any 
knowledge/notes from the time period/documentation that will help me with 
my little experiment in archaic networking? I might just be tired...but 
the berknet configuration doesn't make a whole lot of sense to me. 
(There's also the fact my grasp of C is minimal).

-- 
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects



             reply	other threads:[~2014-06-16 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 12:53 Cory Smelosky [this message]
2014-06-16 14:28 ` Clem Cole
2014-06-16 16:05   ` Ronald Natalie
2014-06-16 20:37     ` [TUHS] Creating 4.3 skeleton filesystem (was Re: 4.1BSD Networking) Cory Smelosky

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=alpine.OSX.2.00.1406160847210.15321@melanie.local \
    --to=b4@gewt.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).