Index: [Article Count Order] [Thread]

Date:  Mon, 12 Nov 2007 21:22:37 +0100
From:  "Taco Scargo" <taco (at mark) scargo.nl>
Subject:  [coba-e:11150] Re: /boot partition
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <02d901c82569$c467a620$14001fac@DELLP4TACO>
References:  <46C82A6F.4010106 (at mark) theanchoragesylvania.com> <C2F2ED1B.1AC7F%webmaster (at mark) muntada.com> <00e601c8253b$a2912ae0$7800000a (at mark) pc11> <47389056.6060006 (at mark) elirion.net>
X-Mail-Count: 11150

Please note that on most BQ installations /etc/grub.conf is a file and not a 
symbolic liink, so it is not updated.

Have a look at /boot/grub/grub.conf instead

Taco
----- Original Message ----- 
From: "Richard Siddall" <cobalt (at mark) elirion.net>
To: <coba-e (at mark) bluequartz.org>
Sent: Monday, November 12, 2007 6:41 PM
Subject: [coba-e:11149] Re: /boot partition


> Steffan wrote:
>> Hello,
>>
>> my /boot is full for 95 %
>> I know it is handled before on the list but I cant find the post back
>>
>> is there some info to how to cleanup the /boot partition Met vriendelijke 
>> groet,
>>
>> Steffan Noord
>>
>
> Goode dag ?
>
> Usually a /boot partition fills up because you have more kernels than
> you need due to downloading updates with yum.
>
> Do an "ls -1 /boot" and you should see a lot of "vmlinuz-2.*" lines.
>
> Unlike most RPMs, old versions of the kernel are kept around so if you
> can't boot into the new kernel, you can drop back to an old one that 
> worked.
>
> Do an "rpm -qa | grep kernel" to see which kernel RPMs are installed.
> You should be able to tell from the version numbers what's the latest
> and greatest.
>
> Have a look at /etc/grub.conf (assuming you're using grub as the
> boot loader) to see which kernel the computer boots from.  (uname -a also
> gives the kernel version.)
>
> If the computer doesn't boot from the latest kernel, do a reboot and
> select that kernel from the grub menu.  Make sure the computer can boot
> successfully from the latest kernel as you'll want to remove most of the
> old kernels.
>
> Once you've confirmed the latest kernel works correctly, delete the old
> kernels using rpm -e and the full version number of the kernel, e.g.:
>
> rpm -e kernel-2.6.18-2.el5
>
> Deleting old kernels should automatically change /etc/grub.conf if
> necessary.  You may want to double-check the settings in /etc/grub.conf
> after deleting kernels.
>
> I hope this helps.
>
> Regards,
>
> Richard Siddall
>
>
>