Marco:
FWIW, the Red Hat kernel RPMs effectively do the following when they
package kernel modules:
strip -g
This is done via the script:
/usr/lib/rpm/brp-strip
which is implicitly run on all executable files packaged in the RPM.
If you ensure that the module .ko file
Well, the best you can do is
strip -R .note -R .comment --strip-unneeded.
If you go for more, module might not be loaded/initialized properlly
Aleks.
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Budde, Marco
>Sent: Sunday, July 24, 2005 11:24 PM
Michael Tokarev wrote:
> Wakko Warner wrote:
> []
> > I would also be interested in this. For instance the AIC7xxx driver has
> > every PCI id in the module I think in the .modinfo section which is not
> > truely required once depmod has been run. []
>
> The .modinfo section, for example the PCI
Wakko Warner wrote:
[]
> I would also be interested in this. For instance the AIC7xxx driver has
> every PCI id in the module I think in the .modinfo section which is not
> truely required once depmod has been run. []
The .modinfo section, for example the PCI IDs, IS required for the
module to
Jan Engelhardt wrote:
> >What is the best way to do this with v2.6.
> >
> >I have tried e.g. to remove all symbols starting with "telos"
> >from the module like this (after kbuild):
> >
> > strip -w -K '!telos*' -K 'telosi2c_usb_driver' telosi2c_linux.ko
>
> Yes, I'd also be interested in what
>What is the best way to do this with v2.6.
>
>I have tried e.g. to remove all symbols starting with "telos"
>from the module like this (after kbuild):
>
> strip -w -K '!telos*' -K 'telosi2c_usb_driver' telosi2c_linux.ko
Yes, I'd also be interested in what sections can actually be stripped, if
What is the best way to do this with v2.6.
I have tried e.g. to remove all symbols starting with telos
from the module like this (after kbuild):
strip -w -K '!telos*' -K 'telosi2c_usb_driver' telosi2c_linux.ko
Yes, I'd also be interested in what sections can actually be stripped, if any.
Jan Engelhardt wrote:
What is the best way to do this with v2.6.
I have tried e.g. to remove all symbols starting with telos
from the module like this (after kbuild):
strip -w -K '!telos*' -K 'telosi2c_usb_driver' telosi2c_linux.ko
Yes, I'd also be interested in what sections can
Wakko Warner wrote:
[]
I would also be interested in this. For instance the AIC7xxx driver has
every PCI id in the module I think in the .modinfo section which is not
truely required once depmod has been run. []
The .modinfo section, for example the PCI IDs, IS required for the
module to
Michael Tokarev wrote:
Wakko Warner wrote:
[]
I would also be interested in this. For instance the AIC7xxx driver has
every PCI id in the module I think in the .modinfo section which is not
truely required once depmod has been run. []
The .modinfo section, for example the PCI IDs, IS
Well, the best you can do is
strip -R .note -R .comment --strip-unneeded.
If you go for more, module might not be loaded/initialized properlly
Aleks.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Budde, Marco
Sent: Sunday, July 24, 2005 11:24 PM
To:
Marco:
FWIW, the Red Hat kernel RPMs effectively do the following when they
package kernel modules:
strip -g module.ko
This is done via the script:
/usr/lib/rpm/brp-strip
which is implicitly run on all executable files packaged in the RPM.
If you ensure that the module
12 matches
Mail list logo
