Why is it when i do a "yum list all kernel*" I only get 4 packages returned from the centosplus repo when in fact there are many many more if I go look in the RPMS folder where it's pulling the packages from?
I'm trying to install the basic unsupported kernel (smp) to get XFS support but it doesn't appear when i do a yum list nor can i seem to get it to install when i specify the rpm name itself. As if it isn't there when clearly it is..
nano /etc/yum.repos.d/CentOS-Base.repo
add the following repos, and it should get more options.
[dries] name=Extra Fedora rpms dries - $releasever - $basearch baseurl=http://ftp.belnet.be/packages/dries.ulyssis.org/redhat/el4/en/i386/dries/RPM...
[dag] name=Dag-RHEL-Yum baseurl=http://dag.linux.iastate.edu/dag/redhat/el$releasever/en/$basearch/dag http://www.mirrorservice.org/sites/apt.sw.be/redhat/el$releasever/en/$basear... http://mirrors.ircam.fr/pub/dag/redhat/el$releasever/en/$basearch/dag http://apt.sw.be/redhat/el$releasever/en/$basearch/dag
On Wed, Jul 05, 2006 at 05:39:26PM -0700, mike opoien enlightened us:
nano /etc/yum.repos.d/CentOS-Base.repo
I won't comment on the choice of editors...
add the following repos, and it should get more options.
Several problems with your suggestion:
1. Dries and Dag both package for rpmforge, so in fact these both give you the same thing.
2. RPMforge does package some kernel modules, but not full kernels.
3. Better than editing the CentOS-Base.repo file, you should create a new .repo file, since the CentOS file could be overwritten on later upgrades.
4. The OP was asking about the unsupported kernel, which is located in the CentOSPlus repository. Try enabling that repository either via the command line or by setting enabled=1 in Centos-Base.repo
5. The better option may be to use the kernel-module-xfs from the testing repo at dev.centos.org. This is updated code from SGI whereas the XFS support in the unsupported kernel is mostly untouched and out of date.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, Jul 05, 2006 at 09:31:22PM -0400, Matt Hyclak wrote:
On Wed, Jul 05, 2006 at 05:39:26PM -0700, mike opoien enlightened us:
nano /etc/yum.repos.d/CentOS-Base.repo
I won't comment on the choice of editors...
I agree. He should be using ed(1). :)
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
Great feedback. You are all dodging around the basic question though and thats why doesn't centosplus show all it's kernels when i do the yum list all kernel*?
centosplus repo *is* enabled in my Centos-Base.repo file..
The behavior with the list command *seems* to be that it only shows the most recent kernel which happens to be 2.6.9-34.107.plus.c4. When i look in the RPMS directory i see a unsupported kernel for 2.6.9.34.106 which doesn't appear in the list (as well as many more).
Gerald
On 7/5/06, Matt Hyclak hyclak@math.ohiou.edu wrote:
On Wed, Jul 05, 2006 at 05:39:26PM -0700, mike opoien enlightened us:
nano /etc/yum.repos.d/CentOS-Base.repo
I won't comment on the choice of editors...
add the following repos, and it should get more options.
Several problems with your suggestion:
- Dries and Dag both package for rpmforge, so in fact these both give you
the same thing.
RPMforge does package some kernel modules, but not full kernels.
Better than editing the CentOS-Base.repo file, you should create a new
.repo file, since the CentOS file could be overwritten on later upgrades.
- The OP was asking about the unsupported kernel, which is located in the
CentOSPlus repository. Try enabling that repository either via the command line or by setting enabled=1 in Centos-Base.repo
- The better option may be to use the kernel-module-xfs from the testing
repo at dev.centos.org. This is updated code from SGI whereas the XFS support in the unsupported kernel is mostly untouched and out of date.
-- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, Jul 06, 2006 at 10:25:06AM -0700, Gerald enlightened us:
Great feedback. You are all dodging around the basic question though and thats why doesn't centosplus show all it's kernels when i do the yum list all kernel*?
centosplus repo *is* enabled in my Centos-Base.repo file..
The behavior with the list command *seems* to be that it only shows the most recent kernel which happens to be 2.6.9-34.107.plus.c4. When i look in the RPMS directory i see a unsupported kernel for 2.6.9.34.106 which doesn't appear in the list (as well as many more).
That is yum's behavior. I'm not sure what else to tell you, it only shows the most recent version. What led you to believe otherwise?
On Thu, 2006-07-06 at 10:25 -0700, Gerald wrote:
Great feedback. You are all dodging around the basic question though and thats why doesn't centosplus show all it's kernels when i do the yum list all kernel*?
Maybe you don't have your config file adjusted to suit your needs? As delivered, the yum.conf has
pkgpolicy=newest
I don't find docs for this param in the normal man/info pages.
centosplus repo *is* enabled in my Centos-Base.repo file.
<snip>
On Thu, 2006-07-06 at 13:40 -0400, William L. Maltby wrote:
On Thu, 2006-07-06 at 10:25 -0700, Gerald wrote:
Great feedback. You are all dodging around the basic question though and thats why doesn't centosplus show all it's kernels when i do the yum list all kernel*?
Maybe you don't have your config file adjusted to suit your needs? As delivered, the yum.conf has
pkgpolicy=newest
I don't find docs for this param in the normal man/info pages.
Since curiosity often results in death to well-known felines, and I don't want to become collarateral damage, I did a little googling for you. Not helpful except to maybe discount any value at all for the parameter I mention. From
http://72.14.209.104/search? q=cache:mMPirhs9kFAJ:www.phy.duke.edu/~rgb/General/yum_article/yum_article.pdf+pkgpolicy+yum+configure+OR+configuration+-newest&hl=en&gl=us&ct=clnk&cd=5
we get this snippet ----------------------------------------------- pkgpolicy can be set to determine the order in which yum chooses to decide between two versions of the same package on different repositories it is using at the same time. -------------------------------------------------
So, no gain, just pain I guess. I wish they'd doc this crap where it belongs and save us all (?) some time.
centosplus repo *is* enabled in my Centos-Base.repo file.
<snip>
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, Jul 06, 2006 at 01:59:40PM -0400, William L. Maltby enlightened us:
On Thu, 2006-07-06 at 10:25 -0700, Gerald wrote:
Great feedback. You are all dodging around the basic question though and thats why doesn't centosplus show all it's kernels when i do the yum list all kernel*?
Maybe you don't have your config file adjusted to suit your needs? As delivered, the yum.conf has
pkgpolicy=newest
I don't find docs for this param in the normal man/info pages.
Since curiosity often results in death to well-known felines, and I don't want to become collarateral damage, I did a little googling for you. Not helpful except to maybe discount any value at all for the parameter I mention. From
http://72.14.209.104/search? q=cache:mMPirhs9kFAJ:www.phy.duke.edu/~rgb/General/yum_article/yum_article.pdf+pkgpolicy+yum+configure+OR+configuration+-newest&hl=en&gl=us&ct=clnk&cd=5
we get this snippet
pkgpolicy can be set to determine the order in which yum chooses to decide between two versions of the same package on different repositories it is using at the same time.
So, no gain, just pain I guess. I wish they'd doc this crap where it belongs and save us all (?) some time.
I bet Seth wouldn't complain if you sent him a patch ;-)
On Thu, 2006-07-06 at 14:07 -0400, Matt Hyclak wrote:
On Thu, Jul 06, 2006 at 01:59:40PM -0400, William L. Maltby enlightened us:
On Thu, 2006-07-06 at 10:25 -0700, Gerald wrote:
<snip>
I bet Seth wouldn't complain if you sent him a patch ;-)
I'd love to. But ATM, I can't even discern OT from non-OT on this list. How am I to presume I know enough about all this stuff that passed me by over the years?
Even more, I'd probably have to read code (again) to have any confidence at all that what I came up with had any value. I did my decades at that and have interest only occassionally now.
I believe I get what I pay for, so only sporadic mumbling gripes of insignificance here.
Ya i couldn't find alternative setting for pkgpolicy either though the more I think about it the less i care. I would prefer it stay set to newest. That *does* seem to be why i don't see many of the older packages even though i'm saying to list all.
I find it interesting that a yum update always grabs the newest kernel regardless of repository or kernel type. e.g. if i run the unsupported hugemem kernel and a newer one comes out that is supported hugemem, it'll install that even though it's not the unsupported kernel. I've also seen it install the regular smp kernel and not the hugemem one because the regular smp kernel was newer. It seems to only care about what kernel is newest and doesn't take context into consideration. Sometimes that'll be from the centosplus repository if i have it enabled, sometime it'll be from the regular repo.. The bottom line is it's best to run yum update carefully when looking for a newer kernel esp if you're dealing with some specific support requirement such as in my case where i'm looking for hugemem, smp, and XFS support.
Gerald
On 7/6/06, William L. Maltby BillsCentOS@triad.rr.com wrote:
On Thu, 2006-07-06 at 13:40 -0400, William L. Maltby wrote:
On Thu, 2006-07-06 at 10:25 -0700, Gerald wrote:
Great feedback. You are all dodging around the basic question though and thats why doesn't centosplus show all it's kernels when i do the yum list all kernel*?
Maybe you don't have your config file adjusted to suit your needs? As delivered, the yum.conf has
pkgpolicy=newest
I don't find docs for this param in the normal man/info pages.
Since curiosity often results in death to well-known felines, and I don't want to become collarateral damage, I did a little googling for you. Not helpful except to maybe discount any value at all for the parameter I mention. From
http://72.14.209.104/search? q=cache:mMPirhs9kFAJ:www.phy.duke.edu/~rgb/General/yum_article/yum_article.pdf+pkgpolicy+yum+configure+OR+configuration+-newest&hl=en&gl=us&ct=clnk&cd=5
we get this snippet
pkgpolicy can be set to determine the order in which yum chooses to decide between two versions of the same package on different repositories it is using at the same time.
So, no gain, just pain I guess. I wish they'd doc this crap where it belongs and save us all (?) some time.
centosplus repo *is* enabled in my Centos-Base.repo file.
<snip>
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Bill
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQBErU+M/1DcCJj5ZgkRAm00AJ9OMLAXJNIP1UM20Jag1Fw13g789QCfWRdv 9kLfCW99ygXYXyMXgIv8nSE= =XB3D -----END PGP SIGNATURE-----
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I find it interesting that a yum update always grabs the newest kernel regardless of repository or kernel type. e.g. if i run the unsupported hugemem kernel and a newer one comes out that is supported hugemem, it'll install that even though it's not the unsupported kernel. I've also seen it install the regular smp kernel and not the hugemem one because the regular smp kernel was newer. It seems to only care about what kernel is newest and doesn't take context into consideration. Sometimes that'll be from the centosplus repository if i have it enabled, sometime it'll be from the regular repo.. The bottom line is it's best to run yum update carefully when looking for a newer kernel esp if you're dealing with some specific support requirement such as in my case where i'm looking for hugemem, smp, and XFS support.
This is exactly why you can include/exclude certain packages in individual repositories, and why the protectbase plugin for yum is nice.
On Thu, Jul 06, 2006 at 12:25:24PM -0700, Gerald wrote:
I find it interesting that a yum update always grabs the newest kernel regardless of repository or kernel type. e.g. if i run the unsupported hugemem kernel and a newer one comes out that is supported hugemem, it'll install that even though it's not the unsupported kernel. I've
You can use the "protectbase" plugin to change this first behavior.
also seen it install the regular smp kernel and not the hugemem one because the regular smp kernel was newer. It seems to only care about
Change DEFAULTKERNEL in /etc/sysconfig/kernel to be kernel-hugemem instead of kernel-smp.
Yum itself will upgrade whatever is installed -- it won't switch between actually _installing_ hugemem and smp unless one is marked as obsoleting the other.
what kernel is newest and doesn't take context into consideration.
Yes; yum is not designed to take "context" into consideration.
-
Gerald -
Jim Perrin -
Matt Hyclak -
Matthew Miller -
mike opoien -
Rodrigo Barbosa -
William L. Maltby