search for: installonly_limit

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 oldest k...

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 --exclude=kernel* >> >> That worked to update everything else, but not remove the oldest kernel...

...about so I can clean it out? I see EIGHT initramfs files in /boot, two per kernel, same name but one has a kdump just before the .img suffix. do I need those for old kernels that I may or may not ever boot? (they're 30 to 50 MB each). For the moment I've edited /etc/grub.conf and changed installonly_limit from 4 to 3. (related question: do I need to manually remove the oldest kernel, having done this, or will yum/grub clean it up the next time there's a kernel to install?) thanks! Fred -- ---- Fred Smith -- fredex at fcshome.stoneham.ma.us -----------------------------...

...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 and I > believe that is what CentOS 7.3 will do by default. Can I just change yum.conf with the setting installonly_limit=2 to limit kernels installed too two?

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 /boot/vmlinuz-0-rescue-2be43759d5354...

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, m...

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

...tOS 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 'rpm -e', and then re-apply the update. In this case, it was necessary to use the 'yum update' command line vs the Update Applet due to an incomplete transaction from the failed update. Devin

...> > I see EIGHT initramfs files in /boot, two per kernel, same name but > one has a kdump just before the .img suffix. do I need those for old > kernels that I may or may not ever boot? (they're 30 to 50 MB each). > > For the moment I've edited /etc/grub.conf and changed installonly_limit > from 4 to 3. (related question: do I need to manually remove the > oldest kernel, having done this, or will yum/grub clean it up the > next time there's a kernel to install?) > I may be off-base here, but isn't that more a yum configuation issue? What is the installonly_limi...

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 --exclude=kernel* > > That worked to update everything else, but not remove the oldest kernel. > > How...

...8 Jan 2019 at 17:58, Robert Moskowitz <rgm at htt-consult.com> wrote: > > > 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 --exclude=kernel* > >> > >> That worked to update everything else, but not remo...

On Tue, 2019-01-08 at 17:22 -0500, 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 --exclude=kernel* > > That worked to update everything else, but not remove the oldest kernel. > >...

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

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.

...>>> >>> Is there an option to make dnf more reliable, to try the mirror url a >>> few times and check its availability? >>> >>> man yum.conf does not >>> >>> # cat /etc/yum.conf >>> [main] >>> gpgcheck=1 >>> installonly_limit=3 >>> clean_requirements_on_remove=True >>> best=True >>> skip_if_unavailable=False >>> >>> ExecStart=/usr/bin/dnf makecache --timer >>> >>> 2. I saw in the mailing list the messages about samba sssd dependency >>> issues. I g...

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 (that's on centos6, might vary in 7)

...lly 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 'rpm -e', and then re-apply the update. In this case, > it was necessary to use the 'yum update' command line vs the Update Applet > due to an incomplete transaction from the failed update. > Right. Ar...

Chris Murphy wrote: > 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). IIRC, we saw discussions elsewhere, and ... I think it'...

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?

On Wed, 16 Nov 2016, Matt wrote: > Can I just change yum.conf with the setting installonly_limit=2 to > limit kernels installed too two? I really wouldn't. You can scrape by with that if you also make sure you don't have dracut-config-rescue installed, but you can find yourself struggling even with that, and so have to micromanage even further. Upgrade a kmod, watch /boot fill up...