> 1) use the Dachstein-CD release with the IPSec that has X.509. > How do I get this "better" IPSec on the CD?
You'll have to burn one. There are instructions for making a new image in the readme, which is easily downloaded from the CD-Contents (no need to d/l the whole CD first!). The fact that your CD probably won't need to be bootable makes burning a new CD a WHOLE lot easier, as you won't have to worry about boot-images, el-torito emulation modes, &c. > 2) not sure my computer can boot a CD (486), so how do I configure > a floppy+CD machine to boot from floppy but use the Dachstein-CD? See the readme. Basically, you just boot off the 1440K floppy image that comes with the CD (I do this a lot when I'm testing, as updates to root are a whole lot faster to test booting from floppy, and I already have enough coasters :). > 3) maybe my own firewall rules, so where is the best place to hook > in my own f/w rules? Same places as always. Note the new rules have hooks for minor customizations, or you can just pull the whole firewall ruleset out and build your own. > Finally, I have a basic (no network) slink devel. system running the > 2.0.38 kernel. If I want to upgrade the kernel to 2.2.19 so the devel > system can be running the same kernel as my LRP (Dachstein), > what problems might I have. Is it as simple as compiling (or > downloading) a 2.2.19 kernel and overwriting a file, or must the kernel > be "installed"? What might fail to work after the upgrade? Hmm...it's been so long since I switched my slink system to 2.2.x I've forgotten. Their used to be some HOWTO info on the Debian pages that covered this. I don't know if those pages have been 'harvested' or not, but you can probably find mirrors or cached files via the search engines. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
