From owner-cvs-all Wed Oct 31 13: 0:12 2001 Delivered-To: cvs-all@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 72F3737B401; Wed, 31 Oct 2001 13:00:07 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id f9VKuT624438; Wed, 31 Oct 2001 12:56:29 -0800 (PST) (envelope-from rizzo) Date: Wed, 31 Oct 2001 12:56:29 -0800 From: Luigi Rizzo To: Alfred Perlstein Cc: Jordan Hubbard , "Jordan K. Hubbard" , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Testin CURRENT Message-ID: <20011031125629.D23297@iguana.aciri.org> References: <41899.1004559389@winston.freebsd.org> <20011031144518.B15052@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011031144518.B15052@elvis.mu.org> User-Agent: Mutt/1.3.23i Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Oct 31, 2001 at 02:45:18PM -0600, Alfred Perlstein wrote: ... > I would like to get a machine installed, -current seems to have other > issues with sysinstall at the moment, but I'll be glad to see what > I can do to fix those if they aren't related to the same problem. if you have the disk space, a good way to test current (at least cross builds and kernel stuff) is to build a PicoBSD image using the latest picobsd script (/usr/src/release/picobsd/build/picobsd) Given the following: XXX is a directory name of your choice "fcvs" is an alias to the cvs command to access the repository: "foo" is the name of a picobsd type (some are already in /usr/src/release/picobsd, e.g. "bridge" or others) # extract a source tree. Only need to do it once, takes # some time. (cd XXX ; fcvs co src) # build libraries and other stuff. You may need to tweak # src/include/stdio.h if you are running a pre-4.4. # You only need this once, it takes some time. # The stuff built here will be put in XXX/usr # picobsd --src XXX/src --init # now you can build picobsd images. You need sufficient # privileges to run vnconfig and mount, which are used # to build the bootable image. However, just compiling # stuff does not require special permissions. picobsd --src XXX/src -n -v foo in build_dir-foo/ you will find the following files: kernel is a bootable kernel (largish) which can be e.g. loaded with etherboot or pxe. This will be always created unless there are errors during the compilation phase. picobsd.bin is a bootable picobsd image, which can be dd'd on a floppy for booting. This file will not be created if it does not fit in a floppy. I have been using this approach for some time lately, and it is quite convenient for doing kernel development. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message