Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Grant Taylor via COFF <coff@tuhs.org>
To: COFF <coff@tuhs.org>
Subject: [COFF] Will someone update the 386BSD Wikipedia page for me?
Date: Fri, 9 Sep 2022 19:53:50 -0600	[thread overview]
Message-ID: <b2f049d3-d371-24d6-af1e-1efcb621394b@spamtrap.tnetconsulting.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 2654 bytes --]

Hi,

Will someone update the 386BSD Wikipedia page for me?  Wikipedia doesn't 
like my IPv6 address at home nor my VPS and I've given up trying to find 
a way to make the edit myself without breaking IPv6 on my network.

The second paragraph of the history page states the following:

"The porting process with code was extensively documented in an 18-part 
series written by Lynne Jolitz and William Jolitz in Dr. Dobb's Journal 
beginning in January 1991."

There are only 17 parts to the series.  My authoritative source is the 
DDJ DVD available on The Internet Archive.  There are 17 articles, 
month's listed below.

In case my ability to find the article sis called into question, the 
Tracing BSD System Calls article from DDJ March 1998 states the 
following in the fourth paragraph.

"(see the DDJ series "Porting UNIX to the 386," by William and Lynne 
Jolitz, January-November 1991 and February-July 1992)"

01 - 91-Jan - PORTING UNIX TO THE 386: A PRACTICAL APPROACH - Designing 
the software specification
02 - 91-Feb - PORTING UNIX TO THE 386: THREE INITIAL PC UTILITIES - 
Getting to the hardware
03 - 91-Mar - PORTING UNIX TO THE 386: THE STANDALONE SYSTEM - Creating 
a protected-mode standalone C programming environment
04 - 91-Apr - PORTING UNIX TO THE 386 LANGUAGE TOOLS CROSS SUPPORT - 
Developing the initial utilities
05 - 91-May - PORTING UNIX TO THE 386 THE INITIAL ROOT FILESYSTEM - 
Completing the toolset
06 - 91-Jun - PORTING UNIX TO THE 386 RESEARCH & THE COMMERCIAL SECTOR - 
Where does BSD fit in?
07 - 91-Jul - PORTING UNIX TO THE 386: A STRIPPED-DOWN KERNEL - Onto the 
initial utilities
08 - 91-Aug - PORTING UNIX TO THE 386: THE BASIC KERNEL - Overview and 
initialization
09 - 91-Sep - PORTING UNIX TO THE 386: THE BASIC KERNEL - 
Multiprogramming and Multitasking, Part One
10 - 91-Oct - PORTING UNIX TO THE 386: THE BASIC KERNEL - 
Multiprogramming and Multitasking, Part II
11 - 91-Nov - PORTING UNIX TO THE 386: THE BASIC KERNEL - Device 
autoconfiguration
12 - 92-Feb - PORTING UNIX TO THE 386: DEVICE DRIVERS - Drivers for the 
basic kernel
13 - 92-Mar - PORTING UNIX TO THE 386 DEVICE DRIVERS - Entering, 
exiting, and masking processor interrupts
14 - 92-Apr - PORTING UNIX TO THE 386 DEVICE DRIVERS - Getting into and 
out of interrupt routines
15 - 92-May - PORTING UNIX TO THE 386: MISSING PIECES, PART 1 - 
Completing the 386BSD kernel
16 - 92-Jun - PORTING UNIX TO THE 386 MISSING PIECES II - Completing the 
386BSD kernel
17 - 92-Jul - PORTING UNIX TO THE 386 THE FINAL STEP - Running light 
with 386BSD



-- 
Grant. . . .
unix || die


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4017 bytes --]

             reply	other threads:[~2022-09-10  1:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-10  1:53 Grant Taylor via COFF [this message]
2022-09-10  2:05 ` [COFF] " Greg 'groggy' Lehey
2022-09-10  2:26   ` Grant Taylor via COFF

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=b2f049d3-d371-24d6-af1e-1efcb621394b@spamtrap.tnetconsulting.net \
    --to=coff@tuhs.org \
    --cc=gtaylor@tnetconsulting.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).