Re: Compiling new kernels4newbies. Consolidating different info from www

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I think, you are right: that's also - nearly - my process, when generating a kernel.
Just a few remarks: (7) 'make dep' is not necessary any more for 2.5 kernels,
according to their change logs.
Instead of copying the output files per hand (or mouse), I do a simple 'make install',
and just call 'lilo', after this. This would replace steps (12,14,15), and I have 
had troubles with kernels, that weren't installed using make.
Placing the kernel tree under /usr/src isn't always necessary: it depends on the
target: for instance, if you apply an uml-patch, you must _NOT_ have any references
to /usr/src.

BTW: step (6) is profitable - its easier and saver, to apply small changes
in the kernel configuration by editing the .config file, and doing a 'make oldconfig', then.
But, here I'd liked to post one question: what is the recommended procedure to translate
a new - say, 2.5 - kernel, based on the .config file of an elder one ? 

..Michael

On Wednesday 29 January 2003 19:56, dballester@kernpharma.com wrote:
> Hello:
>      I'had recomplied some kernels but I know that the internals of this
> proceses are very cryptic for me. I'm trying to read all I can in the www
> about kernel recompilation, but info available differs from site to site.
> Some people usually compiles with make <config-mode>, make dep, make
> bzImage, make modules, make modules_install and copy bzImage to boot. Some
> others seems to be more accurate and make mrproper first of all, make
> clean, depmod -a, etc...
>      With this info is not easy for me to learn the 'perfect' steps to
> recompile and install a new kernel. I've made a list with a merge from this
> sites to see  what's the best way. Your suggestions will be very, very,
> very, appreciated.
>
>      1 Decompress linux sources tarball under /usr/src
>      2 Make a soft link /usr/src/linux that points to the decompressed
> tree.
>      3 If any patch will be installed use patch -p1
>      4 make mrproper ( clean )
>      5 Configure the kernel using make config, menuconfig or xconfig
>      6 ( mine ) backup .config to another name ;)
>      7 make dep ( to resolve dependencies )
>      8 make clean
>      9 make bzImage
>      10 make modules ( here seems to be people saying that's good to rm -rf
> /lib/modules/<kernel-version> if we are recompiling )
>      11 make modules_install
>      12 depmod -a
>      13 backup /boot original image, System.map an /etc/modules.conf or
> change  names and modify lilo or grub properly. ( Me : What happens with
> module-info ? )
>      14  Copy bzImage , System.map to /boot and modules.conf to /etc
>      15 Modify lilo or grub to use new kernel
>      16 Try to restart.
>
> Any tips?
>
> TIA

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux