> Wow, that is simple.
>
> I tried to use the SDK last night to compile madwifi drivers for
> dyne:II, and I failed. It's good to know that the nest option works.
> I'll give that a try tonight.
>
> One question about the nest - once you create it, if you make further
> changes to your system, do you have to "resave" the nest?

No. When you create the nest, it activates and when you change things
they get saved in the nest. The nest also activates on boot-up unless
you explicitly tell it not to (there is a yes/no dialog with a timeout).

You can treat the system just like a regular system.

One small exception is a unionfs-related quirk I ran across compiling
software. ./configure checks for a 'sane build environment' and there
were was a timestamp related issue. I worked around by compiling on my
regular hard drive, which can be accessed through /mnt/hdX/Y.

You can also move around nests or transfer them to different computers
or media by copying the 'dyne' directory.

One thing that didn't work for me were my USB-stick nests. Dyne didn't
recognize them at boot up although I could access the stick with rox.

Carlo