On Fri, 2003-08-22 at 13:00, Kent Borg wrote:
> On Fri, Aug 22, 2003 at 11:40:25AM -0500, Otto Haliburton wrote:
> > There were previous posting. His question was /boot is full. The
> > original response was to go to /boot and delete old kernels. That
> > is where RH places them and never deletes them.
>
> How so? Up2date doesn't let kernels collect in /boot.
>
> Are you installing new kernels with the RPM "-i" switch? If so, then
> rpm is doing what exactly what you are telling it to do. Don't blame
> Redhat.
>
> What Redhat recommends when undating your kernel is to use "-F" which
> will remove the old kernel, and /boot will not grow with each new
> kernel release.
Kent, please don't yell at me, because I completely support what you've
stated. I just wanted to suggest that the "-F" flag *not* be used for
upgrading a kernel, regardless of what Red Hat suggests. IMO, it's much
safer to install ("-i") the new kernel beside the new one, reboot to
test it, *then* delete the old kernel ("-e"). This way, you don't
drastically screw something up before you realize it.
Say, like upgrading your kernel which has custom wireless drivers
compiled as modules... leaving you unable to download the working
kernel.
Not that *I* know anyone who would ever do that. ;-)
--
Jason Dixon, RHCE
DixonGroup Consulting
http://www.dixongroup.net
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
