From owner-freebsd-current Thu Jul 16 19:23:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06891 for freebsd-current-outgoing; Thu, 16 Jul 1998 19:23:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06884 for ; Thu, 16 Jul 1998 19:23:07 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA28858; Fri, 17 Jul 1998 12:22:40 +1000 Date: Fri, 17 Jul 1998 12:22:40 +1000 From: Bruce Evans Message-Id: <199807170222.MAA28858@godzilla.zeta.org.au> To: abial@nask.pl, jdp@polstra.com Subject: Re: Make release fails because kernel is too large Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Does anybody have an idea of what we can take out? It seems likely >> that when CAM comes in, it will further expand the kernel. And CAM >> definitely needs to come in. > >Perhaps with the advent of CAM boot floppies we should also use DEVFS, >which would allow for saving ca. 50kB on inodes' space. More like -15K (e.g., +5K savings for compressed inodes' space -10K for compressed code to register devfs names, and -10K for compressed code for devfs itself). The 2.2 boot floppy has 45K for metadata in the uncompressed (boot) file system. Of this, 12K is very easy to save using `newfs -i large' to reduce the inodes' space from 16K to 4K. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message