From: random832@fastmail.com (Random832)
Subject: [TUHS] Pre-v6 images and 2.11BSD patches
Date: Sat, 12 Dec 2015 03:28:48 -0500 [thread overview]
Message-ID: <m2d1uc83zz.fsf@fastmail.com> (raw)
In-Reply-To: <20151212063317.GA5670@minnie.tuhs.org>
Warren Toomey writes:
> We used the binaries on the s2-bits tape as the binaries for the
> v1 kernel. We had to tweak things a bit so that we could run the
> first C compilers.
I'm talking about the s1-bits tape, though. It contains two
binary kernels (the warm/cold ones described in the manpages),
as raw data in the sections that aren't mentioned in the Readme
file. (i.e. the first 50176 bytes).
I figured this out by analyzing the file and noticing it
contained copies of /etc/init, getty, /bin/chmod, date, login,
mkdir, sh, tap, and ls, which is similar to the lists of
programs mentioned in:
http://minnie.tuhs.org/cgi-bin/utree.pl?file=V1/man/man7/boot.7
http://minnie.tuhs.org/cgi-bin/utree.pl?file=V3/man/man8/bproc.8
I worked out that the rest of the structure also matched, though
I think the sizes were different.
next prev parent reply other threads:[~2015-12-12 8:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 4:54 Peter Jeremy
2015-12-12 5:30 ` Warren Toomey
2015-12-12 6:25 ` Random832
2015-12-12 6:33 ` Warren Toomey
2015-12-12 8:28 ` Random832 [this message]
2015-12-12 7:26 ` Peter Jeremy
2015-12-12 8:20 ` Warren Toomey
2015-12-12 5:33 ` Warren Toomey
2015-12-12 6:01 ` William Pechter
2015-12-12 6:16 ` Random832
2015-12-12 6:17 ` Random832
2015-12-12 6:38 ` Warren Toomey
2015-12-12 7:11 ` Jacob Ritorto
2015-12-12 5:44 ` John Cowan
2015-12-16 21:56 ` Tom Ivar Helbekkmo
[not found] <mailman.17.1449898266.27456.tuhs@minnie.tuhs.org>
2015-12-12 11:25 ` Johnny Billquist
2015-12-17 15:40 ` Tom Ivar Helbekkmo
[not found] <mailman.1.1449901013.3292.tuhs@minnie.tuhs.org>
2015-12-12 11:31 ` Johnny Billquist
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=m2d1uc83zz.fsf@fastmail.com \
--to=random832@fastmail.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).