rpm files themselves (ie, blah-blah.x.y.rpm) can be manually removed.
You may end up downloading it again later, but those electrons need
something to do.
If the package has been installed, use rpm -e to remove the installed
files.
If /root is on /, check in the . files in /root for web browser
cache files, too.
------------------------------------------------------------------------
Jim Wildman, CISSP jim@rossberry.com
http://www.rossberry.com
On Wed, 30 Oct 2002, Mikes work account wrote:
> Take a lesson from what I have just gone through,,
>
> Those files in your boot directory are there because you installed each of
> those kernels and probably via RPM,,,if it is a RedHat distro. As I have
> learned manual and rpm management of files do not mix. If you want to
> remove a kernel do it with the rpm -e command and let that remove all those
> unneeded entries.
>
> I don't know how the other distros work but IMHO at least for RedHat,, don't
> mix manual and rpm management tools.
>
> Michael C. Rock
> Systems Analyst
> Registered Linux User # 287973
>
> "The time has come the Walrus said to speak of many things,,,"
> "Christians give up what they cannot keep,,to gain what they cannot lose"
>
> -----Original Message-----
> From: slug@lists.nks.net [mailto:slug@lists.nks.net]On Behalf Of Paul M
> Foster
> Sent: Tuesday, October 29, 2002 6:23 PM
> To: SLUG Suncoast Linux Users Group
> Subject: Re: [SLUG] What can I safely delete
>
>
> On Tue, Oct 29, 2002 at 05:42:08PM -0500, Thomas Ringate wrote:
>
> > I am updating an older Red Hat system, Release 7.0, using RHN Update Agent
> > and I need some space on the /boot partition.
> >
> > Presently there are four groups of files there
> > module-info-2.2.xxx
> > System.map-2.2.xxx
> > vmlinux-2.2.xxx
> > vmlinuz-2.2.xxx
> >
> > There is one each of these files for the following:
> >
> > 2.2.16-22
> > 2.2.19-7.0.1
> > 2.2.19-7.0.10
> > 2.2.19-7.0.12
> > 2.2.19-7.0.8
> >
> > In lilo.conf, only the
> > 2.2.16-22
> > 2.2.19-7.0.1
> > 2.2.19-7.0.8
> > are mentioned. 2.2.19-7.0.8 is what is being loaded.
> >
> > Not sure why I see these two:
> > 2.2.19-7.0.10
> > 2.2.19-7.0.12
> >
> > Would it be safe to delete those two groups to get the needed space for
> the
> > new update?
> > If I delete those two, is there any need to edit anything at all in
> > lilo.conf since they are not mentioned?
> >
> > In reading the documentation on lilo.conf it says you can have up to 16
> > different load modules, of course you would need disk space to hold them.
> > Since I have never had a need to go back to any of the older versions,
> > should I just delete them all and keep only the current version, and edit
> > lilo.conf
> > to reflect that, and then do the update?
> >
> > I have never tried to do anything like this before.
>
> 1. Back up all the stuff in this directory to somewhere safe.
> 2. Create a boot disk/rescue disk, if not already done.
> 3. Delete the version files from that directory which are not from your
> running kernel. (Use uname -a to get your kernel version.)
> 4. Re-run lilo to ensure safe bootaciousness. ;-}
> 5. Reboot.
>
> If all is okay, then you can start new tinkering in that directory. If
> not, you'll need to reboot with your rescue disk in single-user mode and
> copy the backed up files back to the boot directory. At that point,
> you'll have to experiment a little more to find what's deletable.
>
> Paul
>
>
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:09:55 EDT