From owner-freebsd-small Sat Apr 17 18:27:39 1999 Delivered-To: freebsd-small@freebsd.org Received: from Thanatos.Shenton.Org (Thanatos.Shenton.Org [209.31.147.195]) by hub.freebsd.org (Postfix) with ESMTP id 6ECA614EE9 for ; Sat, 17 Apr 1999 18:27:34 -0700 (PDT) (envelope-from chris@shenton.org) Received: (from chris@localhost) by Thanatos.Shenton.Org (8.9.3/8.9.2) id VAA75382; Sat, 17 Apr 1999 21:33:15 -0400 (EDT) (envelope-from chris) To: freebsd-small@freebsd.org Subject: "kernel" way too large, name not as in docs From: Chris Shenton Date: 17 Apr 1999 21:33:13 -0400 Message-ID: <87r9piww4m.fsf@Thanatos.Shenton.Org> Lines: 44 X-Mailer: Gnus v5.6.45/Emacs 20.3 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Been starting to play with building a PicoBSD kernel for a diskless PPP dial-out box to NAT my LAN. I'd like to be able to hand these out to friends and customers cuz they can't seem to get NT to do this, especially with leased lines. I'm using 3.1-STABLE built from cvsup a few hours ago. I followed the "build" process as described in the docs in the .../picobsd/doc/ dir and don't see a "picobsd.bin" kernel as described in the docs. I do see a "kernel" in the build dir but it's way too large for a floppy. Further it doesn't seem to change with different selections of dial, router, net, or isp. Is there some "make clean" I need to do first? It does seem to be installing old kernel images from .../sys/compile/PICOBSD-*.*/ rather than generating new ones the second time around. Below are the sizes of the kernel and fs.PICOBSD built in "build/" as well as the "kernel" built in /sys/PICOBSD-*.*/: __FILE_____SIZE__________________________ SELECTED_TYPE kernel fs.PICOBSD PICOBSD-*.*/kernel dial (init) 2917359 1638400 2917359 dial (oinit) 2917359 1638400 ?? router 2917359 839680 1925446 net 2917359 1740800 2892088 isp 3309508 1740800 3309508 I just did a build of isp (something I hadn't done earlier) as I was typing this and saw it announcing its load-up: loading kernel text data bss dec hex filename 1212986 1828508 141728 3183222 309276 kernel So on the name issue, is it just that the doc is out of sync with the build process and "kernel" is what I really want? Any hints why my kernel is sooooo large? This looks like cool stuff and I'm anxious to start playing with it. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message