From owner-freebsd-chat@FreeBSD.ORG Fri Oct 3 19:41:46 2003 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15A0716A4B3 for ; Fri, 3 Oct 2003 19:41:46 -0700 (PDT) Received: from s1.stradamotorsports.com (ip30.gte4.rb1.bel.nwlink.com [209.20.215.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2D7543FEA for ; Fri, 3 Oct 2003 19:41:42 -0700 (PDT) (envelope-from jcw@highperformance.net) Received: from s1.stradamotorsports.com (s1.stradamotorsports.com [192.168.1.201])h942fc71048000 for ; Fri, 3 Oct 2003 19:41:38 -0700 (PDT) (envelope-from jcw@highperformance.net) Date: Fri, 3 Oct 2003 19:41:38 -0700 (PDT) From: "Jason C. Wells" X-X-Sender: jcw@s1.stradamotorsports.com To: chat@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=0.0 required=5.0 tests=USER_AGENT_PINE version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Limitations of Crunchgen X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Oct 2003 02:41:46 -0000 I am working on a picobsd-esque system. It works so far. So far I have only crunched binaries of /bin and /sbin with statically liked libraries. The system is halfway between picobsd and minibsd. The intent is to run specialized servers, i.e. DNS only, mail only, KDC only. The system would be bigger than the floppy sized picobsd and so storage is less limited at 64MB of compactflash, but still pretty small. Is there a limit to how much code I can crunch into a single binary? Are problems likely to creep into the system in mysterious ways with massive crunching? What are some of the operational issues of running a system with /bin,/sbin,/usr/bin,/usr/sbin crunched as one big binary? *** The rest is fluff, but I wrote it already, so you can read it if you like. *** If a binary turns out to be 4MB, it will take some time to load. If the binary never gets LRUd out of main memory, it will never be reloaded. That sounds pretty cool to me. Most of the programs in the crunched binary would rarely be run anyway. For example, once bind loads up and reads its zone files, it really doesn't need much disc access. The only time programs would be run is when I login to poke around. I am thinking it will be really nice to read from compactflash once and only once during execution of the first program and then never have to read from "disc" again. Is this a correct assumption regarding how this will work? /bin and /sbin are really no problem. When I started to look at doing this /usr/bin, I started thinking that maybe this is too much stuff to crunch into one big binary. I have read that swapping on compact flash is verboten. I read up on minibsd. I don't like the notion of dynamic linked /bin and /sbin. Plus I am not getting anywhere near the 6.7MB of extra storage consumption by linking statically that that author claims. Well, I have gone and done it. This email risks getting no replies because it's too damn long. I'll give it a go, then come back in a couple days with a two paragraph message. Later, Jason C. Wells