From owner-freebsd-alpha Sun Oct 27 13:27:53 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D0BA37B401 for ; Sun, 27 Oct 2002 13:27:52 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A598B43E88 for ; Sun, 27 Oct 2002 13:27:51 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA19007; Sun, 27 Oct 2002 16:27:50 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g9RLRKo18878; Sun, 27 Oct 2002 16:27:20 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15804.23096.674450.355772@grasshopper.cs.duke.edu> Date: Sun, 27 Oct 2002 16:27:20 -0500 (EST) To: freebsd-alpha@freebsd.org Cc: re@feebsd.org Subject: alpha 5.0 BOOTMFS way too fat .. X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I don't know if its the new toolchain, or if its general kernel bloat, but a 5.0 BOOTMFS is nowhere near fitting onto a floppy: % ls -lR /mnt/ total 1205 drwxr-xr-x 2 root wheel 512 Oct 25 21:37 boot/ -rw------- 1 root wheel 1228800 Oct 25 21:37 kernel.gz /mnt/boot: total 198 -rw-r--r-- 1 root wheel 640 Oct 25 21:37 device.hints -r-xr-xr-x 1 root wheel 196128 Oct 25 21:37 loader* -rw-r--r-- 1 root wheel 229 Oct 25 21:37 loader.rc And the size of BOOTMFS is: % ls -l kernel.gz -rwxr-xr-x 1 gallatin wheel 1396562 Oct 27 16:17 kernel.gz* I'm going to start trying to throw things over the side to lighten the load, but I'm a little unsure how the driver floppy works. May I jettison all drivers which are modules? Or do I need to keep all possible scsi drivers required to boot the machine (in case we booted from a SCSI CD)? Or does a different kernel get used for CD boots? Or can /boot/loader make itself useful and load the drivers? Thanks, Drew PS: My peeking at this in no way represents a commitment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message