kernel emerge results in weird kernel name

mjbjr · Guru Joined: 02 Mar 2003 Posts: 301

I wanted to emerge an older gentoo-dev-sources kernel than
gentoo-dev-sources-2.6.8-r3, 2.6.4 specifically. So I did the following:

emerge /usr/portage/sys-kernel/gentoo-dev-sources/gentoo-dev-sources-2.6.4-r1.ebuild

* After installing a new kernel of any version, it is important
* that you have the appropriate /etc/modules.autoload.d/kernel-X.Y
* created (X.Y is the first 2 parts of your new kernel version)

* For example, this kernel will require:
* /etc/modules.autoload.d/kernel-2.6

* If you choose to use UCL/gcloop please ensure you compile gcloop
* without -fstack-protector.

(snip)

>>> sys-kernel/gentoo-dev-sources-2.6.4-r1 merged.

I do:

localhost new_soft # mkdir /etc/modules.autoload.d/
localhost new_soft # mkdir /etc/modules.autoload.d/kernel-2.6

When I check on the install I see that in /usr/src it's shown as
linux-2.6.4-gentoo-r1

and when I do:

localhost src # emerge -p gentoo-dev-sources
These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild N ] sys-kernel/gentoo-dev-sources-2.6.8-r3

portage doesn't seem to see the just emerged kernel.

Have I done something wrong?
Why doesn't portage see the newly emerged kernel?
Why was the kernel name changed?

Thank you.

Also, I've been looking for a doc that shows what kernel config
choices are needed for a "standard" system these days, as in
what's needed for proper usb functionality, and other "expected
things" by your "typical" user. Probably, something that genkernel
would give, but without using genkernel.

Is there such a doc?

Thank you again.

GatoVolador

Hello,

mjbjr · Guru Joined: 02 Mar 2003 Posts: 301

Thank you for taking the time to reply. I appreciate it.

Pink · Veteran Joined: 24 Jul 2003 Posts: 1062

A couple of things possibly to clarify jayb's post:

When emergeing a kernel it is slightly different than a 'normal' prog as it doesn't remove old kernels (you can have as many kernels in /usr/src as you want).

So you when emerged gentoo-dev-sources-2.6.4-r1, and try to simply do an 'emerge gentoo-dev-sources' it ignores the older kernel(s) and tries to install the latest version in portage (unless you mask them as jayb said). I can see nothing wrong there at all.

I really don't understand what you mean by 'portage/ebuild changed the name of the kernel'.

You installed gentoo-dev-sources-2.6.4-r1 and you have linux-2.6.4-gentoo-r1 in your user sources, i.e. the kernel you installed. If you installed win4lin-sources-2.6.7-r3 you would see linux-2.6.7-win4lin-r3 (or similar).

The kernel name (from portage, only indicates the patchsets that are in the kernel version), so gentoo-dev-sources-2.6.4-r1 is the linux-2.6.4 kernel with the gentoo dev (r1) patches, thus linux-2.6.4-gentoo-r1. Hope that makes sense but as far as I can see nothing is wrong at all.

Anarky · n00b Joined: 25 May 2003 Posts: 30 Location: France

that's not a bug, that's a feature !!! :wink:

if you want to see what versions of a package you have installed, I suggest you :

desertstalker · Apprentice Joined: 18 Sep 2004 Posts: 209

GatoVolador · Posted: Fri Oct 01, 2004 6:49 pm Post subject:

Hello again,

The key is not to be deceived by the Portage output. As PickledOnion points out, merging a new kernel does not unmerge any older versions. You can have as many kernel sources and as many different versions of the same kernel sources as you'd like. For example, I've got at least three versions of gentoo-dev-sources and another couple versions of nitro-sources in my /usr/src with no problems or conflicts.

Hope things are clearer now, regards,
Jay