Hi Diomidis,
Thanks for that link. This is exactly what I'm trying to ascertain, and I'm finding conflicting evidence.
- The socket API was in a state of flux between October '81 and March '82 (when 4.1a was supposedly cut). By March '82 it was mostly there, but not until later in the year did it fully stabilize.
- The BBN stack did not use the sockets API as late as January '82
- What I currently fathom from the SCCS files is that the socket API implementation was hard coded to use the nascent Berkeley stack.
- But the BBN code was likely in the 4.x BSD source tree, outside of SCCS (Berkeley started out with the BBN code, but it morphed quite quickly and drastically)
- In 1985 the BBN code finally enters SCCS (marked 'deprecated'); this code was integrated with the sockets API, and much developed from its 1982 form
Either the below link is correct (and I think I may have contributed to its view in a private mail to Kirk), or there were two different distributions (4.1a BSD with Berkeley network code and 4BSD with BBN network code). The two may have merged into one in peoples' memories: 35 years is a long time. Finding the actual kernel source for the 4.1a distribution could provide clarity on this point.
Perhaps Bill Joy could shed some light on the issue, but I don't have contact details. Having actual source removes all doubt.
Paul
On 1 Dec 2016, at 10:51 , Diomidis Spinellis wrote:
> The best description I could find is the following:
>
> http://minnie.tuhs.org/pipermail/tuhs/2016-September/007417.html
>
> > The 4.1a distribution had the initial socket interface with a
> > prerelease of the BBN TCP/IP under it. There was wide distribution
> > of 4.1a. The 4.1b distribution had the fast filesystem added and
> > a more mature socket interface (notably the listen/accept model
> > added by Sam Leffler).
>
> Diomidis
>
> On 01/12/2016 10:30, Paul Ruizendaal wrote:
>>
>> 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
>>
>
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
Larry McVoy:
I've always morned that he died so early. I would have liked to talk
to him, I love troff to this day.
====
Me too (s/morn/mourn/, of course). I might even have had the
chance to work with him.
The original UNIX crowd were all really neat characters, albeit
sometimes a trifle overly characterful. All nice guys to work
with, too, at least those who were still around when I was at
1127.
Norman Wilson
Toronto ON
We lost J.F.Ossanna in 1977; he had a hand in developing Unix, and was
responsible for "roff" and its descendants. Remember him, the next time
you see "jfo" in documentation.
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
I stumbled onto this by accident, and yes it really is a port of UNIX v1
from PDP-11 assembly into 8086/80386 assembly.
I fired up Qemu and some of the disk images and it booted up!
the directories contain assembly, text files, pdf's, images, and pictures...
I have no idea how to build it I didn't see any make file, but it looks very
interesting!
http://www.singlix.com/runix/index.html
Also you may want to mute the tab, or turn your speakers down, it has an
embedded music player.
I just found a project that has ported Unix V7 to a modern system, and
a search of my TUHS archives finds no previous mention of it:
V7/x86 - x86 port of UNIX V7
http://www.nordier.com/v7x86/index.html
V7/x86 on VirtualBox
http://www.nordier.com/articles/v7x86_vbox.html
The jwhois command identifies the host site as (possibly) located in
Durban, South Africa.
-------------------------------------------------------------------------------
- Nelson H. F. Beebe Tel: +1 801 581 5254 -
- University of Utah FAX: +1 801 581 4148 -
- Department of Mathematics, 110 LCB Internet e-mail: beebe(a)math.utah.edu -
- 155 S 1400 E RM 233 beebe(a)acm.org beebe(a)computer.org -
- Salt Lake City, UT 84112-0090, USA URL: http://www.math.utah.edu/~beebe/ -
-------------------------------------------------------------------------------
Can’t help about that DEC-ism.
Do have these 2.
News from Xerox Corporation:
FOR IMMEDIATE RELEASE
XEROX ANNOUNCES HYPER-ETHERNET
SAN FRANCISCO, CA. Jan 7. 2010 - Xerox today announced Hyper-Ethernet their fourth
generation local area network. In addition to its ability to transmit text data and images, Hyper-
Ethernet enables the transmission of people. ”People transmission over Hyper-Ethernet" according
to Michael Liddle, V.P. of Office Systems. "will greatly reduce elevator congestion and eliminate the
need for video conferencing.“ Order taking for Hyper-Ethemet will begin next month. Installation
will start in Los Angeles in the Third Quarter.
In a related announcement. Wang Labs. headquartered in Hoboken. New Jersey, announced Super-
Hyper Wangnet their twelfth generation local area network. According to Freddie Wang, President
of Wang Labs. "Super-Hyper-Wangnet will not only transmit people over the Wangband, but will
also transmit furniture and buildings over the interconnect and utility bands. These additional
capabilities of Super-Hyper Wangnet are vital to the emerging office of the future." Order taking
for Super-Hyper-Wangnet will begin next month. Installation has already occurred worldwide.
IBM Corporation. who has been rumored to be about to announce a local area network since 1980,
was not available for comment.
xxx
Followed by
Digital Responds to Hyper-Ethernet
TEWKSBURY. MA. April 1. 2010 -- Digital Equipment announced today it's new DECnet Phase
XVIII Architecture. In response to recent Xerox and Wang improvements to Ethernet that provide
people and facility transportation across inter-node links DEC‘s latest DECnet provides these
capabilities as well as providing for the creation of virtual facilities and even countries. These
capabilities are provided by breakthroughs in communications technology that actually uses the
Ether as a communications media. Through the use of a new dedicated NANO-PDP-11/E99
gateway processor system, ETHERGATE, DECnet users can access anywhere in the Ethereal Plane.
This development obsoletes teleconferencing, since meeting groups can create their own common
conference rooms and cafeterias, thus resolving space, travel and dining problems. There may be a
few bugs left, as some of the dissenting DECnet Review Group members have not been seen since
the last meeting held in such a virtual conference facility.
This breakthrough was brought about by a team effort of the Distributed Systems‘ Software and
Hardware engineering teams in a effort to improve on their Tewksbury, Massachusetts facility. In a
compromise decision, Distributed Systems will maintain an ETHERGATE in TWOOO, but it will
connect directly to their new home somewhere in the Shire of their newly defined Middle Earth
reality. Despite some difficulties, the scenery, windows tax breaks, pool and racquetball courts
made the relocation go quite smoothly. Engineering Network topology will not change, as all
forwarding will be done by the TWOOO Ethereal Plane Router residing in the crater at the former
building site.
Utility packages such as Ethereal Person Transfer (EPT) and Ethereal Facility Transfer (EFT)
provide appropriate capabilities for casual users. Sophiscated users can create (SCREATE), access
(SOPEN), and delete (SNUKE) ethereal entities transparently from high level languages using the
Ethereal Management System (EMS) package and the Ethereal Access Protocol (EAP). An
ETHERTRIEVE utility for easy interactive use will be available shortly.
DECnet Phase XVIII follows on the success of the Phase XVI ability to access everyone‘s Digital
Professional wrist watch computer system. This lead to the current Phase XVII architecture, which
has routing capabilities that allow direct communications with the entire Earth population's Atari
home video games.
Distributed Systems architects are hard at work on the next phase of DECnet that will include
multi-plane existence network management (using the NIECE protocol) and galaxy level routing
using 64K bit addresses.
Digital will continue to support it's Gateway products into the Prime Material Plane. These
products include an IBM ANA (Acronym-based Network Architecture) Gateway, the TOLKIEN
product that allows control of all ring based networks, and our Mega-broad-jump-band hardware
which leaps past Wang's products in the hype weary business marketplace.
From our Engineering Net. (You can tell that they're really working on on it. Racquetball courts
indeed!)
David
> On Nov 17, 2016, at 6:00 PM, tuhs-request(a)minnie.tuhs.org wrote:
>
> Send TUHS mailing list submissions to
> tuhs(a)minnie.tuhs.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://minnie.tuhs.org/cgi-bin/mailman/listinfo/tuhs
> or, via email, send a message with subject or body 'help' to
> tuhs-request(a)minnie.tuhs.org
>
> You can reach the person managing the list at
> tuhs-owner(a)minnie.tuhs.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of TUHS digest..."
>
>
> Today's Topics:
>
> 1. OT: USENET article involving DEC machines and atomic tests
> (Dave Horsfall)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 18 Nov 2016 11:54:40 +1100 (EST)
> From: Dave Horsfall <dave(a)horsfall.org>
> To: The Eunuchs Hysterical Society <tuhs(a)tuhs.org>
> Subject: [TUHS] OT: USENET article involving DEC machines and atomic
> tests
> Message-ID: <alpine.BSF.2.11.1611181148020.19595(a)aneurin.horsfall.org>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Hoping someone can help me here, as I've grepped the 'net to no avail.
>
> Back when USENET was supreme and dinosaurs strode the earth, there was a
> hilarious article involving a DEC box (long forgotten it) that was used to
> instrument underground atomic tests. In one scene, the box was atop a
> truck which was right over the hole; they both went skywards, but the data
> was recovered by taking out the core memory boards and plugging them into
> another box.
>
> Does anyone remember it? It does sound rather suss...
>
> --
> Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> TUHS mailing list
> TUHS(a)minnie.tuhs.org
> http://minnie.tuhs.org/cgi-bin/mailman/listinfo/tuhs
>
> ------------------------------
>
> End of TUHS Digest, Vol 12, Issue 5
> ***********************************
Hoping someone can help me here, as I've grepped the 'net to no avail.
Back when USENET was supreme and dinosaurs strode the earth, there was a
hilarious article involving a DEC box (long forgotten it) that was used to
instrument underground atomic tests. In one scene, the box was atop a
truck which was right over the hole; they both went skywards, but the data
was recovered by taking out the core memory boards and plugging them into
another box.
Does anyone remember it? It does sound rather suss...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
> From: Don North
> Track 0 is not used by standard DEC software
I wonder why DEC did't use track 0. The thing is small enough (256KB in the
original single-density) that even 1% is a good chunk to throw away. Does
anyone know? (I had a look online, but couldn't turn anything up.)
If I had to _guess_, one possibility would be that track 0 is the innermost
track, where the media is moving the slowest, and as a result it's more
error-prone. Another is that IBM used track 0 for something special, and DEC
tried to conform with that. But those are pure guesses, I would love to know
for sure.
Noel
