most efficient/fastest way to test sysinst improvements

What is the easiest and fastest way to test sysinst
changes?

In my case, running bochs or qemu is very slow. But using
gxemul to run 
different ports is very fast. So I am cross-building on
amd64 to cats to 
test my sysinst changes. This is very slow as is -- but once
I have the 
build all done I should be able to update sysinst just using
the 
arm--netbsd-elf-gcc.

Then I would just use ftp within the installer to fetch the
new sysinst I 
am working on and try it.

Anyways, what do you all do to test sysinst when you need to
do many 
times?

Several years ago when I modified sysinst to have automated
install (which 
I used in classroom), I think I used a chroot enviroment to
test my 
changes. Now that I remember that, I will try that again
...

  Jeremy C. Reed

On Fri, 28 Mar 2008, Jeremy C. Reed wrote:
> What is the easiest and fastest way to test sysinst
changes?

vnconfig an empty disk image, and sysinst will offer vnd0 as
possible disk 
to install to. Boot the image in qemu later to see if
everything worked 
ok.


  - Hubert

On Fri, Mar 28, 2008 at 09:11:49PM -0500, Jeremy C. Reed
wrote:
> What is the easiest and fastest way to test sysinst
changes?
> 
> In my case, running bochs or qemu is very slow. But
using gxemul to run 
> different ports is very fast. So I am cross-building on
amd64 to cats to 
> test my sysinst changes. This is very slow as is -- but
once I have the 
> build all done I should be able to update sysinst just
using the 
> arm--netbsd-elf-gcc.

If you have a xen sever you could use an INSTALL_XEN*$
kernel. A domU
boots very fast 

-- 
Manuel Bouyer <bouyerantioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la
difference
--