The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Andy Kosela <akosela@andykosela.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Unix Kernel Size
Date: Sat, 30 Jun 2018 13:31:49 -0600	[thread overview]
Message-ID: <CANCZdfr07b1i+FoSpAN99-OuZSkDHXwYc1r+n5oUA5zvMJu2nA@mail.gmail.com> (raw)
In-Reply-To: <CALMnNGhuh6K6dLisGTtvJEbCmcyv3uu-MwrneEYct=iHHw-4nQ@mail.gmail.com>

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

On Sat, Jun 30, 2018 at 1:11 PM, Andy Kosela <akosela@andykosela.com> wrote:

>
>
> On Saturday, June 30, 2018, Warner Losh <imp@bsdimp.com> wrote:
>
>> Greetings,
>>
>> I'd like to thank everybody that sent me data for my unix kernel size
>> stuff. There's two artifacts I've crated. One I think I've shared before,
>> which is my spreadsheet:
>> https://docs.google.com/spreadsheets/d/13C77pmJFw4ZBmGJuNarB
>> UvWBxBKWXG-jtvARxJDHiXs/edit?usp=sharing
>>
>>
> It would be interesting to compare it to Linux throughout the history.  I
> can still compile a minimal latest Linux kernel that is around 2M.  Not bad
> if you ask me.
>

It's possible to build FreeBSD much smaller as well (some ARM ports can get
that small)... But that's not the comparison I was going for since that
often understates the effect of the SCSI/SATA stack you need these days, or
the network stack, or other technology that's considered 'standard.' It's
entirely due to ease of use and cheap memory.

I didn't include a growth of the Linux kernel due to the less-prevalent use
of GENERIC-type kernels there, and a lack of good data sources I could mine
quickly for apples-to-apples comparisons over time.

Warner

[-- Attachment #2: Type: text/html, Size: 2016 bytes --]

      reply	other threads:[~2018-06-30 22:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30  0:57 Warner Losh
2018-06-30 19:11 ` Andy Kosela
2018-06-30 19:31   ` Warner Losh [this message]

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=CANCZdfr07b1i+FoSpAN99-OuZSkDHXwYc1r+n5oUA5zvMJu2nA@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=akosela@andykosela.com \
    --cc=tuhs@minnie.tuhs.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).