before i make this suggestion on the forum, i'd like to make sure i
know what i'm talking about.
working with vbox on ubuntu 10.10 and reading section 2.3.2 of user
manual, end of point 1 where it reads:
"Alternatively, if you have built your own kernel, /usr/src/linux
should point to your kernel sources. If you have not removed the files
created during the build process, then your system will already be set
up correctly."
strictly speaking, i don't think the above is true anymore, at least
not on my ubuntu system.
first, if you've installed the source from official packages, then
(AFAIK) these days, on most major distros, there is no actual
"/usr/src/linux" symlink anymore. instead, what you'll find is the
symlink /lib/modules/<kernelversion>/build which, for each installed
and bootable kernel, links to the corresponding
/usr/src/linux-headers-... directory, and that's how any compile
process will locate the correct version of kernel headers against
which to build any modules for the currently running kernel.
that pattern also holds for the number of people (including me) who
choose to roll their own kernels from a tarball or from a recent git
checkout. in cases like that, when that new kernel is installed, that
/lib/modules/<kernelversion>/build symlink will then be set to point
at the location of the source tree used to build the kernel.
in short, referring specifically to the "/usr/src/linux" symlink as
the pointer to the kernel sources seems out of date. the more
accurate way to describe it would be to say that one should verify
that, for the running kernel, make sure the
/lib/modules/<kernel>/build symlink points to the directory with the
corresponding kernel headers. that rule would seem to work for both
packaged headers and for people building their kernels from the pure
source.
does that make sense?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
------------------------------------------------------------------------------
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages,
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
