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
On Sun, Mar 07, 2004 at 05:05:27PM +0100, Sam Ravnborg wrote:
On Sun, Mar 07, 2004 at 03:01:31PM +0100, Arjan van de Ven wrote:
and it's missing the symbols from
module files.
sure but the module files are generally installed...
I'm aiming for a situation where I can build external
On Sun, 2004-03-07 at 14:46, Andreas Gruenbacher wrote:
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
On Sun, Mar 07, 2004 at 05:45:22PM +0100, Andreas Gruenbacher wrote:
From a distribution kernel pov; I already ship a subset of files for building
modules against (basically include/, the KConfig and makefiles), which only
not 100% works because I don't ship vmlinux.
We have tried that
