similar to: CentOS 7 - Limiting rescue kernel imeges

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)

On 08/23/2015 12:23 PM, Luigi Rosa wrote: > 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: > <snip> > Is there a way to keep rescue images within a certain limit? man yum.conf , search for installonlypkgs

Hi, 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 version after install new one, how to disable it? Thanks.

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 &

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

Sorry - noob-ish question.. I have been having problems on a CentOS 4.2 server following an upgrade to the latest version of SugarCRM (segfaults in Apache and some functions not working). Someone has just posted in the SugarCRM forums that they had exactly the same problems on CentOS 4.2 and they fixed them by upgrading from PHP 4.3.9 to 5.0.5. Being a more cautious chap, I'd like to try an

I have 4 kernels in /boot, leaving on 20MB which is not enough for the next one. I had installonly_limit= set at 5, as there were some kernel problems.? After I got the error that there was not enough room for another kernel, I set installonly_limit= to 3 and did the update with --exclude=kernel* That worked to update everything else, but not remove the oldest kernel. How can I remove the

I have 2 servers: On both, I did yum update. One upgraded the kernel, the other didn't. Why? TIA, Dave Augustus

--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

Hi all, I installed XEN on a CentOS 6 server, as per these instructions: http://www.crc.id.au/xen-on-rhel6-scientific-linux-6-centos-6-howto/ And the server now gives this error on reboot: PANIC: early exception 0e rip 10:0 error 10 cr2 0 These are the packages that were installed before the reboot: Total download size: 33 M Installed size: 116 M Is this ok [y/N]: y Downloading Packages:

On 1/8/19 5:30 PM, mark wrote: > Robert Moskowitz wrote: >> I have 4 kernels in /boot, leaving on 20MB which is not enough for the >> next one. >> >> I had installonly_limit= set at 5, as there were some kernel problems. >> After I got the error that there was not enough room for another kernel, >> I set installonly_limit= to 3 and did the update with

I've recently had this problem on two C7 systems, wherein when doing "yum update", I get a warning about /boot being low on space. both systems were installed using the partition size recommended by Anaconda, right now "df -h" shows /boot as 494M, with 79M free. I don't store unrelated crap on /boot, I assume that yum and/or grub will manage it for me. So, why, after

>> What size is recommended for the /boot partition? After doing a fresh >> install and lengthy backup restore I realized I only made it 200M. Is >> this going to be a problem? > > Mine was about 500 MB and I removed some kernels because I got a warning the > partition was getting full. > > With only two kernels installed, 182 MB are used. I would suggest 1 GB

Default boot volume on Fedora is 500M, with a kernel installonly_limit of 3. So far this seems sufficient, even accounting for the "rescue kernel" (which is really a nohostonly initramfs, which is quite a bit larger than the standard hostonly initramfs used for numbered kernels).

I have a CentOS 6 machine that was initially installed as CentOS 6.4 in May of 2013. It's /boot filesystem is 200M which, IIRC, was the default /boot size at the time. The most recent kernel update (2.6.32-573.18.1.el6) fails because of lack of space in /boot. The workaround is edit /etc/yum.conf, reduce installonly_limit from 5 to something lower (I used 3), remove the oldest kernel via

First off - let me say I am not an administrator.?? I need to know?if there is an easy way to increase my /boot partition.? When I installed CentOS 6 after running 5, it was my oversight not to increase the /boot size.? it's too small and I can't do yum updates. if it's not easy to actually increase it, is it safe to take a chunk in my root filesystem (like /new.boot or something) and

Here we go again: Hi all. Most of you already know about my problems (well, my computer?s problems ;-) ), since we?ve been discussing on the forum. Hughesjr recommended me to post here, so let?s see, I have my faith on you I have a dedicated server with RH9 that I upgraded to CentOS 3.4 . Everything ok, but after the first yum upgrade and reboot I get this when I try to do a yum update:

Hi all. Most of you already know about my problems (well, my computer's problems ;-) ), since we've been discussing on the forum. Hughesjr recommended me to post here, so let's see, I have my faith on you. I have a dedicated server with RH9 that I upgraded to CentOS 3.4 . Everything ok, but after the first yum upgrade and reboot I get this when I try to do a yum update: yum

Hello everybody, What is the status of the freeipa/sssd and samba conflicts in the repositories? I can not wrap my mind around that two big packages are not getting security updates anymore, because they are conflicting. I will go to FOSDEM in Belgium this year to figure out more, but I am considering moving my centos systems to rockylinux. Kind regards, Jelle de Jong On 12/16/22 16:59,

What size is recommended for the /boot partition? After doing a fresh install and lengthy backup restore I realized I only made it 200M. Is this going to be a problem?