| 1 |
Graham Murray <graham <at> gmurray.org.uk> writes: |
| 2 |
|
| 3 |
You have to copy the .config from the running (old) |
| 4 |
> kernel to the new kernel directory before running make oldconfig. If you |
| 5 |
> start with the default config, then you have to run make menuconfig (or |
| 6 |
> config or xconfig) to customise it every time. |
| 7 |
|
| 8 |
|
| 9 |
Hmmmmm, |
| 10 |
|
| 11 |
|
| 12 |
I thought when you install a new kernel, you just change the symbolic link. |
| 13 |
|
| 14 |
example (old kernel linux-2.6.30-gentoo-r4) |
| 15 |
New kernel (linux-2.6.30-gentoo-r5) |
| 16 |
|
| 17 |
|
| 18 |
cd /usr/src |
| 19 |
rm linux |
| 20 |
ls -sf /usr/src/linux-2.6.30-gentoo-r5 linux |
| 21 |
cd linux |
| 22 |
make menuconfig |
| 23 |
|
| 24 |
|
| 25 |
At this point the new kernel sources (linux-2.6.30-gentoo-r5) |
| 26 |
automatically copies over the .config from the version |
| 27 |
of the kernel you are actually running. If no changes |
| 28 |
are required, save and build and setup new kennel. If something |
| 29 |
changes then the .config is modified by 'make menuconfig'. |
| 30 |
|
| 31 |
So minor kernel version revisions are trivial, but major |
| 32 |
kernel revision updated (like 2.6.30.x to 2.6.31.x) require |
| 33 |
your perusal of the menuconfig choices.....(caveat emptor). |
| 34 |
|
| 35 |
Did I miss something? Dirt simple. |
| 36 |
|
| 37 |
Here are my steps: |
| 38 |
|
| 39 |
from /usr/src/linux: |
| 40 |
make && make modules_install |
| 41 |
|
| 42 |
then |
| 43 |
cp System.map /boot/System.map-2.6.30-gentoo-r5 |
| 44 |
cp arch/x86_64/boot/bzImage /boot/kernel-2.6.30-gentoo-r5 |
| 45 |
cp .config /boot/config-2.6.30-gentoo-r5 |
| 46 |
|
| 47 |
|
| 48 |
Edit grub. Keep at least 2 copies of know working kernels |
| 49 |
around, in case you have to revert or look at something old |
| 50 |
|
| 51 |
Or did I miss something. That 'oldconfig' stuffage is |
| 52 |
not required any more. |
| 53 |
|
| 54 |
Or did I miss something? |
| 55 |
|
| 56 |
Last, if you are talking about hardware that is fixed |
| 57 |
(mobo, Hard drive (file systems), video cards(video drivers) |
| 58 |
etc etc, I always hard compile that into the kernel. I'd add to |
| 59 |
that mouse and keyboard, cause headaches can occur if |
| 60 |
those are loadable (others will disagree). But if you swap out |
| 61 |
usb keyboards quite often, either compile all choices into the |
| 62 |
kernel or use loadable modules. |
| 63 |
|
| 64 |
|
| 65 |
Stuff like external HD, usb or things that routinely get |
| 66 |
plugged and unplugged to/from the system, should definitely |
| 67 |
be loadable modules. imho. |
| 68 |
|
| 69 |
|
| 70 |
hth, |
| 71 |
James |
Archives