Mr O wrote: > >Also, package uninstallation. Apparently to remove an RPM package you just >type 'rpm -u or -e (package name) and that's all right? Seems the computer >wants to tell me these packages aren't installed. Is there a work around for >that? Tar.gz files are just drop into the directory and do 'make clean' >right? Trying to make some space here. Thanks for the help y'all. > You can try rpm -q <package name> to see if the package is installed. You don't need to include versioning information, so if you have snafu-1.3-4.i386 installed, just type rpm -q snafu and it will let you know if the package is installed. If it's installed, use rpm -e <package name> to erase it. If you just have the .rpm files around, you can just delete them, they are not tied to the packages on the system in any way. Perhaps this is why it's telling you they are not installed? Otherwise, if rpm -q tells you the package isn't installed, but you have some good reason to think it is, your rpm database might be corrupted. I've had this problem only once, and it was really a hardware problem, the hard drive I was using was damaged and getting worse. There are some tools to try to repair the database, but I don't know how to use them. Make clean will just delete the compiled object files, libraries, and executables built for an application you've compiled yourself. This can free up a considerable amount of space. Try running it on whatever kernel you've compiled, it won't affect the kernel image you copied over to /boot. Of course, if you ever need to tweak configuration or if you're making changes to source and need to recompile, it will have to build everything all over again.
Kahli
