Re: Knowing you Patched the Kernel

["Jamin W. Collins" <jcollins@asgardsrealm.net>]

On Tue, Apr 29, 2003 at 10:46:33PM -0500, Doug MacFarlane wrote:

> How do you know you successfully patched the kernel?
> 
> I have PATCH_THE_KERNEL = AUTO and use the --apply_patched option to
> the make-kpkg command.
> 
> I also redirect all the output (via a > compile.output redirection) to
> a text file so I can read the messages and/or error messages.  
> 
> I thought that I had added the FreeSwan patch, but I can't tell.
> grepping compile.output for freeswan produces no matches.  The
> Makefile in the FreeSwan patch directory only echos text when there
> are errors.
> 
> How does one know it worked?  I'd hate to beat my head against the
> wall trying to get FreeSwan to work when I didn't actually get the
> kernel patched . . . . 

For the freeswan patch, you can check your .config file for IPSEC
entries.  You should have something like the following:

   CONFIG_IPSEC=m
   CONFIG_IPSEC_IPIP=y
   CONFIG_IPSEC_AH=y
   CONFIG_IPSEC_AUTH_HMAC_MD5=y
   CONFIG_IPSEC_AUTH_HMAC_SHA1=y
   CONFIG_IPSEC_ESP=y
   CONFIG_IPSEC_ENC_3DES=y
   CONFIG_IPSEC_ALG=y
   # CONFIG_IPSEC_ALG_MD5 is not set
   # CONFIG_IPSEC_ALG_SHA1 is not set
   # CONFIG_IPSEC_ALG_SHA2 is not set
   # CONFIG_IPSEC_ALG_3DES is not set
   CONFIG_IPSEC_ALG_AES=m
   # CONFIG_IPSEC_ALG_BLOWFISH is not set
   # CONFIG_IPSEC_ALG_CAST is not set
   # CONFIG_IPSEC_ALG_CRYPTOAPI is not set
   # CONFIG_IPSEC_ALG_NON_LIBRE is not set
   # CONFIG_IPSEC_ALG_NULL is not set
   CONFIG_IPSEC_ALG_SERPENT=m
   CONFIG_IPSEC_ALG_TWOFISH=m
   CONFIG_IPSEC_IPCOMP=y
   CONFIG_IPSEC_DEBUG=y
   # CONFIG_IPSEC_NAT_TRAVERSAL is not set
   
Also, near the top of the output you should see some indication of the
patches being applied.

-- 
Jamin W. Collins

This is the typical unix way of doing things: you string together lots
of very specific tools to accomplish larger tasks. -- Vineet Kumar