All,
I am trying to build a custom kernel, following the howto and some stuff i found on the forums (mkspec.patch)
1. the mkspec.patch gives an error:
[root@centos linux]# patch -p1 < mkspec.patch (Stripping trailing CRs from patch.) patching file scripts/package/mkspec Hunk #1 succeeded at 103 with fuzz 2 (offset 22 lines). Hunk #2 FAILED at 115. 1 out of 2 hunks FAILED -- saving rejects to file scripts/package/mkspec.rej
2. When i create an rpm out of the standard configfile (/boot/config....) the RPM file created is about 100mb which to me seems a bit large...?
Test wrote:
All,
I am trying to build a custom kernel, following the howto and some stuff i found on the forums (mkspec.patch)
- the mkspec.patch gives an error:
[root@centos linux]# patch -p1 < mkspec.patch (Stripping trailing CRs from patch.) patching file scripts/package/mkspec Hunk #1 succeeded at 103 with fuzz 2 (offset 22 lines). Hunk #2 FAILED at 115. 1 out of 2 hunks FAILED -- saving rejects to file scripts/package/mkspec.rej
- When i create an rpm out of the standard configfile (/boot/config....)
the RPM file created is about 100mb which to me seems a bit large...?
Personally I have always compiled my kernels a different way.
Grab the sources from www.kernel.org.
# tar -jxf kernel-2.6.20.tar.bz2 Decompress them. # make menuconfig <change your settings appropriately, often the only thing I change is the CPU type> (if this doesnt run properly try yum install ncurses-devel) Exit out of make menuconfig
# make bzImage # make modules # make modules_install # make install
If you have a dual core machine run each make command after menuconfig with -j2, replacing the number 2 with the amount of cores you have. This will run multiple compile jobs at once to save time.
Usually works ok for me - tho I never need to distribute my kernels so your milage may vary.
My first post to the list.
Alan
Alan,
The method you describe is the "standard" way of compiling a kernel, but for Centos the method seems to vary...
http://webui.sourcelabs.com/centos/mail/user/threads/Run_a_more_recent_kerne... http://www.howtoforge.com/kernel_compilation_centos http://wiki.centos.org/HowTos/Custom_Kernel
Test wrote:
Alan,
The method you describe is the "standard" way of compiling a kernel, but for Centos the method seems to vary...
http://webui.sourcelabs.com/centos/mail/user/threads/Run_a_more_recent_kerne... http://www.howtoforge.com/kernel_compilation_centos http://wiki.centos.org/HowTos/Custom_Kernel
The guide on the Wiki is maintained and is thoroughly tested (and ammended as necessary) for each new kernel release so I would strongly suggest you stick with that method. If you have any issues following that methodology I'm sure Akemi and Alan, the maintainers of that page, will be happy to assist you. Akemi is active on this list and I'm sure will respond in due course.
On Tue, Nov 11, 2008 at 1:56 AM, Ned Slider ned@unixmail.co.uk wrote:
Test wrote:
Alan,
The method you describe is the "standard" way of compiling a kernel, but for Centos the method seems to vary...
The guide on the Wiki is maintained and is thoroughly tested (and ammended as necessary) for each new kernel release so I would strongly suggest you stick with that method. If you have any issues following that methodology I'm sure Akemi and Alan, the maintainers of that page, will be happy to assist you. Akemi is active on this list and I'm sure will respond in due course.
Thanks, Ned, for waking me up by calling out my name loudly :-D
As Ned said correctly, you (OP) are doing it right by following the CentOS way. The "standard" way is strongly discouraged when building the CentOS kernel.
The problem I see is that your patch does not apply verbatim on the CentOS kernel. Take a look at the .rej file and find where it is failing. Line numbers are apparently not matching.
Akemi
-
Akemi Yagi -
Alan M Goodman -
Ned Slider -
Test