This one time, at band camp, Ken Foskey wrote: >Ahhh but this will destroy my current kernel settings for my development >machine. Not good, the last thing I want is freeswan on my dev box. > >There are more tricks to it than that.
Get a kernel tree somehow, from kernel.org or by installing a Debian kernel-source package. Make a directory in your home, like ~/linux. Get into that directory, unpack the kernel source (kernel-source-2.4.20 puts it in /usr/src/kernel-source-2.4.20), cd in and make menuconfig. Run fakeroot make-kpkg --revision=foo.1 kernel_image and it'll create a deb or your kernel which you can stick on any machine. If you want freeswan, there's a kernel-patch-freeswan package, too, which will install itself into /usr/src/modules. The manpage for make-kpkg talks about modules and patches, but here's how I do it: vi ~/.kernel-pkg.conf maintainer := Jamie Wilkinson email := [EMAIL PROTECTED] priority := Low patch_the_kernel := YES root_cmd := fakeroot MODULE_LOC = /home/jaq/src/linux/modules and so I unpack the module code (in my case, Michel Daenzer's drm-trunk for PPC) into ~/src/linux/modules and run make-kpkg --revision=willow.1 modules_image which bulids a package for the drm modules to install along with the kernel that was built for the same kernel. Oh, you run that make-kpkg in the toip of the kernel tree that you're building the modules for, not the modules directory. Same goes for patches, they get insalled into /usr/src/patches by default and make-kpkg can just read them from there (no need to make a local dir as make-kpkg just needs to read the patches, writes only to your kernel tree) -- [EMAIL PROTECTED] http://spacepants.org/jaq.gpg -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
