Greg Lopp on Fri, 9 Feb 2001 16:39:12 -0500 |
On Fri, Feb 09, 2001 at 04:08:45PM -0500, Rupert Heesom wrote: > On 09 Feb 2001 14:31:03 -0500, Greg Lopp wrote: > > On Fri, Feb 09, 2001 at 12:36:44PM -0500, Rupert Heesom wrote: > > > Mine looks like > > total 10 > > drwxr-xr-x 9 root root 1024 Feb 6 1996 . > > drwxr-xr-x 19 root root 1024 Feb 5 14:39 .. > > lrwxrwxrwx 1 1007 1007 12 Oct 23 23:56 linux -> linux-2.2.17 > > drwxr-xr-x 17 root root 1024 Feb 20 2000 linux-2.0.34 > > drwxr-xr-x 15 root root 2048 Feb 16 2000 linux-2.2.11 > > drwxr-xr-x 15 root root 1024 Feb 21 2000 linux-2.2.12 > > drwxr-xr-x 15 root root 1024 Feb 21 2000 linux-2.2.13 > > drwxr-xr-x 15 root root 1024 Sep 5 20:56 linux-2.2.14 > > drwxr-xr-x 15 root root 1024 Oct 24 21:32 linux-2.2.17 > > drwxr-xr-x 7 root root 1024 Jul 22 2000 redhat > > > > Greg: > > Based on your msg re the /usr/src directory, I tried changing mine - I > changed the "linux" fiel to be a link to the "linux-2.2.17" directory, > extracted the 2.2.17 kernel archive (which should have extracted into > /usr/src/linux..... > > What happened was that the archive extracted into /usr/src/linux, > changing the link file to be a directory. Did I do something wrong? No. I think that's normal (sad to admit that I haven't done that in a while.) You don't have to have a link or dirs that describe the kernel version, but it makes it easier to keep track. Just do cd /usr/src rm -rf linux-2.2.17 mv linux linux-2.2.17 ln -s linux-2.2.17 linux to remove the old dir, move the one you just extracted to a descriptive name and create the sym link. > > My directory now looks like (note - no link) - > > -rw-rw-r-- 1 root root 18130021 Feb 8 20:44 > kernel-source-2.2.17-14.i386.rpm > drwxr-xr-x 14 1007 1007 4096 Sep 4 13:58 linux > drwxr-xr-x 4 root root 4096 Feb 2 13:38 linux-2.2.14 > drwxr-xr-x 6 root root 4096 Feb 9 03:00 linux-2.2.17 > -rw-r--r-- 1 root root 17561308 Feb 9 12:06 > linux-2.2.17.tar.gz > -rw-r--r-- 1 root root 19090206 Feb 2 13:41 > linux-2.2.18.tar.gz > -rw-r--r-- 1 root root 24644981 Feb 2 13:36 > linux-2.4.1.tar.gz > drwxr-xr-x 7 root root 4096 Jul 22 2000 redhat > > > On the VMware side, each time you change the kernel, you need to run the > setup script again, it's modules have to be able to work with the > current kernel. When running the setup script, I got the following > msgs: > > ----------------------- > Trying to find a suitable vmmon module for your running kernel. > > None of VMware's pre-built vmmon modules is suitable for your running > kernel. Do > you want this script to try to build the vmmon module for your system > (you need > to have a C compiler installed on your system)? [yes] > > What is the location of the directory of C header files that match your > running > kernel? [/usr/src/linux/include] > > The path "/usr/src/linux/include" is an existing directory, but it does > not > contain at least one of these directories "linux", "asm", "net" as > expected. /usr/src/linux/include/asm is a symlink to asm-i386. This symbolic link would (I assume) normally be created as a result of make config. I assume you would want to create the same link, as I doubt you are using an alpha, m680X0, mips, ppc, s390, or sparc processor. cd /usr/src/linux/include ln -s asm-i386 asm Greg ______________________________________________________________________ Philadelphia Linux Users Group - http://www.phillylinux.org Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|