-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello all,

   I plan on running NetBSD 4 beta until the release version is ready.

   Let me first say that I've been running into some peculiarities with
the build system. I don't know if I'm using it wrong, or if there's a
problem somewhere, but just an instance is that sometimes I have to run
the build.sh-script twice (with identical command line). First it will
fail somewhere, and second time it will pass. Also, it understands that
it should build my custom kernel, but it doesn't understand _how_ to do
that. Is this any of this of interest to anyone? I could try to get a
more detailed description of the "problems", but since it takes several
hours to run the build, I'm not going to do that unless I know someone
is in the least interested in it.

   Anyway, to my question.. After battling the build system, I've
finally got a working NetBSD 4 booting off my USB memory key. The theory
is that it should use the sysctl init.root knob to chroot to wd0a once
it has booted.

   I have "kind of" verified that it works. It does boot, and it does
chroot (but to a non-existing device), but I didn't dare to chroot to my
real wd0a (it uses a dummy entry for now).

   Is there any danger in booting NetBSD 4 beta off my USB memory stick,
and have to init.root chroot to my 3.1 system on my hard drive? I'm
planning on moving my system to 4.0 beta completely, but I'd like to
start by finding out if I can get the encrypted root to work properly
before I begin repartitioning and installing 4.0, and doing so is much
easier if I start with a simple 4.0 kernel + 3.1 userland transition.

- --
Kind regards,
Jan Danielsson

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (NetBSD)

iD8DBQFGuz91uPlHKFfKXTYRChBgAJ4yD1rcV++4Q0TP6Wu4Vg9AGzvD3wCfYJKM
MAn+FuYi1zajeVWpvWoh31A=
=nOV6
-----END PGP SIGNATURE-----