Trying to install the VMWare demo from VMWare.com. After installing all the files, I get the following message when trying to run vmware-config.pl: What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] If I hit enter for the defaul location, I get this: The path "/usr/src/linux/include" is a kernel header file directory, but it does not contain the file "linux/version.h" as expected. This can happen if the kernel has never been built, or if you have invoked the "make mrproper" command in your kernel directory. In any case, you may want to rebuild your kernel. This is a fresh install of 7.2 from the weekend. Is there anything to be done besides rebuilding the kernel? If not, can someone point me to a good document on rebuilding the kernel? I searched the SuSE site, and I found a document that basically said, "If you're not an expert, Don't Do It!" Obviously, I'm not an expert . . . . Thanks --Michael
On Monday 13 August 2001 14:50, Michael Molloy wrote:
Trying to install the VMWare demo from VMWare.com. After installing all the files, I get the following message when trying to run vmware-config.pl:
What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include]
If I hit enter for the defaul location, I get this:
The path "/usr/src/linux/include" is a kernel header file directory, but
it does not contain the file "linux/version.h" as expected. This can happen if the kernel has never been built, or if you have invoked the "make mrproper" command in your kernel directory. In any case, you may want to rebuild your kernel.
This is a fresh install of 7.2 from the weekend. Is there anything to be
done besides rebuilding the kernel?
If not, can someone point me to a good document on rebuilding the kernel? I searched the SuSE site, and I found a document that basically said, "If you're not an expert, Don't Do It!"
Obviously, I'm not an expert . . . .
you may not be an expert, but does SuSE think you become an expert by doing nothing? I have tried almost everything I can think of and of course I have broken things, and I have tried to fix them, but if I can't fix them, I just re-install. Now I have set up an extra partition with a copy of my SuSE on it and I do all the experimentation on it before trying it on my original copy. I have not mastered rebuilding a kernel yet, but Im still trying. David M.
On Monday 13 August 2001 15:07, David McGlone wrote:
On Monday 13 August 2001 14:50, Michael Molloy wrote:
Trying to install the VMWare demo from VMWare.com. After installing all the files, I get the following message when trying to run vmware-config.pl:
What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include]
If I hit enter for the defaul location, I get this:
The path "/usr/src/linux/include" is a kernel header file directory, but
it does not contain the file "linux/version.h" as expected. This can happen if the kernel has never been built, or if you have invoked the "make mrproper" command in your kernel directory. In any case, you may want to rebuild your kernel.
This is a fresh install of 7.2 from the weekend. Is there anything to be
done besides rebuilding the kernel?
If not, can someone point me to a good document on rebuilding the kernel? I searched the SuSE site, and I found a document that basically said, "If you're not an expert, Don't Do It!"
Obviously, I'm not an expert . . . .
you may not be an expert, but does SuSE think you become an expert by doing nothing? I have tried almost everything I can think of and of course I have broken things, and I have tried to fix them, but if I can't fix them, I just re-install. Now I have set up an extra partition with a copy of my SuSE on it and I do all the experimentation on it before trying it on my original copy. I have not mastered rebuilding a kernel yet, but Im still trying.
David M.
If done right... you should be able to happily play with building a kernel and yet retain the ability to retreat to your current kernel. It is a matter of changing your /etc/lilo.conf file to allow booting either the new or the old kernel. If the new doesn't work... just reboot the old. Even those who can rebuild kernels in their sleep do this.. because you never know when something might not work right..... -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 08/13/01 15:32 + +----------------------------------------------------------------------------+ " Change is inevitable, except from a vending machine."
Let me try to give a useful reply (which basically consists of quoting Robert C. Paulsen's reply to my similar question some time ago -- see below): On 13-Aug-01 Michael Molloy wrote:
Trying to install the VMWare demo from VMWare.com. After installing all the files, I get the following message when trying to run vmware-config.pl:
What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include]
If I hit enter for the defaul location, I get this:
The path "/usr/src/linux/include" is a kernel header file directory, but it does not contain the file "linux/version.h" as expected. This can happen if the kernel has never been built, or if you have invoked the "make mrproper" command in your kernel directory. In any case, you may want to rebuild your kernel.
I believe the file
/usr/src/linux-2.4.4.SuSE/include/linux/version.h
will be created when you do the following:
1. Install the kernel sources. This should create and populate
/usr/src/linux-2.4.4.SuSE
2. Create the correct configuration file as follows:
make cloneconfig
make menuconfig
You don't need to change any configuration options while in
menuconfig but you do need to save the configuration when you
exit.
3. Build the modules:
make dep
make modules
That last step (make modules) will take a long time, but once
it is complete vmware will be able to build its modules.
The above worked for me -- the VMWare installation went OK,
including the building of its modules.
NOTE: There is no need to build the kernel nor to install the
modules. I suspect that things will be in good enough shape for
vmware before the make modules completes, but I did let it run to
completion myself.
NOTE 2: The above description differs from what SuSE has on its
web site. What I have described is simpler and since it doesn't
install a self-made kernel you haven't voided your support
agreement as you do when following SuSE's directions.
I left one thing out of my earlier message. I needed to delete
the file:
/etc/vmware/not_configured
at some point -- don't remember exactly when. I think it was
just after following the procedure I described and before
actually running VMWare.
--
____________________________________________________________________
Robert Paulsen paulsen@texas.net
I hope it works,
Ted.
--------------------------------------------------------------------
E-Mail: (Ted Harding)
participants (4)
-
Bruce Marshall -
David McGlone -
Michael Molloy -
Ted.Harding＠nessie.mcc.ac.uk