Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 31 Oct 2001 12:56:29 -0800
From:      Luigi Rizzo <rizzo@aciri.org>
To:        Alfred Perlstein <bright@mu.org>
Cc:        Jordan Hubbard <jkh@winston.freebsd.org>, "Jordan K. Hubbard" <jkh@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject:   Testin CURRENT
Message-ID:  <20011031125629.D23297@iguana.aciri.org>
In-Reply-To: <20011031144518.B15052@elvis.mu.org>
References:  <bright@mu.org> <41899.1004559389@winston.freebsd.org> <20011031144518.B15052@elvis.mu.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011031125629.D23297>