[Chugalug] Small /boot partitions must go!

wes wes at the-wes.com
Tue Nov 12 19:49:12 UTC 2013


that's the problem I've seen... every time a system update includes a new
kernel, it keeps the old one, and never prunes them.

-wes


On Tue, Nov 12, 2013 at 8:34 AM, Randy Yates <lpcustom at gmail.com> wrote:

> I'm just curious as to why one would need 1gb for /boot. Are we keeping
> the last 10 kernels just in case? Or is there another reason I'm missing?
>
>
> On Tue, Nov 12, 2013 at 10:47 AM, John Aldrich <jmaldrich at yahoo.com>wrote:
>
>> Quoting Mike Harrison <cluon at geeklabs.com>:
>>
>>  On Mon, 11 Nov 2013, Lynn Dixon wrote:
>>>
>>>> We have always ran 500MB for our /boot on our RHEL4, RHEL5, and  RHEL6
>>>> machines.
>>>> Having said that, we are also very proactive  when it comes to  server
>>>> maintenance as well.
>>>>
>>>
>>> Sometimes I babysit systems that don't get accessed very often, or
>>> can't be accessed very often.
>>>
>>> And this was an Ubuntu system.. with 900mb,
>>>
>>> I noticed the Redhat systems I just put up used a 500mb partition,
>>> and left it.. I'm not sure (yet) how well Yum cleans up /boot
>>> after new kernals. But I'll be babysitting them closer.
>>>
>>>  Redhat / Fedora does a pretty good job of cleaning up after new kernels.
>>
>> _______________________________________________
>> Chugalug mailing list
>> Chugalug at chugalug.org
>> http://chugalug.org/cgi-bin/mailman/listinfo/chugalug
>>
>
>
>
> --
> Google reads my email!
>
> _______________________________________________
> Chugalug mailing list
> Chugalug at chugalug.org
> http://chugalug.org/cgi-bin/mailman/listinfo/chugalug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://chugalug.org/pipermail/chugalug/attachments/20131112/30f537bc/attachment.html>


More information about the Chugalug mailing list