From owner-freebsd-hackers Mon Oct 2 04:10:59 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA07156 for hackers-outgoing; Mon, 2 Oct 1995 04:10:59 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA07142 for ; Mon, 2 Oct 1995 04:10:50 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id VAA23721; Mon, 2 Oct 1995 21:09:12 +1000 Date: Mon, 2 Oct 1995 21:09:12 +1000 From: Bruce Evans Message-Id: <199510021109.VAA23721@godzilla.zeta.org.au> To: bde@zeta.org.au, davidg@Root.COM Subject: Re: FreeBSD 2.1 will require a minimum of 8MB for installation. Cc: hackers@freefall.freebsd.org, jkh@time.cdrom.com, julian@ref.tfs.com Sender: owner-hackers@FreeBSD.org Precedence: bulk >>and a few minutes with `nm -n /kernel | less' showed the following >> >>5) 32K statically allocated normally-unused nfs log buffer `nfsdrt'. >>6) 5.5K statically allocated normally-unused nfs log buffer `nfsrtt'. > I'm not able to confirm this; the size of the arrays as near as I can tell >is much smaller than this - less than 1K each total. >>7) 48K statically allocated normally-unused matcd table `matcd_data' >> (enough for 16 drives!). Oops. `nfsdrt' is only 3K and `matcd_data' is only 6K. > Is this in -current or -stable? I just looked at the result of compiling >the matcd driver, and I can't confirm your results: Oops again. It is for a -current GENERIC. >[corbin:CORBINX] size matcd.o >text data bss dec hex >10704 1328 6916 18948 4a04 This only shows the static part of the bss. Global common data is not shown because it doesn't belong to any single object file. There should be very little global common data, but I don't trust drivers not to have it. > Also, since the table you mentioned is uninitialized data, it should appear >in the .bss in any case...this isn't a problem - we're only interested in the >actual size of the binary. Surely there is more of a problem fitting everything at runtime than just loading it? Bruce