The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: fair-tuhs@netbsd.org (Erik E. Fair)
Subject: [TUHS] Porting 2.11 BSD
Date: Mon, 23 Nov 2015 00:40:40 -0800	[thread overview]
Message-ID: <26595.1448268040@cesium.clock.org> (raw)
In-Reply-To: <20151123090509.Horde.anntqPoOVbgXR9r5HlrgBxs@avocado.salatschuessel.net>

With regard to cooperating with extant system firmware, this is a problem that
NetBSD has on almost every platform it runs on (and it runs on many). You can
find many examples of how to cooperate or work-around firmware bootloaders in
our BSD-licensed codebase:

	http://www.netbsd.org/

Further, we've got a standard secondary booter framework, though we retired
a.out quite a few releases ago. See src/sys/arch/*/stand (for "stand-alone")
in our source repository. Or grab the source tarballs as you see fit.

Some of this is deja vu for me: I was a co-founder of the "Undergraduate
Computing Facility" (UCF) at UCB in 1982, and helped set up the Z8002 based
Onyx system in B50 Evans Hall that was our first and for a long time, only,
computer. The undergrads who used that system to learn Unix ported many a BSD
utility to that system (at least the ones that weren't too RAM-hungry),
starting with BerkNet so we could move files around easily & have E-mail.

	good luck,

	Erik <fair at netbsd.org>



  reply	other threads:[~2015-11-23  8:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21 13:00 Oliver Lehmann
2015-11-21 13:36 ` Jacob Goense
2015-11-21 14:03 ` Hellwig Geisse
2015-11-21 14:39   ` Clem Cole
2015-11-22  0:13 ` Random832
2015-11-22  0:27   ` Michael Kerpan
2015-11-22  2:04     ` Jonathan Gevaryahu
2015-11-22  0:30   ` William Pechter
2015-11-22  1:36     ` Oliver Lehmann
2015-11-22  2:13       ` William Pechter
2015-11-23  0:56         ` Nick Downing
2015-11-23  8:05           ` Oliver Lehmann
2015-11-23  8:40             ` Erik E. Fair [this message]
2015-11-25  0:09               ` Al Kossow
2015-11-25 10:14                 ` Oliver Lehmann
2015-11-25 11:25                   ` Nick Downing
2015-11-25 11:46                     ` Nick Downing
2015-11-25 11:56                       ` Oliver Lehmann
2015-11-25 12:10                         ` Nick Downing
2015-11-25 11:51                     ` Oliver Lehmann
2015-11-25 12:01                       ` Nick Downing

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=26595.1448268040@cesium.clock.org \
    --to=fair-tuhs@netbsd.org \
    /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).