> holds true for normal packages, but also for the kernel RPM. There isn't > any mystic involved in a kernel RPM, so a rpm -qpi kernel.rpm will tell you > exactly where everything is going to end. > Now with tarballs I often have a hard time figuring out where everything is > placed after a make install. Alexander...maybe it's just my ignorance when it comes to rpms but my "gripe" about them is that I can't direct where those files are going. Am I wrong here? For instance, when it comes to kernel, I'd like to open it up in my home user directory and do a patch & compile there, keeping it completely separate from the operational system and even the operational source. Is there a way to do that? Cheers --- Larry
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
