Kernel Compilation Question

Kernel Compilation Question

[Woody.Wu]

i got a RedHat box which running a 2.2.x kernel.  since its too old, i
decided to upgrade it to 2.6.x, but this might involving upgrading of
gcc, libc and lots of other things.  i don't want to bother to do that
and think i can build a kernel in another newer system (a slackware
running 2.6.x) and copy needed stuff over to the old box.  is it
possible?  if so, what stuff i have to copy from the newer box to the
old box? what i can imaged by far are: the bzImage file, the
/lib/modules/2.6.x directory.  are there still other things?

thanks in advance. 

-------------------------------- 
Landis+Gyr Metering (Zhuhai) Ltd. 
Tel:   +86 756 3229181 ext 2616 
Fax:   +86 756 3229183 
Email: Woody.Wu@cn.landisgyr.com 

Virginia Woolf: Someone has to die Leonard, in order that the rest of us
should value our life more. 

        - The Hours (2002) 


  

Re: Kernel Compilation Question

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

On Mon, 26 Sep 2005 09:00:44 +0200, "Woody.Wu" said:
> i got a RedHat box which running a 2.2.x kernel.  since its too old, i
> decided to upgrade it to 2.6.x, but this might involving upgrading of
> gcc, libc and lots of other things.  i don't want to bother to do that
> and think i can build a kernel in another newer system (a slackware
> running 2.6.x) and copy needed stuff over to the old box.  is it
> possible? 

If it's a RedHat old enough to include a 2.2 kernel, and you have to ask if
it's doable, I can *guarantee* that you don't have the technical experience
to track down all the little details.  That's a long time ago, and there will
be all sorts of little tiny things (for instance, if you use ipchains, you'll
need to switch to ipfilter instead).

It's possible, but by the time you chase down all the pre-requisites and
co-requisites, you will be better off just actually upgrading to something
more recent - even if you get it to work, you get all the joy the *NEXT* time
you have to make a system change.



[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

RE: Kernel Compilation Question

[Woody.Wu]

> -----Original Message----- 
> From: Alan Cox [ mailto:alan@lxorguk.ukuu.org.uk] 
> Sent: Monday, September 26, 2005 6:17 PM 
> To: Woody.Wu 
> Cc: linux-kernel@vger.kernel.org 
> Subject: Re: Kernel Compilation Question 
> 
> 
> On Llu, 2005-09-26 at 09:00 +0200, Woody.Wu wrote: 
> > and think i can build a kernel in another newer system (a slackware 
> > running 2.6.x) and copy needed stuff over to the old box.  is it 
> > possible?  if so, what stuff i have to copy from the newer 
> box to the 
> > old box? what i can imaged by far are: the bzImage file, the 
> 
> 
> Possible but there is so much stuff that has changed (and 6.x 
> has no updates any more for security fixes). 
> 
> I do a series of CD updates from 6.2 to 7.3, then 7.3 to 9 
> then 9 to Fedora Core 2, and FC2 to FC3 - If I had to do it 
> that way. But really it'll be quicker to back it up reinstall 
> and restore users/config/filestore 

thanks. can i download thoese 6.2 to 7.3 and 7.3 to 9 upgrading CDs from
redhat's site?  and by 'back it up and resinstall and restore', did you
mean i back up my files and install a new redhat from scratch?

thanks. 

> 
> 
> 

Re: Kernel Compilation Question

[Alan Cox]

On Llu, 2005-09-26 at 09:00 +0200, Woody.Wu wrote:
> and think i can build a kernel in another newer system (a slackware
> running 2.6.x) and copy needed stuff over to the old box.  is it
> possible?  if so, what stuff i have to copy from the newer box to the
> old box? what i can imaged by far are: the bzImage file, the


Possible but there is so much stuff that has changed (and 6.x has no
updates any more for security fixes).

I do a series of CD updates from 6.2 to 7.3, then 7.3 to 9 then 9 to
Fedora Core 2, and FC2 to FC3 - If I had to do it that way. But really
it'll be quicker to back it up reinstall and restore
users/config/filestore

Kernel compilation Question

[Balaji Ravindran]

Hi all,

I tried compiling the wireless 2.6 kernel on my debian machine using
make-kpkg and being lazy, i just did make defconfig, and saw that my
compilation went fine without any issues, but i noticed that there was
no ramdisk image that was generated when i installed the linux-image*.deb.

i did use --initrd option,

Was it because, using make defconfig compiles everything on the kernel
itself? Aren't there any 'm' option in defaults?(dunno just asking if
this is the case)

or did i miss something out

Please see if i missed some step

Summary of steps performed.

extracted wireless 2.6 source onto /usr/src

created symbolic link

make defconfig (i did not copy my existing config file to .config, i
just wanted to try out make defconfig option)

make-kpkg --initrd --append-to-version=foo --revision=bar kernel_image
modules_image kernel_headers

this created 2 files linux-image* and linux-headers*, i was missing the
modules image also(but that was a second question)

did dpkg -i linux-image*

updated grub and placed files in /boot, but did not create initrd image.
Why is that?

Thanks

Balaji R

Kernel compilation Question

[Balaji Ravindran]

Hi all,

I tried compiling the wireless 2.6 kernel on my debian machine using
make-kpkg and being lazy, i just did make defconfig, and saw that my
compilation went fine without any issues, but i noticed that there was
no ramdisk image that was generated when i installed the linux-image*.deb.

i did use --initrd option,

Was it because, using make defconfig compiles everything on the kernel
itself? Aren't there any 'm' option in defaults?(dunno just asking if
this is the case)

or did i miss something out

Please see if i missed some step

Summary of steps performed.

extracted wireless 2.6 source onto /usr/src

created symbolic link

make defconfig (i did not copy my existing config file to .config, i
just wanted to try out make defconfig option)

make-kpkg --initrd --append-to-version=foo --revision=bar kernel_image
modules_image kernel_headers

this created 2 files linux-image* and linux-headers*, i was missing the
modules image also(but that was a second question)

did dpkg -i linux-image*

updated grub and placed files in /boot, but did not create initrd image.
Why is that?

Thanks

Balaji R

Re: Kernel compilation Question

[Stefan Lippers-Hollmann]

Hi

On Saturday 21 November 2009, Balaji Ravindran wrote:
> Hi all,
> 
> I tried compiling the wireless 2.6 kernel on my debian machine using
> make-kpkg and being lazy, i just did make defconfig, and saw that my
> compilation went fine without any issues, but i noticed that there was
> no ramdisk image that was generated when i installed the linux-image*.deb.

For questions about Debian specific packaging helpers like 
kernel-package[1], you would better contact debian-user@lists.debian.org 
instead.

> i did use --initrd option,
[...]

Please read /usr/share/doc/kernel-package/README.gz [2], it explains which 
hook scripts you have to configure for generating an initramfs, --initrd is
not sufficient anymore[3] (since kernel-package 12.000).

Also consider that the Debian kernel team considers kernel-package to be 
deprecated in favour of the upstream kernel build system's own 
"make deb-pkg" target[4]. 

Unrelated to this topic, I'd suggest to take the configs of your running 
(distribution-) kernel as starting point, because this likely introduces 
the least amount of surprise (ide vs. libata storage layer, etc.).

Regards
	Stefan Lippers-Hollmann

[1]	http://packages.debian.org/sid/kernel-package
[2]	http://git.debian.org/?p=users/srivasta/debian/kernel-package.git;a=blob;f=README (line 284ff)
[3]	http://www.golden-gryphon.com/blog/manoj//blog/2009/04/07/Not_your_father__39__s_kernel-package/
[4]	http://lists.debian.org/debian-kernel/2009/10/msg00613.html

Re: Kernel compilation Question

[Balaji Ravindran]

Hi Stephen,

Thanks for your reply. Wow, the four references that you provided makes lot more sense to me. I shall try using some examples in readme mentioned below.

Thanks

Balaji R
On Nov 21, 2009, at 10:10 AM, Stefan Lippers-Hollmann wrote:

> Hi
> 
> On Saturday 21 November 2009, Balaji Ravindran wrote:
>> Hi all,
>> 
>> I tried compiling the wireless 2.6 kernel on my debian machine using
>> make-kpkg and being lazy, i just did make defconfig, and saw that my
>> compilation went fine without any issues, but i noticed that there was
>> no ramdisk image that was generated when i installed the linux-image*.deb.
> 
> For questions about Debian specific packaging helpers like 
> kernel-package[1], you would better contact debian-user@lists.debian.org 
> instead.
> 
>> i did use --initrd option,
> [...]
> 
> Please read /usr/share/doc/kernel-package/README.gz [2], it explains which 
> hook scripts you have to configure for generating an initramfs, --initrd is
> not sufficient anymore[3] (since kernel-package 12.000).
> 
> Also consider that the Debian kernel team considers kernel-package to be 
> deprecated in favour of the upstream kernel build system's own 
> "make deb-pkg" target[4]. 
> 
> Unrelated to this topic, I'd suggest to take the configs of your running 
> (distribution-) kernel as starting point, because this likely introduces 
> the least amount of surprise (ide vs. libata storage layer, etc.).
> 
> Regards
> 	Stefan Lippers-Hollmann
> 
> [1]	http://packages.debian.org/sid/kernel-package
> [2]	http://git.debian.org/?p=users/srivasta/debian/kernel-package.git;a=blob;f=README (line 284ff)
> [3]	http://www.golden-gryphon.com/blog/manoj//blog/2009/04/07/Not_your_father__39__s_kernel-package/
> [4]	http://lists.debian.org/debian-kernel/2009/10/msg00613.html