-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, Jun 17, 2007 at 12:18:57AM -0500, Doug Sutherland wrote: > I didn't know that make oldconfig would recognize new > options and prompt you for them. I guess that's because > I don't usually use oldconfig. Since having the right config > is the most important part of the kernel build, I always do > it from scratch, with only the new source tree and nothing > old in there. Oh boy. If I did that instead of being able to use oldconfig, I'd be upgrading to my own kernel build every 3 years or so. When I want to upgrade to a newer version, I take the .config from my existing version, slap it into the new source tree, do make oldconfig, compile, reboot, and bingo. The only scenario where this doesn't fully work is when going from 2.2 to 2.4, and from 2.4 to 2.6. When I did that, I still used oldconfig to take care of anything obvious (options marked as new), but I did go through both times, and verified the whole config carefully before compiling. Greg - -- web site: http://www.romuald.net.eu.org gpg public key: http://www.romuald.net.eu.org/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) - -- Free domains: http://www.eu.org/ or mail dns-manager at EU.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGdLxa7s9z/XlyUyARAjLHAJ9l4gi7n7g24zWen78w5dutUdA7HQCfXP5c 2rFFUIuM8nleMsBJ76U4Xsk= =Kqd2 -----END PGP SIGNATURE-----
