similar to: do not uninstall old when yum install new

--On Tuesday, March 26, 2019 10:07 AM +0800 wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote: > I have a specific needs that requires yum do not to uninstall old > version when install new one. For example, I found that > yum install kernel > will install new kernel, and old kernel will remained. But > yum install <something-else> > will uninstall old

The latest CentOS 5 kernel, 2.6.18-8.1.15.el5 broke my box and I had to drop back to 2.6.18-8.1.14.el5 before I could play DVDs with either Xine or mplayer. ( xine-0.99.5-1.el5.rf & mplayer-1.0-0.36.rc1try2.el5.rf ). This is no big deal to me -- as long as I can make certain that the older kernel doesn't go away. If I understand the installonly plugin correctly, an entry of tokeep=4 in

HI, with "exclude" in yum.conf I can exclude kernel-updates via: exclude=kernel* If I use installonlypkgs, what happend exactly? Like: installonlypkgs=kernel kernel-smp kernel-devel kernel-smp-devel kernel-largesmp kernel-largesmp-devel kernel-hugemem kernel-hugemem-devel What's the difference betwenn update and installonly? Thanx! ttyl, Django -- "Bonnie &

Nicolas Thierry-Mieg wrote on 24/08/2015 00:24: >> installonly_limit=3 >> >> >> This parameter works for standard kernel images, but does not work for >> rescue images: >> > <snip> >> Is there a way to keep rescue images within a certain limit? > > man yum.conf , search for installonlypkgs (that's on centos6, might vary in 7)

In order to keep only 3 kernel images on a CentOS 7 I edited /etc/yum.conf and I put installonly_limit=3 This parameter works for standard kernel images, but does not work for rescue images: $ ls -al /boot/vmlinuz* -rwxr-xr-x 1 root root 5027376 May 13 20:46 /boot/vmlinuz-0-rescue-2554e2ffad84452bb07401bed0a61089 -rwxr-xr-x 1 root root 3084288 Jun 27 06:42

I just updated to the most recent version of yum. I noticed that my yum.conf file had changed. The old one has: installonlypkgs=kernel kernel-smp kernel-devel kernel-smp-devel kernel-largesmp kernel-largesmp-devel kernel-hugemem kernel-hugemem-devel The new one does not have this option listed. I don't remember if that was a default setting or if I added it in. Do I need that line to be

> -----Original Messages----- > From: "Steven Tardy" <sjt5atra at gmail.com> > Sent Time: 2018-02-26 10:48:48 (Monday) > To: "CentOS mailing list" <centos at centos.org> > Cc: > Subject: Re: [CentOS] How to update modules in iniramfs fastly > > On Sun, Feb 25, 2018 at 8:29 PM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> > wrote:

Fine, it seems that upgrade kernel is the only effective solution. > On 18 Oct 2017, at 10:00 PM, Stephen John Smoogen <smooge at gmail.com> wrote: > > On 18 October 2017 at 04:50, wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote: >> I googled this issue and found so many people have encountered, but most of >> them just said "the newer kernel doesn't

> -----Original Messages----- > From: "Steven Tardy" <sjt5atra at gmail.com> > Sent Time: 2019-04-28 13:02:18 (Sunday) > To: "CentOS mailing list" <centos at centos.org> > Cc: > Subject: Re: [CentOS] Who is responsible to load NIC driver when boot up > > On Sat, Apr 27, 2019 at 11:44 PM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> >

I googled this issue and found so many people have encountered, but most of them just said "the newer kernel doesn't have this problem, so upgrade kernel". We can't upgrade kernel easily, so we need to *really* solve this problem. On 10/18/2017 04:41 PM, John Hodrien wrote: > On Wed, 18 Oct 2017, wuzhouhui wrote: > >> Does anyone have encountered same problem or

What do you mean? Wouldn't the kernel version always be the actual running version of the kernel that was booted? Ben On 3/26/19 6:16 PM, wuzhouhui wrote: >> -----Original Messages----- >> From: "Benjamin Hauger" <hauger at noao.edu> >> Sent Time: 2019-03-27 00:15:21 (Wednesday) >> To: centos at centos.org >> Cc: >> Subject: Re: [CentOS]

Hi, Recently, I encountered a interesting phenomenon that CentOS 6.3 running as normal even if I (my colleague, actually) installed a kernel that build for CentOS 7.x (e.g. kernel-3.10.0-327.el7.x86_64.rpm). I found kernel is mismatch accidentally when I using "uname -r" to check kernel version. So my question is what the harmness we will get if I install a el7 rpm into a el6 system?

Hi, I have a machine that recently had some file system corruption. fsck was able repair the file system but I am getting the following error when I try to do yum update: [Errno 21] Is a directory: '/var/lib/yum/yumdb/e/2f883c08e3b596b66fcc19c6b4d73b11c9aaa43e-e2fsprogs-1.41.12-14.el6_4.2-x86_64/checksum_type' In searching Google, some suggested renaming the yumdb but that just results

I know dracut can update modules in initramfs, but I think it is too slow. So I'm wondering what is the fastest way to update modules in initramfs of CentOS 7? Thanks!

Hi I have a small question about NIC driver (e.g. i40e) loading. Who is responsible to load i40e driver? And how does he knows we should load i40e, instead of ixgbe? Thanks.

I'm trying to find out from which repo I got xiphos and its matching sword libraries from, and somehow am not finding it. hints, anyone? thanks! -- ------------------------------------------------------------------------------- Under no circumstances will I ever purchase anything offered to me as the result of an unsolicited e-mail message. Nor will I forward chain letters,

Hi, I am a developer who worked on CentOS. Recently I am working on porting one of my block drivers from CentOS 6.x to CentOS 7.x. In newest kernel (kernel-3.10.0-693.17.1.el7) I found there is an issue in submit_bio()'s first argument: void submit_bio(int rw, struct bio *bio) The type of bi_rw of struct bio is unsigned long, and the number of enum rq_flags_bits also exceeds 32, so we

OS: CentOS 6.5. After I set multicast_router of bridge and it's port to 2, like following: echo 2 > /sys/devices/virtual/net/eth81/bridge/multicast_router echo 2 > /sys/devices/virtual/net/bond2/brport/multicast_router Then soft lockup occured: Message from syslogd at node-0 at Jan 9 15:47:12 ... kernel:BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0] And the call

I have a local yum repository for CentOS4, and from time to time I add new (custom) kernel RPMS. However, when I run 'yum update' on an SMP box, yum 'installs' the new kernel, kernel-devel and kernel-smp packages, but 'updates' the kernel-smp-devel package. i.e. I end up with multiple versions of the kernel, kernel-devel and kernel-smp packages, but only the latest

On the subject of kernel updates: I had my install kernel (2.6.18-8.el5xen) and 2.6.18-8.1.8.el5xen on the box. I was unable to originally boot the update (8.1.8xen) because of the 3ware driver issues (I needed to use a driver floppy at install time). I jumped through some hoops (which I am struggling to understand) with weak-updates to get the 2.6.18-8.1.8 kernel to see my raid devices, which