similar to: How do I remove a kernel

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

On Tue, 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

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

I have the following kernels on my /boot: 2.6.18-128.1.6 2.6.18-92.1.18 2.6.18-92.1.22 I'm low on /boot space and need to remove the oldest version. It appears that I cannot use yum to remove since all of the versions are the same (only the release is different). I believe that I can use rpm to remove the old version, but I also need to remove them from the grub.conf. Any other

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

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

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

Hello CentOS users, in the recent time I keep getting the logwatch warnings from my 2 dedicated servers running CentOS 7.4.1708. I guess because of the numerous kernel updates (because of Spectre+Meltdown) in the near past? Could someone please suggest me, which files in my /boot partition would be safe to delete? I would like to avoid the situation of having to boot the rescue partiton etc.

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,

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

On 2/19/19 1:50 AM, Aki Tuomi via dovecot wrote: > > > On 17.2.2019 10.46, Aki Tuomi via dovecot wrote: >> >>> On 17 February 2019 at 10:38 Odhiambo Washington via dovecot < >>> dovecot at dovecot.org <mailto:dovecot at dovecot.org>> wrote: >>> >>> >>> On Sun, 17 Feb 2019 at 11:34, Marc Weustink via dovecot < >>>

Le mardi 25 avril 2017 ? 11:19 +0200, Robert Moskowitz a ?crit : > /usr/lib/ld-2.17.so This file is not part of CentOS 7, nor CentOS 6 ? -- Laurent Wandrebeck <l.wandrebeck at quelquesmots.fr>

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

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)

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

Le mardi 25 avril 2017 ? 11:36 +0200, Robert Moskowitz a ?crit : > > On 04/25/2017 11:29 AM, Laurent Wandrebeck wrote: > > Le mardi 25 avril 2017 ? 11:19 +0200, Robert Moskowitz a ?crit : > >> /usr/lib/ld-2.17.so > > This file is not part of CentOS 7, nor CentOS 6 ? > > I am running Centos 7 armv7hl > > So it IS possible that I am missing something that

On 03/02/2017 08:53 PM, Warren Young wrote: > On Mar 2, 2017, at 6:36 PM, Robert Moskowitz <rgm at htt-consult.com> wrote: >> I want to image the drive at various 'checkpoints' so I can go back and redo from a particular point? >> what dd params work? >> >> dd if=/dev/sdb of=os.img bs=1M count=3210 > That looks plausible. (I haven?t verified your count

I have performed the 5.1 update via the 5 repo on a couple of systems. I then went to switch these systems to my new local repo using ther $releasever variable. It still has the value of 5, not 5.1 Where is this set? Why was it not changed to 5.1? On the one clean install from the 5.1 isos, $releasever is at 5.1 I think.

In my new Centos7 BIND DNS server, I am seeing messages in logwatch about GeoIP. Something new for me to learn about, and it seems, configure. Checking to see what packages are available I find: GeoIP.armv7hl 1.5.0-11.el7 @centos-base_rbf GeoIP-data.noarch 1.5.0-11.el7 base GeoIP-devel.armv7hl 1.5.0-11.el7 base

On 5/25/2017 10:04 AM, Robert Moskowitz wrote: > > > On 05/25/2017 09:32 AM, Leon Fauster wrote: >>> Am 25.05.2017 um 15:27 schrieb Robert Moskowitz <rgm at htt-consult.com>: >>> >>> Thanks. I followed this to: >>> http://mirror.centos.org/centos/7/os/x86_64/Packages/ >>> >>> And could not find any of the following: