Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I want to install Trend Micro ServerProtect on my CentOS 4.3 box, and have the following mini-dilemma.
The latest version of the kernel is 2.6.9-34.0.2.EL. As of this morning, the latest version supported by the Trend product appears to be 2.6.9-34.0.1.EL. Unfortunately, as I built (& patched) the box only a couple of days ago, the base version of the kernel at install was 2.6.9-34.EL, and the patched kernel is now at 2.6.9-34.0.2.EL. IOW, as I have installed and patched some time after the initial release, I don't have the intermediate version (2.6.9-34.0.1.EL) available to me.
While one solution is to run the base version of the kernel (2.6.9-34.EL), I would prefer if possible to run the latest version which is supported by the Trend product.
So: is there some way to force yum specifically to install an intermediate (earlier than latest, later than base) version of a package?
Thanks for any suggestions :-)
Last edited by neiljt; 07-14-2006 at 05:48 AM.
Reason: disambiguate title & main question
I thought Yum would only have the latest & gratest packages in it's reposities, unless you've found some reposity that holds a bit older packages or have created one yourself. Usually packages eat up a lot of space, so package reposities (like the ones used by Yum, pacman, apt etc..) only hold the latest packages since they're the ones people usually want to have. I recommend you to hold a cache of older versions on disk if it's possible, if you like to use such a package manager. I really don't know if there is a reposity for yum which would have older packages, but try searching by Google. I'd bet the ordinary reposities do not hold old packages if they have a possibility to use newer ones..
Are you unable to get the base package and patch it to the version you need?
I was hoping get a kernel package for the distro to get a match with the Trend Micro product. As it turns out, the "kernel hooking" module in question doesn't recognise as valid the kernel version I rolled back to, despite supposedly supporting this level. I suspect some kind of validation requirement for the "official" RHEL distro as opposed to the CentOS one I am using (grr, gnash, moan, etc.).
I'm only installing this thing to comply with site requirements, and not aware of any real value to doing so (though if anyone would like to jump in and educate me, I'd be interested!), so my hope is that the kernel hooking module is not necessary to run the product with some reduced capability that nonetheless complies with the requirement that this box should be accessible to a central AV server for our site.
Had the same issue. The installer checks /etc/redhat-release, which is different from RHEL's redhat-release. For CentOS 4.3 replace the contents of /etc/redhat-release with
Red Hat Enterprise Linux ES release 4 (Nahant Update 3)
Backup the original first of course. SPLX installs fine afterwards.
Thx a lot, I can install SPLX 2.5 using the about method now, but the SPLX can't be able to load the kernel module even I downloaded the SPLX kernel that same version with the Centos os Kernel i.e. "splxmod-2.6.9-34.ELsmp.o"