#1: OK, let's start with first cases. Where did you download the tar.gz file to? I didn't move the *old* linux source code (linux-2.0.36) into a "/usr/src/linux" directory (that wasn't the impression I had from the McKinney outline). Besides, isn't 2.0.36 already *in* the /usr/src/linux-2.0.36 directory? Why bother moving it to a /usr/src/linux directory? #2: I used tar zxpvf linux-2.2.3.tar.gz I don't recall where it moved the file the first time. Again, my question is, where are you when you type "tar zxpvf", etc., and where was your 2.2.4.tar.gz file located when you issued the command? #3: When I did a cd linux (from root) I didn't get anywhere (as I described in my earlier message). I was thinking that setting the link meant that wherever you were, if you typed "linux" (or /linux, maybe), it would take you to the linked directory. Looks like that isn't correct? So let's assume then that you do cd linux from within /usr/src. OK. I'm comfortable with that. #4: I was following the McKinney instruction to make xconfig, but that didn't do anything. A man config search turned up several options, including make oldconfig!. So I did that (I figure, why throw away my old configuration work, although I realized that there are some important differences between 2.0.36 and 2.2.x kernels that may make this not a good idea). The second time I just did make config, and got the whole ball of wax of configuration choices. It reminded me of installing 5.3! I'm ready to do it again, although I sometimes wonder why... I'll do the RPM search thing, but apparently just typing "RPM -U name-of- RPM doesn't actually install the new files. At least as far as I can tell. But what's a simple way of finding out which version of any program, like Samba or the DHCPclient, a person has? I read this list regularly (even though it generates a lot of activity!) and I have searched the archive from time-to-time, just to find out these sorts of things. And what more *do* I have to do to ensure that all of those security updates I downloaded in the form of RPM's actually *do* get installed? Michael Perry said: I just did the 2.0.36 to 2.2.4 move. HEre is what I did. I went to the /usr/src directory and did mv /usr/src/linux /usr/src/linux2036. This creates a directory for my old kernel sources to live in. I then read the kernel howto and untarred the linux tar.gz sources with the command, "tar zxpvf linux2.2.4.tar.gz" and it moves the new sources into their home in linux. Now if you do a cd linux you are in the 2.2.4 sources tree. While in /usr/src/linux, do a make menuconfig and look at the topmost line of the program and it will say what kernel its compiling against. As far as finding exactly what you have with rpm files, try using the rpm -q command against a filename like rpm -q gtk. Dont include the entire rpm name; just the major name. If you have a file and you are unsure what version it belongs to try using the rpm -qf filename. IT will return what rpm the file belongs to. This is useful when you have a version of something you are unsure of and whether that version belongs to the most current rpm or whatever. Hope this helps. -- -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>