Well, that's not really the technique that I was going to use. That uses large files that you mount as encrypted filesystems, rather than encrypting the entire partition. Here's what I plan to do:
1) tar.bz2 entire current system of slack. Send it over to my main box and burn it on a cd.
2) Create a boot floppy w/ cryptoapi enabled so that I can make 2 partitions, /dev/hda1 (8MB... /loader) will be used to mount encrypted /dev/hda2 (/).
3) Unpack the contents of my backup cd onto the newly created partitions and see if it works.
4) repeate steps 1-3 over and over again till the freak'n thing works
I'm using this as a guide for the encryption part:
http://hints.linuxfromscratch.org/hints/cryptoapi.txt
But I was just wondering if this is going to suck up a crapload of memory.... Anybody done something like this before?
Or does anybody have any good baseline tests I can do so I see what it takes up?