> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:redhat-list- > [EMAIL PROTECTED] On Behalf Of Kent Borg > Sent: Friday, August 22, 2003 12:14 PM > To: [EMAIL PROTECTED] > Subject: Re: /Boot is full - advice please > > On Fri, Aug 22, 2003 at 01:03:56PM -0400, Jason Dixon wrote: > > 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. > > That makes fine sense, in fact that is what I did with the most recent > Redhat kernel release because of what I read in this thread. > (Particularly because I don't have a CD ROM drive for this notebook.) > > I was responding to a post that said Redhat fills up /boot with old > kernels, when Redhat actually does nothing of the sort. > > > -kb > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED] > https://www.redhat.com/mailman/listinfo/redhat-list up2date does not delete old kernels from /boot or /usr/src, it continually adds them and that is what happened to the person who started this thread. Those of us who also experiment with other archives besides RH are used to manually removing and adding kernels and don't usually have this particular problem, but there is another aspect to removing with rpm's and that is it completely removes source and all other stuff and if you don't want do that and just want to remove the old kernel from grub and /boot you might consider doing it manually.
-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
