Hello Arjan, On Sun, 2004-03-07 at 14:03, Arjan van de Ven wrote: > > > > Could you explain what is the actually gain of using the > > modversions file your patch creates. (modpost changes) > > distributions don't like to install the vmlinux since it's big(ish) and > means customers need to download a new vmlinux at each kernel erratum. > The same information is btw also present in System.map so imo the real > solution is to make modpost use System.map instead ;)
System.map doesn't have the hashes, and it's missing the symbols from module files. External modules may require symbols that live in another module. There are also a number of other minor differences that could probably be worked around. Now it would be possible to extract the modver symbols from the installed vmlinux and .ko files when needed, but note that we may be building modules for kernels that are not currently running, and for which those binaries are not even installed. So this sounds like a bad idea. Cheers, -- Andreas Gruenbacher <[EMAIL PROTECTED]> SUSE Labs, SUSE LINUX AG ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
