freebsd-skq/tools
phk e493c53029 Release the evil twin of nanobsd.sh: sysbuild.sh
quoth the README:

I have been running -current on my laptop since before FreeBSD 2.0 was
released and along the way developed this little trick to making the
task easier.

sysbuild.sh is a way to build a new FreeBSD system on a computer from
a specification, while leaving the current installation intact.

sysbuild.sh assume you have two partitions that can hold your rootfs
and can be booted, and roughly speaking, all it does is build a new
system into the one you don't use, from the one you do use.

A partition named /freebsd is assumed to be part of your layout, and
that is where the sources and ports will be found.

If you know how nanobsd works, you will find a lot of similarity.
2009-01-17 20:30:06 +00:00
..
build add missing options 2008-09-23 16:15:42 +00:00
debugscripts o Correct comments: remove a reference to non-existent gdbinit.9 man page; 2006-05-22 07:12:25 +00:00
diag Start the dreaded NOFOO -> NO_FOO conversion. 2004-12-21 08:47:35 +00:00
kerneldoc Remove ISDN4BSD (I4B) from HEAD as it is not MPSAFE and 2008-05-26 10:40:09 +00:00
KSE Start the dreaded NOFOO -> NO_FOO conversion. 2004-12-21 08:47:35 +00:00
LibraryReport
regression Be more Solaris-friendly. 2009-01-16 18:09:49 +00:00
sched - Add a new source configuration menu option that allows hiding and 2009-01-17 11:19:15 +00:00
test This is simple testing program for revision 185647. 2008-12-06 13:23:53 +00:00
tools Release the evil twin of nanobsd.sh: sysbuild.sh 2009-01-17 20:30:06 +00:00
install.sh Arguments to options aren't necessarily separated with whitespace. 2004-07-07 09:38:14 +00:00
make_libdeps.sh - Add cddl/lib to the list of library directories. 2007-10-01 18:11:43 +00:00
README

$FreeBSD$

This directory tree contains tools used for the maintenance and
testing of FreeBSD.  There is no toplevel Makefile structure since
these tools are not meant to be built as part of the standard system,
though there may be individual Makefiles in some of the subdirs.

Please read the README files in the subdirs for further information.