The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: random832@fastmail.com (Random832)
Subject: [TUHS] Kernel Sizes
Date: Sat, 20 Jan 2018 14:22:27 -0500	[thread overview]
Message-ID: <1516476147.3105555.1242251720.684D327E@webmail.messagingengine.com> (raw)
In-Reply-To: <CANCZdfoG5nEBtYefo=W3nOEY4FSoqixRMPh_4JncY=JyPAR8Lw@mail.gmail.com>

On Sat, Jan 20, 2018, at 13:11, Warner Losh wrote:
> For a presentation I'm doing this summer on FreeBSD, I thought it would be
> cool to get the kernel sizes for various old flavors of Unix. I see numbers
> for v5, v6 and v7 in the tuhs tree view, and it appears these versions are
> complete enough for me to extract the kernels themselves. However, I see
> nothing prior to that.

There is a possibly V2 era kernel (two, actually) on the s1-bits tape image, but it's been too long since I looked at this and I don't recall exactly how to extract them. I posted about this at the time, but there wasn't any interest - I'd determined that s1 was in fact an "init tape" as described in V1 boot.7 and V3 bproc.8. Those manpages do mention the size that was allocated on disk/tape for each kernel in those eras: 6K and 7-8K words [so twice that number of bytes], respectively.

To determine how much headroom was in this allocation, I just now went through and checked the s1-bits file for empty 512-byte blocks. It consists of 25 blocks of data (12800 bytes), followed by 4 blocks of zeros. I think that region of the tape was the bootloaders followed by the "cold boot" kernel. Then there are 22 blocks (11264 bytes) of data [then 10 blocks zeros], which was IIRC the other kernel (the "warm boot" kernel, which did not contain code for reinitializing the filesystem). The rest of the tape (not kernel images) is 490 blocks (245 KB) of data, followed by 27 blocks of 0xFF.


  parent reply	other threads:[~2018-01-20 19:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-20 18:11 Warner Losh
2018-01-20 18:33 ` Donald ODona
2018-01-20 19:22 ` Random832 [this message]
2018-01-20 21:14 ` Michael Kjörling
2018-01-21  0:19 ` Warren Toomey
2018-01-21  1:41   ` Andy Kosela
2018-01-22  3:51   ` Warner Losh
2018-01-22  4:39     ` Grant Taylor
2018-01-22  6:53       ` Warner Losh
2018-01-21  2:08 ` Dan Stromberg
2018-01-21  2:13   ` Steve Johnson
2018-01-21  4:24     ` Warner Losh
2018-01-21 22:53       ` Greg 'groggy' Lehey
2018-01-22  1:19         ` Steve Nickolas
2018-01-21 22:03 Doug McIlroy
2018-01-21 22:36 Doug McIlroy
     [not found] <mailman.4.1516572202.3873.tuhs@minnie.tuhs.org>
2018-01-21 23:42 ` Paul Ruizendaal
2018-01-22 10:46 Rudi Blom

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=1516476147.3105555.1242251720.684D327E@webmail.messagingengine.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).