From: jsteve@superglobalmegacorp.com (Jason Stevens)
Subject: [TUHS] looking for 4.1a BSD full kernel source
Date: Sat, 3 Dec 2016 12:16:19 +0800 [thread overview]
Message-ID: <0F0B9BFC06289346B88512B91E55670D2FED@EXCHANGE> (raw)
I'm not sure if my other reply got though, so I'll try again...
I found the source to the BBN stack in the CSRG CD's it's on CD 4
/sys/deprecated/bbnnet
LINT.bbn 08-Aug-2016 06:37 3.5K
NOTES 08-Aug-2016 06:37 4.6K
RELAY.bbn 08-Aug-2016 06:37 1.2K
SCCS/ 08-Aug-2016 06:37 -
fsm.h 08-Aug-2016 06:37 1.2K
fsmdef.h 08-Aug-2016 06:37 9.6K
hmp.c 08-Aug-2016 06:37 12K
hmp.h 08-Aug-2016 06:37 3.2K
hmp_subr.c 08-Aug-2016 06:37 6.5K
hmp_traps.c 08-Aug-2016 06:37 3.5K
hmp_traps.h 08-Aug-2016 06:37 2.7K
hmp_var.h 08-Aug-2016 06:37 1.4K
ic_output.c 08-Aug-2016 06:37 5.7K
icmp.c 08-Aug-2016 06:37 17K
icmp.h 08-Aug-2016 06:37 3.3K
in.c 08-Aug-2016 06:37 12K
in.h 08-Aug-2016 06:37 2.0K
in_pcb.c 08-Aug-2016 06:37 11K
in_pcb.h 08-Aug-2016 06:37 1.9K
in_proto.c 08-Aug-2016 06:37 4.9K
in_var.h 08-Aug-2016 06:37 2.2K
ip.h 08-Aug-2016 06:37 3.3K
ip_input.c 08-Aug-2016 06:37 29K
ip_output.c 08-Aug-2016 06:37 14K
ip_usrreq.c 08-Aug-2016 06:37 3.8K
macros.h 08-Aug-2016 06:37 4.4K
net.h 08-Aug-2016 06:37 2.4K
nopcb.h 08-Aug-2016 06:37 318
raw_input.c 08-Aug-2016 06:37 9.4K
rdp.h 08-Aug-2016 06:37 15K
rdp_cksum.s 08-Aug-2016 06:3
7 4.4K
rdp_fsm.c 08-Aug-2016 06:37 4.5K
rdp_input.c 08-Aug-2016 06:37 9.6K
rdp_macros.h 08-Aug-2016 06:37 7.9K
rdp_prim.c 08-Aug-2016 06:37 13K
rdp_states.c 08-Aug-2016 06:37 34K
rdp_subr.c 08-Aug-2016 06:37 8.4K
rdp_usrreq.c 08-Aug-2016 06:37 21K
seq.h 08-Aug-2016 06:37 415
sws.h 08-Aug-2016 06:37 326
tcp.h 08-Aug-2016 06:37 8.6K
tcp_input.c 08-Aug-2016 06:37 12K
tcp_prim.c 08-Aug-2016 06:37 9.8K
tcp_procs.c 08-Aug-2016 06:37 28K
tcp_states.c 08-Aug-2016 06:37 20K
tcp_usrreq.c 08-Aug-2016 06:37 22K
udp.c 08-Aug-2016 06:37 5.2K
udp.h 08-Aug-2016 06:37 1.1K
udp_usrreq.c 08-Aug-2016 06:37 7.0K
I've been meaning to try to try to manually mash stuff together but just
haven't gotten around to it.
> ----------
> From: Paul Ruizendaal
> Sent: Thursday, December 1, 2016 4:30 PM
> To: tuhs at minnie.tuhs.org
> Subject: [TUHS] looking for 4.1a BSD full kernel source
>
>
> Hi,
>
> I'm trying to find out exactly what was in the 4.1a BSD distribution, as
> far as the kernel is concerned. The image in the CSRG archive comes from a
> tape that had a hard read error and does not include any kernel sources.
> Some of the kernel files were already covered by SCCS around that time,
> but not everything. My main focus is to understand tcp/ip networking in
> 4.1a and whether the kernel could be built with either the Berkeley or the
> BBN network stack.
>
> Does anybody know where I could find a full set of kernel sources for the
> 4.1a BSD kernel?
>
> Many thanks in advance!
>
> Paul
>
next reply other threads:[~2016-12-03 4:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 4:16 Jason Stevens [this message]
2016-12-02 9:37 ` Paul Ruizendaal
-- strict thread matches above, loose matches on Subject: below --
2016-12-01 8:30 Paul Ruizendaal
[not found] ` <0f3795f4-fb98-3370-510c-347a272dddae@aueb.gr>
2016-12-01 10:40 ` Paul Ruizendaal
2016-12-01 14:27 ` Clem Cole
2016-12-01 20:13 ` Paul Ruizendaal
2016-12-01 21:28 ` Clem Cole
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=0F0B9BFC06289346B88512B91E55670D2FED@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).